I worry about a snowball of brittleness created be munging names together. Editing, adding, displaying and searching would then be required to dynamically create names as they try to access the data. A search for multiple artists in a field would become a ugly thing.
What about turning those fields into a list of values when more than one value exists. A simple test could detect them and do the right thing in each scenario. Editing, adding, displaying and searching could use their best mechanisms accordingly without making up variable names everywhere on a record by record basis. Erica Sent from [Proton Mail](https://proton.me/mail/home) for Android. -------- Original Message -------- On Wednesday, 02/18/26 at 01:45 समीर सिंह Sameer Singh <[email protected]> wrote: > I was looking at the source code of emms-info-native-vorbis.el, specifically > the emms-info-native-vorbis-extract-comments. AFAICT the function correctly > extracts the multi value tags correctly, but in emms-info-native function the > latest value of the tag overwrites the previous ones. > A simple fix would be to define a list of tags which could have multiple > values, and if the tag is encountered, concatenate the values with a > separator, for eg. "Artist1 | Artist2 | Artist 3" > How does this sound? > > On Wed, 18 Feb, 2026, 6:04 am Yoni Rabkin, <[email protected]> wrote: > >> समीर सिंह Sameer Singh <[email protected]> writes: >> >>> vorbis allows multiple instances of the same tag field, which is commonly >>> used for tracks with multiple artists, composers etc. >>> >>> But emms does not seem to support it. So I was wondering how do you >>> guys handle this scenario? >> >> I don't see a reason not to add support for this feature. Repeated-field >> support is kind of spotty and variable across different players and >> readers. >> >> -- >> "Cut your own wood and it will warm you twice"
