Linux Audio Users (LAU) Mailing List
The Linux Audio Users mailing list, commonly known as LAU, is the community discussion channel for people who do real work with audio on Linux. It is not a developer list and it is not an announcement feed. It is the place where recording engineers, live performers, podcasters, sound designers, and system integrators ask questions, share solutions, and discuss the practical realities of using Linux as a professional audio platform. If you have ever struggled with JACK configuration, wondered why your USB interface drops frames after twenty minutes, or needed advice on which distribution handles real-time audio best, LAU is where those conversations happen. Below I cover who LAU is for, what kinds of discussion the list carries, the etiquette conventions that will get your messages read and answered, what to do before posting your first message, and how LAU connects to the other Linux audio lists. For the full picture of the community, see the LAD community hub.
Who LAU Is For
LAU serves anyone who uses Linux for audio work and needs a community to interact with about that work. The definition of "audio work" is broad. It includes music production, live sound, podcast recording, field recording, sound design for games or film, scientific audio measurement, and any other application where you need sound to work reliably on a Linux system.
You do not need to be an expert to participate. LAU explicitly welcomes questions from people who are just getting started. The list has long-time contributors who have been running Linux audio professionally for over a decade, and their willingness to help newcomers is one of the reasons the community continues to grow. What the list does expect is that you make a reasonable effort before asking. Check the FAQ first. Search the archives. Include relevant details in your question. These are not gatekeeping requirements. They are practical conventions that make the list work efficiently for everyone.
LAU is not the right venue for developer-level questions about kernel code, driver internals, or audio API implementation details. Those belong on the developer list. If you are not sure whether your question is a user question or a developer question, default to LAU. If it turns out to be a deeper technical issue, someone will suggest moving the discussion.
What Gets Discussed on LAU
The range of topics on LAU reflects the range of things people actually do with Linux audio. Typical threads include hardware compatibility reports for specific audio interfaces, JACK and PipeWire configuration for particular workloads, latency troubleshooting, application-specific questions about DAWs like Ardour, REAPER, Qtractor, and Bitwig, plugin hosting and compatibility across different formats, distribution comparisons for audio work, monitoring setup and routing, MIDI configuration, and workflow discussions about how people actually use their systems in production.
Some of the most valuable threads are the ones where someone describes their entire setup and workflow. These posts give other users concrete reference points for what a working Linux audio system looks like in practice. They also frequently surface configuration details or tricks that people have been using for years without ever documenting publicly.
Troubleshooting threads are the backbone of the list. The accumulated archive of solved problems is one of the most valuable resources in the Linux audio ecosystem. When you solve a problem with help from the list, consider posting a follow-up summary of the solution. That summary becomes findable in the archives and helps the next person who encounters the same issue.
Etiquette and Message Format
LAU follows standard mailing list conventions that have been established over decades of technical email communication. These are not arbitrary rules. They are patterns that make asynchronous, text-based discussion work well across large groups of people. The foundational reference for email message formatting is RFC 2822, which defines the Internet message format that mailing lists depend on.
Send messages in plain text. HTML email is unreliable across different mail clients, clutters archives, and is often filtered more aggressively by spam detection. Your message should be readable as raw text with no formatting dependencies.
Use inline replying. When responding to a message, quote the specific passage you are addressing and write your response below it. This creates a readable conversation structure that makes sense in the archives, where people may read the thread months or years later. Top-posting, where you write your entire response above the quoted message, loses the connection between specific points and specific responses.
Write descriptive subject lines. "Need help" is not useful. "USB audio dropouts on PipeWire 0.3.65 with Focusrite Scarlett 2i2" is useful. The subject line is the first filter that determines whether someone with relevant knowledge opens your message or skips it.
Do not cross-post the same message to multiple Linux audio lists. If you subscribe to both LAU and the developer list, choose the appropriate one for your topic. Cross-posting fragments the discussion and irritates people who subscribe to both.
Before You Post
Subscribe to the list through the subscription page and spend some time reading before your first post. A week of reading gives you a feel for the list's culture, the level of detail people expect, and the topics that are currently active. You will also see how experienced contributors handle questions and discussions, which gives you a model for your own participation.
Search the archives before posting a question. Your problem has almost certainly been discussed before. If you find a relevant thread but it does not fully answer your question, reference it in your message. This shows that you have done the groundwork and helps responders understand what you already know.
When you do post, include your system details: distribution, kernel version, sound server and version, audio interface, connection type, and the exact symptom or question. The more specific your message, the faster and more accurate the response. A detailed first message often gets a working solution in a single reply. A vague first message starts a multi-day back-and-forth of clarifying questions before anyone can help.
How LAU Connects to Other Lists
LAU is one of three principal Linux audio mailing lists. The developer list carries technical discussion about code, APIs, kernel subsystems, and architectural decisions. The announce list carries release notices, event announcements, and project updates. LAU sits between them as the community discussion space for people who use the tools that the developers build.
Many of the active LAU contributors also follow the developer list and the announce list. When a new release is announced on the announce list, the practical questions about how it affects real-world setups show up on LAU. When a bug report on LAU reveals a code-level issue, the investigation continues on the developer list. The three lists are designed to work as a system, and the LAD community hub provides the navigational structure to move between them.
If you are primarily a user and want to stay informed without following high-volume developer discussion, subscribe to LAU for community interaction and the announce list for release notifications. That combination covers the information most users need without overwhelming your inbox.