Bugzilla – Bug 10528
Group discs doesn't work for MP3
Last modified: 2011-09-19 06:27:28 UTC
I've set: "Threat multi-disc sets as a single album" The album is stored in directories such as: ....\My Album\Disc 1\ ....\My Album\Disc 2\ I've set DISCNUMBER tags to 1 or 2 for all tracks. The album name is exactly the same on all tracks. The files are only tagged with ID3v2.3 tags, no ID3v1 tags exists. The problem is that the discs still show up as two separate albums with exactly the same name, I would have expected them to show up as a single album. In SlimServer 6.5 this works correctly so it only appears as a single album with the tracks from both discs. The problem seems to exists in all 7.x releases, I've tested it with latest 7.0.x, 7.3.0 and latest 7.3.x and latest 7.4. If I put all tracks from both discs in a single directory it works correctly. When using FLAC files it works correctly even if the tracks are stored in different directories for each disc. So the problem seems to only be related to MP3 files.
It actually works as long as the last track on the first disc has the same artist as the first track on the second disc. This is of course always true for non compilation albums, so for non compilation albums it always works. For albums with multiple artists it works if: - If you have set ALBUMARTIST, because then the artist on the above mentioned tracks are the same. - If the last track on first disk actually have the same artist as the first track on the second disk. It's however it's not enough if COMPILATION=0 is set because then the artists still differs. So the problem is caused by albums with multiple artists but it's not completely related to if SqueezeCenter consider it to be a compilation album or not. Looking at the code there seems to be some check against artist and last scanned track in some circumstances, the following bug report is also mentioned in the code in Slim/Schema.pm: [url]https://bugs-archive.lyrion.org/show_bug.cgi?id=4361[/url] It feels like this could happen on FLAC also, its probably just a matter of which DISC, DISCC, DISCNUMBER tags you have set and in which order the files are scanned. Most of the multi disc albums I have in my collection contains multiple artists, so if the "Treat multi-disc sets as a single album" option should make any sense it really has to work for albums like this.
Created attachment 4558 [details] Files to reproduce the problem The mp3 files in this zip can be used to reproduce the problem. You will need to set the "Threat multi-disc sets as a single album" before scanning with the mp3 files in the attached zip. On Linux you get: 2 instances of "Multi Disc Album 1" (with 2 tracks per album) 1 instance of "Multi Disc Album 2" (with 4 tracks) On Windows you get: 1 instance of "Multi Disc Album 1" (with 4 tracks) 2 instances of "Multi Disc Album 2" (with 2 tracks per album) If it behaves correctly you should get: 1 instance of "Multi Disc Album 1" (with 4 tracks) 1 instance of "Multi Disc Album 2" (with 4 tracks) As specified in my previous post, the problem is reproducible when the last track on the first disc has a different artist than the first track on the second disc. The reason it behaves differently on Linux and Windows is probably that the scanning order of the tracks are different.
Brandon: your comments on this?
Looks like Schema.pm might need some rework. See also bug 10583 (might stem from same logic faults) https://bugs-archive.lyrion.org/show_bug.cgi?id=10583
I am also experiencing this problem and it affects FLAC too Erland's theory (about track names as the scanner moves between discs) looks correct to me(In reply to comment #4) > Looks like Schema.pm might need some rework. > See also bug 10583 (might stem from same logic faults) > https://bugs-archive.lyrion.org/show_bug.cgi?id=10583
This is a well known problem that was introduced in 7.0. See bug 7869. Simple workarounds are: For multi-disc compilations you must set a COMPILATION=1 tag (or TCMP in MP3 files with ID3v2 tags) in addition to DISC (or DISCNUMBER, etc.). For multi-disc non-compilations, set an ALBUMARTIST tag (or TPE2 in MP3 files with ID3v2 tags) in addition to DISC (or DISCNUMBER, etc.). This is only necessary when there are multiple artists. Most often these albums would be marked compilations, so if you're using COMPILATION=0 to override this, you should also set ALBUMARTIST.
is this really a bug? shouldn't it be closed? it seems to me that the greatest hits logic can be over-riden with comp tags, and/or maybe some combo of Disc tags and AA tags. if thats true, is there still an issue here?