-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ts file with audio opus codec - the audio is disabled #6317
Comments
Opus in TS is not a supported segment format of HLS.js. |
@obecny Although not officially supported. We have got opus working via.
Which then gets passed to the browser. YMMV though and I doubt it would be considered an hls.js bug if you have issues |
@robwalch In Shaka I have implemented this support, see shaka-project/shaka-player#6387 (if you are interested...) |
Containerless opus and opus in fmp4 are supported. You don't need any special configuration with the latest release. To support Opus in TS we would need a feature request and contribution (PR) adding support. Some details on why you need this format would be helpful as well. Adding more TS decoders to HLS.js bloats the library payload for users who only need to play HLS with codecs and containers supported on a majority of platforms. |
What version of Hls.js are you using?
1.5.7
What browser (including version) are you using?
chrome Version 122.0.6261.129 (Official Build) (arm64)
What OS (including version) are you using?
mac os Monterey
Test stream
https://github.com/obecny/hls-opus-testing
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
http-server
here is the output from ffmpeg for file1.ts
Program 1
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720, 24 fps, 23.92 tbr, 90k tbn
Stream #0:1[0x101]: Audio: opus (Opus / 0x7375704F), 48000 Hz, stereo, fltp
Expected behaviour
the audio works fine
What actually happened?
there is no audio
Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: