Bug 1706 - Artist tracks with defined Genre and No Genre are both sorted under defined Genre
: Artist tracks with defined Genre and No Genre are both sorted under defined G...
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: 6.1.0
: PC Other
: P4 minor with 1 vote (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-24 10:22 UTC by Jason Holtzapple
Modified: 2011-03-16 04:40 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Holtzapple 2005-06-24 10:22:28 UTC
I noticed this one after the recent database upgrade for playlistdb-bmf branch.

If you have some tracks by the same artist that have a genre tag and some that
do not, browsing by Genre shows all the tracks by that artist under the defined
Genre - even the ones without genre tags. I hope that makes sense. This behavior
has changed from before the branch was merged.

NetBSD 1.6.2/perl 5.8.7/SlimServer_v2005-06-24
Comment 1 Todd Markelz 2005-06-27 06:31:15 UTC
I've noticed this bug as well, here is the best way I can explain it.

If Band A has a SINGLE song tagged with genre X, and you browse to genre X you
will see EVERY album and song by Band A.

For me this really makes browsing/playing by genre not even an option. For
example, I've created a "Live" genre and have marked all live performance tracks
as such. The problem is that if I try to play all my "Live" tracks at once I get
every track by every band that has atleast one live track in my collection.

I usually keep up with the nightly release so I don't know exactly when this bug
came up. I am currently running: Windows Professional/SlimServer_v2005-06-20
Comment 2 Dan Sully 2005-06-27 07:13:27 UTC
Fix commited as subversion change 3571.

There is now a preference under the Settings-> Behavior menu.
Comment 3 Chris Owens 2008-03-11 11:28:23 UTC
This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!