How to get many ins and outs for Cubase?

I recently bought an Audient EVO 16, hoping to add some connectivity to my Windows Cubase system (currently UR44). Now I find that I cannot use multiple devices (using different drivers) at the same time. And ASIO4ALL introduces latency issues.

So how do you get, say, 32 inputs and outputs connected to Cubase? What about 64?

You buy an audio interface with 32 or 64 ins and outs.

Also multiple interfaces of the same brand often (always?) lets you use the same driver for both.

I use the RME HDSPe RayDAT and connect all I/O via ADAT.

The advantages are:

  • all analog is kept outside the box to avoid interference
  • the best and most stable drivers in the business
  • wordclock option
  • analog I/O is easily changed or reconfigured without having to change drivers
  • can still use legacy hardware frontends and pres via ADAT
  • combat planned obsolesence

The disadvantages are:

  • limited to I/O with ADAT connectivity
  • need at least one DAC to hear anything

As an aside, I ask why you would need 64 or more channels? In practice, you only need the number of input channels that you plan to record simultaneoulsy.

You’re on a good start with your EVO16, just add two EVO SP8 to its optical inputs to have 24 inputs in a simple clean setup.

If you need 32 or even more??.. ask EVO support… not sure if you can do it.

One might have hardware gear, like synths and audio effects, that one does not want to plug out/plug in all the time but keep connected.
But 64 seems a lot to me, too.

Agreed, as I do too, with an ADA8000 cheaply providing 8 additional inputs for a few ancient synths connected to the RayDAT with one optical cable.

Indeed 64 channels is a lot. I was just curious what people were doing to get that if they needed it.

And yes, my plan was to add two EVO 8 units to get 24 channels. That’s all that platform will support through the EVO 16 system.

The last time I was using multiple interfaces was when I used Sonar with WDM drivers. I could use different interfaces at the same time. So I was not prepared for the shock of only being able to use one driver with ASIO.

Thanks.

The idea is to avoid resampling of the audio signal when Cubase outputs it.
This idea surely was great 20 years ago. If it is still great in 2024 is another question.

Something like RME digiface with ferrofish or similar convertors will get you high input count over usb. For 64 or more channels professionally then realistically no-one is likely doing that on a usb connection. Stuff like Rednet or Dante is designed for this.

I understand that ASIO streams directly from the hardware vs WDM, for example, streams via the OS.

Just questioning, does anyone know if it would be possible to make ASIO drivers such that different drivers could work together?

No, it is technically impossible to make two ASIO drivers work together in one DAW. All these aggregate drivers (like ASIO4ALL) use several WDM/WASAPI devices and bridge that to one ASIO driver.

The Yamaha TF series digital mixers gives you a 34x34 USB audio interface, and you get a fully featured digital mixer at the same time. I use a TF1 as the centerpiece of my studio audio flow, and it works great with Cubase:

No, it is technically impossible to make two ASIO drivers work together in one DAW. All these aggregate drivers (like ASIO4ALL) use several WDM/WASAPI devices and bridge that to one ASIO driver.

That wasn’t really my question sorry if it wasn’t clear. What I mean is, could the ASIO drivers be coded so that they can work together.

¯_(ツ)_/¯

main-qimg-385c92bb5a6d471040e6c3fbe7e26f8d-lq
Mr. LaHatte!

Ok, So you know I’m not speaking of the current situation, right?

IF it is technically impossible to re-create ASIO drivers such that two different drivers can work together, then please explain how that can possibly be the case.

I know someone who was testing Coconut not so long ago. It appeared to work reasonably well, but there were latency considerations…
It’s still a kluge though to circumvent the multiple device limitation in Windows - in the same way that ASIO4ALL , ASIO Link, etc are.
To answer @lahatte’s question, I’m pretty sure that, if there was a way to code ASIO drivers to handle multiple devices, someone (RME?) would have done it by now. It would be an opportunity to sell more hardware so why not?

Well if that were to occur you would no longer have 2 drivers, there would only be 1 driver supporting 2 different product lines. This hasn’t happened yet & seems to me unlikely to ever occur.

Why? Here’s some speculation

  • Different hardware designs require different behavior from their drivers. One size won’t fit all.
  • Competitors would need to share their IP. For RME their great drivers are a competitive advantage that they probably don’t want to see in M-Audio’s hands for example.
  • Low demand. Folks going for a high I/O count generally have a gameplan. For many this will mean sticking with a single brand for simplicity. Plus if you are expanding via ADAT connections you can already mix brands - which is 2/3rds of the way there.