ASIOCreateBuffers fails if no underlying hardware device is selected about synchronousaudiorouter HOT 4 CLOSED

SAR doesn't currently have particularly extensive logging but you can get some information by using the DebugView tool from Microsoft: https://technet.microsoft.com/en-us/sysinternals/debugview.aspx

Run as admin and enable global win32 capture. You should see messages from SarAsioWrapper (and possibly the Focusrite driver as well).

Are you using the 32 or 64 bit version of Studio One? And 32 or 64 bit version of Windows 8.1?

Unfortunately I'm not currently able to reproduce your issue as Studio One is crashing while "initializing MIDI engine" on my machine... (unrelated)

from synchronousaudiorouter.

64 bit windows, tried both versions of Studio One. In the meantime I tried it with another DAW and it's working (with a few UI issues, but otherwise totally fine), so it's most likely an issue with the combination of Studio One and the driver, not my system in general.

I think what might be happening is that Studio One expects the driver to report at least one port, but when the driver is first initialized none are returned since I didn't get a chance to select the Focusrite driver yet.

I'll try the DebugView tool though and report back with what I got.

from synchronousaudiorouter.

Ah, I see the problem now. Studio One is not letting you access the ASIO control panel if the init fails. SAR currently requires a hardware device to be selected in order to open the device, because it mimics the supported sample rates and other parameters of the underlying device. Should be possible to implement a fix for this. If you open SAR in Studio One after having configured it with your other DAW, does it work?

from synchronousaudiorouter.

Yes, it does!
Well, it crashed once for an unknown reason and on subsequent starts it worked, so I'll assume that crash was probably unrelated. It also doesn't have the UI issues I get with Bitwig.

from synchronousaudiorouter.