This seems like it should be easy, but I’m not getting it.
I’m trying to record the audio from a YouTube video into Cubase 10.5 pro using the loopback function on the UR816c.
The sticking point seems to be that there is no way to route the “system audio” to whatever inputs you would use to assign to record into a channel.
What am I missing?
Thanks!
Chris
Try to set the interface as default audio device so that the system audio plays through it.
Windows or Mac?
Version ?
Yep. System audio is playing through the outputs of the interface.
I just can’t seem to select any inputs on the record-armed track that will be able to record those outputs.
Chris
Windows 10.
Cubase Pro 10.5
ASIO Link Pro (now free) will provide the patch-bay required to route audio among WDM, ASIO apps, and optionally - streams on your local/LAN/WAN network. It should work with any audio interface that has ASIO Drivers.
If your audio device doesn’t have native ASIO drivers you’ll also need something like ASIO4ALL.
Step 1. Install and Configure ASIO Link Pro to use your preferred audio interface (Directly if it has ASIO drivers, or via ASIO4ALL if not).
Step 2. Configure ASIO Link Pro to multi-client status. Enable the LOOPER loopback racks (needed if you want to route between multiple ASIO based hosts).
Step 3. Use the windows settings panel to direct your browser to send audio to one of the 4 ASIOVADPRO devices.
Step 4. Launch Cubase.
Set Cubase to use the ASIO Link Pro device.
Studio Setup/Audio System
Connect the Cubase mixer busses you wish to monitor from to the ASIO Link channels you wish to use. You can have up to 64 inputs, and anything can be routed into them via ASIO Link. Your audio device, other ASIO apps, or your 4 ASIOVADPRO WDM virtual cables.
In my case, I’ll be using the control room to monitor and it connects straight to a set of Equator D5 powered monitors that are connected to outputs 1&2 on my Delta 1010 interface. Since 1&2 leads straight to my Delta 1010, where my monitors are connected, I won’t need to route anything in the main asiolinktool.exe instance.
Tap F4
Also set up inputs from ASIO Link of your choosing to record from. You can have up to 64. I’ll keep it simple here and just set up two on channels 1&2. I also have a set of ear cans plugged into outputs 7 & 8 on the Delta 1010 I’d like to use from the control room…
Note: the first ASIO Driver Out Mix channels in the main asiolinktoo.exe instance of ASIO Link Pro will usually go directly to your audio card outputs. In my case the Delta 1010 has 12 outputs (1-8, plus Stereo SPDIF, plus a live monitor/mix)…beyond that I can use ASIO outputs for a variety of other purposes.
If I’d used a high channel for my Control Room outputs beyond what my audio card addresses, then I’d need to connect them in the main asiolinktool.exe panel (again, a green icon in system tray).
Say I’d used channels 33 & 34 instead of 1 & 2 for my control room routing…then I’d conntect 33 & 34 ASIO Driver Out Mix pins to LOOPER OUT 33 & 34, then connect the LOOPER IN pins 33 & 34 tto the respective ASIO Driver Out Mix pins for my Delta 1010 outputs.
Step 6. This time find the Cubase instance of ASIO Link Pro in your system tray (green icon again).
Connect the appropriate ASIOVADPRO Speakers In ports to the ASIO inputs you want to use in Cubase.
…
Now Audio is routed from Firefox into Cubase. The Cubase Control room is routed to my Delta 1010 where I can monitor.
Oh, I almost forgot. Sometimes stuff comes in 6 or 8 channels…it’s possible to mix it all down to a single stereo pair from here, or you could set up more inputs (or even a surround sound bus) in Cubase.
…
So the key to getting this working is to remember that when working in the ‘multiclient’ mode, you connect your outputs to the actual audio interface in the asiolink.exe instance.
You can also connect ASIOVADPRO SPEAKERS IN here in the main asiolinktool.exe instance for live monitoring purposes. It’s also where you’ll take care of setting up network streams.
You connect your inputs in the ASIO Link Pro instance for the HOST/DAW you’d like to route things INTO. If you want to route among ASIO apps then you’ll use the LOOPER feature (usually on higher channels) from the main asiolink.exe instance, and then route it into the HOST/DAW(s) of your choice using their associated system tray instances of ASIO Link Pro.
Bump, since I went back and overhauled the mini tutorial.
If you turn on loopback the system audio (all audio playing through the interface) should be on first 2 inputs.
Sorry for the delay… I got this sorted. I was looking for activity in the metering in DSPMixFX which wasn’t happening. I did notice that, when DSPMixFX was set to “live cast” - I could see the input coming into inputs 1+2 on the mixer within Cubase.
Thanks!
I am trying to route flstudio 20 to go inside cubase, using asio link pro as you showed, but it doesn’t work. 
I have cubase le ai 12 so it is a little bit different, for example there is no control room, but i am sure it can be done. @Brian_Roland could you please make a tutorial as the one you made, but this time routing flstudio output to be recorded into cubase audio track? I tryied again and again but i could not do it. thank you.
Apologies, but I do not yet have Cubase 12.
Perhaps these ASIO Pro tips might help.
Make sure Asio Pro is configured to:
Enable LOOPER loopback racks
Make sure the Main ASIO Link Pro instance ‘asiolinktool.exe’ has the “Enable multi-clients” ticked so it’s green.
Whatever audio interface you assign the initial ASIO Link Pro instance to use will get the first set of ASIO Driver IN and OUT ports.
I.E. If your interface has 8 outputs, and 8 inputs, then those will be assigned to ports 1 - 8 in the driver respectively (Showing in Cubase and other apps as LinkOut1 - 8).
Rember that things you wish to route INTO an application should be done in the ASIO Pro Instance for that app.
If you wish to route from one ASIO application to another, then you will need to use the loopback rails. Send the ASIO Driver Out ports you’ve assigned Cubase to use for output to some loopback rails, then you can use those ports to get streams INTO a different app.
If you wish to route a stream out of an application, and then back into itself, again, you’ll want to use the loopback rails.
Consider this scenario:
Imagine you have an audio interface with 8 inputs, and 8 outputs. (Mine actually has 12 if I count the Monitor Mix, and SPDIF connection, while only having 10 outputs counting SPDIF…but In this scenario pretend it’s a straight and simple 8X8 audio interface)
So…in your matrix, those are already set up as ASIO IN and OUT 1-8.
This means that anything you assign inside Cubase using the ASIO Link driver OUTPUT ports 1 - 8, are already going to route OUT to your audio device. In this theoretical example,
I can use all the output ports above 8 to route things around from ANY ASIO app into looback rails, and ultimately to anything I like other than my audio device. Apps that use Windows Direct drivers don’t need the loopback rail. You can connect those directly to inputs in the DAW instance of ASIO Link. More on that in a moment.
As a general rule of thumb, in this multi-client mode…I don’t need to connect any ‘output wires’ in the Cubase Instance of ASIO Link at all. We’ll be doing ASIO output routing through the main asiotool.exe instance and loopback rails. More on that in a bit.
So, I’ve just gone ahead and used the out mix hot button to connect everything to loop back rails, then unhooked ports 1 - 8. You can use the loopback rails for 1-8 if you need them for some reason (to send those outputs to some other ASIO DAW), but for this scenario I know I won’t be using them.
That takes care of outputs, and gives me a 1:1 correlation for every possible connection above port 8.
So now, if I load a second ASIO DAW, I can connect his outputs to anything above 8 and then route it into Cubase. In this example, lets launch Dorico, and send his output to ports 15 and 16
.
Then I’ll go to Cubase and set up an input to get Dorico’s stream from Ports 15 and 16.
As for the INPUTS coming from your audio interface. You’ll need to first connect 1-8 (or whatever interface inputs you’ll be using for the session) inside Cubase itself, then pull up the Cubase ASIO Link Instance and connect the ASIO Driver IN jacks to the corresponding inputs you want routed INTO Cubase.
In Cubase, just go ahead and set up ASIO Link base inputs 1-8 in relation to the audio device. Then connect them straight through in your Cubase ASIO Link instance from the system tray. Also note, you might not see an ASIO Link instance in the system tray until you have assigned something to the ASIO Link driver from within Cubase. Since I’ve already set up looback rails with a 1:1 correlation, I can also connect pins 15 and 16 here, and I Now have Dorico’s output routed into Cubase!
Next lets imagine a scenario where I wish to bring in an audio stream from a non ASIO application. In this example I’ll just bring in Youtube from my Edge Browser.
First I’ll direct Windows to assign one of the ASIOVADPRO Mix drivers.
Then I’ll assign some unused ASIO LinkIn ports in Cubase. I’ll use channels 17 and 18 in this example since I just want to get a simple stereo stream coming in. Of course I could set up 8 for full surround sound if I wanted…but instead we’ll just mix it all down to stereo (some Youtube vids do have some kind of surround sound, and the ADPRO drivers support up to 8 channels).
And in the Cubase instance of ASIO Link Pro, connect the ASIOVADPROD SPEAKERS IN pins to ASIO HOST IN MIX. Notice how I connected the middle and back channels as well…optional, you could just connect pins 1 and 2 if you know your vid will only be in stereo. This is just one way to get a quick mix down if a vid has back channels or something. ASIO Link even has a little mixer grid if you need that to adjust the levels of anything in the matrix, at nearly any point (Click In or Out Mix buttons to get those).
So, now I have two different apps routed INTO Cubase. I can do any monitoring and recording of these streams from the Cubase mixer.
Now, what if I want to send stuff from Cubase OUT to something. How about skype (a non ASIO app)? No problem…
Pick a pair of ASIO Link channels that aren’t already being used and set them up as outputs in Cubase. I’ll use channels 33 and 34 in this example.
I’ll set the Skype Microphone input as one of the unsued ASIOVADPRO Drivers. In this case I’ll go for the Mix 02.
Then I’ll go to the main asiolinktool.exe instance and connect those outputs to the ASIOVADPRO MIX 02 OUT.
Now I have a set of outputs on the Cubase Mixing Console that I can route whatever portions of my mix I like out to skype.
In general, I’d use AUX Sends to designate whatever channels I’d to send over skype…because sometimes we don’t want to send EVERYTHING to our skype call ALL THE TIME.
I.E. I’ll set up my mic, which is plugged into inputs 1&2 on my audio interface, and an audio track that I want sent along with my voice, and use AUX SENDS on those Mixer channels to send them to the Skype Outputs.
Alternatively, if you wanted, you could skip the step of making a dedicated Skype output in Cubase, and just send everything that’s coming out of your mains (same thing going out of your AUDIO INTERFACE outputs).
You could also bypass Cubase all together using ASIO Link, and connect your mic and your Cubase Mains directly to Skype, and ‘mix it’ from inside ASIO Link itself! Your options are many…
You can bring audio from Skype into Cubase in the same we described for bringing in Youtube. Simply assign Skype’s output to one of your ADVADPRO devices from its own configuration panel (or the one in windows if the app does it that way), and bring it into Cubase. Use the Cubase mixer to decide where to send that so you can record, hear, and adjust volume and such as you see fit.
Again, you can bypass Cubase all together with your sykpe output if you prefer, and just connect it straight to the out pins of which ever audio device outputs you want to hear it over, and adjust the volume with the revelvant ASIOVADPRO SPEAKERS IN, IN MIX matrix.
And this is pretty much how it works. Obviously you can connect things to multiple places and do mixing in ASIO LINK Pro itself. You don’t have to do a 1:1 relationship like I have set up for simplicity sake.
The point is…
Route stuff INTO your ASIO Apps using the instance of ASIO Link that goes with a specific app. All the instances will be tucked away in your system tray.
Route OUTPUTS in the main asiolinktool instance. If it needs to go to another ASIO app, then do it through a loop back rail here first, and then over in the app’s ASIO Link instance, connect the corresponding loop to the assigned ASIO Pro LinkIn channels.
Hope this helps some…
Thank you very much!! I found the interface quite difficult but i will try again carefully line after line
I installed ASIO Link Pro and now have loopback without even stealing two channels from the interface. Intimidating interface (at first), but seems to work well.
