PipeWire Crackling Latency Fix: Proven Ubuntu Guide (2026)

Pipewire crackling latency fix is one of the most common audio troubleshooting searches for Linux users. You open a game, start a DAW, or simply play music, and suddenly your audio is filled with pops, crackles, and delays.

When you need a pipewire crackling latency fix, you are dealing with audio buffer underruns or misconfigured sample rates. This comprehensive guide provides proven methods to eliminate audio crackling and reduce high latency on PipeWire.

1. Root Cause

When you search for a pipewire crackling latency fix, the issue typically stems from buffer underruns. The audio buffer (called “quantum” in PipeWire) is too small for your system to fill in time.

PipeWire’s default quantum is often set to 128 or 256 samples. At 48kHz, 128 samples is about 2.7ms of latency. This is great for low latency but can cause crackling if your CPU cannot keep up. The system tries to process audio in real-time, but when it falls behind, the buffer empties, causing a pop or crackle[reference:0][reference:1].

Another major cause is sample rate mismatches. When the system switches between 44.1kHz and 48kHz dynamically, it can cause resampling lag and crackling[reference:2]. The PipeWire official documentation notes that forcing a fixed sample rate can eliminate these issues.

Audio device power management can also cause problems. When the audio device goes to sleep during silence, it creates a pop or crackle when audio starts playing again[reference:3]. Understanding these root causes helps you apply the right pipewire crackling latency fix.

2. Adjust Quantum (Buffer Size) Settings

The most effective pipewire crackling latency fix is adjusting the quantum (buffer size). A larger buffer reduces crackling but increases latency.

# Temporary fix (applies immediately)
pw-metadata -n settings 0 clock.force-quantum 1024

# Permanent fix
mkdir -p ~/.config/pipewire
cp /usr/share/pipewire/pipewire.conf ~/.config/pipewire/
nano ~/.config/pipewire/pipewire.conf

In the configuration file, find the context.properties section and modify these lines:

default.clock.quantum = 1024
default.clock.min-quantum = 1024

Start from 1024 and work your way down. Try values like 512, 256, and 128 until you find the lowest stable setting[reference:4]. The PipeWire GitLab Wiki recommends testing with pw-top to monitor buffer usage.

Outcome: Adjusting quantum resolves the pipewire crackling latency fix issue by preventing buffer underruns.

3. Force a Fixed Sample Rate

Dynamic sample rate switching can cause crackling. Forcing a fixed rate provides a reliable pipewire crackling latency fix.

# Check current sample rate
pw-metadata -n settings 0 clock.rate

# Force 48kHz
pw-metadata -n settings 0 clock.force-rate 48000

# Or force 44.1kHz
pw-metadata -n settings 0 clock.force-rate 44100

To make it permanent, add this to ~/.config/pipewire/pipewire.conf:

default.clock.rate = 48000
default.clock.allowed-rates = [ 48000 ]

According to the PipeWire documentation, setting clock.force-rate to 0 allows the sample rate to vary again[reference:5]. Most audio hardware works well at 48kHz.

Outcome: Forcing a fixed sample rate resolves the pipewire crackling latency fix issue caused by resampling lag.

4. Configure PipeWire-Pulse for Lower Latency

Applications using the PulseAudio compatibility layer may need separate tuning. This is an essential pipewire crackling latency fix for PulseAudio apps.

mkdir -p ~/.config/pipewire
cp /usr/share/pipewire/pipewire-pulse.conf ~/.config/pipewire/
nano ~/.config/pipewire/pipewire-pulse.conf

Find the pulse.properties section and modify these values:

pulse.min.req = 1024/48000
pulse.default.req = 1024/48000
pulse.min.frag = 256/48000
pulse.min.quantum = 256/48000

According to community testing, starting from 128 (default) and finding the closest value to 32 that makes your sound stable is the best approach[reference:6]. The Ubuntu Community Help recommends adjusting these values to match your quantum settings.

Outcome: Configuring pipewire-pulse provides a comprehensive pipewire crackling latency fix for PulseAudio applications.

5. Enable Pro-Audio Profile

The Pro-Audio profile bypasses unnecessary processing for lower latency. This is a powerful pipewire crackling latency fix for professional audio work[reference:7].

# Check available profiles
pactl list cards | grep -A 20 "Profile"

# Set Pro-Audio profile (replace card name)
pactl set-card-profile alsa_card.pci-0000_00_1f.3 pro-audio

To make it permanent, create a WirePlumber configuration file:

mkdir -p ~/.config/wireplumber/wireplumber.conf.d/
nano ~/.config/wireplumber/wireplumber.conf.d/51-set-profile.conf

Add this content:

monitor.alsa.rules = [
  {
    matches = [
      { device.name = "~alsa_card.*" }
    ]
    apply_properties = {
      device.profile = "pro-audio"
    }
  }
]

The Pro-Audio profile exposes all raw hardware channels and bypasses unnecessary processing stages[reference:8].

Outcome: Enabling Pro-Audio profile provides a professional-grade pipewire crackling latency fix.

6. Keep Audio Device Awake

Audio device power management can cause pops and crackles. Keeping the device awake provides a simple pipewire crackling latency fix[reference:9].

# Download and build keep-audio-awake
git clone https://github.com/8bitaustin/Keep-Audio-Awake
cd Keep-Audio-Awake
gcc keep_audio_awake.c -o keep_audio_awake -lpulse-simple -lpulse
./keep_audio_awake

This program plays a continuous stream of silence through PipeWire, keeping the audio device active at all times without making any sound[reference:10]. To auto-start on login, create a systemd user service:

mkdir -p ~/.config/systemd/user
nano ~/.config/systemd/user/keep-audio-awake.service

[Unit]
Description=Keep audio device awake
After=pipewire.service pipewire-pulse.service

[Service]
ExecStart=%h/.local/bin/keep_audio_awake
Restart=on-failure

[Install]
WantedBy=default.target

Outcome: Keeping the audio device awake resolves the pipewire crackling latency fix issue caused by power management.

7. Increase Resample Quality

Higher resample quality can reduce artifacts but uses more CPU. Adjusting it can provide a pipewire crackling latency fix for some users.

mkdir -p ~/.config/pipewire
cp /usr/share/pipewire/pipewire-pulse.conf ~/.config/pipewire/
nano ~/.config/pipewire/pipewire-pulse.conf

Find stream.properties and modify:

resample.quality = 10

The default is 4. Values range from 0 (fastest, lowest quality) to 15 (slowest, highest quality). According to PipeWire documentation, quality 4-5 is sufficient for most users[reference:11].

Outcome: Increasing resample quality provides a pipewire crackling latency fix for audio quality issues.

8. Restart PipeWire Services

A simple service restart can resolve temporary issues. This is a quick pipewire crackling latency fix to try first.

systemctl --user restart pipewire pipewire-pulse wireplumber

If the issue persists, try stopping the socket and restarting:

systemctl --user stop pipewire.socket
systemctl --user restart pipewire pipewire-pulse wireplumber

According to the Ubuntu Community Help, a logout or reboot may be needed if this doesn’t reset the services properly[reference:12].

Outcome: Restarting services resolves the pipewire crackling latency fix issue caused by temporary service failures.

9. Use PIPEWIRE_LATENCY Environment Variable

For specific applications, setting the PIPEWIRE_LATENCY environment variable provides a targeted pipewire crackling latency fix.

PIPEWIRE_LATENCY=1024/48000 steam
PIPEWIRE_LATENCY=2048/48000 firefox

This forces a specific latency for a stream or filter[reference:13]. The value is expressed as quantum/samplerate, e.g., 1024/48000 gives about 21ms of latency. According to the PipeWire man page, this is only a suggestion but the configured latency will not be larger[reference:14].

Outcome: Using PIPEWIRE_LATENCY provides an application-specific pipewire crackling latency fix.

10. Advanced: Tune Real-Time Priorities

For advanced users, tuning real-time priorities provides the ultimate pipewire crackling latency fix[reference:15].

# Check current RT limits
ulimit -a | grep real-time

# Add user to audio group
sudo usermod -a -G audio $USER

# Create limits configuration
sudo nano /etc/security/limits.d/audio.conf

Add these lines:

@audio - rtprio 95
@audio - memlock unlimited

Reboot for changes to take effect. According to the PipeWire official documentation, real-time scheduling is essential for low-latency audio processing. The rt.prio setting in PipeWire can be adjusted for higher priority[reference:16].

Outcome: Tuning real-time priorities provides a professional-grade pipewire crackling latency fix for demanding audio work.

11. Frequently Asked Questions

What causes PipeWire audio crackling?

Audio crackling is caused by buffer underruns when the system cannot fill the audio buffer in time. This is often due to small quantum settings, sample rate mismatches, or CPU load.

How do I fix crackling in PipeWire?

Increase the quantum (buffer size) with pw-metadata -n settings 0 clock.force-quantum 1024, or permanently set default.clock.quantum = 1024 in ~/.config/pipewire/pipewire.conf.

What is quantum in PipeWire?

Quantum is the buffer size in samples. Smaller quantum = lower latency but higher risk of crackling. Default is usually 128 or 256 samples.

Does PipeWire have high latency by default?

PipeWire’s default latency is low (around 2.7ms at 128 samples). However, some configurations may have higher latency, and you can adjust it with quantum settings.

How do I change sample rate in PipeWire?

Use pw-metadata -n settings 0 clock.force-rate 48000 to force a fixed sample rate. Set default.clock.rate in pipewire.conf for permanent changes.

What is the Pro-Audio profile in PipeWire?

The Pro-Audio profile bypasses unnecessary processing and exposes all raw hardware channels. It is designed for low-latency, high-performance audio.

Can I use JACK applications with PipeWire?

Yes, PipeWire provides JACK compatibility through pipewire-jack. You can run JACK applications without a separate JACK server.

How do I check PipeWire buffer usage?

Use pw-top to monitor buffer usage and see if your system is experiencing underruns.

Does PipeWire use more CPU than PulseAudio?

PipeWire can use more CPU at low latency settings. Adjusting quantum and resample quality can help balance performance.

What should I do if none of these methods work?

Check your system’s real-time scheduling limits, consider using a low-latency kernel, or file a bug report on the PipeWire GitLab with detailed logs from pw-top and journalctl.

12. Conclusion

The pipewire crackling latency fix is achievable with the right configuration. From adjusting quantum to enabling the Pro-Audio profile, this guide covers all effective methods. Start with the simplest solution — increasing the quantum with pw-metadata — and escalate only if necessary. For more information, visit the PipeWire official documentation, the PipeWire GitLab Wiki, or the Ubuntu Community Help. With this proven guide, you can overcome the pipewire crackling latency fix challenge and enjoy clear, low-latency audio.

For more Linux troubleshooting, explore our Linux Hub and guides on Linux sound not working fix, Ubuntu broken packages fix, and Ubuntu failed to fetch apt update fix. With the right approach, you can resolve the pipewire crackling latency fix issue and keep your audio system running optimally.