An interesting discovery re play order

Long story short: Just got a Clip Zip, great player. Added audio books, all was peachy until it hit a book with 400 odd files. All tags were good, but the play order was screwed. 10, 20, 30…90. then 100, 110, 120. Anyway, suffice it to say that it was very wrong. I read a thousand posts about tag versions, firmware updates, leading zeroes, the absence of slashes (or presence of them) and just about every other possibility, combination and workaround. I decided to do some experimenting and I found what was causing MY problem. It may or may not apply to other play order problems, but I felt it was worth posting regardless.

I was using TITLE xxx/yyy AND TRACK xxx/yyy

The problem disappeared by simply dropping the TRACK yyy

eg.

Title: No Time For Goodbye 001/489

Track: 001/489

this fails.

but…

Title: No Time For Goodbye 001/489

Track: 1

works

Just to see if it was the /yyy and not the leading zeroes in the track number, I tried…

Title: No Time For Goodbye 001/489

Track: 001

works just fine.

There are so many other possible combinations that it would take me more time than I am prepared to spend, but suffice it to say that the combination off TITLE xxx/yyy AND TRACK xxx/yyy screws with play order big time.

What I don’t get is why this is all so hard? Never once did I see a reply from Sandisk themselves saying, 'this is how it works, and these are the fields that get priority, and blah blah" I looked pretty hard for a definitive answer, but never found one. Maybe I didn’t look hard enough.

Anyway, my work is done here, for now, and I hope this post can resolve some other people’s play order issues.

If this particular ‘fix’ has been covered before, I apologise for duplicating it.

Thanks for the tips–just wish this all was incorporated into the player and fixed . . . . :frowning:

No probs, I just hope it helps someone who has a similar issue. I suspect there are more issues that cause the wonky sorting though :confounded:

A simple OFFICIAL explanation, or piece of accurate documentation would do me :dizzy_face:

@biggus wrote:

No probs, I just hope it helps someone who has a similar issue. I suspect there are more issues that cause the wonky sorting though :confounded:

 

A simple OFFICIAL explanation, or piece of accurate documentation would do me :dizzy_face:

 

Here? From SanDisk?