Bugzilla – Bug 3046
VA artists incorrecly displayed in Browse Genre
Last modified: 2008-09-15 14:38:25 UTC
I have just upgraded from 6.2.1 to 6.2.2 and have hit a problem with compilation albums. I have "Group Compilation Albums Together" set and expect all my compilation albums to appear under "Various Artist". This is working fine - However the compilation artists are also seperatly listed under their own names when viewed using browse by genre. SlimServer Version: 6.2.2 - 6245 - Linux - EN - utf8
I'm having this problem as well. Except I've only ever installed version 6.2.1 (on Linux) and "various artists" has never worked for me, under "browse genre" or anywhere else. I have a few tracks where the artist is actually "Various". Maybe that has something to do with it.
I have this exact problem, as per the original bug logger; as of 6.2.2, various artists that work everywhere else correctly do work correctly when browsing by genre. For example, Browse Music -> Artists lists all major artists, with others listed correctly under 'Various Artits'. Browse Music -> Browse by Genre -> Electronic (for example) lists ALL artists tagged as Electronic.
Fixed in change 7154
*** Bug 3337 has been marked as a duplicate of this bug. ***
While this bug has been fixed (thanks for that), the count stats at the top of the web pages are now out whenever VA is selected in a browse menu (eg, Browse Artists->Various Artists, or Browse Genre->(genre)->Various Artists), or when VA appears in the artist menu under Brose Genre->(genre). Stats show "0 albums with 0 songs by <x> artists" even when there are albums with songs displayed in the menu. Also the <x> artist count includes individual track artists and does not group then under VA, but I dont know if this is intended or not.
Dan - the change to Base.pm in this fix seems to mean browse by Genre with sqlite an inordinate length of time. Without it queries are less than a second, but with it it can take over 400 seconds... Can it be optimised in some way?
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.