John Armstrong

The ASIO4All / Jamulus issue has been identified to Volker and the friends who write Jamulus code, so I guess if it was possible to improve things, it would already have been considered.

Thanks for your interest and reply! It looks like the ASIO4All issue is still open (305 on github), and I can see nothing in the Jamulus change log that has addressed it. I last tested it on 18 December, on Jamulus 3.6.2, so I'm convinced it is still a problem people will see.

Hi Rachel, As you can probably tell by the delay, I'm new to SourceForge and did not see your message until today. I had expected email contact from SourceForge for anything new, but that did not happen. if. Sorry. Jamulus Launcher makes no checks on the type of sound device. A Jamulus user can choose a device that won't work, just as they always could. What Jamulus Launcher offers is for a user to throw away that copy of Jamulus, and to start anew. Hopefully the user will select only 48kHz devices...

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...