>On a track by track basis, you don't even have to do a query. If >you're scanning tracks and a track has an ALBUMARTIST field, then skip >all of the compilation determination queries and logic. > Yes, if scanning each track in turn, it could do a lookup to see if the track has an Album Artist. However, that's another SQL query executed for every track, and would make scanning slower if there are not Album Artist tags. i.e. my library has ~30,000 tracks, of which only ~3000 have an album artist (most of those are compilation songs having COMPILATION=1 and ALBUMARTIST=something).
So in my case, 10% of the track scans would be faster, and 90% a little slower. Maybe worth a try for in-process scanning, but will have different effects according to the way a user manages their tags. For out-of-process Full SC scanning, I think a single DB call like mine that finds all albums to make compilations would be faster. >I believe the only time a track with an ALBUMARTIST field would be part of a >compilation is with either explicit COMPILATION=1 or ALBUMARTIST=Various >Artists tagging. Setting ALBUMARTIST=Various Artists doesn't make an album a compilation (unless something has changed). The only way to have a compilation album with an Album Artist is to specify both tags. eg. COMPILATION=1 AND ALBUMARTIST=Various Artists works well. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
