I have continuous problems with the Jacktrip app and Windows 11, and hoped we could collect some already proven problems and solutions, since there is no public repository of the issues and requests people send into the Zendesk.
For example: I use Voicemeter under Windows to route my interface and DAW signals to Jacktip, but Jacktrip crashes all the time while initially loading. I could not find any potential reasons for Jacktrips behaviour.
We’ve found that many Windows audio drivers are unstable and cause JackTrip (or any other ASIO audio application) to crash when they try to use them. JackTrip scans all your interfaces at startup, so this is what is most likely happening. Currently there are two known Windows audio drivers that cause JackTrip to crash:
It’s possible that Voicemeeter provides drivers are also unstable? The only known work-around is to remove the faulty drivers from your computer.
Thanks Mike! I can confirm that Realtek ASIO does not function properly and the one from Steinberg also is problematic, especially because both are pre-installed on various devices.
For a generic ASIO driver, ASIO4ALL is working well for me, albeit tricky to configure and operate. If anyone has questions about ASIO4ALL please feel free to ask me.
Has this been resolved? I feel like you should address it on the software side, instead of all of your users have to address it on the cllient side.
Hi @aaron.m.weisberg and Welcome! Thanks for your inquiry regarding using ASIO drivers for the Windows version of JackTrip.
I believe that this issue has been resolved in the latest build JackTrip App 2.4.0 - #6 by miked
Perhaps @miked will have further comments regarding this issue.
Let me also add that Windows users will always need to ensure that ASIO drivers are installed on their computer either via an external device that has ASIO drivers from the manufacturer, or use ASIO4ALL. Then the latest version of JackTrip should detect it automatically.
ASIO drivers are not part of the JackTrip program. They run in conjunction with the computer’s sound system which might include an external audio interface.
Windows audio drivers are notoriously slow, and do not run fast enough for JackTrip. Many years ago, Steinberg came up with ASIO in order to force Windows audio to run faster.
from What is ASIO?
The ASIO protocol was developed by Steinberg, the makers of the popular multi-track recording software Cubase. The primary goal of ASIO sound card drivers was to solve one vexing problem for digital music producers: latency. Latency is a short delay between the time an audio signal enters into a system (i.e. your computer) and the time when it exits the system. You’ve probably noticed latency before while talking on the phone with someone watching the same TV channel as you. There’s a slight delay between the time the audio from their TV enters into their phone and emerges out your handset, so that the two devices are out of sync. This is latency.
More info on Sweetwater:
https://www.sweetwater.com/sweetcare/articles/roland-difference-between-asio-wdm-mme-drivers/
I’m not sure what issue you are referring to. The ASIO requirement for Windows is something that only Microsoft can address.
Windows audio drivers are written and published by the audio device manufacturers, and is something that only they can address.
These problems are universal across all software on Windows, and in no way are unique to JackTrip.
@miked I was referring to the issue of JackTrip support for ASIO, and your comment that with Version 2.4.0, only the “official” signed release of JackTrip supports ASIO. Sorry my brain cross referenced those posts.
It seems that @aaron.m.weisberg is suggesting that the server code somehow reconcile any ASIO issues rather than the user clients.
I think your comment above rectifies that suggestion. Thank you
It is entirely a function of the user to set up the drivers and devices they want to use with the JackTrip client.