JACK is a system service that allows for the interconnection of audio between applications. Early versions of Mixbus required that JACK be installed on your system. Mixbus no longer requires or expects JACK to be installed. Mixbus uses your sound card directly via ASIO (Windows), Core Audio (Mac) or ALSA (Linux ).
If you would like to interconnect the audio of different applications into Mixbus, then you can download and install JACK for your system. JACK is not a Harrison product, and we cannot provide email support for JACK users. However you will find a lot of JACK users on our forum, because JACK is a powerful utility.
JACK creates virtual audio and MIDI ports that can be connected and shared between nearly any application on your system. If the application is JACK-aware ( i.e. it was compiled with the JACK libraries) then it will have some additional features such as sample-accurate transport control and sync. There are many third-party apps that can control JACK connections, save and restore your connections, or even route the audio or MIDI using Ethernet. Mixbus is fully JACK-enabled, and it can save all the JACK connections that are made to it. Mixbus can also use JACK as a sync source, or it can be the master sync source.
JACK control from within Mixbus is straightforward:
When you select JACK as the Audio System, there is only one parameter: the buffer size option. Buffer size allows you to adjust the latency of the recording system. The 256 samples shown here is equivalent to 5.8ms, which creates less latency that having a sound source 6’ away from you (sound takes about 6.6ms to travel 6’). You can also disconnect from JACK from this window.
A full description of JACK timecode sync is beyond the scope of this manual. You can learn more about JACK at JackAudio.org