Linux audio

Making sound by banging rocks together 44 thousand times per second

Professional audio IO on linux: possible, but not fun.

General setup

The low latency kernel is usually recommended for audio.

apt install linux-lowlatency

However, try without. I found that with my system, the linux-lowlatency setup led to frequent problems; The razer blade laptop would frequently reboot upon waking from sleep. There is some vague mentions on the internet about how this is maybe to do with interaction with the NVIDIA GPU drivers, and other miscellaneous speculation, but nothing that seems so certain or updated that I will bother linking to it here. Further, as an intermittent problem, it will take longer to debug than I have in my life to make music.

Using Windows VSTs on Linux

As distinct from running Linux VSTs on Linux, which is now a thing apparently? Not, AFAIK, a common thing.

Apparently, it is sometimes possible if painful to run Windows VSTs on linux. Not, crucially, for Native Instruments whose Kontakt is my favourite sampler, but for others.

LinVst and vst-bridge seem to be actively supported methods. (Of historical note, the dead projects vstserver and dssi-vst.)

Ontology of Linux sound systems

🏗 Include the different standards, sub-standards, compatibility layers, compatibiility layers standards, legacy and surly coexistence APIs.

See the lengthy techradar intro or the optimisic ubuntu studio intro. The practical renoise intro gets you there

What I took from this is that there are a lot of standards that interact in complicated ways, but only some them matter, probably.

Pulseaudio is the amateur version in that it is universally supported everything works without you thinking about it (and crucially, everything works at once, so you can play audio through your DAW and also preview samples in you sample previewer without quitting one or the othere), but it doesn’t necessarily work well. Failure modes, notably being sloooooow, glitching, not supporting fancy routing.

Jack is the “pro” version that supports realtime operation and such. Jack is itself a rather complicated nest of standards, but it seems you can ignore a lot of the weirdness and just choose the default implementations of all the internal bits and everything works ok. Bitwig for example, works beautifully on jack but is prone to glitches in pulseaudio mode.

There is also ALSA a backend driver layer that some pro-audio apps use to directly talk to you soundcard. (and also Jack and Pulseaudio can use?) Where you use it directly it will lock the rest of the system out of access to the soundcard, but the app that ha stolen ALSO will work beautifully without configuration.

As far as I can tell, if you do several different things with your computer the aspirationally working setup is jack with a pulseaudio front-end and an ALSA back-end. However the system defaults are typically far from this.


Cadence reputedly eases much pain in managing the jack infrastructure, and is recommended by Bitwig users.

JackAss routes midi from jack-blind hosts:

JackAss is a VST plugin that provides JACK-MIDI support for VST hosts. Simply load the plugin in your favourite host to get a JACK-MIDI port. Each new plugin instance creates a new MIDI port.

Virtual ports for bidirectional patching

  • How do I refer to a soundcard so that the name always works?.

  • Difference between qjackctl and patchbay.

  • Beginner’s guide to jack via a DAW (Ardour)

  • internal routing with JACK explains why you can’t make it do what you expect with routing sub-buses to different apps — you need lotsa virtual channels:

    With a basic implementation of JACK now set up, we can begin to tweak JACK to our needs—internal routing. For those of you with larger 8-channel interfaces, you probably have noticed a slight problem with JACK: you do not have all eight microphone inputs available anymore! This is because we need to tell JACK how many inputs we want (both in and out).

    For OS X users, simply adjust the Virtual I/O settings under Preferences until your hearts content and you should be good to go. For Linux and PC users however, things are not so easy. While the Channel I/O option sounds like a perfect match, it really does nothing most of the time. Instead we need to edit an .INI file.

    • Close down JACK, as well as any connected apps.
    • Go to where you installed JACK (most likely C:Files(x86)).
    • In the 32 or 64 bit folder (depending on what version you are using) there is a file called JackRouter.ini
    • Open JackRouter.ini with Notepad, and change the input and output values to however many channels you want. Presto!
    • Restart Jack Control, enter your DAW, and you should now have a multitude of inputs and outputs at your disposal.

    perhaps this is /etc/jackdrc and ~/.jackdrc on Ubuntu?

  • Ubuntu recommends using a GUI for config then persisting to disk.

  • How to add extra sound cards to your jack setup



The advice seems to be basically: don’t touch the configuration if you possibly. The defaults work. That’s the whole point. However, I have had limited success with that approach.

Manuel Amador Briz CC BY-SA 3.0:

Pulseaudio muntology

Jack + PulseAudio

Jackd statement.

While PulseAudio is running, JACK cannot access the same soundcard that Pulse is using. Even though in theory ALSA provides mechanisms for this to be possible (e.g. “dmix” device access), they do not work well enough to support both of these systems reliably.

What worked for me is the recent qjackctl method:

apt install qjackctl pulseaudio-module-jack

Then configure qjackctl to run the following command after startup. > Copy it into "Setup…" > "Options" > "Execute script after Startup":

pactl set-default-sink jack_out

This seems to work. (reboot is required to get the modules working correctly.)

Background: this is the apotheosis of option 3 of the many types of interaction between pulse audio and jack.

You can also use the KXStudio method, which I have not tried:

Install Cadence from the KXStudio repositories. From within Cadence you can enable the ALSA and PulseAudio bridges with the GUI. Done.

Of course, for this you need to install the KXStudio repositories.

A comprehensive walkthrough of the potentials and pitfalls of this method is the asbak’s run-through.

The Bitwig way: jack and maybe ALSA

Here is a recommended setup for

sudo apt-get install alsa-tools alsa-tools-gui alsamixergui patchage jackd2 \
  jackd2-firewire qjackctl a2jmidid gmidimonitor

See also Linux realtime audio config.


I wonder if this minimalist audio OS makes life better

No comments yet. Why not leave one?

GitHub-flavored Markdown & a sane subset of HTML is supported.