-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Malformed sound on Pale Moon #6110
Comments
Hi @pnaf,
To confirm: If the UA does not include "Firefox" when running HLS.js in Pale Moon 32.5.2 (Linux 64-bit GTK3) on Ubuntu 22.04.3 LT, then HE-AAC v1 audio is not played correctly? After a quick search, I am inclined to think that this issue is related to this workaround: hls.js/src/demux/audio/adts.ts Lines 65 to 76 in cd12094
I'm assuming that this workaround is required for the version of Pale Moon you are running or any gecko based user-agent requiring this workaround. |
For historical context, this workaround goes way back to the initial M2TS AAC demuxer contribution (#121). A feature-detection based alternative to user-agent detection would be nice. Maybe we could test for
YouTube and Twitch are not necessarily using AAC SBR (HE-AAC) with less than 24kHz. A better comparison would be other against other MSE based player using exactly the same HLS asset and setting. Does the same thing happen using video.js v8 or shaka-player? |
Hi @robwalsh,
Yes. As far as I can tell, the example streams I mentioned seem to have HE-AAC v1 audio.
I'm not hearing this sound issue with any of the Video.js demos or any of the MPEG-TS demos for Shaka Player. In fact, I played both the "adaptive qualities" and "480p only" versions of Big Buck Bunny from the HLS.js demo page on Shaka Player, and the audio from both videos played perfectly fine. Just to double-check, I played the same Big Buck Bunny videos using HLS.js and Shaka Player on different tabs, and HLS.js consistently continued to play malformed sound. #6111 fixes the issue locally on my end, although I absolutely agree that we should switch to a feature-detection method at some time in the future. |
If that's the case we should investigate what the difference in remuxed output is - there may be a fix that removes the workaround. |
Hi @pnaf. I have a change that removes the user-agent specific workarounds in #6627. I would like to know if this resolves the malformed sound issues you've been experiencing. You can try it here: https://bugfix-adts-to-esds.hls-js-4zn.pages.dev/demo/ |
Hi @robwalch. Sorry, I just saw your message now. Yes, on Pale Moon 33.3.0, I can see that the issue no longer occurs on the Thank you! |
What version of Hls.js are you using?
v1.5.1
What browser (including version) are you using?
Pale Moon 32.5.2 (Linux 64-bit GTK3)
What OS (including version) are you using?
Ubuntu 22.04.3 LTS
Test stream
https://test-streams.mux.dev/x36xhzz/url_6/193039199_mp4_h264_aac_hq_7.m3u8
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
Firefox
to not appear on the browser's user agent).Expected behaviour
Audio continues to play correctly.
What actually happened?
Audio plays at an extremely low pitch with crackling. Meanwhile, audio continues to play perfectly fine on all other websites like YouTube and Twitch.
Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: