# Multivalue Felder; hier unterschiedliche Darstellung

**URL:** https://community.mp3tag.de/t/multivalue-felder-hier-unterschiedliche-darstellung/49077
**Category:** Allgemein
**Created:** [May 25, 2020, 10:46am UTC](https://community.mp3tag.de/t/multivalue-felder-hier-unterschiedliche-darstellung/49077 "2020-05-25T10:46:28Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [May 25, 2020, 11:31am UTC](https://community.mp3tag.de/t/multivalue-felder-hier-unterschiedliche-darstellung/49077/2 "2020-05-25T11:31:22Z")

</div>

Vielleicht hilft dir dieser Thread und die Liste der unterschiedlichen Darstellungen:

> [@FLAC - Composer issue with semicolon separator](https://community.mp3tag.de/t/flac-composer-issue-with-semicolon-separator/19749/13):
>
> 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 th…

---

_[View the full topic](https://community.mp3tag.de/t/multivalue-felder-hier-unterschiedliche-darstellung/49077)._