JJZolx wrote: > I requested support for both COMPOSERSORT and CONDUCTORSORT tags, but I > don't believe the changes have been committed. Haven't really had a good > chance to test, but I'll try to do so later. > > http://bugs.slimdevices.com/show_bug.cgi?id=18096
COMPOSERSORT etc does not work in 7.9. Reading the comments in the bug report, I think the issue about multiple sort fields is a bit of a red herring. There are already multiple fields with ARTISTSORT and ALBUMARTISTSORT and the somewhat arbitrary scheme of precedence works. You need a separate tag for COMPOSERSORT so that it gets matched to the COMPOSER tag, not some other contributor. There are many (mostly dead) composers who are not artists so won't otherwise acquire a sort key unless they are deliberately added as artists. BTW I am a bit confused about ORCHESTRA. This is not listed as a contributor field in the database schema as far as I am aware. I thought the contributor fields are ARTIST, ALBUMARTIST, COMPOSER, CONDUCTOR, BAND and TRACKARTIST, so we need a sort field to match each of those tags. I use TRACKARTIST in my classical music tagging scheme for the soloists etc who are not the main artist. This requires multiple names (separated by a semi-colon). I think that would work OK with the sort key so long as the order is the same - it seems to work that way with ARTIST. I thought of a work-round by using dummy files with just the missing ARTIST and ARTISTSORT tags, but it really is rather ugly. ------------------------------------------------------------------------ MDE's Profile: http://forums.slimdevices.com/member.php?userid=49291 View this thread: http://forums.slimdevices.com/showthread.php?t=102688 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
