# FLAC - Composer issue with semicolon separator

**URL:** https://community.mp3tag.de/t/flac-composer-issue-with-semicolon-separator/19749
**Category:** Support
**Created:** [January 31, 2018, 10:42pm UTC](https://community.mp3tag.de/t/flac-composer-issue-with-semicolon-separator/19749 "2018-01-31T22:42:09Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [February 24, 2018, 9:38am UTC](https://community.mp3tag.de/t/flac-composer-issue-with-semicolon-separator/19749/13 "2018-02-24T09:38:09Z")

</div>

> [@DTW](#):
>
> Am I on the right track or just made one long composer name?

I think that you are on the right track and the question should end "and just made one long composer name" (not "or").  
You see the dilemma that only very few players can deal with multi-value fields. That is why you see only one if you use that feature.  
If you merge the multi-value fields to just one (and get one long string), then you get the phenomenon that some players split this long string into separate entries and others leave it in the original long form.  
And then there are players that can deal with multi-value fields but show them as a merged long string.  
And there are players that use the long string for one kind of display and the split one for other views (WMP does).  
WMP does the split  
iTunes takes the long string  
foobar can deal with multi-value fields.  
And MP3tag can help you to get the best solution for the abilities of your favourite player.  
(BTW: for players that split strings, it would be "semicolon-space" as separator)

---

_[View the full topic](https://community.mp3tag.de/t/flac-composer-issue-with-semicolon-separator/19749)._