Which suboptimal ASIO Driver should I use when away from interface?

[alexis]

Hi,

I’ll be traveling now and then in the nearish future, and I could see doing some editing/mixing in Cubase 14 Pro on my Microsoft Surface Pro 6, without my interface.

I was wondering which of the ASIO drivers that appear in my Cubase 14 Pro Audio System drop down window would be the best for me to choose … if that’s even a reasonable question?

• Generic Low Latency ASIO Driver
  ASIO4ALL v2
  Steinberg built in ASIO Driver
  Yamaha Studio USB ASIO
  ReaRoute ASIO (x64)
  iConnectivity ASIO Driver (Surface Pro is PC)

Even if there is not a definite one better than the other sort of thing, how should I choose?

Thank you!

[The Elf]

The Steinberg driver should do the job for you - after all, ASIO is Steinberg's technology. It does essentially the same job as ASIO4ALL, which, as a Cubase user, I see no point in installing in future.

[N i g e l]

Yamaha own Steinberg, so those two might be similar

[Wonks]

An aside, but I have to delete the Steinberg ASIO driver in Cubase (13 and 14) if I want to be able to select my Presonus Quantum ASIO driver, otherwise it simply doesn’t show up in the selectable list.

[chotitek]

I recommend the Generic Low Latency ASIO Driver if simplicity is your priority. It’s designed for basic use and works well with onboard soundcards without requiring additional configuration. While it may not offer the lowest latency, it’s stable and easy to set up.

[The Elf]

An aside, but I have to delete the Steinberg ASIO driver in Cubase (13 and 14) if I want to be able to select my Presonus Quantum ASIO driver, otherwise it simply doesn’t show up in the selectable list.

Weird. Have you contacted Steinberg with that one, as it sounds potentially nasty?

[Wonks]

I really can’t be bothered with Steinberg’s non-existent customer service. 3 months for the last reply from them. Life’s too short.

[N i g e l]

I really can’t be bothered with Steinberg’s non-existent customer service. 3 months for the last reply from them. Life’s too short.

your problem rang a bell that suggested to me that you could unplug & uninstall all your USB drivers and then reinstall them with the troublesome ones first [or at least in the first 10].

This was a solution to a problematic KORG driver that didnt show up on drop down menus when installed.
The problem was that it was on page 2 of the list of USB drivers [10 per page]
and it needed to be on page 1 to be seen. Why this was the case when a mouse or printer driver could be installed anytime is beyond me.

[Wonks]

It's the one and only Thunderbolt driver in this case!

[Wonks]

And I only got/get the single choice of ASIO driver - no huge list.

[The Elf]

This was a solution to a problematic KORG driver that didnt show up on drop down menus when installed.
The problem was that it was on page 2 of the list of USB drivers [10 per page]

I *still* have this problem with my Korg/ARP Odyssey. It beggars belief that Korg seemed to get stuck on this, when every other manufacture managed around it.

[OneWorld]

This was a solution to a problematic KORG driver that didnt show up on drop down menus when installed.
The problem was that it was on page 2 of the list of USB drivers [10 per page]

I *still* have this problem with my Korg/ARP Odyssey. It beggars belief that Korg seemed to get stuck on this, when every other manufacture managed around it.

Yep, I had the same problem, and yes it is bewildering that Korg imposed this restriction. Yes 10 might seem an adequate number of devices, but once one considers dongles, keyboards, mice, printers, interfaces, instruments...10 is soon used up

[The Elf]

The 10 device limit was a well-known limitation back in the days of Windows 3.1 and into Windows 7. Back then it was just the way things were. It was a limitation that Microsoft's architecture imposed.

But for Korg to them stumble over it in Win10 and Win11?! And to not offer a solution of their own making? Unforgivable IMHO.