Replies: 2 comments 10 replies
-
Oh! That's an important hint. Nice. It's possible that there's really not much effort necessary to make this happen. Will look into that. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes, this works! Awesome! Really glad you pointed me to audio loopback devices. I still think #999 is important, but this is a good and quick workaround. Will be in 2.16.5. |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Reaper now natively implement audio loopback devices. The main benefit is this allows a user to use reaper standard recording arming and monitoring for capturing output of a virtual output as opposed to using receive, which always sends signal to the output.
(https://reaper.blog/2022/10/669-update/)
Using this (along with MIDI loopback) should in principle provide an alternative to #999 .
As an example, I can have a setup like this
with potentially a virtual instrument on "Ext HW" track that sends it output to "Aux Loopback1" (here set to not record, but monitor only)
The routing would look like this
And playtime would see this with track 1 using "Aux Loopback1" input.
It looks like it "almost works" - playtime in fact sees the signal, but says the input is unsupported.
Beta Was this translation helpful? Give feedback.
All reactions