>One thing that I've done in my library is to define an ALBUMARTIST for >_every_ non-compilation album, even when it's exactly the same as the >artist on every track. With the way SqueezeCenter works to determine >the artist to display for each album, this makes the interface a little >quicker. Without an album artist, SC looks at the artists from every >track in an album. On a web page with, say, 50 albums, SqueezeCenter >does 100s of db queries. With an album artist defined, it just needs >to do one query per album. Still not ideal - it should be doable with >a single query that pulls all the albums on a page. > Interesting. It shouldn't be any different. At scan time, a single contributor is stored in the album record. It's also stored in the album to contributors link table, where there are more than one album artist contributor, but that can still be returned in a single query.
Having an albumartist for regular albums changes the behaviour subtlely I think, as the songs will have track artist roles, not artist roles. You also get the artist listed twice (on an album context "Artist:" and "Album Artist:", and in track context "Artist:" and "Track Artist:"). _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
