Support and General Use > Hardware

Sansa AMS: Musepack (SV8) issue?

(1/2) > >>

some-xtc:
Hello Guys,

I've already opened a task here:
http://www.rockbox.org/tracker/task/11476

My assumption is that this is a Sansa AMS specific problem, because it only occurs on my two rockboxed Samsas (and not on a e260v1 or M:robe 100 for example).
If this is true (hopefully some of you could check this with other models), then it should be at least mentioned in the wiki.

some-xtc:
No suggestion?
No one can reproduce this bug?
(try this samples: http://samples.mplayerhq.hu/A-codecs/musepack/sv8/ )

I think, this is a quite serious issue, because FuzeV1 was promoted on 3.6 to stable with SV8 ...

AlexP:
I doubt many people use musepack to be honest.  While we of course want to eliminate bugs, I wouldn't put this at the top end of serious :)

some-xtc:
Well, a changelog is like a promise :D


I can understand, that this is not at the top end, but - like I already said - this should be at least mentioned in the wiki (if my assumption is true):
http://www.rockbox.org/wiki/SansaAMS#Specific_problems

Chronon:
This was just committed and the bug report is now closed:

--- Quote ---r28197: Finally fix FS #11476 (data abort when playing some sv8 mpc files on lowmem targets like Clip+/Fuzev1/Fuzev2). This fix disables loading of seek tables from the sv8 bitstream. Those table are located at the end of sv8-files. When playing sv8 files this resulted in seek to filebegin, then fileend, then back to filebegin. Such seeking behaviour results in heavy rebuffering when playing files on targets with low RAM.
--- End quote ---

Posting this for those who find this topic via a search, since some-xtc got the news of the fix already via the Flyspray task.

Navigation

[0] Message Index

[#] Next page