Mbr m3u8 stream fails to play on v1.6.0 or higher

[denivladislav]

What version of Hls.js are you using?

1.6.0

What browser (including version) are you using?

Google Chrome 137.0.7151.56 (Official Build) (arm64)

What OS (including version) are you using?

Mac OS Sonoma 14.6.1 (23G93)

Test stream

https://a-chaplygina.erlyvideo.ru/mbr/index.fmp4.m3u8

Configuration

{
  debug: true
}

Additional player setup steps

No response

Checklist

• [x] The issue observed is not already reported by searching on Github under https://github.com/video-dev/hls.js/issues
• [x] The issue occurs in the stable client (latest release) on https://hlsjs.video-dev.org/demo and not just on my page
• [x] The issue occurs in the latest client (main branch) on https://hlsjs-dev.video-dev.org/demo and not just on my page
• [x] The stream has correct Access-Control-Allow-Origin headers (CORS)
• [x] There are no network errors such as 404s in the browser console when trying to play the stream

Steps to reproduce

1. Use hls.js v1.6.0 or higher.
2. The stream fails to start playing

Expected behaviour

Mbr stream works with hls.js 1.6.0 or higher

What actually happened?

When using hls.js v1.6.0 or higher, the video fails to start playing.

However, when using v1.5.20 the video starts playing.

Console output

I created two codesandbox examples to demonstrate the problem. The logs may be seen there:

hls.js v.1.5.20

hls.js v.1.6.0

Chrome media internals output

[robwalch]

Hi @denivladislav,

~Are you able to reproduce the issue in the latest release v1.6.5?~

I am able to reproduce the issue, but do see problems with audio source buffer mime type occurring in v1.5.x.

[warn] > [buffer-operation-queue]: Exception executing "audio" SourceBuffer operation: NotSupportedError: Failed to execute 'changeType' on 'SourceBuffer': Changing to the type provided ('audio/mp4;codecs=mp4a.40.1') is not supported.

[robwalch]

The asset fails to play in Safari and QuickTime Player.

[robwalch]

#7304 works around the SourceBuffer creation issue present in all releases. The asset seems to work about as well as it did in previous builds with this change, but still has encoding and packaging issues that impact streaming and playback.