- Status Unconfirmed
- Percent Complete
- Task Type Bugs
- Category Codecs
- Assigned To No-one
- Operating System Sansa AMSv2
- Severity Low
- Priority Very Low
- Reported Version Release 3.8.1
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#12160 - APE codec random loud noise during playback
Hardware: Clip+ 8GB using internal memory
Problem: Playback of most APE files results into passages of loud noise during playback. The music is totally gone and noise is ear deafening loud. When rewinding, till music is heard, and replaying the problem part, error can be reproduced _sometimes_.
In other cases it either runs fine, or the problem occurs elsewhere in the file.
Since the problem does not always occur in a specific part of a APE file, it is hard to attach a sample file.
Problem persisted between ape files encoded in high and normal setting.
Using winamp + monkey audio 3.99 APE plugin, these files never shown problems.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I haven't had this happen but there was an issue that was fixed that was completely reproducable. However, there is also a bug with buffering that if any forced rebuffer happens and the codec holds pointers across buffering calls, can result in those pointers becoming invalid because rebuffering works by restarting a fill at the handle's current position in the buffer with the new file position instead of where that data would naturally end up in the buffer for the new file position. I'm not saying that's what this is caused by for sure (ti could be) but it's more of a heads up on things that are wrong that haven't been fixed or codecs assume the pointer will be valid. There is also more probability with smaller ram sizes because rebuffer will be more likely.
The fact that it's not consistent makes me lean towards buffering or codec's use of it and not the deep codec internals.