Hi, I want to ask you something. Yesterday, I did a stream with both in-game audio as well as microphone audio as I normally do. However, for some reason, OBS Studio found it fitting to play a little prank on me and decided to completely randomly switch input device from my headset-microphone to the vastly inferior USB webcam-microphone. I have no idea how it did that and my question is, how do I prevent this from happening again?
I was completely unaware during the stream and afterwards I felt it kind of ruined the whole broadcast in a way, though I still accept it as a viable episode in a series of episodes. (you can hear the problem yourself by going to https://www.twitch.tv/videos/151894527) .. I checked the settings and found that there were three options: "Default", "USB Microphone" (crappy one) and a Realtek-option (can't remember the exact name right now because I am at work) and I had it set to "default"; maybe that's the problem, though OBS Studio has always defaulted to the headset before yesterday.
Naturally, I have now switched to the Realtek-setting which I'm guessing is the driver for my HyperX Cloud headset, but I want to make sure this doesn't happen again. Is it possible that Windows 10 had something to do with this or is it something else? Have you ever heard about this kind of problem before?
I was completely unaware during the stream and afterwards I felt it kind of ruined the whole broadcast in a way, though I still accept it as a viable episode in a series of episodes. (you can hear the problem yourself by going to https://www.twitch.tv/videos/151894527) .. I checked the settings and found that there were three options: "Default", "USB Microphone" (crappy one) and a Realtek-option (can't remember the exact name right now because I am at work) and I had it set to "default"; maybe that's the problem, though OBS Studio has always defaulted to the headset before yesterday.
Naturally, I have now switched to the Realtek-setting which I'm guessing is the driver for my HyperX Cloud headset, but I want to make sure this doesn't happen again. Is it possible that Windows 10 had something to do with this or is it something else? Have you ever heard about this kind of problem before?
