Linux Audio Resource Links

After years of working with Linux audio professionally, the single biggest frustration I see from newcomers is not a lack of information. It is too much information scattered across too many places, with no clear indication of what is current, what is obsolete, and what actually applies to their specific problem. This directory exists to solve that. It is a curated collection of internal links into the reference material organized through the LAD community hub, structured by topic so you can find what you need without guessing which page to start on. Below I cover links for latency and performance tuning, API and developer resources, audio quality references, benchmarking and measurement tools, and community and event listings. Each section explains what the linked resource covers and who it is most useful for, so you spend your time reading relevant material rather than scanning through pages that do not match your current need.

Latency and Performance Resources

Latency is the topic that brings most people to Linux audio resources in the first place. Whether you are tracking live instruments, running software synthesizers in real time, or trying to get monitoring delay low enough to be imperceptible, the latency resources page is where you should start. It covers PREEMPT_RT kernel configuration, scheduler behavior under audio workloads, IRQ handling and CPU affinity, buffer sizing strategies, and the practical limits of how low you can go before stability degrades.

What makes the latency reference particularly useful is that it does not just describe settings. It explains the reasoning behind them. Understanding why a 64-sample buffer at 48 kHz imposes a 1.3 ms deadline on every callback in the chain is more valuable than knowing which number to type into a configuration file. When you understand the constraint, you can diagnose problems that no configuration guide anticipated.

The latency material connects directly to the measurement tools available on this site. If you are seeing XRUNs or inconsistent timing, the benchmarking resources covered below give you the diagnostic workflow to identify the bottleneck rather than guessing at configuration changes.

API and Developer References

If you write audio software for Linux, or maintain plugins, drivers, or system integration code, the API resources page is the developer-facing counterpart to the latency guide. It covers the ALSA kernel and userspace APIs, including the practical differences between mmap and read/write access modes that determine how your application interacts with hardware buffers. It walks through JACK's routing model, process callback rules, and transport synchronization. It covers PipeWire's native API, its JACK and PulseAudio compatibility layers, and the session management patterns that determine whether your application plays well with others.

The API reference is written for working developers, not for people reading about audio programming abstractly. The examples reflect real integration patterns that ship in production code, and the explanations focus on the decisions you actually face: when to use blocking versus non-blocking I/O, how to handle sample rate changes without crashing, why your plugin host and your JACK client disagree about buffer size, and what happens at the kernel boundary when your userspace code misses a deadline.

Developers working on performance-sensitive code should cross-reference the API page with the latency resources. The two are complementary: the API page tells you how to talk to the audio stack, and the latency page tells you what the stack demands in return.

Audio Quality and Standards

Audio quality on Linux is a broader topic than most people realize. It is not just about bit depth and sample rate. It encompasses the entire signal path from capture through processing to output, including where format conversions happen, how dithering is applied, what resampling algorithms are used when sample rates do not match, and where quantization artifacts can creep in if the pipeline is not configured correctly.

The audio quality guide covers these topics in depth. It is written for people who care about measurable signal integrity, not for people chasing subjective impressions. If you are working in mastering, forensic audio, scientific measurement, or any domain where signal accuracy matters, the quality guide explains what Linux gets right, where the common pitfalls are, and how to verify your signal path with objective measurements rather than listening tests alone.

The quality material overlaps with both the latency and API resources in specific areas. Buffer underruns affect signal quality directly. API choices determine where format conversions happen in the pipeline. Reading all three in combination gives you the complete picture of how audio moves through a Linux system and where things can go wrong.

Benchmarking and Measurement Tools

Opinions about audio performance are easy to form and hard to verify. The benchmarks section provides the tools and methodology to replace opinions with measurements. It covers how to generate reproducible test loads, how to capture timing data that reveals actual system behavior, and how to interpret the results in a way that maps to real-world audio workloads.

Benchmarking is not just for power users. If you are evaluating hardware for an audio workstation, comparing kernel configurations, or trying to determine whether a distribution's default settings are adequate for your needs, the benchmarking tools give you objective data. The difference between a system that works and a system that almost works is often invisible until you measure it, and the benchmarks section gives you the methodology to do that reliably.

Community and Event Resources

Linux audio has always been community-driven, and the community's institutional knowledge lives in the discussions, presentations, and collaborative work that happened at specific moments in time. The events section documents the gatherings, conferences, and sprints where significant technical decisions were made, where new projects were announced, and where the people behind the code met face to face to work through problems that mailing list threads could not resolve.

The event listings are not just historical records. They are context for understanding why the Linux audio stack looks the way it does today. Design decisions that seem arbitrary often make sense when you know they were the result of a room full of developers working through competing constraints at a specific event. If you want to understand the rationale behind architectural choices in JACK, ALSA, or the early PipeWire discussions, the event context often provides answers that code comments and commit messages do not.

How to Use This Directory

If you are a musician or producer setting up a Linux audio workstation, start with the latency resources and the audio quality guide. These two pages cover the practical knowledge you need to get a reliable, good-sounding setup running.

If you are a developer building audio software, start with the API resources and cross-reference with the latency material as needed. The benchmarks section will help you validate your work under realistic conditions.

If you are new to the Linux audio community entirely, the LAD hub provides the broader context for how these resources fit together, and the event listings help you understand the community's history and trajectory. Every link in this directory leads to substantial reference material, not thin overview pages. Pick the topic that matches your current problem and follow it through.