Heya, I'm having problems with HTML5's audio buffering. Say that a 10 minute mp3 is downloading and playing, and audio.buffered.end(0) has reached 3 minutes. If I then set the currentTime to 5 minutes, I see a single 'progress' event claiming that audio.buffered extends from 0 to 5 minutes, and then I stop receiving 'progress' events. audio.networkState stays at NETWORK_LOADING, and audio.readyState is HAVE_CURRENT_DATA. audio.play() & audio.pause() then seem to do nothing. The audio then seems stuck in this state until I rewind currentTime to before 3 minutes (the point at which it had buffered up to before setting currentTime), at which point it will continue downloading and behave normally. This doesn't happen every time, but does seem to crop up in 90% of cases. I'm having trouble producing a reliable test case given it relies on setting the currentTime before the browser gets around to buffering that segment. is there anything I can do to provide more information? -Jonathan
I came up with a test page where you can play around with buffering and skipping forwards. Hopefully it displays the problem more clearly.
Of course, it might help if I told you what the URL of that page was... http://boos.audioboo.fm/test/player.html
I am able to find this Wayback Archive copy: http://web.archive.org/web/20140806111235/http://boos.audioboo.fm/test/player.html Although it seems to not work on Chrome Canary 120 and show only two outputs: loadstart error ^ Same in Safari Technology Preview 180. Unfortunately, we don't have test case in case of this bug. I think by 2010, this bug might have fixed (if not), we have another copy of bug with reproduction available. I am going to CC some engineer to share their input or if they can mark this as 'RESOLVED WONTFIX' or create reduction to reproduce (if it is reproducible).