Hi all,

I was browsing through the developer's page over on riocar.org, and I discovered that you can have custom shuffle modes. That's awesome -- one of the shuffle modes that I really want (especially after uploading new tunes) is "most recently added".

That sounds like it's a function with CTIME as priority. To see how CTIME orders the playlist, I set up the following shuffles in my config.ini:

[custom]
shuffle0=By ctime,CTIME=1,RANDOM=0
shuffle1=By -ctime,-CTIME=1,RANDOM=0
shuffle2=By -ctime=32768,-CTIME=32768,RANDOM=0
shuffle3=By ctime=32768,CTIME=32768,RANDOM=0
shuffle4=By ctime=32700,CTIME=32700,RANDOM=0

Then I hit down,down,down to play everything. I remember what the first tunes I put on the player are, as well as the last tunes I put on.

Since ctime is gets larger for newer files, I would expect shuffle0 to order the playlist in order that the files were added (since shuffle plays the highest score first). I have shuffle1 set up to see if it's the reverse of shuffle0. Since TIME is scaled from 0 to 32000 with higher values being least recently played, shuffle0 and shuffle1 could produce a shuffle order in the reverse of what I'm expecting. Shuffle2 and shuffle3 I added under the idea that if CTIME is scaled from 0 to 32000, the CTIME values might be down at one end of the range. I was looking at the shuffle by year example when I added those. shuffle4 I added to see if I might be dealing with an overflow issue. I also tried various permutations like CTIME=1000 and -CTIME=1000.

None of the shuffles I've tried has given me what I expected to see. Shuffle2 came close a couple times, but it doesn't do it consistently.

Ultimately, I'd like something that shuffles like this (I think):
(ctime for newest),-PLAYS=10,RANDOM=1

That should play the newest unplayed songs before the newest played songs, with a touch of randomness.

Any suggestions?

I would suggest you try again with beta13, released within the past minute or two...

From beta13 release notes:

Fixed: Can't use ctime in custom shuffles (#1796)

.

Isn't irony just so ironic sometimes?

Oh, dear. And to think I wasted an hour at work digging up that old thread (that I could have piggybacked this onto), and typing that all in.

Thanks...

Yeah what a shame he spent all that time analyzing this problem when the fix was probably released right as he hit the "Post" button.

Yeah what a shame he spent all that time analyzing this problem when the fix was probably released right as he hit the "Post" button.

Not only that, but I did all the analyzing and testing parts between the hours of 11pm and 2am the night before, which means I didn't get to bed early enough to wake up and go surfing before work in the morning.

Just saw this after I posted the answer for this in the General forum. With the CTIME fix in beta13, just use the following line:

shuffle0=Newest First,-CTIME=32000