Troubleshooting JACK

Under certain circumstances, JACK may not work as expected. Here are a few tips to help you troubleshoot JACK operation.

Is JACK available?

Under menu Help -> System Info you will be able to see if JACK has actually been loaded by HD24connect. If HD24connect says Loaded, it means it found JACK and is using it. If HD24connect cannot find JACK, make sure the JACK module is in the search path of HD24connect.

• For Windows users, it is recommended that the DLL file of JACK is placed in the same folder as HD24connect. It must be called libjack.dll.
• For Mac users, the .dylib file of JACK needs to be placed in the application bundle under HD24connect.app/Contents/MacOS/. It must be called libjack.dylib
• For Linux users, the jack shared object libjack.so (or similar) needs to be placed in the startup directory of HD24connect and must have the name libjack.so.

Note that instead of placing the JACK library in the folder of HD24connect, the system search path can also be used; c:\windows\system32 or /usr/local/lib/ would be good locations as well. If you choose to do this, beware of overwriting existing files.

Is the JACK server running?

If the JACK server is not running, JACK audio will not be available, and HD24connect will play back audio through the default system audio output device instead.

If there is no sound

If JACK is running, HD24connect detects it but yet there is no sound, check if audio is being routed out of HD24connect to an audio output device, or to a program that in turn outputs audio to an audio output device.