![]() Okay, maybe some of you experts can help me.Ģ) Use Reaper to supply audio (which is being provided by a ReaStream from a second computer), to the video capture software. ![]() Definitely increses the latency to a noticeable level, but not untenable. IIRC I have mine set to around 128 or more when using WASAPI. You need to increase that to get rid of those. The snaps and crackles are because your buffer size is too small. So I switch to WASAPI when I need to do that. ![]() OBS looks for sound coming through the computer's audio system, but when using Focusrite's ASIO drivers, Reaper talks directly to the soundcard, and as such no audio goes through the system such that OBS can hear it. tried some different setups but no luck! □įirst let me say that I was mistaken regarding recording audio in OBS using the Focusrite ASIO drivers. No 1 is worst as I could add in sound from another source but of course it would be nice if sound rec worked. And yes, I can simultaneously record audio in OBS while running Reaper, using Focusrite's ASIO driver.Ĭan I be so bold as to ask you to share your settings? I have just recently tried using OBS for capturing the screen in Reaper but I run into two problems:ġ The playback in Reaper sounds horrible w snaps and crackles while recording I've got a Focusrite Scarlett 2i4, and its drivers are rock solid and VERY low latency, on the order of 3ms or so. Getting an audio interface with its own ASIO drivers is the only solution to this that I'm aware of. You can increase the buffer size to reduce the pops and crackles, but then you'll get higher latency. WASAPI is inherently higher latency, which is why ASIO drivers exist. If you opened a browser and tried to play something with audio, you won't hear it. NOTHING else can use the sound while an app using ASIO4ALL is running. The issue there is that ASIO4ALL completely takes over your soundcard.
0 Comments
Leave a Reply. |