[padenot]

This is planned, and important, and we'll fix it hopefully soon, it's long overdue. I'm sorry this hasn't happened yet, it's always a game of priorities that can never satisfy everybody on time. It however ranks fairly high on my personal list.

As one could imagine it's a bit (read: a lot) more complicated than just pausing the AudioContext after some time of silence, but we'll get it fixed regardless, it's possible because others did it. There are tradeoffs we're willing to do.

Source: Firefox implementer of a lot of things around this, editor of the Web Audio API standard.

[zoogeny]

Please don't take this kind of criticism personally. There was a recent blow up from an open source maintainer because he viewed this kind of criticism as a frustration.

Just know that most people understand everything you are saying here. Many things to do, finite amount of time.

I have personal experience of Firefox developers going above and beyond to make high-usage sites work for their users. I know first hand the lengths they will go to when issues affect users. Thank you and keep plugging away.

[godelski]

I'm a long time Firefox user and have no intention of changing. I fully agree but want to make an important distinction. Sometimes people are complaining about development work and sometimes people are complaining about priorities. This is definitely the latter and I do not think it necessarily a developer issue. Firefox does have the opportunity to become so much greater, but it does require a lot of work and time. I'd argue, give the developers the time and resources. I know Mozilla has their hands in a lot of pies, but Firefox is probably the most important one, even if it isn't the most revenue generating one. Firefox is the symbol of Mozilla and it needs to be the best. The developers have proven how much they can change things and make things better. The Rust partial rewrite was nothing short of a success. So I want to see that progress continued and to keep pushing in that direction.

[JohnBooty]

Thanks for all of your hard work. Firefox is so important.

[darkwater]

Thank for your work, from a Firefox user. Also, the OP is probably already aware of this:

"It's not perfect as resuming takes a little bit of time and it may not always resume, as there are multiple paths to starting audio. But it's good enough for me."

[noah_buddy]

I would like to become a better use of Firefox by debugging issues I find locally. Any guidance on where to start?

[buovjaga]

Dev doc index is here, includes links to articles about debugging: https://firefox-source-docs.mozilla.org/

[noah_buddy]

Thank you!

[patcon]

Thank you for your words on this, and energy on everything else!

[EasyMark]

For every one person "complaining" there are 999 of us quiet ones out here that use and love your product hours out of every day . I hope devs at firefox can cut through gruff articles with click baity titles and extract nuggets of usefulness from them though.

[JoshTriplett]

Thank you for your work on this!

I think many people would be curious to hear about the additional complexity above and beyond "suspend when silent", if there's an already-written thing you could link to.

(I do know that resume-when-playback-starts sometimes causes the first bit of audio to get lost, or all of the audio for short things like notification sounds.)

[genewitch]

I have a record player with bluerooth that doesn't understand 45s exist, even though the manufacturer included the adapter; also Bluetooth drops out during quiet parts, such as those in podcasts or old radio programs or any music made prior to 1997 within reason.

So I ask: define silence. Define sleep. Because you get it wrong you have a $200 device headed for the landfill.

[2big2fail_47]

why do you have a record player with bluetooth in the first place. isn't that against the very concept of an analogue medium?

[rambambram]

Big thanks from a Firefox user.

[Centigonal]

I appreciate you and everybody else's work on Firefox! Thank you!

[moffkalast]

> we'll fix it hopefully soon, it's long overdue. I'm sorry this hasn't happened yet

If one could describe the state of Bugzilla in two sentences, that would be it :P

[h14h]

I hope this kind of thing can shoot up the priority queue! Battery-stealing and generally janky behavior is likely the main reason folks stop using a piece of software.

Thanks for your work, and for talking about the issue on a public forum! It's so critically important that Firefox maintains/increases relevancy. I'm sure it's unbelieveably difficult work given the resources behind Chromium & Blink.

[lknuth]

Thank you! Your work is keeping the web open.

[pentagrama]

Thank you for your work and also sharing the status here. There is a bugzilla link to follow the progress of the fix?

[Glyptodon]

On Linux there are weird audio issues that lead to speaker pop, and sometimes opening a new tab can make the audio running from other tabs permanently distorted and static-y until you reboot. (Not a complaint. I've always wondered if it was a browser or audio system issue.)

[kruffin]

When I had this issue, it was fixed by disabling and removing the speech-dispatcher. Something to do with text to speech (I never use it but is sure to be a pain if you do need it) automatically doing things that corrupt the audio stream globally.

https://tqdev.com/2021-firefox-ubuntu-crackling-sound

[pacifika]

Yeah I’m getting this feedback on video calls. I thought maybe it was related to hibernation or microphone input level resetting to 120%

[zX41ZdbW]

Thanks! What the article does not tell is why it plays white noise (instead of silence).

[jsheard]

It might be that nothing is actually being played, but opening an audio session wakes up your systems DAC/amplifier so you can hear the analog noise floor. In that case the noise is actually always there during playback, you're just more likely to notice it during silence.

Computers are a really hostile environment for audio, if possible you're always better off getting an external audio interface to put some distance between the analog signal path and any EMI spewing components.

[joecool1029]

I knew about OP's problem for years with discord's piece of shit webapp being the most egregious offender. For my system the sound falls into a low power state and there's an audible pop/click when something wakes it up. Even with the tab silenced and all notifications turned off it would still periodically do this. Other sites that used WebRTC had same problem but not as frequent. I think I worked around the issue eventually by disabling the automatic low power state at the expense of some additional battery consumption.

[II2II]

> Computers are a really hostile environment for audio

My first thought was the author should be happy that they don't live back in the bad old days of computing. Audible noise was the norm, even when you were playing audio. At least for PCs with sound cards. I don't recall the situation being quite as bad on other platforms. Modern PCs are much better on this front.

I have vague recollections of a quote from the Computer Chronicles in the mid-1990's. It went to the effect of turning a $2000 computer into a $200 stereo ...

[tonyarkles]

And don’t forget RFI if a cell phone was close to your speakers. You’d hear a noise right before your phone started to ring!

[ltrls23]

It was used in some nice electronic music!

Dual Band – GSM (1998): https://www.youtube.com/watch?v=ntKOJdht3t8

Mav – HGP (2005): https://www.youtube.com/watch?v=ZacenNeu4fw

Tatarola – Who Is Calling (2007): https://www.youtube.com/watch?v=hTOyaG7VYKw

[andrecarini]

I could even hear an actual radio broadcast coming off my speakers whenever they were powered. Maddening!

[cafeinux]

This kind of thing amazes me. Radio is such a simple, yet omnipresent, technology that even something not made to listen to radio can accidentally catch and play the signal like an actual radio player would. I sure hope it's never going away.

[Semaphor]

> You’d hear a noise right before your phone started to ring!

Hah, haven’t thought about that in a long time. That’s the anecdote that feels unbelievable if I hadn’t frequently experienced it myself.

[TeMPOraL]

That was an incidental but very useful feature!

[myself248]

Sometimes that was pretty useful though; you could infer a lot about the system's state by listening to the faint hints of bus activity!

[Asooka]

Back in the CRT days my speakers would make noise whenever I scrolled a website, lol.

[h43z]

Cool to hear. This should deserve to be a high priority bug. Thanks for your work on firefox.

[4ndrewl]

Thank you for all your work on Firefox!

[stefanka]

Thank you!!