SpacingBat3
Static noise when other caller is muted
Aknowledgements
-
[X] I have checked that there's no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.
-
[X] I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself. I have tested if this bug occurs on Chromium/Chrome or any other Chromium-based browser that uses unpatched/upstream Chromium engine.
-
[ ] I have tried running the build from the
masterbranch and it does not have any fixes implemented according to my issue. -
[ ] My issue describes one of the unstable and/or not fully implemented features.
-
[X] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).
Operating System / Platform
🐧️ Linux
Operating system architecture
x64 (64-bit Intel/AMD)
Electron version
20.0.3
Application version
3.8.8
Bug description
Sometimes, when the person I'm on a call with is muted, Electron will play flat static.
Additional context
Notice: This issue was automatically generated by WebCord.
Workaround: Sometimes having the person unmute and mute again stops the static noise.
I'm pretty sure this is more a headphone/speaker thing, not something Electron takes care of. On Linux, I can hear the static noise at all BT headphones I used in every application that stopped playing audio after a while. However, at least for me, the static noise should stop to play after a while (like 10-30s) if there's no source emitting the audio. However in case of BT devices, I think this is dependant from the software support of power saving of the devices.
And even if that would be a bug with WebCord, I doubt I'll fix it – again, it isn't me who take care how website audio is played using the system APIs neither I know how Discord does handle that currently on their side (it could be either a browser engine bug or a bug with Discord website).
I can guarantee you it's not my headphones. Regardless of whether or not it's fixable, I know for a fact it's coming from webcord/electron; I was able to eliminate it by lowering webcord's volume in the volume mixer so that's definitely the source.