Hi Guys, maybe one of you have managed to resolve a similar issue.
I have the Logitech G633 headset. Since the day I got them on Discord if I mute the mic by folding up the mic boom Discord refuses to detect the mic when I unmute. This only happens if the mic is muted for more than a couple of seconds. I havent actually timed it but its fine if I say mute the mic to cough and unmute it immediately but if I mute the mic to go make coffee I have to leave the channel and rejoin before the mic will be detected again. I assumed this was an issue with Discord so I logged a bug with them, they told me to update to the latest versions and to also try the latest test release etc etc. None of that worked and after a while I received a response vaguely blaming it on drivers. This was such a weak excuse that I assumed they really just dont know so I lived with it and moved on with my life.
Last night I joined a Teamspeak chat while playing with some new peeps and the mic does the exact same thing with Teamspeak. With teamspeak I have to completely close Teamspeak and open it if I want the mic to work again.
I have no issue with Skype. While the mic is in this not pulling through to the application state I can see mic levels in Windows recording devices so the mic is definitely working and pulling through to the OS...
Any suggestions? Has anyone else come across this? I have only tried Win7 so not sure if Win10 will fix this?
I have the Logitech G633 headset. Since the day I got them on Discord if I mute the mic by folding up the mic boom Discord refuses to detect the mic when I unmute. This only happens if the mic is muted for more than a couple of seconds. I havent actually timed it but its fine if I say mute the mic to cough and unmute it immediately but if I mute the mic to go make coffee I have to leave the channel and rejoin before the mic will be detected again. I assumed this was an issue with Discord so I logged a bug with them, they told me to update to the latest versions and to also try the latest test release etc etc. None of that worked and after a while I received a response vaguely blaming it on drivers. This was such a weak excuse that I assumed they really just dont know so I lived with it and moved on with my life.
Last night I joined a Teamspeak chat while playing with some new peeps and the mic does the exact same thing with Teamspeak. With teamspeak I have to completely close Teamspeak and open it if I want the mic to work again.
I have no issue with Skype. While the mic is in this not pulling through to the application state I can see mic levels in Windows recording devices so the mic is definitely working and pulling through to the OS...
Any suggestions? Has anyone else come across this? I have only tried Win7 so not sure if Win10 will fix this?
