Support and General Use > Audio Playback, Database and Playlists

WMA fast forward not-quite-right for longer files

<< < (2/2)

OldSchool:
It seems to depend mainly on the file length; anything more than 4 or 5 minutes long will cause trouble, but only with WMA files. It doesn't seem to matter how much of the file is played in real time before the seek.

These files were ripped from my CD collection, using either EAC or Audio Converter (E-soft), and are encoded at 128 Kbps. For shorter WMA files (< about 4 minutes), created using the same software, the seek works fine.

I'll try some different encoding rates. Please let me know if there's anything else I can do or try.

 

ilikedirt:
Hi. I encountered the same problem. All my WMA files don't seek beyond ~3 Minutes (bitrate is 192kbps). Build r16060.

ilikedirt:
I went through the recent daily builds to find out when the bug was introduced. The bug doesn't happen in builds up to Januar 5th r15998 but appears in r16002. I guess it has to do with this commit "If seek fails, don't insert nonsense for the current position. Also, make one of the error messages a bit more clear."

Beyond which time seeking fails also seems to be dependent on the overall lenght of the file. I can't seek beyond ~3minutes in a 5 minutes long files, but can seek up to ~5  minutes in a 10 minutes long file (and so on, e.g. 4 minutes in a 7 minutes long file).

r15998 Shows something else though... The time seems to be miscalculated on my files as the songs don't end when the seekbar is full, they rather play on above the calculated time (foobar2000 shows length of 5:44 for one of my songs, rockbox shows the same length but plays up to 9 minutes)

OldSchool reported something for r15996 so this might be something else... In build r15998 I can seek to what seems to be the end of a 10 minutes long WMA file but then is not as rockbox plays over the "end" of the file.

saratoga:

--- Quote from: ilikedirt on January 17, 2008, 12:20:42 PM ---I went through the recent daily builds to find out when the bug was introduced. The bug doesn't happen in builds up to Januar 5th r15998 but appears in r16002. I guess it has to do with this commit "If seek fails, don't insert nonsense for the current position. Also, make one of the error messages a bit more clear."

--- End quote ---

That commit makes rockbox tell you if the seek fails rather then pretending they worked while still playing from the original location.  Before then it would simply update the screen but not actually seek.  Did you confirm that you can actually seek before that commit?  If its playing past the end of the file, then it sounds like it did not manage to seek.

ilikedirt:
No, you're right. It just looks as if it seeked to the end of the file, but then I'm somewhere in the middle of the file and then it looks as if it played past the end.

Navigation

[0] Message Index

[*] Previous page