sansa clip+ unpredictible rewinding and ffwd with long files

[TOTAL]

this issue has persisted for several versions at least, very noticeable with mp3 files as long as 15 hours.

the device loses the focus

upon stopping - you may end up being bounced by several minutes ahead

single press of ffwd rwd for jump by a preset time also gets messy.

I am using tts files made with dspeech, balabolka, natural reader, etc

[saratoga]

This is just how mp3 seeking works with long files. The seek table is very inaccurate so once you stop you may end up earlier in the file.

[TOTAL]

good to know. thanks.

how about other compressed formats of comparable size?

[saratoga]

The only format I know for sure will work fine with very long files is WMA.  ASF is actually really well designed in that regard.  I also think AAC (or anything else in .mp4/m4a) won't work because there is no way our parser can handle such long files.

I'd just cut the files into 1 hour segments.  Rockbox is gapless, so theres no loss.   

[Llorean]

Why's it bad when you stop? I can understand how seeking could be a problem (in matching displayed time to a precise location in the file) but surely when resuming you can resume at a precise location since you aren't seeking to a time, but rather to an exact "known" point? Bookmarks as well.

I remember having an issue where I could rewind and end up *later* in the file than previously, which also seems like it should be impossible since if someone has attempted to seek backward the one place you know they can't possibly have meant to go to is a place further forward in the file.

[TOTAL]

It is bad when you are doing complicated audiobooks, where you may have troubles understanding the grammar of the sentences before  you attempt to decipher the meaning. It is a great hindrance to realise that you have been bounced somewhere, when you just wanted to hear the last part again.

I guess I will give the wmp format a try and if it does not work, I will get back to slicing long files.