Can't play with TS segment 15 FPS

[robertvxt]

What version of Hls.js are you using?

1.4.7

What browser (including version) are you using?

Chrome 114.0.5735.199

What OS (including version) are you using?

Windows 10, Windows 11

Test stream

No response

Configuration

{
  "debug": true,
  "enableWorker": true,
  "lowLatencyMode": true,
  "backBufferLength": 90,
  "manifestLoadingTimeOut": 30000;
  "levelLoadingTimeOut: 30000;
  "manifestLoadingMaxRetry": 4;
}

Additional player setup steps

No response

Checklist

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

Steps to reproduce

1. Prepare hls.m3u8 playlist with TS segment. e.g.

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:1
#EXT-X-MEDIA-SEQUENCE:15
#EXTINF:1.001000,
live_000000000015.ts

2. Play with hls.js

hlsObject.loadSource(urlPath);
hlsObject.attachMedia(video);
hlsObject.on(Hls.Events.MANIFEST_PARSED, function () {
            video.currentTime = playTimer;
            video.autoplay = true;
            video.play();
});

• I also tried to use the demo hls.js from https://hlsjs.video-dev.org/demo/ but still can't play and console output log just very simple.

• How do I attach the TS segment for example?

Expected behaviour

Can play TS segment

What actually happened?

Can't play TS segment with 15 FPS

Console output

[log] > Debug logs enabled for "main" in hls.js version 1.4.7

Chrome media internals output

No response

[robertvxt]

Any help on this?
Sorry I'm newbie with this player

[robwalch]

Please include full logs and a sample stream.

[robertvxt]

@robwalch Please use https://drm.kunai.tv:84/hls.m3u8 stream

I've tried to use the demo: https://hlsjs.video-dev.org/demo

Following is the log during play by above demo page:
hls_js_15FPS.txt

[robertvxt]

@robwalch any explanation when mark to Work as expected ?

[robwalch]

https://hlsjs.video-dev.org/demo/?src=https%3A%2F%2Fdrm.kunai.tv%3A84%2Fhls.m3u8%20&demoConfig=eyJlbmFibGVTdHJlYW1pbmciOnRydWUsImF1dG9SZWNvdmVyRXJyb3IiOmZhbHNlLCJzdG9wT25TdGFsbCI6ZmFsc2UsImR1bXBmTVA0IjpmYWxzZSwibGV2ZWxDYXBwaW5nIjotMSwibGltaXRNZXRyaWNzIjotMX0=

Plays in Safari and Firefox. Does not in Chrome.

[robertvxt]

Can't play on chrome or safari

But possible play by firefox

[robertvxt]

so this is problem of safari/chrome or my stream format?

[robwalch]

Take a look at dev-tools > Media tab > demo page > Messages. File a Chromium bug with steps, including the link above, expected and actual results.

I can play the media in Firefox 115 and Safari 16.5.1 on macOS 13.4.1. There is nothing indicating this is an HLS.js bug. In Chrome MSE appends the muxed fmp4 without any errors, but the buffer is empty as a result.

[robwalch]

so this is problem of safari/chrome or my stream format?

Could be both (Safari Desktop and iPad only - iPhone does not support MSE required by HLS.js). File bugs against the browsers and link here. Thanks.

[robertvxt]

Thanks @robwalch ,
I saw chrome://media-internals/ complained
ISO-BMFF container metadata for video frame indicates that the frame is a keyframe, but the video frame contents indicate the opposite. I will dive deeper into the stream generation and check with chromium community.

In addition, I've tried on Safari iPad and it's able to play the stream. But somehow, there are symptoms as following:

Should this be expectation also?

[robwalch]

Should this be expectation also?

There is an open issue for Safari TS>mp4 mux artifacts #5526 that may be related.

Providing a few files that reproduce the artifacts along with a description of the original source, or a comparison to playback using native playback in Safari (does src=m3u8 not produce these artifacts?) will help recognize, track, and test the issue and possible fixes.

[robertvxt]

Thanks @robwalch for supporting, let's close this for now.