Snapcast

Snapcast (Synchronous audio player) plays audio streams time sychronized on multiple devices over network using a server and a client component. The server picks up an audio stream from a fifo pipe, thus it can be combined with any audio source that is able to write to a pipe. The Snapserver is able to handle multiple streams at once. The assignment of clients to streams and their volume is controlled via a JSON-API.

Server
The Snapcast server should run as its own user:group e.g. (default created during emerge).

A sample config that makes snapserver pick up an audio stream from the named pipe looks like this:

To start snapserver now run:

To start snapserver at boot time run:

For all snapserver options please see.

Client
The basic configuration for the client looks like this:

This will run snapclient as daemon using the default sound card. It will try to find servers on the network using Avahi, if avahi-daemon is installed and running.

To start snapclient now run:

To start snapclient at boot time run:

Desktop environment/selecting sound card
To make use of PulseAudio/use snapclient in your desktop environment (to be able to use snapclient alongside with other audio sources, control its volume, etc.) you would start it as your desktop user instead of letting the init system control it.

To get a list of sound cards, and select the right one, run:

To use PulseAudio for example, use  with the   command line option:

Snapclient should now appear in your list of audio playing applications of PulseAudio.

Audio source
To make some testing noise, random bytes can be shoved into the snapservers pipe:

Snapcast can basically be used with anything that is able to write PCM audio to a fifo.

MPlayer example
To make MPlayer play something over Snapcast use:

MPD example
To hear music with MPD over Snapcast create a new audio_output in the using the fifo module:

The sample rate setting is the default one used by Snapcast. Different sample rates can be used but must be set in the snapserver config file first.

Multiple input streams
Snapcast is able to handle multiple input streams per server instance. The server also assigns the clients dynamically to streams.

Each stream is added with another  option and its own fifo to the snapserver config.

Controlling Snapcast
Assignment of streams to clients as well as volume, name, and latency of each client is controlled over a JSON-API provided by snapserver. The API documentation can be found on GitHub.

There are some (GUI-) implementations using that API, like

Snapdroid
The developer of Snapcast also made an Android app, Snapdroid.

It can connect clients to streams, set volumes, etc. Moreover it implements a Snapcast client on Android, making it possible to play a Snapcast stream on an Android device.