Chris Pearce [:cpearce (Not reading bugmail)] Reporter
	Description • 14 years ago

If we're receiving a WAV file at a rate less than we need to play it, nsWaveDecoder's buffering logic doesn't kick in.

STR:
1. Get a rate controlled web server and a large WAV file (for example http://pearce.org.nz/video/zurie-piratesxaimusremix.wav ).
2. Serve said large WAV file using a rate less than the bitrate of the file.
3. WAV's audio element switches between readyStates HAVE_CURRENT_DATA and HAVE_FUTURE_DATA and plays audio in stops and starts. The nsWaveDecoder doesn't switch into a buffering state and buffer a large chunk of data.

	cajbir (:cajbir)
	Comment 1 • 14 years ago

Bug 635649 refactors the wave backend to use the nsBuiltinDecoder code. This should either fix this bug, or make it generic for all backends. Will retest when patch lands.

	cajbir (:cajbir)
	Comment 2 • 14 years ago

Bug 635649, the wave backend refactoring, has landed. nsWaveDecoder no longer has specific buffering logic for that backend. If the problem still occurs in the generic code shared amongst all backends please raise a bug for that.

	u279076
	Comment 3 • 14 years ago

I cannot reproduce this -- VERIFIED FIXED