>the caveat would be if you wanted SC to know something was a comp that >also had an Album Artist defined. i haven't felt that need yet, but i >might one day. > I don't think there should ever be a case of an album having both album artist and compilation. And, because of the apparent bug, it wouldn't work anyway. Compilation tag seems to take precidence over album artist. Personally, I think the precidence should be the other way round, in that SC guesses when an album is a compilation, but never guesses album artist.
I don't think there's ever the need to set a compilation tag, and the prescence of one can stop album artist tags from working. That was the main point of this sub-thread; the rest of this mail is small clarifications/corrections in terminology. >> Not strictly correct, which may confuse people, but I know what you >> mean. You use TPE2 to get Album Artist info in the SqueezeCenter >> library. From thereon (eg. when discussing browsing the library), you >> should discuss it as Album Artist. > >not "strictly correct"? its correct enough. i don't know why anyone >would have been confused. > >i don't see any issue with how i put it, but if specifically clarifying >that TPE2 can be read into SC as album artist helps anyone, kool. > My point is that the Scanner is used to read tags into the library, and then SC uses the library content. SqueezeCenter library doesn't store TPE2 in its library, it stores contributor roles, and TPE2 is stored as Band or can be stored Album Artist. Therefore it is confusing to say SC sorts by TPE2, especially for libraries consisting of songs in different media formats, as TPE2 only has meaning for mp3 files. >SC does not group/sort by TPE2. > >i was with you until the last sentence! you seemingly contradict >yourself. thats [the last sentence] exactly what it does, IF the >option (8001) is enabled. > SC didn't sort/group by TPE2 before enhancement 8001, and it still doesn't. Enhancement 8001 introduced a mechanism in the scanner for getting TPE2 to be stored as Album Artist. SC has always correctly sorted/grouped by Album Artist. TPE2 is not mentioned or used anywhere in SC, other than in the scanner. It's an important distinction to make. >> The scanner doesn't need to read a Compilation tag if an album artist >> is defined (either Album Artist, or TPE2). > >this is where all things get murky b/c SC/slim never makes clear how >things are supposed to work. > True. More documentation (or definitive wiki information) would be useful. >my understanding is that if comp tags are present, SC will read them, >and store them, regardless of if it finds data for album artist or not. >i guess thats different from your understanding. clearly, slim is >unclear on this. > The problem is that album artist and compilation are mutually exclusive; a decision needs to be made if an album is a compilation (various performing artists with no album artist) or an album (all performing artists the same or has an album artist). An album can't be both - it's meaningless. I believe there was a post in the past about the actual order that the scanner processes tags (someone read the code). I think that the scanner reads the compilation tag first and doesn't set album artist and track artist contributor roles if it finds a compilation tag. That seems to tie in with InTheBath's problem, as his album artist tags were being ignored (had artist roles reported for the songs and not track artists). He has subsequently removed COMPILATION=0 and everything is working. I think that album artist tags should be detected first by the scanner. If there is a consistent artist for every song on the album (or album artist for each song), the album can't be a compilation. As long as songs are tagged correctly to not have both an album artist or a compilation, the results should be fine. >> So, to sum it up, if you need album artist on an album, apply the same >> album artist value to every song on the album. > >and what made you think i didn't know that? > It wasn't specifically aimed at you - it was general information for anyone who may read this thread. Maybe I wasn't being clear enough though. I've had issues myself with this in the past. I only add album artist tags when an album needs it (there's no point going through the other 99.9% of my collection adding album artist tags when it's not necessary). Initially, when I found some albums that had one guest performer, I added an album artist tag just for that one song. This is not good enough - the SC scanner isn't clever enough to realise that an album artist for a song matching the artists on the other songs. i.e. you end up with an album that has some songs with artist roles and some songs with track artist roles. ALL songs need the album artist, such that all songs have track artist roles, and no artist roles, otherwise this leads to trouble in some library browsing modes (can't remember exactly where things go wrong). >are you saying that if comp=0 that SC will not populate the internal to >SC db ALBUMARTIST field if valid data for that field is present in the >tag? > Yes, apparently so. >what about if there is no comp tag, or if it is comp=1? > No compilation tag is fine. I assume compilation=1 would also cause skip album artist detection (would result in artist contributor roles, and no album artist or track artist roles). >if comp=0 truly stops the field from being populated, then i would >definitely call that a bug. so is that the reality? Yes. _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
