The JUCE version of OBS ASIO does not function properly with ReaRoute ASIO.

[tjwrona]

Plugin Version
v3.2.1f (latest) -- This regression occurred when the library was converted to use JUCE. (I have confirmed that the old BASSASIO version does still work, but unfortunately the BASSASIO version does not function correctly with the latest version of OBS so I am stuck on version 29 until OBS ASIO is fixed)

Describe the bug
With the JUCE version of OBS ASIO I am no longer able to send audio from one application into Reaper using ReaRoute ASIO, and then out of Reaper to OBS using ReaRoute ASIO. (It is possible that the JUCE version is causing OBS to try and take exclusive control over the ASIO device?) The older BASSASIO version is fully functional.

Post a log of OBS-Studio:
2024-12-23 20-53-14.txt

To Reproduce
For a simple test configure Rocksmith 2014 (or any other application) to send audio to Reaper using ReaRoute ASIO via inputs 1/2:

Note: Rocksmith ASIO indexes start from 0, not 1

Then configure Reaper to send and receive audio from Rocksmith via ReaRoute ASIO inputs 1/2:

Then configure Reaper to send audio out to OBS through ReaRoute outputs 3/4.

In OBS, receive that audio on ReaRoute ASIO inputs 3/4:

With OBS CLOSED I can send audio from Rocksmith into Reaper and the audio plays back fine. The second I open OBS and OBS tries to access ReaRoute ASIO the audio becomes completely distorted and unusable.

Closing OBS restores the audio back to good quality.

Re-opening OBS will break the audio again.

It is consistently reproducable.

Expected behavior
Audio should remain clear when OBS is opened and OBS should be able to receive audio from ReaRoute ASIO while another app sends audio to Reaper through ReaRoute ASIO at the same time.

Additional context

IMPORTANT: This is also reproducible without Rocksmith.

If I send audio into Reaper via ReaRoute ASIO from any application, and then out to OBS via ReaRoute ASIO the same problem seems to happen. I have also tested sending audio into Reaper from VoiceMeeter and then out of Reaper to OBS.

HIGH IMPACT TO ROCKSMITH STREAMERS

This is a problem that impacts many Rocksmith streamers on Twitch. A lot of Rocksmith streamers use ReaRoute ASIO to send audio to and from Rocksmith, and then also use ReaRoute ASIO to send audio to OBS. This bug is preventing us from upgrading to a newer version of OBS so we are stuck on OBS 29.

Rocksmith is a very picky game when it comes to audio so ReaRoute is one of the only viable options.

[Phantatsy]

I can attest to this being an issue.

[tjwrona]

I tried using ReaStream as a workaround, but I get pops/crackles with ReaStream into OBS. :(

For other users who have this issue I have heard ReaStream may be a viable workaround. For me personally it doesn't seem to work.

[FaBBad]

It's the way how was configured by code. I think it has solutions but as I don't code I can only report to check if is all good or not.

[mattCorriveau12]

I can confirm that this is still and issue. If the OP says old versions of OBS and OBS ASIO work together, I'm going to try to install those, because the latest versions do not play well together. The distortion and crackling makes the audio unusable.

I have a focusrite solo going into Reaper, and reaper interfacing with Rocksmith input and output. That works great, And I'm able to open up OBS with no audio issues. As soon as I install the asio plugin and add the ReaRoute device however, the audio distortion and crackling starts.