Some drivers (Like Synchronous Audio Router) need to be configured first to set the number of (enabled) channels, but Jamulus won't even let you select the ASIO driver if it does not support the minimum number of channels....
In this case you get an error message and the previous driver is selected, so no way to enter the drivers ASIO control panel to enable/configure the channels.
I suggest this error message should only appear when you try to connect with invalid ASIO settings, not on selecting the driver.
Last edit: Peter Goderie 2020-12-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can perhaps shed some light on the ASIO4All settings issue, the one that was raised in #305 and is linked to this one. I have researched it in depth and found no fix, but I have provided a way to manage it without disaster in the front-end called Jamulus Launcher, a script that I put on SourceForge on Boxing Day.
I'm another barbershop singer, working with two choruses. Quite a few guys have been caught by the ASIO4All / Jamulus lock-out after selecting a non-compatible (non-48 kHz) ASIO4All device through Jamulus. Even restarting the machine did not fix it. The method of recovery has been to edit their Windows registry - not good if the user is inexperienced, so we've done it via Zoom and screen sharing.
ASIO4All saves sound device settings in the Windows registry. There's a default set (this is what ASIO4All Offline Settings changes), plus a set for any app that has ever used ASIO4All. When an incompatible sound device has been selected, Jamulus Settings does not allow access to ASIO4All until the offending sound device has been disabled in the ASIO4All registry entries. Identifying which ASIO4All registry entries to alter is a nightmare, because the app and the sound devices are identified only by hex hash codes (maybe some of you more experienced coders can dig further into this, but I can't). Awkwardly, if the ASIO4All defaults happen to be set to an incompatible device, then the lock-out takes place the first time Jamulus is launched.
Jamulus Launcher gets round the problem by making a new Jamulus app for each instance the user requires. A new set of ASIO4All settings in the registry is thus created when Jamulus is launched, and (if ASIO4All defaults are ok), it will work in Jamulus. If the user now selects an incompatible sound device in ASIO Setup in Jamulus, that particular Jamulus instance will be locked out, but another instance can be easily created that will work fine. For more info, have a look at the Readme for Jamulus Launcher.
Of course, if Jamulus could detect and reject the user's selection of an incompatible sound device in ASIO Setup, life would be simpler and safer. It may not be technically possible, because ASIO4All will have saved it's (bad) settings before Jamulus gets control back from ASIO Setup.
Jamulus Launcher was written to reliably start several instances of Jamulus reliably, each with its saved settings, including ASIO4All settings. It's crude but effective!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I ran into problems with some ASIO drivers...
Some drivers (Like Synchronous Audio Router) need to be configured first to set the number of (enabled) channels, but Jamulus won't even let you select the ASIO driver if it does not support the minimum number of channels....
In this case you get an error message and the previous driver is selected, so no way to enter the drivers ASIO control panel to enable/configure the channels.
I suggest this error message should only appear when you try to connect with invalid ASIO settings, not on selecting the driver.
Last edit: Peter Goderie 2020-12-30
Hi Peter - is this the same issue as you are experiencing? https://github.com/corrados/jamulus/issues/305
Hi Gilgongo,
The issue is not quite the same, though seems to be related.
At least the solution seems to be the same.
OK well I'll link this to it for when anyone takes another look.
I can perhaps shed some light on the ASIO4All settings issue, the one that was raised in #305 and is linked to this one. I have researched it in depth and found no fix, but I have provided a way to manage it without disaster in the front-end called Jamulus Launcher, a script that I put on SourceForge on Boxing Day.
I'm another barbershop singer, working with two choruses. Quite a few guys have been caught by the ASIO4All / Jamulus lock-out after selecting a non-compatible (non-48 kHz) ASIO4All device through Jamulus. Even restarting the machine did not fix it. The method of recovery has been to edit their Windows registry - not good if the user is inexperienced, so we've done it via Zoom and screen sharing.
ASIO4All saves sound device settings in the Windows registry. There's a default set (this is what ASIO4All Offline Settings changes), plus a set for any app that has ever used ASIO4All. When an incompatible sound device has been selected, Jamulus Settings does not allow access to ASIO4All until the offending sound device has been disabled in the ASIO4All registry entries. Identifying which ASIO4All registry entries to alter is a nightmare, because the app and the sound devices are identified only by hex hash codes (maybe some of you more experienced coders can dig further into this, but I can't). Awkwardly, if the ASIO4All defaults happen to be set to an incompatible device, then the lock-out takes place the first time Jamulus is launched.
Jamulus Launcher gets round the problem by making a new Jamulus app for each instance the user requires. A new set of ASIO4All settings in the registry is thus created when Jamulus is launched, and (if ASIO4All defaults are ok), it will work in Jamulus. If the user now selects an incompatible sound device in ASIO Setup in Jamulus, that particular Jamulus instance will be locked out, but another instance can be easily created that will work fine. For more info, have a look at the Readme for Jamulus Launcher.
Of course, if Jamulus could detect and reject the user's selection of an incompatible sound device in ASIO Setup, life would be simpler and safer. It may not be technically possible, because ASIO4All will have saved it's (bad) settings before Jamulus gets control back from ASIO Setup.
Jamulus Launcher was written to reliably start several instances of Jamulus reliably, each with its saved settings, including ASIO4All settings. It's crude but effective!