I upgraded to Cubase 14 and now REASTREAM doesn’t seem to be supported. I’m hoping their not losing compatibility with plugins like what happened with my Nexus. Anyone try using REASTREAM with C14?
VST2 plugins are now disabled by default. You can re-enable them in the plugin manager. Just note, that they will probably stop working completely with later versions of Cubase
Thanks… hopefully they upgrade ReaStream. Omnisphere wasn’t working either, I’m currently installing an update for it that’s supposed to make it vst3.
Windows or Mac?
Windows here…
I’ve migrated away from reStream and use ASIO Link Pro these days. It’s free!
It’s a heck of a zero latency ASIO patch bay (has both 64bit and 32bit versions). Even allows incorporating WDM audio into the ASIO grid.
It simply provides an ASIO backend for whatever ASIO driver you have/prefer. Pre and post daw routing/mixing to your heart’s content 
It supports network streams up to 16 channels per instance over the LAN, and/or over localhost.
Loopback rails to the max…so you have plenty of channels to route anything ASIO/WDM to/from any app on the system, and/or any other machines on your LAN that can also run an instance of ASIO Link Pro.
In multi-client mode, it’s a little tricky to figure out at first, but once you wrap your head around it it’s easy to use, and simply amazing.
It’s not obvious that docs are included, but they are included and get put into the ASIO Link Pro folder in “Program Files”.
Another little app that comes in handy for getting audio routed from one ‘plugin slot’ in some host to a plugin in slot in another host on the same system is Wusik Audio Connect. In quite a few cases involving ASIO hosts, it needs to cheat and work through WDM drivers with ‘monitor’ toggled to mimic a loopback. It’s not great if you need tight latency…but it does seem to be stable and reliable (on my system anyway) in situations where a little lag is acceptable it does come in handy.
One example where I use Wusik is getting audio from some External gear onto the Dorico mixing console for processing. I don’t know why Dorico has made it all the way to v5 and still won’t give us the UI to put external kit plugged into the audio interface on the Mixing console. Oh well, it is what it is.
1 Like
I’m Windows. And I took your advice and tried Asio Link Pro. I’m using OBS, Voicemeeter and Cubase. I have everything for Asio Link Pro installed the way a few videos said to install it. It’s even patched by G.A. but I’m not getting any sound. I’m wondering if Voicemeeter is the problem now or OBS. I’m seeing signal flow inside of ALP but when I select the ASIO LINK 1 in OBS…no sound.
Voicemeeter? Is that also an ASIO backend?
Not sure what that does…if it’s also an ASIO backend it might be redundant. You won’t need it anymore with ASIO Link.
At any rate, the thing that I found confusing about ASIO Link Pro at first is that in multiclient mode, each app that uses ASIO Link as the driver gets its own fresh instance in the system tray.
You should connect ‘inputs’ in the instance for the app that needs input from the matrix.
Output routing that isn’t pointing straight to an interface output by your ASIO app(s) will be done in the main “asiolinktool.exe” instance.
Example
Example…
I launch ASIO Link with these settings…
Here is my Main ASIO Link instance…it is named"asiolinktool.exe" in the system tray.
In my case, I have a pair of Delta 1010 interfaces that share a clock and combine into the same driver to give me 24 inputs (Counting SPDIF IN and Mixed/Monitoring), and 20 outputs (16 1/4" balanced analog, and 2 sets of Stereo SPDIF channels).
The inputs from my Delta 1010 setup show up in the 2nd pinkish colored row.
The outputs that correspond directly with my audio interface, I know are 1-20.
Anything on the ASIO DRIVER OUT MIX from 21 and up are free for me to do whatever I like with.
Notice I don’t have anything patched at all in my main instance but a few looper channels from 27-32.
In my case I like to route Windows System Audio through Channels 25&26 (I route it through bidule first, so I can insert effects and such), Dorico into the ASIO Link driver on channels 27&28, I have a special stand-alone instance of the old Yamaha S-YXG50 that connects to ASIO Channels 29&30. The last two I just keep linked up in case I need them quickly with some other ASIO app.
Since I treat Cubase as my main Mixing App that everything else ultimately pipes through, I have it set up to connect directly to ASIO Link outputs on my Delta 1010 Audio Interface. At the moment I have a pair of Equator D5 monitors on channels 1&2 of the Delta 1010, a pair of Yamaha NS-10M monitors on channels 11 & 12, and a headphone amp on Channels 13&14.
The way I’m setting this up…in order to HEAR anything, it must go through Cubase first…and then Cubase sends it out to my speakers/headphones.
So, to get things into Cubase, I need to first set some connections up in Cubase itself…
I want to bring in two devices that are connected to my Delta 1010…
A stereo bottle mic that plugs into channels 7&8 on my Delta 1010. I like to set it up as an External Instrument rather than a direct Input. I get more mixing options like this!
And a Roland Fantom XR that plugs into SPDIF channels 9 & 10 on my Delta 1010…
Over in Dorico I set it to use ASIO Link channels 27&28 (remember I set up looper connections for these channels in the main asiolinktool.exe instance)
And I set up inputs for it in Cubase. I did it as an External Instrument rather than a direct input, because it’s way more flexible in terms of using effects, moving it around on the Mixing Console, etc.
I’m using nano host and a virtual MIDI port to keep the old S-YXG plugin in service (It’s an old 32bit plugin, and newer versions of Cubase aren’t passing SYSEX through stuff like jbridge anymore). So I’ve set up Nano Host to use ASIO Link channels 29 & 30.
I set this up in Cubase…
Before any of this works, I need to put all this stuff in the Cubase Instrument Rack. (They show up under Steinberg/External Plugins).
Then open the special Cubase instance of ASIO Link in the system tray.
And make some connections…
So, what if I want to bring in audio from some WDM app? Here I’ll bring in audio from my Edge Web Browser.
In that case, I’d have the browser use one of the special ASIOVAD PRO drivers.
Set up another input in Cubase…
Add it to the Instrument Rack…
And make the connection in my ASIO Link “Cubase14.exe” instance from the system tray.
At this point I have two ASIO apps, and one WDM app routed INTO Cubase 14.
So what if I want to set a mix from Cubase OUT to something else. How about Skype?
In this case I’ll create a new output bus in Dorico just for a skype mix…
I’m going to choose an unused set of channels well past anything my Delta 1010 rig uses, and also avoid channels I’m already using thus far.
In my main “asiolinkprotool.exe” instance, I’ll connect this to one of the ASIOVADPRO MIX OUT drivers…
And set Skype to get its input from this special driver…
Now I have a bus dedicated to sending whatever I like out to Skype. I could use Group channels and/or AUX Sends to isolate a special mix just for this bus.
How about OBS Studio? Same concept…
Make a bus for it in Cubase and put it in the rack…
Set OBS Studio to get audio from an ASIOVADPRO driver.
And connect it in the main asiolinktool.exe instance…
Now my mixing console looks like this…and I have everything I need on the console to get audio IN from a Mic, Fantom XR, S-YXG50, Dorico, and the Edge Web Browser.
I have output busses at hand for a Main Mix, Skype, and OBS Studio.
As for stuff you might want to pull in or send OUT over the network drivers…again, you’ll do that from the main asiolinktool.exe instance.
For things you want to bring IN from the network driver…again, open the special asiolink instance for the app you’re trying to bring it in from and connect it there.
Note, there is a LOT you can do internally in ASIO Link itself. It’s not a requirement to pipe everything through Cubase as I have it here.
The same basic rules still apply though. Do outputs in the main asiolinkprotool.exe instance. Do ASIO inputs in the special instances that each ASIO app gets. Do WDM through the special ASIOVADPRO drivers.
1 Like
Reastream is VST 1.0 and will never get updated, it’s a very old plugin that was already unstable in previous Cubase versions.
I know Reastream was easier to setup but you can use Sonobus or any other alternative that will offer you more flexibility.
1 Like
I’m seeing the audio in OBS now. I think the problem was with OBS itself…which is SUPER UNSTABLE I never unistalled voicemeeter yet. Voicemeeter pretty much routes audio, and YES it’s now obsolete. It wasn’t able to see DAW outputs. So I needed REASTREAM for routing DAW outs to OBS which was routed to Voicemeeter and finally to streaming software. Now I probably don’t even need voicemeeter anymore as ASIO LINK should be able to simplify my workflow/chain. Thanks Brian. I think I had heard about ALP years ago but it looked so complicated I ended up trying the REASTREAM option…
1 Like