I have a fundamental question about what to expect from Various Artists
processing. I've only just started to use this feature. I believe
that with 7.6, "Group compilation albums together" is now the default.
Say I have two albums with embedded cuesheets, both albums in the same
genre:
Album #1: "Harp Chamber Works - Montreal Chamber Players.flac", with
the following PERFORMER tags:
"Roussel, A"
"Ropartz, J G"
"Debussy, C"
"Ravel, M"
"Koechlin, C"
..and with the album artist tagged as "Various".
Album #2: "Chamber Works with Violin and Viola - La passion de la
liberté - Marie Viaud, Michel Michalakakos.flac" with just a single
PERFORMER tag:
"Koechlin, C"
After a scan, I see two artists:
"Various Artists"
"Koechlin, C"
Browsing to artist "Koechlin, C", I see both albums. This is what I
expect.
To generalize, is it the expected behavior that, unless a PERFORMER has
at least one album where he/she is the _sole_ PERFORMER, that PERFORMER
remains ghettoized in the VA list?
I can see the desirability of this behavior: it reduces clutter. But
it seems to me that it has one big limitation:
Say I have an important PERFORMER who only appears on VA albums. Under
the current scheme, that PERFORMER is only listed under VA albums, not
as a separate artist. But if I tag an album with that PERFORMER as the
-_album_artist_-, in order to indicate the artist's importance, wouldn't
it make sense for the VA scanning logic to recognize that and "promote"
that PERFORMER to be worthy of a separate artist listing?
In my above example, if I tagged the "Harp Chamber Works - Montreal
Chamber Players.flac" album with the album artist "Ropartz, J G", then
I would expect to see the following artists listed in the all-artists
list:
"Various Artists"
"Koechlin, C"
"Ropartz, J G"
Is this an easy-to-implement enhancement request? *-"Album Artists
should always get an entry in the artists lists, regardless of their VA
status"-*. With embedded cuesheets, identifying the album artist is
easy: it's the 1st PERFORMER tag not associated with a track.
Or is this a can of worms? Would it be really difficult to get the
current scanner to do this? Does the current db structure even
acknowledge a contributor as an "album artist"?
Would it be possible to implement this fairly easily by defining a new
*-role-*: "album artist" e.g. "7" (or whatever number we're up to now
in terms of roles) and any {contributor_album:role == 7, contributor}
gets promoted to the artists list?
To me, that seems like it would involve the least changes to the
scanner code and the artists query code logic.
--
gharris999
------------------------------------------------------------------------
gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115
View this thread: http://forums.slimdevices.com/showthread.php?t=77928
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
