Installation for Linux
Make sure you read the Getting Started page.
Debian and Ubuntu
Debian repository (convenient)
Jamulus is included in the Debian 11 (“bullseye”) repository and can be installed by typing the following in terminal (Open it with e.g. CTRL+ALT+T):
sudo apt update && sudo apt install qjackctl jamulus
This is the easiest and most convenient way to install Jamulus although it won’t give you the latest features.
Manual install (latest version)
If you want to get the most recent release, you need to install or update Jamulus manually:
- Download Jamulus (.deb)
- Update apt by opening a console window (CTRL+ALT+T should work) and type:
sudo apt-get update
- Navigate to where you downloaded the installer and either double-click on it, or use the command line:
sudo apt install ./jamulus_3.8.1_ubuntu_amd64.deb.
- Once installed, you can delete the file and close any console windows.
Note that if you need to upgrade Jamulus to a newer version, just download the new .deb file and re-install as above.
For installers on other distributions, see their package managers and Repology. If an up to date version of Jamulus is not included in your distribution, you might want to compile Jamulus from source following the compile guide You may also wish to use one of the contributed installation scripts.
Set up your hardware
Configure JACK with QjackCtl
Jamulus clients need JACK to run, but you need to configure that first. The recommended method is to use
- Launch QjackCtl. You will see the Qt JACK Control utility main page
- Configure your audio hardware as follows (the exact settings for JACK will depend on what your audio hardware is capable of):
- Set the audio Interface to the one you want (there may be several in the list)
- Set the Sample Rate to 48000
- Set the Frames/Period to 128 and Periods/Buffer at 2 at first
Restart JACK for the new settings to take effect
With JACK running and configured, launch Jamulus.
If you get problems with sound breaking up (in particular XRUN errors reported by JACK/QjackCtl) try setting bigger values (e.g. 256 frames or 3 periods). Lower ones (e.g. 64 frames) could bring better performance but maybe more sound problems. See the troubleshooting page otherwise.
Take a look at the