>No one really knows why it's needed but I personally suspect they >exists to store less data during scanning and save some space on disk. >The problem is just that it results in more complex browsing logic so >I'm pretty sure it would be better to just have two roles in the >database even if it means the database would contain a bit more roles. I suspect it was initially to do with the "Group compilation albums together" or "List compilation albums under each artist" setting.
i.e. ignore track artist roles if "Group compilation albums together", such that artists that only appear as guests would not be listed, and only consider listing artists, album artists, and optionally bands, composers and conductors. I guess this intended to make performance quicker than having to work it out through a more complex sequence of joins between album -> track -> artists, and also if the setting was changed, it would not require a rescan? I think of "track artists" as artists that appear on tracks, when there is an album artist, such that only the album artist would be listed for an album, and only the track artists when looking at information about a track. Which makes sense, but more sense would be for all tracks to have track artists, and all albums to have album artist, and not have "artist role" at all. _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
