JJZolx;512817 Wrote: > It may be new, but I think it makes a lot of sense. A lot of people > have tagged compilations like this, so it short circuits the logic that > says _any_ ALBUMARTIST means not a compilation. I don't think it's a good idea to make special cases for particular values within string tags.
The logic becomes more complex. "If there's an album artist tag that is the same on all songs on the album, the album is not a compilation, unless compilation = 1 OR all songs have album artist = Various Artists". i.e. if there is bad tagging such that album artist is not consistent across all songs on an album, what would happen? "Various Artists" may not be the correct string to look for - some users may use "VA" or "Various", etc, as their various artists name. So such logic could lookup the library prefs string and compare against that, but then if that string is changed, it would need to recalculate compilation flag on all albums. I think Andy said already that there are no "tidy-up" phases for the in-proc scanner; it works everything out on the fly per-track. I guess that means that when scanning an album with varying contributors that isn't explicitly marked as a compilation, when the first song is processed, it creates an album that is not a compilation, and then the next song with a different artist would make it a compilation. After that, it's already marked as a compilation, so it stops early when processing further songs on the album. -- Philip Meyer ------------------------------------------------------------------------ Philip Meyer's Profile: http://forums.slimdevices.com/member.php?userid=95 View this thread: http://forums.slimdevices.com/showthread.php?t=74700 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
