3.1.2.1272 Sort orders in AutoPlaylist not work properly

[nohitter151]

but this sort order is so in your face i can't see how you don't notice it.

Could you explain then? Because Rusty, me, and Owyn all seem to agree that there is no problem here. I think the disconnect between us is just a fundamental misunderstanding of how these sort rules are applied on your and KIJACC's part.

[rovingcowboy]

the post i did just before you did this one is where i explained what it is doing.

[Ludek]

Sure, debug log could tell something, because we will see the SQL query in the log and this way we could review whether there is something bad with the query.
But much more usefull would be to test it directly on your DB.
i.e. If you could compress your C:\Documents and Settings\<user>\Local Settings\App Data\MediaMonkey\MM.DB and send it via RapidShare.com and attach the link here then we could repro your issue by using the DB and we could look into it.

[Bex]

If one looks closely in NH's first pic and at the bitrate 69 and the following titles, it is clear that the titles are sorted incorrectly. The reason for this is that MM sorts according to the exact Bitrate and not the rounded (or rather cut off) Bitrate that is displayed in the main window (the same goes for Length). If this is correct or incorrect can be discussed but I guess that is from where the confusion originates.

[rovingcowboy]

Bex then why does it do the same thing when not using bitrate as a sort rule.

1 album 2 artist 3 title

don't use the bitrate in that rule
and it still messes up.

[Peke]

Ok I Also tested this without success to replicate invalid sorts and Here is the result of one simple (I have Auto=Playlists that have 4+ sorts to get what I want):

Multi Sort.jpg (180.42 KiB) Viewed 3214 times

[Ludek]

Yes, the Peke's image clearly shows it works right. So if you have another image prooving that this sort order doesn't work then put it here.

I agree with Bex that the confusion here could be with sort orders like Length that is stored in milliseconds in the database, but in MM interface is shown in seconds. Therefore one would expect that 4:53 = 4:53, but currently 4:53 is not 4:53, because there are always some milliseconds that differentiate it. Therefore any other order added sub to this order (Length) has no effect. Hopefully it is more clear now.
Tracked here: http://www.ventismedia.com/mantis/view.php?id=6071

[rovingcowboy]

well i just got the new updated beta version i'll check and see if anything done there has changed it to work for me.

but the lenght is one of the things that was messing up on me. i did not know that you also used miliseconds on it to sort with. and only showed the first 3 numbers of the time on the display. that makes senses now as to why that was messing up. and why the ones after it was not being shown right.

i did stop using the length and bit rates in my sorts, but when i still got the error in ony the words it was messing my thoughts up which made me think it was in the code. it still might be in the code but i'll have to check again, as to what code it might be caused by the monkeys or one of the plugins for the monkey? i only use a few non default plugins. and they all seem to be working fine but one still might be causing this.

[Ludek]

Check it later once 1277 will be available, because I fix it a while ago, see:
http://www.ventismedia.com/mantis/view.php?id=6071

[rovingcowboy]

i see where you got the lenght and bit rate to sort the way they do but show proper to users.

but i still have to test as to why the titles and the artists and albums get this mess up sort on my system it might be the plugin from tecnojnky called tweakmonkey. as that is the last one i added. and it does have a few display troubles here. but so i'll start with removing that one. but its such a good script full of good tweaks i'd hate to have it be the cause of an error?

[rusty]

rovingcowboy,

If you're seeing the bug with text fields, can you please share a screengrab that clearly illustrates it ?

Thx.

-Rusty

[rovingcowboy]

if i get it i'll do more then that i'll send the debug report to you. but i just installed the latest version update so it might be fixed. but i really was seeing the same error with text and not numbers, however like i said it might be a plugin or even have been fixed. .

[rusty]

No need for a debug log--just a screen grab is fine. Thx.

-Rusty

[rovingcowboy]

found the answer in my bug on this.

sent it in the reply email message about the other bug.

but in short so others know.

the text fields with the number in also get the same error effect.

songs titled like 500 miles from home or 6 more miles to the grave yard. or 16 candles.

or albums titled for the songs like Hwy 40 Blues. or Greatest Hits Vol. 2
will all cause the error cause the numbers are there.

oh forgot even artists with numbers in their name cause the error like HWY 101, or U 2.

hopefuly ludeks fix will work on that too in the 1277 version.

[rusty]

Roving cowboy,

A screencapture would be best for us to understand the issue.

Thanks.

-Rusty