Developer Documentation

Developing Clients

You may browse the programming documentation for the client API. (Run ninja -C build doxygen to generate this documentation from the source tree).

If you want to write a volume control application, make sure to read this.

Also, make sure to set properties on all PA connections, make sure to read this.

Finally, make sure you know everything about latency control!

Here are some examples that uses the async (complex) API, Sample Async Device List and Sample Async Playback.

Talk to PA over D-Bus

Using the native protocol as described is the most common way to talk to PA, but PA can expose D-Bus interfaces as well:

Developing PulseAudio

Instructions for building and installing the current development version.

You can contribute to PulseAudio via Gitlab, by filing issues on our tracker or submitting merge requests.

When working on PulseAudio, please mind the Coding Style.

Developing Modules

There are several reasons for writing loadable modules for PulseAudio:

  • Extended device driver support
  • Protocol support beyond ESOUND's protocol and the native protocol. (such as NAS or a subset of aRts)
  • New programming interfaces such as XMLRPC or DBUS for controlling the daemon.
  • Hooking audio event sources directly into PulseAudio (similar to module-x11-bell)
  • For low latency applications such as VOIP: load the VOIP core directly into PulseAudio and have a slim GUI frontend to control it.

There is currently a little bit of documentation available on how to write loadable modules for PulseAudio. Beyond this, read the source, Luke! If you are interested in writing new modules feel free to contact the authors in case you have any questions.

Some things that might be relevant for people hacking on specific modules:

Porting to other platforms

Emerging Features