# multiline field delimiter

**URL:** <https://community.mp3tag.de/t/multiline-field-delimiter/15578>\
**Category:** Support\
**Created:** [March 12, 2014, 9:57pm UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578 "2014-03-12T21:57:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tagmusing](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/ee59a6/32.png) [@tagmusing](https://community.mp3tag.de/u/tagmusing)\
**Post date:** [March 12, 2014, 9:57pm UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578/1 "2014-03-12T21:57:39Z")

</div>

Hello,  
I'm new to mp3tag and tagging. At the moment I try to decide on a tagging method for my music files.  
While thinking about tag layout I stumbeld about the multiline tag field and I wonder how to separate values into different tags.  
With a list of artist like this: artist1, artist2, artist3... in the artist field,  
it should be easy to separate the artists in multivalue fields, as the "," is the delimiter, but how could I do it with multiline fields, where there seems to be now visible delimiter?

artist1  
artist2  
artist3  
...

Another queistion would be, if and how player/music library software displays multiline fields. I wonder if to use them at all or just use list fields?

I hope anyone can help me.

---

<div class="post-metadata">

**Author:** ![chrishirst](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@chrishirst](https://community.mp3tag.de/u/chrishirst)\
**Post date:** [March 12, 2014, 10:44pm UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578/2 "2014-03-12T22:44:29Z")

</div>

> [@tagmusing](#):
>
> Hello,  
> I'm new to mp3tag and tagging. At the moment I try to decide on a tagging method for my music files.  
> While thinking about tag layout I stumbeld about the multiline tag field and I wonder how to separate values into different tags.  
> With a list of artist like this: artist1, artist2, artist3... in the artist field,  
> it should be easy to separate the artists in multivalue fields, as the "," is the delimiter, but how could I do it with multiline fields, where there seems to be now visible delimiter?
> 
> artist1  
> artist2  
> artist3  
> ...

[https://docs.mp3tag.de/scripting](https://docs.mp3tag.de/scripting)  
Last item in the list.

line breaks in Windows are two characters long chr(10) + Chr(13)

> [@tagmusing](#):
>
> Another queistion would be, if and how player/music library software displays multiline fields. I wonder if to use them at all or just use list fields?

That depends ENTIRELY on the player you are using.

---

<div class="post-metadata">

**Author:** ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)\
**Post date:** [March 13, 2014, 6:20am UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578/3 "2014-03-13T06:20:09Z")

</div>

> [@tagmusing](#):
>
> ... how could I do it with multiline fields, where there seems to be now visible delimiter?  
> artist1  
> artist2  
> artist3  
> ...

**$regexp(%MULTILINE\_TAG\_FIELD%,'[\r\n]+','\\\\')**

==\> multivalue tag field

DD.20140313.0820.CET

---

<div class="post-metadata">

**Author:** ![tagmusing](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/ee59a6/32.png) [@tagmusing](https://community.mp3tag.de/u/tagmusing)\
**Post date:** [March 13, 2014, 8:31am UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578/4 "2014-03-13T08:31:01Z")

</div>

Thank you for your fast answers!  
I looked around in the forum and the help files, but I didn't recognize it. But I have to admit, that regular expressions are still a mystery to me and my brain shuts down seeing the 🙂

So I think i would have to use DetlevDs

> [@](#):
>
> $regexp(%MULTILINE\_TAG\_FIELD%,'[\r\n]+','\\')

in an action "replace with regular expression" and there in the line "regular expression"

but Chris Hirst i have no idea, how to put the $meta\_sep(x,sep) from the scripting help that you indicated into an action.  
I believe I understand that it transforms a multiline filed in a list separated by my chosen seperator (sep). But how do I use it in an action?

For the player, I use foobar on my pc, but so far without any configuration of the interface and columns. And I use squeezebox (so far only as radio) but I want to play my music over the network with it. And it is the reason I started investigating the hole tag buisiness. On my pc with foorbar i only navigate by folders, so far without using tags.  
I don't even know if squeezebox can display multiline tagfileds.

The reason for my initial question was, that don't want to choose a tag format, which i can't use later and even worse, don't know how to transform to adapted to future necessities.

Thanks again!

By the way DetlevD I'm from Wuppertal, too. But not living there at the moment.

---

<div class="post-metadata">

**Author:** ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)\
**Post date:** [March 13, 2014, 11:15am UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578/5 "2014-03-13T11:15:37Z")

</div>

> [@tagmusing](#):
>
> ... so I have to use ... in an action "replace with regular expression" and there in the line "regular expression"

You can use the given $regexp() scripting expression as is, in the action "Format value".

> [@tagmusing](#):
>
> By the way DetlevD I'm from Wuppertal, too. But not living there at the moment.

The world is so small ... ![:rolleyes:](https://community.mp3tag.de/uploads/default/original/1X/3a79e8b0b7d169b30216785521d7c6f4f895c421.gif ":rolleyes:")

DD.20140313.1315.CET

---

<div class="post-metadata">

**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\
**Post date:** [February 9, 2026, 12:24pm UTC](https://community.mp3tag.de/t/multiline-field-delimiter/15578/6 "2026-02-09T12:24:57Z")

</div>

Closed on February 9, 2026, 12:24pm UTC


