Rob Walch

Isolating which browsers and browser versions impact you will help troubleshooting. The media error is usually a code 2 "decode" error. There are platform-specific cases related to MSE append order...

Here's the list of issues sighting the same SourceBuffer error "Failed to execute appendBuffer on SourceBuffer: The HTMLMediaElement.error attribute is not null" with my summary notes: - #6808 Attributed this...

The interstitial-controller has a `shouldPlay` state flag used to resume playback after source resets. I suppose a similar `seekTarget` could be maintained when a seek is issued and interrupted by...

> I tested it on Safari and Firefox and from brief testing it didn't seem to be an issue on those browsers. Is this specific to Chrome MSE playback? If...

After reproducing this in Chrome 130 on mac, simply issuing another seek won't do the trick. Only one `buffered` TimeRange is reported so there is no signal that the decoding...

So this asset contains overlapping samples?

HLS.js’s back buffer flushing doesn't operate on media less than a target durations behind the playhead. It is completely diabled by default and only set to 90 seconds on the...

If frames are being removed that should be reflected in the buffered ranges. I don't see how this is not a bug in Chrome. > particularly step 9 and the...

I should add that I reproduced the issue with default settings: No HLS.js back buffer removal whatsoever. If HLS.js was performing back buffer removal, I would expect it to re-buffer...

@luwes and @cjpillsbury, Were you able to workaround or resolve this issue? It's not a bug in hls.js as far as I can tell. HLS.js can add an option to...