The downside is it can be very confusing to set up and use, and the developer is deceased so there’s no support, no future updates, and a minimal user base so it’s hard to find anyone to answer basic questions. I’ve done something very similar to what you’re describing using ODeus ASIOLink Pro, which I found to be a great multi-client ASIO wrapper that adds zero latency and has built in virtual audio cable functionality. I think ASIO4ALL can do it, but I’ve had too many issues with ASIO4ALL over the years to recommend that. If Windows is going to force GP and the DAW to only use one device for the input and output, then either the device drivers have to be support multi-client (many do, but the Focusrite drivers for the Scarlett don’t) or you have to have some software that will function as an aggregator. I don’t recall using a DAW or other Windows application that lets you choose a different ASIO device for your input and output.

I don’t know if the equivalent of that is even possible in Windows. In your Mac example it looks like you’re bringing guitar audio into GP through your Scarlett, then routing it out over Blackhole. I don’t think any of this is as straight forward in Windows as it is on Mac. Is there any way to reduce that latency or is there an alternative product with lower latency? I’m not a Windows user but I’m being told that Virtual Audio Cable has a very high latency.

And, it was quite a nightmare to get a stable setup with ASIO4ALL. But unfortunately, I could’nt reduce the buffer size of ASIO4ALL under 512 samples (multiples of 44kHz were not available?!!). LoopBeAudio software = ~29ms (using the ASIO4ALL driver)įor the LoopBeAudio solution, I had to use the ASIO4ALL driver because it made it possible to agglomerate both the RME hardware audio interface and the LoopBeAudio virtual software audio interface in GP. RME UCX loopback = ~12.5ms (using the RME driver) So what I measured is only the additionnal latency introduced by the audio loopback. So, I simply recorded a DX7 percussive sound “straight” out of the plugin and after the loopback, and mesured the relative delay. I wanted to report the additionnal latencies achieved when using the hardware loopback of my RME UCX with regard to the LoopBeAudio software for Windows. Regarding my evaluation of loopbeaudio, this is an older report: So I prefer to use the RME hardware loopback. I heard that it is in contrary very quick?!īut as it behaves as an audio interface, I needed to aggregate it with my RME audio interface and had to therefore use ASIO4ALL which introduces latency with regard to the RME audio drivers.

Vb audio cable windows 10