Complete First-Time Setup Guide for Qtractor on Ubuntu 26.04

1. install and prepare the system
2. verify audio works
3. configure PipeWire/JACK
4. configure Qtractor
5. record audio
6. record while playing other tracks
7. export projects
8. tune latency
9. troubleshoot problems

Qtractor is a lightweight Linux DAW (Digital Audio Workstation) for audio and MIDI recording, a hard disk recorder and digital audio workstation application for Linux. If you appreciate highly stable, ultra-lightweight, and low-overhead tools, Qtractor is exceptional. Its developer (Rui Nuno Capela) is incredibly active, having just pushed version 1.6.0 33 days ago as of this writing.

It's setup might be challenging. On Ubuntu, most problems come from:

• JACK / PipeWire / ALSA conflicts
• Permissions
• Wrong audio device selection
• Monitoring setup
• Sample-rate mismatches
• USB devices reconnecting
• Tracks not armed correctly

This guide walks through a strategic / systematic / stable setup from zero, and covers the common failure cases along the way.

PART 1 QUICK START SETUP

1. Understanding the Linux Audio Stack

Modern Ubuntu audio typically works like this:

Applications
 ↓
PipeWire
 ↓
JACK compatibility layer
 ↓
ALSA drivers
 ↓
Audio hardware

For Qtractor, the recommended setup is:

• PipeWire enabled
• JACK compatibility enabled
• Qtractor using JACK mode through PipeWire

2. Install the Required Packages

Install everything needed:

sudo apt update

sudo apt install \
qtractor \
pipewire \
pipewire-audio \
pipewire-pulse \
pipewire-jack \
wireplumber \
qpwgraph \
alsa-utils \
qjackctl \
ffmpeg

Useful tools:

helvum and pavucontrol are listed as reference but not in the installation list, as many experienced Linux audio users eventually stop opening Helvum entirely and do everything through qpwgraph -- In daily use:

• Use qpwgraph as your primary routing tool.
• Use Helvum only if you prefer its simpler visual layout or want a quick sanity check of the PipeWire graph.

For pavucontrol, I'm using KUbuntu so I installed pavucontrol-qt instead.

3. Reboot

After installation:

reboot

This ensures all audio services start cleanly.

4. Verify the Audio System Is Running

Check PipeWire:

systemctl --user status pipewire

Check WirePlumber:

systemctl --user status wireplumber

Check Pulse compatibility:

systemctl --user status pipewire-pulse

You should see:

active (running)

5. Verify Audio Devices Exist

Check Playback Devices

aplay -l

Check Recording Devices

arecord -l

Check PipeWire Audio Nodes

wpctl status

You should see sections like:

Audio
 Devices
 Sinks
 Sources

Typical onboard audio may appear as:

Built-in Audio Analog Stereo

6. Verify Sound Playback Works

Test speaker output:

speaker-test -c 2

You should hear alternating left/right sound.

Press:

Ctrl+C

to stop.

7. Verify Microphone Input Works

Open the ALSA mixer:

alsamixer

Press:

F6

Select your sound card.

Verify:

• capture channels are enabled
• input volume is reasonable
• channels are not muted

Muted channels show:

MM

Enabled channels show:

OO

Toggle mute with:

M

Make sure microphone input works by doing a test recording:

pw-record /tmp/test-rec.wav
pw-play /tmp/test-rec.wav

8. Verify PipeWire Audio Routing

Launch:

qpwgraph &

You should see:

• audio devices
• playback nodes
• capture nodes
• PipeWire graph connections

This tool becomes extremely important later.

9. Launch Qtractor Properly

Recommended launch method:

pw-jack qtractor &

This ensures Qtractor uses PipeWire s JACK compatibility layer correctly.

10. Configure Qtractor Audio Settings

Inside Qtractor:

View → Options → Audio

Recommended settings:

Setting	Value
Driver	JACK
Sample Rate	48000
Buffer Size	256 or 512
Channels	Stereo

Restart Qtractor after changes.

Didn't find the above part. The workaround is to use pw-top to verify what PipeWire is actually using:

Start pw-top

👁

Then look for:

QUANT RATE

Example:

QUANT 1024
RATE 48000

Meaning:

Buffer Size = 1024
Sample Rate = 48000 Hz

11. Verify Qtractor Audio Engine

When Qtractor opens:

Verifying Qtractor Started Correctly

When Qtractor opens successfully, three things should be true:

1. no engine errors appear
2. transport controls are active
3. audio meters function correctly

The last two are important because Qtractor can sometimes open partially working even when the audio engine is not fully operational.

If the engine fails to start, or partially working, see troubleshooting later.

11.1 Verify Transport Controls Are Active

The transport controls are the playback/record controls usually located near the top toolbar.

Typical controls include:

What Active Means

When the audio engine is working correctly:

• buttons respond immediately
• Play starts timeline movement
• Stop halts playback
• Record engages recording mode
• time counter advances during playback
• playhead moves smoothly across timeline

Visual Indicators of a Working Transport

Timeline Movement

Press:

Play

Expected result:

• playhead moves left-to-right
• timeline counter advances continuously
• transport clock changes in real time

Example:

00:00:01
00:00:02
00:00:03

If the counter stays frozen:

• audio engine likely failed
• JACK connection may be broken
• transport backend may not be running

Play Button State

When playback begins:

• Play button usually highlights or changes state
• Stop becomes available
• CPU/audio indicators may activate

If Play immediately returns to idle:

• engine likely stopped internally
• invalid routing or backend failure possible

Record Button Behavior

When Record is enabled:

• global Record button lights up
• armed tracks indicate recording readiness
• pressing Play starts actual recording

If Record cannot be enabled:

• transport engine may not exist
• audio backend failed initialization

What Broken Transport Looks Like

Common symptoms:

Verify JACK Transport Exists

Open:

qpwgraph

You should see Qtractor nodes such as:

qtractor

or:

qtractor-master

If Qtractor does not appear at all:

• JACK compatibility failed
• Qtractor engine not started

Verify Engine Messages

Inside Qtractor:

View → Messages

A healthy startup usually shows messages similar to:

JACK started
Audio activated
MIDI activated

Didn't see that, but on openning new files, saw:

Session closed.
Session started.
New session: "Untitled1".
MIDI connections change.
Audio connections change.

Problematic examples:

Cannot connect to JACK server

or:

Audio device not available

11.2 Verify Audio Meters Function Correctly

Meters confirm that audio signals are actually flowing.

Even when transport works, meters may reveal:

• missing routing
• silent inputs
• muted tracks
• disconnected outputs
• inactive monitoring

Types of Meters in Qtractor

You may see:

Verify Playback Meters

Import or record a short audio clip.

Press:

Play

Expected behavior:

• track meters move dynamically
• master output meters move
• audio is heard from speakers/headphones

What Healthy Meter Movement Looks Like

Meters should:

• rise and fall continuously
• react to loud/quiet audio
• peak near louder sounds
• return downward smoothly

Example:

Verify Recording/Input Meters

Arm an audio track.

Speak into microphone.

Expected behavior:

• armed track input meter reacts immediately
• louder speech produces higher levels
• silence returns meter near zero

If Input Meter Moves But Nothing Records

Possible causes:

• global Record not enabled
• playback never started
• recording path invalid
• disk write permissions issue

If Playback Meter Moves But No Sound Is Heard

Possible causes:

• output routing broken
• wrong playback device
• muted system output
• disconnected PipeWire graph

Check:

qpwgraph

Verify:

Qtractor Output

System Playback

If No Meters Move At All

Most likely causes:

Proper Recording Levels

Avoid recording too quietly or too loudly.

Recommended Recording Peaks

Typical safe peak range:

-18 dB to -6 dB

Avoid constant clipping near:

0 dB

Clipping Indicators

Red meter peaks indicate clipping/distortion.

If clipping occurs:

• reduce microphone gain
• reduce interface input gain
• lower ALSA capture level

Verifying Meter Activity Outside Qtractor

If uncertain whether Qtractor or the system is failing:

Run:

pw-top

Speak into microphone.

You should see activity changes for:

• input nodes
• Qtractor nodes
• output nodes

This confirms PipeWire signal flow exists.

Final Healthy-State Checklist

A fully working Qtractor session should have ALL of these:

If all are true, the audio engine, routing, recording, and playback systems are functioning correctly.

👁

(Image not reflecting the actual Qtractor GUI)

PART 2 FIRST RECORDING

12. Create a New Session

Inside Qtractor:

File New

Create a dedicated project folder.

Recommended structure:

Projects/
 Song/
 audio/
 exports/
 backups/

13. Add an Audio Track

Track Add Track

Choose:

Mono is usually correct for microphones.

14. Arm the Track for Recording

Click the track s red record-arm button.

The track is now ready to record.

15. Enable Main Recording

Press the global Record button in the toolbar.

16. Start Recording

Press:

• Play
• or Spacebar

Recording begins.

Waveforms should appear.

17. Verify Recorded Audio Works

Stop recording.

Rewind.

Press Play.

Verify:

• waveform exists
• audio is audible
• meters move during playback

If not, see troubleshooting later.

PART 3 UNDERSTANDING ROUTING

18. Linux Audio Routing Basics

Signals travel like this:

Microphone

PipeWire Input Node

Qtractor Input

Track

Master Output

Speakers

If any connection is missing:

• no sound
• silent recording
• missing monitoring
• playback problems

19. Verify Input Connections

Open:

qpwgraph

Verify:

Audio Input Device

Qtractor Capture Input

Example:

alsa_input

qtractor:input_1

20. Verify Playback Connections

Verify:

Qtractor Master Output

System Output

Example:

qtractor:output_1

alsa_output

PART 4 MONITORING

21. Monitoring While Recording

Monitoring means hearing yourself while recording.

Two methods exist.

Software Monitoring

Handled by Qtractor.

Pros:

• hear effects/plugins live

Cons:

• more latency

Enable monitoring in track settings.

Hardware Monitoring

Handled directly by audio interface hardware.

Pros:

• near-zero latency

Cons:

• no software effects while recording

22. Verify Monitoring Works

Arm track.

Speak into microphone.

Verify:

• Qtractor meters move
• audio is heard in headphones/speakers

If meters move but nothing is heard:

• monitoring disabled
• routing incorrect
• output muted

PART 5 MULTITRACK RECORDING

23. Recording While Playing Existing Tracks

Typical workflow:

• existing music plays
• new track records simultaneously

24. Procedure

Existing Tracks

Leave unarmed.

New Track

Arm only the new recording track.

Start Recording

Press:

Record + Play

Now:

• old tracks play normally
• new audio records simultaneously

25. Verify Synchronization

After recording:

• rewind
• play all tracks together

Verify timing alignment.

PART 6 IMPORTING AND EXPORTING

26. Import Audio Files

Drag and Drop

Drag WAV/FLAC into timeline.

Manual Import

Right-click Track Import Audio

27. Export Final Audio

File Export Audio

Recommended settings:

28. Convert WAV to MP3

ffmpeg -i mix.wav mix.mp3

PART 7 MIDI RECORDING

29. Verify MIDI Devices

aconnect -i

You should see connected MIDI devices.

30. Add MIDI Track

Track Add Track MIDI

31. Verify MIDI Routing

In:

qpwgraph

Verify:

MIDI Keyboard

Qtractor MIDI Input

PART 8 LATENCY AND PERFORMANCE

32. Buffer Size Recommendations

33. Verify Current Audio Performance

Run:

pw-top

Important fields:

34. Avoid XRUNS and Crackling

If audio crackles:

• increase buffer size
• close heavy applications
• avoid Bluetooth audio
• use wired headphones
• avoid USB hubs

PART 9 TROUBLESHOOTING

Organized from most common to least common.

35. Qtractor Audio Engine Will Not Start

Symptoms

• engine start error
• transport disabled
• playback unavailable

Solution 1 Launch with PipeWire JACK

pw-jack qtractor

Solution 2 Kill Old JACK Servers

killall jackd

Restart PipeWire:

systemctl --user restart pipewire
systemctl --user restart wireplumber

Solution 3 Verify JACK Driver Setting

Inside Qtractor:

View Options Audio

Set:

Driver = JACK

36. No Sound During Playback

Verify Output Routing

Open:

qpwgraph

Verify:

Qtractor Outputs

System Playback

Verify Output Device

Open:

pavucontrol

Verify correct output device selected.

Verify System Audio

Run:

speaker-test -c 2

37. Recording Is Silent

Verify Input Routing

In:

qpwgraph

Verify:

Input Device

Qtractor Capture

Verify Input Gain

Run:

alsamixer

Increase capture gain.

Verify Input Device

Open:

pavucontrol

Check:

Input Devices

Verify Signal Activity

Run:

pw-top

Speak into microphone and watch activity.

38. Monitoring Does Not Work

Verify Monitoring Enabled

Enable monitoring on the track.

Verify Output Routing

Check in:

qpwgraph

Avoid Double Monitoring

Disable either:

• hardware monitoring
• software monitoring

not both simultaneously.

39. Built-in Audio Analog Stereo Missing

Verify ALSA Detects Hardware

aplay -l

and:

arecord -l

Restart PipeWire Stack

systemctl --user restart pipewire
systemctl --user restart wireplumber
systemctl --user restart pipewire-pulse

Then verify:

wpctl status

Verify Audio Profiles

Open:

pavucontrol

Go to:

Configuration

Set profile to:

Analog Stereo Duplex

Reload ALSA

sudo alsa force-reload

Restart PipeWire afterward.

Verify Kernel Detection

dmesg | grep -i audio

and:

lspci | grep -i audio

40. Audio Device Disappears Randomly

Disable Audio Power Saving

Create:

sudo nano /etc/modprobe.d/disable-audio-powersave.conf

Add:

options snd_hda_intel power_save=0
options snd_usb_audio power_save=0

Reboot.

Avoid USB Hubs

Connect interfaces directly to motherboard ports.

Check Kernel Logs

dmesg | tail -50

Look for:

• USB resets
• disconnects
• power faults

41. Crackling, Pops, Distortion

Increase Buffer Size

Inside Qtractor:

View Options Audio

Try:

512

or:

1024

Verify CPU Load

pw-top

42. HDMI Audio Takes Over

Open:

pavucontrol

Select correct analog output manually.

43. Broken Audio Graph Connections

Restart WirePlumber:

systemctl --user restart wireplumber

Reopen:

qpwgraph

Reconnect missing nodes.

44. Complete Diagnostic Sequence

When audio problems happen, check in this order:

wpctl status

qpwgraph

pw-top

alsamixer

pavucontrol

Those tools diagnose most Linux audio problems quickly.

👁