Bugzilla – Bug 5725
iTunes compilation support
Last modified: 2012-02-27 17:33:31 UTC
We've been doing some testing with 6.5.4 and 7.0 with regards to iTunes and reading in compilation albums. What we'd expect to happen is not happening. In the past, if you had a compilation album read in via iTunes it tended to get put into multiple folders-- one for each artist-- and in each folder would be one or more song files. Slimserver would read that album as multiple albums because it was saved into multiple folders. (if it was saved to 9 folders, it'd list 9 albums for that one album.) But, now, in 6.5.4 and in 7.0 Slimserver is reading it all as 1 album. Regardless of how many folders the files are saved to. Is this a fix or is this a bug? Or more broadly, what is the intended behavior? Details: * We tested with 6.5.4 on Windows XP * we tested with 7.0a (Oct. 10th build) on Windows Vista Procedures we tried to follow...
Dan, what is your definition of compilation album in this instance? For example do the files in question have a compilation tag and if so is it set to 0 or 1? Another example would be if the files in question have an Album Artist tag set. Is it possible the difference you are seeing is a result of how iTunes now organizes the files?
A sample file would probably be helpful.
This issue has been tested under: A) Windows XP-Pro, Slimserver 6.5.4, Slimserver 6.5.5 and I tunes 7.4.2.4. B) Windows Vista- Home Basic, Slimserver 7 and iTunes 7.1.1.5. Here are the steps for both tests; Expected behavior:- 1) Using iTunes we ripped a music CD with 33 songs and 33 artists. The music CD is a compiled one; without any change to the basic setting of iTunes, iTunes default configuration is compilation enabled. 2) I tunes created a folder with the name Compilation in its music folder location. 3) iTunes ripped the CD as one album (folder) and stored it inside the compilation folder, Slimserver could find the album and browse by artists names and songs names without any problem. This is the expected behavior of the Slimserver. Unexpected behavior:- 1) Using iTunes, we highlighted all the songs from the CD and accessed the (Get Info) for all the songs files and we unchecked the compilation option. 2) iTunes created 33 folders one for each artist name, and each artist folder contained the song file belong to the artist. This is expected for iTunes. 3) We changed Slimserver configuration to (not using iTunes) and made it point to the iTunes’ music folder where the new folders had been created, using the music folder option of the Slimserver 4) From the perspective of how the Slimserver software works we should have seen a 33 folders (albums) one for each artists, this did not happen, Slimserver sees only one folder and 33 songs and 33 artists but only one album. Manually we added another folder for testing, Slimserver sees the new folder as a new album (two albums now) but stills concedering the all the 33 folders created by iTunes as one album .
Steven: the compilation album we were testing with has nearly every track with a differenct artist. iTunes sets the compilation tag to "yes" by default and originally ripped to a single folder containing all tracks. We forced the compilation tag to "no" and then iTunes ripped the album to 32 discreet folders. In both cases though, SlimServer read all files as 1 album. Ross: we have the CD in house if you want to test. We'll attach one of the files to this bug as well.
Created attachment 2249 [details] File With compilation tag on.
Created attachment 2250 [details] File with compilation tag off
I am going to take a look at this one when I get a chance.
I have determined that the DISC tag is causing SC to group the tracks together as one album when it should not. If I remove the DISC tag from the files in question SC behaves the way I expect. It sounds similar to bug 4361 but not exactly. Investigating further.
Dan, do you happen to know what version of the server first started this new behavior? I am trying to track down what may have caused the change.
I don't really know, no. I hadn't tested this behavior in a while.
I'm marking this as a duplicate of Bug 4361 and will add additional notes there. *** This bug has been marked as a duplicate of 4361 ***
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.