You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 7, 2024. It is now read-only.
It seems to me that the easier solution would be to change Discord from Push-to-talk to Voice Activity.
If you're not pressing your MicSwitch PTT key, Discord won't get any Mic Input and VA won't be triggered. Once you press it Discord thinks you're just using VA normally since it has no idea MicSwitch was previously cutting of the microphone.
If you're using MicSwitch I'm guessing you'd want to change all your programs to either Voice Activity or Continous Mode (if available). From their perspective you're just not speaking when MicSwitch is muting your microphone, so no need for PTT or Muting in those apps.
Fully agree, the whole idea is not to manage multiple ptt hotkeys in different apps and to have it in a single place
Though I do agree with @spiralofhope that this could be confusing for some people to understand at first.
Maybe a small paragraph under the Installation section in the Readme that recommends enabling VA or Continuous Mode in all your apps and why could be helpful to a lot of people.
@guyyst I think you understand the problem well; I agree that it would be appropriate for all voice software being set to always-on/voice-activity and then to centralize the push-to-talk/cough button/etc. hotkey(s) through MicSwitch.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With MicSwitch 1.0.253, using Discord (latest version as of 2023-04-19), push to talk does not work; Discord remains muted.
Discord is itself set to perform push to talk with same key, in this case the ` (backtick) key.
The workaround is to have MicSwitch "suppress" disabled.
Three things work:
I don't know that MicSwitch can check for Discord and operate differently, so I'd say this is a documentation problem.
The text was updated successfully, but these errors were encountered: