>If everyone wanting to use such a feature has to hit the forums and have a >three day >long dialogue with someone before being able to understand it fully, then it's >a bug. > Certainly lacking any official information for how it should work. But it's not complicated - in most cases, users do not need to add compilation tags, especially COMPILATION=0.
>An album is either a compilation or it's not. Okay, I agree - each album in the music library should either be a non-compilation or compilation. Obviously, there's lots of different content that could be put in the tag (setting COMPILATION=Yes, for example), but it should result in the database holding a 0 or 1 for each album. COMPILATION=0 is used I think for people that split album files across more than one folder, to tell the scanner that they are part of the same album, not separate albums. >There is no other state, including "guest artist album". No third state for Compilation, but there is another logical scenario. A non-compilation album with differing artists on tracks. That cannot be represented solely by a compilation tag, it needs another tag to define the album artist (otherwise you have multiple albums). >The grouping (or more accurately, artist list inclusion) Not sure I follow you on this. What do you mean by artist list inclusion? I think grouping is more accurate; it's more than just putting the artist in the artist list, and affects other things (such as denoting who the album artist is when browsing Albums). >should be controlled by a single, simple >preference. The one that exists now is all that's needed, but it's not >implemented fully. Not sure what you are talking about here - what preference is not implemented fully? _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
