https://bugs.kde.org/show_bug.cgi?id=508170
--- Comment #5 from pallaswept <[email protected]> --- (In reply to John Mickelonis from comment #4) > (In reply to Nate Graham from comment #3) > > That's preeeeeetty esoteric. I'd say we can start by just muting the > > physical devices and see if that's good enough. > > Not good enough for me, at least. > > I stream on Twitch, and my mute button has become useless for me now, as it > also mutes my game audio. Without knowing how your setup is wired, there's a strong likelihood that the game audio should be passing through virtual devices, so that solution would be OK for you. If you're playing on the same PC you're streaming from. If you had the audio coming in via a hardware cable from another PC to a line-in on your linux streaming PC (dual-PC streaming normal kind of setup) this won't help, though. You could mark that device as virtual, and exclude it from the Mic mute, but yeh, assuming all audio inputs are microphones is incorrect... and there's no real way to programmatically tell them apart. I mean, think of a hardware mic preamp that outputs into a line-level input on the machine; it's a mic, physically, but as far as the system is concerned, it's just a normal line-in. You might consider streaming the audio digitally from the game PC to the stream PC in that case. It's better anyway, and it'd all be virtual devices. Still... making the "mic mute" key perform "force mute all input devices" is a problem, as with making the "speaker mute" key perform "force mute all output devices". > Honestly I liked the old behavior, where it just muted the default device. The new behaviour copies the old behaviour for sinks, which is "let's make it uniform in behaviour" which makes sense... except the old behaviour for sinks was also a problem (which nobody at KDE knew about until I brought it up here, so this isn't really their fault)... so now it's uniformly a problem. That'll be all fine when the solution is uniformly applied :) But yeh this is kinda old for such a serious bug report. I know it doesn't effect everyone but it does effect several extremely common use-cases and the effect is catastrophic. Is there anything we could do to help, Nate? -- You are receiving this mail because: You are watching all bug changes.
