Monitoring Device bug?

[Josh D]

So, I figured out how to fix the issue, but basically, when booting up OBS after not using it for a while with a monitoring device already set in the advanced audio options, OBS won't output to that capture card.

To fix it, I had to set the monitoring device to default, hit apply, and then set it back to the capture card to get it to work.

Interestingly, the device will work, because if I set my speakers in Windows to the capture card, then the audio is picked up on the other end, but it just won't work in OBS unless I switch the monitoring device to default and back to the cap card again. Even restarting OBS or restarting the computer won't fix it; I have to switch the monitoring device in advanced.

I'm not sure if this is a bug, or if it's something about the cap card I'm using(EVGA XR1), but just thought I'd throw this out there for anyone else having this issue.

 

[Lawrence_SoCal]

I doubt a bug... but maybe. Here, I make obvious my lack of detail knowledge in this area... so maybe someone else can advise us and we both can learn

What I've come across with modern hardware (DisplayPort monitor in my case, with a 3.5mm audio out), is Windows 10 detecting and adding the monitor as an audio device, regardless if anything plugged into it. Then, once OBS start it tends to hang onto devices. So, if Windows considers the default Audio output (playback) device to be something different with today's OS restart, and I don't notice until AFTER I start OBS, then getting OBS back to using the desired Audio output(playback) device is not as simple as changing the OS audio out default. I see this as more of a change in Windows OS behavior, and its impact with OBS' assumptions and use cases. [ I can see good reason why OBS wouldn't change audio devices when 'default' selected. OBS authors had to make an assumption one way or the other.. I'm fine with their choice and it seems the safer way to not mess up a stream/recording mid-activity unexpectedly]

Not knowing better previously, found that exiting OBS, changing OS default Audio then re-starting OBS got me back to where I expected (but was obviously tedious and cumbersome). Doing as you noted regarding Monitoring device I found to be much quicker/simpler.
I suspect if you checked OS Sound Devices _before_ starting OBS, and making sure items matched your expectations, OBS would be fine [but maybe something else going on??].

I'm curious in your case if this is an OS 'feature' of your starting the OS [default behavior which prioritizes getting to desktop over making sure everything full started first], and the capture card drivers not fully loaded/activated when you start OBS?

 

[therentabrain]

This has been vexing me for some time. Most apps, Zoom for example, will notice when you plug/unplug/change your audio and video devices, and adjust accordingly. Some old apps get flummoxed and you have to restart them. OBS acts like an older app. It should be able to notice that the devices have changed, and reconnect as needed, but it fails to.

Disclaimer: I was using the newest OBS but it kept crashing in the middle of shows, so I downgraded. Hoping to try the latest again soon.

 

[Lawrence_SoCal]

No, not 'old' app. rather a function of OBS Studio's intended use... where exclusive access to Sources is often appropriate.
Moving Devices around mid Recording/Streaming session is a terrible idea, representing a mis- (or complete lack of)understanding how device enumeration works at OS layer. in which case, PEBKAC.