Version: 2.1.1 (using 4.2.2 (KDE 4.2.2), Kubuntu packages) Compiler: cc OS: Linux (x86_64) release 2.6.28-13-generic I have a dynamic playlist with two entries: 99%: rating > 3 stars 1%: rating = no stars (which I am told really means "unrated") amarok just played a song with two stars :-( It doesn't seem like that should ever happen with these filters.
Something similar just happened again: dynamic playlist with two entries: 99%: rating > 3.5 stars 1%: rating = no stars amarok just put a song rated with 3.5 stars on to the playlist.
As near as I can tell, this bug seems to occur on about 1% of the songs added to the playlist. Perhaps this frequency-of-occurrence has something to do with the fact that one of the two filters for the dynamic playlist is set to 1%?
Well, yes, of course. Try setting it to 100%, you should get the desired result AFAIK.
If I do that, then half the songs are from one filter and half are from the other, which isn't at all right. So this i not FIXED.
If I do that, then half the songs are from one filter and half are from the other, which isn't at all right. So this is not FIXED.
If I understand you correctly, you want to play songs with a rating equal or superior to 3.5, but also have 1% of unrated songs, right? Then put the option for the 3.5 rated to 100% and leave the unrated proportion at 1%. What result do you get then?
setting status to "waitingforinfo"
Well, just as in the case where the first filter is set to 99%, mostly it plays songs that meet the criteria. But every now and then, a song that does not match any of the criteria gets played. Just this morning I had the filters set to: 100%: rating = 5 stars 1%: rating = no stars and a song with 4.5 stars was added to the playlist.
I can't reproduce this, as I have almost no ratings, just erased my database. Somebody else maybe?
Changing version, since I presume this is still valid for 2.2.0, right?
I haven't seen this particular bug yet in karmic, although I think I've seen all the others that I created (plus one new one that I need to report). You might want to switch this to NEEDSINFO and I'll report if I see it in karmic.
Well, the easiest is to actually close it. Feel free to reopen the report if you can reproduce this with Amarok 2.2.0 or 2.2.1, due in a few days.
I've reopened it. I have a dynamic playlist that should choose only songs that have 3 or more stars. Hitting "Repopulate" just put a song with 1½ stars on the playlist. (Running 2.2.0 from the official karmic repositories.)
Doc, since we are releasing 2.2.1 these days, could you test again? There was some work on the dynamic playlists in the mean time. Setting to NEEDSINFO
When it gets into an official Kubuntu repository, I can test it again. Probably by then 2.2.2 will be near release :-(
Doc, it will be in the kubuntu-backports PPA next week.
Closing for lack of feedback. Most likely fixed already in trunk, Feel free to reopen if you can reproduce it with a valid backtrace with either Amarok 2.2.1 or 2.2.2
Well, like I said, I when it gets into an official Kubuntu repository, I'll test it. That situation has not changed. I'm not sure why you're asking for a backtrace. A backtrace implies a crash, and this bug is not associated with a crash; so even if the bug is still present in the next update from Canonical, I won't be able to provide a backtrace.
My bad, I did a copy-paste while closing old info requests.