I have two interfaces I want to use in Studio One simultaneously. Is this even possible? One only has mic inputs, the other one only has direct input.

 

That's not really possible out of the box, if I recall correctly. But you might be able to join both interfaces using some clever routing like virtual audio cable/voicemeeter. The only issue is that you might have latency problems.

 

I have Studio One myself, so you can only select one device!

You can, of course, route your second audio interface to the first audio interface's line input via a jack.
What are your audio interfaces called?

 

Yes, you could route it via Jack, or VB Cable..

I used 2 interfaces with Reaper, but i had to have two instances of Reaper running. I see that Studio One does not allow that, so if you want your can try using some other daw(like Reaper) for the second interface...if it is only for recording.

 

Yes, possible to do in macOS using an Aggregate Audio Device, and can be combined with a routing program like Rogue Amoeba Loopback.

I was running a MotuM4 and an ICON Pro Audio Duo 22 Live at the same time for about 6 months.

Im not 100% sure about how all DAWs can utilize the I/Os from both interfaces tho, as you would have to do all of that routing outside of the DAW, then use the Aggregate Audio Device as the Input and Output within the DAW.

Edit: I should also mention that the drivers can conflict between 2 interfaces. I had odd system wide behavior with both interfaces. For example macOS preview would not play back audio and videos without both interfaces connected.

 

You can via A dat.
I have my Quantum 2626 hooked up to the Pro 40 via A Dat cables. the 2626 is the master with the pro40 the slave.

 

Hi Ghostwriter,
it is possible. Take a look at Matrix:
https://vb-audio.com/Matrix/index.htm
Good luck

 

Hi folks, great suggestions here. Thanks. VB Virtual Cable actually looks the easiest (so far). Let's see what happens.

 

Yes. I use it! Good software but add a little bit latency.

 

noones mentioned asio 4 ALl here yet which is the og mulit interface hack

 

Never used it for multiple interfaces, but ASIO4ALL is goated software and had helped me out a bunch on Windows systems with audio driver issues. Must have software IMO.

 

asio link pro is free and has very little latency, 0.7ms here i thought but the manual says no additional latency

 

Last edited: Aug 19, 2025 at 10:08 PM

Bear in mind that without joining the interfaces by a clocking scheme (word clock, SMPTE, ADAT (same as word clock, really), MTP might even work if you can figure a way to do it), you WILL get clock drift, and find it difficult to record more than a few seconds without seeing tracks drift out of sync. If it's just for recording short punch ins it can be worthwhile doing aggregating, otherwise it's far less trouble to just buy a single bigger interface.

 

Just want to note that in macOS with a created Aggregate Device in Audio MIDI Setup, you can choose which interface is the slave clock and you can also toggle drift compensation per device in your Aggregate Device. Needed this for my setup.

 

Interesting, I didn't know that's possible.
Do you know how MacOS manages to do that?
Like how does it sync up two quartz oscillators in two different boxes that have not direct connection and are not meant to be slaved? Is MacOS internally resampling both signals and syncing the resampled output?

 

Honestly that's a very good question. That's basically at the limits of my current knowledge without doing some research as to how macOS handles this.

If I had to make an educated guess it would be more in line with your latter comment, where macOS resampling the secondary device and lining it up with the slave clock (at the cost of latency?)

Here's some info about the feature provided by RA:

https://rogueamoeba.com/support/knowledgebase/?showArticle=Loopback-AggregateDeviceHandling

Here's an image of an mock aggregate device I created in Audio Midi Setup:



Edit: Here's a gearspace thread where a couple people discuss this exact thing:
https://gearspace.com/board/music-c...sing-two-interfaces-mac-drift-correction.html

I personally haven't experienced both devices drifting as one guy states, but the guy says that, because you're trying to clock sync 2 interfaces together in the OS software, it involves sample rate conversion on the secondary device, which may render it difficult to use for live recording due to layency.

I don't remember exactly what my setup had in terms of latency using the Aggregate Device in Logic Pro, but it wasn't good. Think 50+ ms

 

Last edited: Aug 20, 2025 at 4:06 AM

It's worth mentioning that if you have 2 interfaces and one of them has ADAT I/O and supports additional channels being received via ADAT, thats probably the most direct "using 2 interfaces at the same time" on one computer and would work flawlessly. Or maybe that's just creating a single Frankenstein interface.

Most likely not going to work for your case as most budget interfaces dont have ADAT support.

 

I love ALP since I replaced Voicemeeter that was giving audible latency.

However, even if you can disable the multiclient option, it's difficult to involve two different ASIO drivers within the same DAW or app.

I mean, in past I used Traktor and Ableton in the same laptop, both with ALP, disabling multiclient option and giving Traktor a proprietary ASIO driver for a connected external audio interface and to Ableton the internal audio interface, generic ASIO driver (was it ASIO4ALL? duh I can't remember).
The nice thing about ALP is that you can have as many ASIO drivers linked to as many apps, provided PC is able to cope with them.

I think here the solution can be much more complicated, maybe impossible with ASIO routers like ALP or Voicemeeter.

BTW I would like to have some feedback from someone who used extensively Coconut. Does it work? Latency?

I tried the sister site version, but crks don't work in any possible way in any system, they just don't launch.

 

Last edited: Aug 20, 2025 at 9:14 AM

Aggregate devices in macOS are sort of how you’re thinking about it, but with a few key differences. On macOS, you can combine multiple audio interfaces into an Aggregate Device. One interface is the master clock, and the others are automatically resampled in software to stay in sync. CoreAudio handles all of this, so timing usually isn’t an issue, even if the interfaces aren’t physically connected. The drift correction is only applied to the non-master interfaces. You can also run into other situations with digital connections like spdif coax, which carry their own clock.
In an actual studio situation, you'd probably end up going with an external clock generator.

It's different from Windows, because the separate ASIO drivers often will not sync automatically. Consumer and lower end pro-sumer interfaces can drift more, while gear with word clock keeps everything tighter. Pro Tools can see aggregate devices, but it won’t create them for you automatically — I remember 10.5 listing a Pro Tools Aggregate Device in your inputs/outputs during installation; Rogue Amoeba’s Loopback does the same, which is annoying to me.

How many channels of i/o is someone really trying to get by doing any of this though? An interface with enough i/o leaves so much less room to create issues.

 

VB Audio Matrix Coconut allows up to 7 ASIO devices.