Can't use Synchronous Audio Router as an ASIO Device with Jack about synchronousaudiorouter HOT 6 OPEN

I was not able to use SAR with Jack until using another program (Ardour) which supports opening ASIO driver configuration panels. The problem was that SAR was never configured. After using another program to configure SAR, Jack plays with SAR just fine.

from synchronousaudiorouter.

Well, it works just fine on my machine.

I'm using JACK, SAR, tascam audio interface as the asio driver backend of SAR, and Reaper on windows 10. The buffer size I provide to SAR is 64, which is also the minimum size of tascam audio interface driver.

from synchronousaudiorouter.

Just wanted to drop a note here for others with this problem:
If your ASIO device reports a minimum latency of >10 ms, Portaudio(which is used by Jack in this setup) will decide a minimum buffer size matching that latency, no matter what you set using the -p option. In my case, using an XR18 mixer, I managed to fix the problem in the control panel of its ASIO driver where the latency was settable.

from synchronousaudiorouter.

I have a STRANGE issue that occurs now and then and is unfortunately an issue right now.

I do weekly livestreams and play guitar at the top of each livestream. I run a licensed version of Reaper and have the Syncronous Audio Router installed to send the main out from the SARS output endpoints (using the ASIO driver for my Behringer UMC404HD interface of course) to Windows which is then captured in Streamlabs OBS as an audio input source on my scene. If you use OBS or Streamlabs you know what I mean

Crazy thing is that every now and then, (once every few months maybe at most) even though I haven't touched ONE THING in ANY application to change this audio routing, Windows stops receiving any audio from the output so, in turn, Streamlabs isn't getting any audio as well. WTH?!

I feel like I've tried everything, uninstalled SARS, reinstalled SARS (latest version), reconfigued Reaper, played with the Windows properties for the SARS audio output (Windows does see these SARS outputs AND inputs as soon as I launch Reaper and when I close Reaper, these disappear from Windows so Windows IS seeing it.

So frustrating as I use this a LOT and never make changes to the configuration that worked the day before and it just stops working. Has anyone else ever experienced this? Do you have any suggestions I can try? There are no wrong answers, just people helping people. Thank you in advance for your help.

from synchronousaudiorouter.

I was not able to use SAR with Jack until using another program (Ardour) which supports opening ASIO driver configuration panels. The problem was that SAR was never configured. After using another program to configure SAR, Jack plays with SAR just fine.

I found this utility helped me see and configure some ASIO tools on Windwos 10: https://sourceforge.net/projects/asiocpl/

from synchronousaudiorouter.

Until earlier today I had the same problem as the issue creator. By now I managed to make it working (sort of, more on it beloew).

First of all, asiocpl and such is good, but these won't add the audio endpoints to the system, they just maintain a configuration file in %APPDATA%\SynchronousAudioRouter\default.json.
To make the endpoints appear, you need to use an ASIO client (is this the good term?) that will initialize the SAR ASIO server (again, is this the good term, or did these just stick to me from JACK? From now on I'll assume it is). Such cleants are DAWs like Reaper, and also JACK, which can be managed with QjackCtl (packed in JACK Windows installer) or Catia or a few other managers.
With any client you want to use, you need to set it up so it will use the SAR audio server. In QjackCtl, this happens in the setup->settings\parameters\interface, which you should change to ASIO::SynchronousAudioRouter, then OK and Start, or in Reaper, it's Toolbar->Options\Preferences\Device, audio system to ASIO and ASIO Driver to SynchronousAudioRouter, then additionally also select the range from the dropdowns (both for placback and recording) which ones to open up, but here you don't need to press "start", because it (re)connects as soon as you close the ASIO config dialog. In my very fresh so possibly wrong experience QjackCtl (or JACK itself, who knows) automatically opens up all channels, whether there is a configuration for that I don't know, but Setup->Settings\Advanced has some settings that might be it.
If you received erros here, read the last pharagraph.

As I haven't used Reaper anymore, I can't say much more about it, but in QjackCtl's Graph window, after starting the JACK server, I was able to see all the playback devices per channel, and also in the Sound window (mmsys.cpl). With this graph window you can make connections between playback and capture devices, and so you already achieved what Virtual Audio CAble from vb-audio can do, just without any limits. (except hardware limits, now only they apply).

Probably that's known among the earlier adopters, but it's not easy to find so I document it here: in the last signed version of SAR (0.13.1), there's a deadlock bug that will cause any ASIO clients and other software that deals with audio endpoints on the system to stop responding. This also means that any such software will hang around until you restart the system, because even with PsKill with SYSTEM privileges, you won't be able to stop them.
This bug is triggered if an ASIO client tries to disconnect from SAR. With QjackCtl this happens when you stop the JACK server, and in the case of Reaper it can happen a lot earlier, because as I mentioned earlier going into the ASIO config dialog and changing settings will make Reaper to reconnect to SAR, which is a disconnect, and then a reconnect, of course.

There is also another bug in that version that breaks autodetecting changes to the SAR config file, which means that if you added or removed endpoints while SAR was being used by something, it won't detect the changes (or in a better case it does but very slowly, under a few minutes time).
With these 2 bugs coupled you must deal with the settings very carefully in production, because you can crash your sound system very easily. But as I read here and on the discord chat, these have been fixed in 1.13.2

To the dev: I did not wanted to whine about bugs in the older version, I just waned to collect my findings here so if someone finds it, they may spend less time on setting up SAR :)

Also, for anyone wondering about the signing problem: no, you can't sign the driver yourself. In the case of Windows 10, it's hardcoded (as far as I know, feel free to fix me if I'm wrong) into the system that the driver signature's sig chain's root cert should be a specific one from microsoft, and it's very unlikely that anyone will every obtain that.

If you had problems with Reaper or JACK when setting the interface to SAR:
Although my sound hardware had a Realtek ASIO driver by default (by this I mean even before I started setting up this new audio system, probably from the official drivers for my motherboard), I needed to install ASIO4ALL because with the realtek ASIO interface SAR just wouldn't work, because Reaper would throw me with errors all the time, not speaking about JACK being unable to start. By installing ASIO4ALL 2, and setting that as the hardware device for SAR, it started coming together: Reaper was able to use the SAR audio interface and the endpoints I set up in SAR's configurator appeared in the Windows Sound menu. From that on I was also able to connect to SAR with JACK, as I described above.

from synchronousaudiorouter.