Bugzilla – Bug 3002
Gaps in high-bitrate WMA VBR files
Last modified: 2008-12-18 11:38:39 UTC
Firmware 29 and 33 from the 6.5 trunk is causing higher bitrate VBR files to stutter horribly. It sounds like a mangled cassette tape - the sound is continuous, just that it is all garbled, distored, and crunchy sounding. I reverted to svn 5087, which contains firmware 27 - no stuttering. Next I reverted to svn 5150 which contains firmware 28 - no stuttering. So firmware version 29 (and not 33 as I'd reported in my forum post) seems to be the culprit of the WMA VBR encoded files stuttering. It could be something changed in the server that is the cause, instead of the firmware, but I haven't tried anything to determine this, as I'm not sure of the firmware inter-dependencies. Net setup is belkin pre-n, which does not have, nor has ever had, any dropout or connectivity issues. As a workaround, forcing local wmadec transcoding via convert.conf allows normal playback.
I was able to reproduce this in fw 28 as well.
Mike, if you're still subscribed to this bug, just how high are your high-bitrate VBR files?
Still subscribed. I had previously ripped tracks with WMP, ripping settings at WMA-VBR max quality. Although the dialog box for setting the ripping options says the tracks will range from 240-355Kbps, they seem to be much higher. My tracks are more like 425-490+ Kbps. I'd like to clarify that playback never had gaps (eg. areas of silence), rather the sound was simply terrible. Someone changed the title of this bug report, which is fine, but I just wanted clarify the problem more precisely. I'll send you a track if you want one - let me know.
Note that this problem does not just just occur on WMA files. I am having the same problem with MP3 files. I will update with the exact bitrate, but it seems to be happening to ALL tracks in my library. I have no non-mp3 files. Please see bug 3125 as well.
Chris: I suspect that this is improved for high bitrate WMA files in the latest 6.2.2 with the changes in the latest firmware. Can you verify?
FYI - I tested w/43 and I no longer experience the problem. I'm using 6.5.
thanks, Mike!