Oh dear, yes you have found a mess. I've been working on a better formatting system for the browser. If you are grouping by artist I believe that might be correct. It is just the display. When adding to the playlist adding the track should only add one.
There could be a field format for artist which concatenates them. That would give one track, but if the order is different between different tracks the grouping wouldn't work so well. Maybe sorting the concatenate for the grouping and display. That cold be done with a variant of the 'get' function. Just off the top of my head. I'll look into code later today. Erica Sent from Proton Mail for Android. -------- Original Message -------- On Friday, 02/20/26 at 11:49 समीर सिंह Sameer Singh <[email protected]> wrote: Hi, I have implemented this feature such that if, say browsing by artists, a multi-artist track will appear under every artist listed in the metadata. for example Track1 has artists: A1 and A2, so when in emms-browser it will appear as: A1 - Track1 A2 - Track1 The problem with this approach is if someone decided to add all of the tracks of A1 and then of A2, Track1 will get added twice. This is not desirable IMO. So should we deduplicate the tracks in a playlist? But this will break other workflows right? Are there any other solutions for this problem? Thank You On Thu, Feb 19, 2026 at 3:32 AM Erica Lina <[email protected]> wrote: > > You are welcome. > > I can help too. > Especially the search and filters. > > I also added some fields to Flac a year ago or so. > > Erica > > > Le 18 février 2026 22:37:19 GMT+01:00, "समीर सिंह Sameer Singh" > <[email protected]> a écrit : >> >> On Wed, Feb 18, 2026 at 4:45 PM Erica Qi <[email protected]> wrote: >>> >>> >>> 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. >> >> >> Yeah, this sounds reasonable. I will try doing this. >> >> Thank You. >> >>> >>> Editing, adding, displaying and searching could use their best mechanisms >>> accordingly without making up variable names everywhere on a record by >>> record basis. >>> >>> Erica >> >>
