macOS : Speakers popping when pausing/seeking videos
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: haniasita, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/119.0
Steps to reproduce:
- Use a 2019 16" MacBook Pro running macOS Sonoma 14.1
- Access a video streaming website (i.e. YouTube or Netflix) and open a video
- Pause or seek trough the video
Actual results:
The speakers produce a very unpleasant and distracting "pop" every time playback stops, relative to how loud the sound was at stop time.
This issue ONLY affects Firefox.
When pausing/playing/seeking :
- Safari does not do this (tested with the same YouTube & Netflix videos)
- Music does not do this
- GarageBand does not do this
- IINA/VLC does not do this
The issue has persisted trough a full system wipe and reinstall.
Expected results:
No sound should be heard when playback stops.
I have made a video demonstrating the issue but I cannot attach the file here due to the file size limit.
I've therefore posted it on YouTube as an unlisted video : https://www.youtube.com/watch?v=E2vjuZSqazo
As you can hear in the video, the pop is intermittent, varies depending on the audio that was currently played, and does not happen on Safari.
Please note that this only happens when using speakers. The problem does not happen when using either the headphone jack or wireless earbuds.
Comment 3•7 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 4•7 months ago
|
||
Very subtle, but I think I hear it.
Possibly cubeb related. We have a couple audio related issues there. ni Kinetik for investigation.
I have been able to reproduce this bug using AirPlay from my iPhone to my Mac, and while running a heavy workload on a Parallels VM.
Thus, I think this is a hardware/driver/macOS issue rather than a Firefox issue. Still strange why Firefox would do it and not Safari, but I think this issue can be closed nevertheless.
Thank you for you time.
Updated•6 months ago
|
Description
•