Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Where can I find the patch for Bug 1358372

  • 2 respostas
  • 3 têm este problema
  • 1 exibição
  • Última resposta de cor-el

more options

On my computer it doesn't even matter if your connected to the internet. Just open Firefox and check your volume mixer. You'll see at least 3 (three) or more instances. Its frustrating, especially when your trying to control the volume when playing music. I tried looking everywhere and cannot find the fix. Please Help!

On my computer it doesn't even matter if your connected to the internet. Just open Firefox and check your volume mixer. You'll see at least 3 (three) or more instances. Its frustrating, especially when your trying to control the volume when playing music. I tried looking everywhere and cannot find the fix. Please Help!

Todas as respostas (2)

more options

I think if there were a patch, you would see it as an attachment to the bug...

In the Volume Mixer on Windows 7, there is a master slider for the actual output of the current audio device, which overrides the individual application levels. Only the processes that are currently playing will have activity on their sliders, so it's easy to see which one needs adjustment. I don't know how Windows 10 works in this regard.

Is the problem that sites are not giving you volume controls for their players? If you just want to mute a site, you can use the icon on the tab. See: Mute sound in Firefox tabs.

more options

The bug is about multiple processes that each have their own volume setting. Once the maximum number of content processes have been opened then a new player will use one on the already present content processes.

You can consider to set this maximum to one content process as a workaround.

You can modify multi-process settings to see if this has effect.

  • set dom.ipc.processCount to 1 if it is currently set to a higher value (4)

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.