Media Source Extensions appendBuffer recovery

Question

How can I recover from appendBuffer errors resulting from the following scenarios?

• missing data
• data out of order

Answer 1

Only guesses here...I would assume that out-of-order recoverability depends on format of the media container being decoded (WebM, Ogg, etc). Browsers' decodeAudioData function worked fine when receiving Ogg Opus files with explicitly out-of-order/missing pages (created with opus-file-splitter). I would assume that browsers use the same underlying stream decoding implementation for both decodeAudioData and MSE buffers, therefore MSE should handle missing pages/segments without issue.

Unfortunately, MSE does not support audio/ogg codecs="opus" so my test files can't be immediately used for testing. I'm not yet familiar with WebM container, but I eventually be doing tests with re-ordering audio/webm codecs="opus" files into MSE for another project and can let you know the results when that happens!