ASIO INPUT CAPTURE

[marshallt]

I use the Asio Input Capture source to send audio directly to OBS from my DAW. I use Reaper. Reaper has an app called ReaRoute that allows me to send a stereo audio output from Reaper to any program that will use ReaRoute. OBS 100% does via the ASIO Input Capture source option.
Every time I close OBS, and then reopen it to use it, the ASIO Input Capture option is muted. I must open the source, change the Reaper Client 1, and Reaper Client 2 choices to any random choice, and then back to where they were originally set(Reaper Client 1, and Reaper Client 2). If I do not perform this change every time I use OBS to stream to YouTube, my live stream is silent until someone lets me know it is silent.
I never monitor OBS, because of the latency the program introduces. This problem should also be fixed, but that is for another thread.

OBS should fix this problem. It creates unnecessary program changes, and mutes a Live Broadcast.

 

[Lawrence_SoCal]

my recollection - OBS Studio does NOT natively include an ASIO Input Capture source option.
are you referring to the 3rd party plugin ?? https://github.com/Andersama/obs-asio
in which case, OBS Studio isn't involved, right? and you should be asking the plugin author?

Regardless, I'm be watching this to thread to see if someone with direct insight comments (I'm not such a person)

with that said
- latency when OBS Studio open isn't something to be 'fixed' ... it almost always means either your system is under-powered and/or your OBS Studio settings are incompatible with your systems capabilities... whether you are CPU, GPU, RAM or other limited? can't say, it depends on your specific scenario...
you didn't make things worse by using Studio Mode (2X rendering workload), did you?
- I too am looking at DAW into OBS Studio.. there are numerous threads about the Operating System issues associated with Audio, and ASIO. I'm only guessing here, but 1 possibility is that while the audio input Device name may stay the same (Reaper Client X) that does NOT mean the underlying device ID/GUID/whatever stays the same (which many applications, and I suspect OBS Studio, uses). The device ID issue arises frequently with multiple USB cameras of same make/model. Its an OS thing.
I mention this only as I could imagine there may not really be anything OBS Studio could do, without a complete audio interface re-design... then again, maybe it is somethign else completely... as noted up front, I have no direct experience with Reaper or ASIO with OBS Studio

But I am looking for digital audio out of my Presonus AR12 USB into a simplified DAW to OBS Studio... and Reaper VST plugin was one recommended approach.. but your description sounds interesting in terms of audio routing. Reaper's DAW has been mentioned as a simpler than Studio One DAW (my DAW needs are super simple)