dpotts;685957 Wrote: 
> I don't think ALBUMARTISTSORT can have anything to do with this bug. I
> get the problem for artists who appear only on albums that have no
> ALBUMARTIST or ALBUMARTISTSORT.
> 
> I can make the problem go away by correcting either of the two
> conditions I named: either remove the nonASCII characters (from
> ARTISTSORT only, leaving the nonASCII characters in the other sort
> order tags) or remove the offending names from COMPOSER and/or
> CONDUCTOR. In the first case, the names are sorted properly as directed
> by the sanitized ARTISTSORT tag. In the second, the names are sorted
> properly even with nonASCII characters in the ARTISTSORT tag.
> 
> LMS didn't always have this bug. It's relatively new, probably
> introduced in SBS 7.6.0. The earliest clear description of the problem
> I've found is in the bug report filed by Johan S in July of last year:
> http://bugs.slimdevices.com/show_bug.cgi?id=17304

I've had similar issues and I think I've traced it to the ARTISTSORT
field specifically (I don't really use any of the other sort fields). 
I've voted for the bugs listed.  

My solution when this first showed up, and it does seem to have started
occurring around 7.6, but I'm not positive, was to just use all ASCII
codes for the sorting fields (leaving the primary fields with the
non-ASCII characters).  The fields generally sort correctly now; I
can't think of cases where they are not sorting correctly, but I have
very few files where these characters come into play.


-- 
emalvick
------------------------------------------------------------------------
emalvick's Profile: http://forums.slimdevices.com/member.php?userid=35382
View this thread: http://forums.slimdevices.com/showthread.php?t=90661

_______________________________________________
ripping mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/ripping

Reply via email to