Audio
- Thread starter pepeh
- Start date
Settings -> Audio -> Monitoring Device (or something like that, from memory), immediately below the global sources.
This is the only physical audio output from OBS. It would be wonderful if it had several, like another copy of the same selection for each track (total of 7 now), but at the moment, that's it.
Also be aware that OBS has trouble driving some sound cards, while others are okay. If yours does have a problem, it'll manifest as an ever-increasing delay until it's unusable. Disrupting the stream to that card resets the delay, but it continues to drift out of sync again.
You can choose a different card and change it back again, or you can unroute a problematic source from the monitor and route it back again, or you can mute and unmute the source. If you use the mute option, it'll affect the stream too, which probably had nothing wrong with it, unless you have two copies of the same source: one to stream and leave alone, and one to monitor and "blink" every so often to get it back in sync.
Virtual sound cards don't have this problem (but might have another one, based on my recent experience), so you can send the monitor to one of those and then "bounce" it from there to the real destination, but then you need a virtual thing that can do that.
This is the only physical audio output from OBS. It would be wonderful if it had several, like another copy of the same selection for each track (total of 7 now), but at the moment, that's it.
Also be aware that OBS has trouble driving some sound cards, while others are okay. If yours does have a problem, it'll manifest as an ever-increasing delay until it's unusable. Disrupting the stream to that card resets the delay, but it continues to drift out of sync again.
You can choose a different card and change it back again, or you can unroute a problematic source from the monitor and route it back again, or you can mute and unmute the source. If you use the mute option, it'll affect the stream too, which probably had nothing wrong with it, unless you have two copies of the same source: one to stream and leave alone, and one to monitor and "blink" every so often to get it back in sync.
Virtual sound cards don't have this problem (but might have another one, based on my recent experience), so you can send the monitor to one of those and then "bounce" it from there to the real destination, but then you need a virtual thing that can do that.
If I'm correct in what you're referring to, it's actually a Bluetooth problem, so *any* operating system will have it, not just Windows. Because of limited bandwidth, BT makes you choose between high-quality speakers and no mic, or low-quality speakers and a mic. If *anything*, *anywhere*, asks for the mic, then it's forced into the low-quality mode.
There are several ways to fix it, all of which boil down to ensuring that *nobody* is using the mic.
That reminds me of another pitfall: continuing to use the "Default" selection in OBS, after install and initial testing. "Default" follows the operating system's choice, so it's good for a know-nothing fresh install to show that it works. But if the OS changes, including automatic for who-knows-why, OBS follows that change, which can make it suddenly stop working with no apparent cause. (the same signal path is looking at something different now)
The way to fix this one is to NEVER use "Default" beyond that initial fresh-install testing. Always change it intentionally to the specific device that you're going to use. Then it keeps working, and doesn't switch on you. (and doesn't care what the speaker icon says in the tray)