Bug when seeking m4a files [Sansa Clip Plus] V3.13

[WAWA01]

I have Sansa Clip Plus using Rockbox version 3.13 (b662e3a).

When I try to seek m4a files (move forward or backward) the playback goes back to the beginning of the file.
Is there a way to fix this? maybe the dev version doesn't have this issue?

Here's an example file: https://mega.co.nz/#!NckmQQzI!t5Q0FQS5LQSYN5gwZZtPamradO7pquMndiJMvNimphs

Thanks.

[saratoga]

Looking at that file, the seek frames are computed correctly, but the seek table in the header always decodes locations to the start of the file.  I don't know much about MP4, but maybe the file isn't meant to be seekable (was it a streamed file?).  Most likely repacking the file with a tool like mp4box, ffmpeg or some other mp4 tool will rewrite the seektable and fix the problem. 

[WAWA01]

It was streamed yes.

By repacking the file do you basically mean to resave the file with these programs?
Looks like those two you mentioned doesn't have GUI, is there a more noobish program that you know of?

[saratoga]

By repacking the file do you basically mean to resave the file with these programs?
Looks like those two you mentioned doesn't have GUI, is there a more noobish program that you know of?

I think there about a thousand GUIs for both of those programs.  I haven't used any of them however. 

[WAWA01]

Okay I'll look for it.

Looking at that file, the seek frames are computed correctly, but the seek table in the header always decodes locations to the start of the file.

BTW, what did you use to check that? (or how did you do it?)

[saratoga]

Okay I'll look for it.

Looking at that file, the seek frames are computed correctly, but the seek table in the header always decodes locations to the start of the file.

BTW, what did you use to check that? (or how did you do it?)

I added comments to this file:

http://git.rockbox.org/?p=rockbox.git;a=blob;f=lib/rbcodec/codecs/libm4a/m4a.c;h=5fe778ac033c689f7496e72f806194e1484a5aff;hb=HEAD#l152

Then did a few seeks using the simulator and looked to see what positions and file offsets were calculated.