Linux Audio Developers (LAD) Mailing List

The Linux Audio Developers mailing list, known as LAD, is the technical discussion channel for the people who build the Linux audio stack. It is where kernel subsystem patches get reviewed, sound server architectures get debated, plugin API standards get proposed, and the hard engineering problems of real-time audio on a general-purpose operating system get worked through in public. If you write code that touches ALSA, JACK, PipeWire, LV2, LADSPA, or any of the infrastructure that Linux audio depends on, LAD is the list where that work is coordinated and discussed. Below I cover what the list actually addresses, who should subscribe, what belongs on LAD versus other lists, the posting conventions that make technical threads productive, and how LAD relates to the user and announce lists in the broader community. For the full picture, see the LAD community hub.

What LAD Covers

LAD is a developer list in the truest sense. The discussions that define it are about implementation: how code works, how it should work, why it does not work in specific situations, and what changes are needed to fix or improve it. Topics span the full depth of the Linux audio stack.

At the kernel level, LAD carries discussion about ALSA driver development, interrupt handling strategies for audio hardware, timer precision, scheduling latency under different kernel configurations, and the ongoing integration of real-time capabilities into mainline kernels. The PREEMPT_RT patch set, its interaction with audio workloads, and the long effort to merge its components upstream have been recurring LAD topics for years.

At the sound server level, LAD is where JACK's routing model, transport synchronization, and session management were designed and refined through public discussion. PipeWire's development brought a new generation of architectural discussions to the list, covering its compatibility layers, its graph-based processing model, and its approach to replacing both PulseAudio and JACK without breaking existing workflows.

At the plugin and application level, LAD covers API design for plugin standards like LV2, the evolution of LADSPA, the GUI hosting challenges that plugin developers face, and the interoperability problems that arise when different applications make different assumptions about the underlying audio infrastructure.

The common thread is that LAD discussion is about building and maintaining the infrastructure. Configuration questions, user workflow discussions, and application-level help belong on the Linux Audio Users list.

Who Should Subscribe to LAD

The primary audience is developers who are actively writing or maintaining code in the Linux audio stack. If you are contributing patches to ALSA, maintaining a JACK client library, developing a PipeWire module, writing LV2 plugins, or working on audio application code that interacts directly with the Linux audio APIs, LAD is your primary community channel.

LAD is also valuable for developers who are not yet contributing but plan to. Reading the list gives you a deep understanding of how the stack works, what design decisions were made and why, where the current pain points are, and what the community considers important. That context is difficult to obtain from documentation alone, because documentation captures what was decided but rarely captures the alternatives that were considered and rejected.

Power users who want to understand the technical evolution of the tools they depend on also benefit from following LAD. You do not need to write code to find value in understanding what is being built and why. If you manage audio infrastructure for a studio, a broadcast facility, or a venue running Linux, knowing what changes are coming and what problems are being addressed helps you plan and make informed decisions about upgrades.

If you are primarily looking for help using Linux audio tools rather than building them, the user list is a better starting point. You can always add LAD later as your involvement deepens.

What Belongs on LAD

A message belongs on LAD if it involves code, architecture, API design, or system-level behavior that requires developer-level understanding to discuss productively. Specific examples include: patch submissions and code review discussion, design proposals for new features or API changes, bug reports that include analysis at the code level, performance investigation that involves profiling, tracing, or kernel behavior, compatibility discussions between different audio subsystems, and technical post-mortems of problems that reveal stack-level issues.

The quality of LAD discussion depends on participants including substance in their messages. A patch should come with a description of the problem it solves, the approach taken, and any trade-offs involved. A design proposal should include enough context for reviewers to understand the constraints. A bug report should include reproduction steps, diagnostic output, and any analysis you have already done.

What Does Not Belong on LAD

User-level questions about configuration, application settings, hardware compatibility, and workflow do not belong on LAD. These are legitimate questions, but they belong on the user list where the community is organized to answer them. Posting a user question on LAD typically results in either silence or a polite redirect, neither of which helps you get an answer quickly.

Release announcements and event notices belong on the announce list. LAD is for discussion, not broadcast. If you have released a new version of your software, post the announcement to the announce list. If you want to discuss the technical changes in that release, a separate thread on LAD is appropriate.

General Linux questions that are not specific to audio infrastructure also do not belong on LAD. Even if your question is technical, if it is about general kernel configuration, network setup, or desktop environment issues that are not directly related to audio subsystems, a general Linux support channel will serve you better.

How LAD Connects to Other Lists

LAD is one of three coordinated mailing lists that serve the Linux audio community. The subscription overview covers all three and helps you choose the right combination for your needs.

In practice, many LAD subscribers also follow the user list and the announce list. Bugs discovered through user reports on the user list often spawn developer threads on LAD. Releases announced on the announce list generate technical discussion on LAD about the implementation details. The three lists function as a system, with different types of discussion flowing to the appropriate venue.

The user list is the natural complement to LAD. Developers who follow both lists understand both the implementation perspective and the user experience perspective, which produces better software. If you only follow one list, you get half the picture. Following both gives you the complete view of how Linux audio tools are built and how they are used, which makes you a more effective contributor regardless of which side you primarily work on.