Bugzilla – Bug 51
split artists by / (per the ID3v2 spec) and enter them separately (optional)
Last modified: 2008-09-15 14:37:04 UTC
The ID3 spec allows for multiple artists to be specified by separating them with a slash. The server should (optionally) allow for each artist to be added to the database individually for searching and browsing.
While this is being fixed, we should also support multiple individual artist tags within a single ID3 tag set. Also consider doing both slashes and multiple tags for genre as well.
Subject: Re[2]: [slim] Slimserver feature request -- additional 'browse by" capabilities Date: December 27, 2003 2:08:27 PM PST To: discuss@lists.slimdevices.com Reply-To: discuss@lists.slimdevices.com Saturday, December 27, 2003, 1:33:22 PM, you wrote: db> According to the ID3 spec, you can put multiple artists in the artist db> tag, separated by slashes to indicate multiple people. db> What do folks think of making this work for genres as well? According to the ID3v2.3 spec, multiple genres are supported when using ID3v1.1-style when using the TCON tag. The genres are referenced by their numeric value, and are surrounded by parentheses: "(21)(39)" This would be interpreted as "Ska" with a "Noise" subgenre refinement. http://www.id3.org/id3v2.3.0.html#TCON If the tag uses ID3v2.4, then multiple strings are available in all T*** tags, as they're separated by null-terminators appropriate for the encoding. "21" $00 "Eurodisco" $00 http://www.id3.org/id3v2.4.0-frames.txt (search for TCON) The only thing not supported directly are multiple free-form genres in ID3v2.3 tags. I haven't followed the id3v2 mailing lists in some time, so I don't know if there are other accepted workarounds for this. But I think the slimserver should support multiple genres as specified, and then make '/' separation for ID3v2.3 tags an optional server setting, since this isn't supported by the spec. -Scott _________
artist, genre, composer, band, etc split by /, ; and \0 as of Nightly build April 1.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.