sendspin 7.2.0

Synchronized audio player for Sendspin servers

sendspin

Connect to any Sendspin server and instantly turn your computer into an audio target that can participate in multi-room audio.

Sendspin CLI includes three apps:

• sendspin - Terminal client for interactive use
• sendspin daemon - Background daemon for headless devices
• sendspin serve - Host a Sendspin party to demo Sendspin

When using an explicit app (daemon, serve, or player), put it immediately after sendspin. For example, use sendspin daemon --name Kitchen, not sendspin --name Kitchen daemon.

Quick Start

Run directly with uv:

Start client

uvx sendspin

Host a Sendspin party

uvx sendspin serve --demo
uvx sendspin serve /path/to/media.mp3
uvx sendspin serve https://retro.dancewave.online/retrodance.mp3

Installation

With uv:

uv tool install sendspin

Support for Chromecast devices requires installation of extra dependencies:

uv tool install 'sendspin[cast]'

Install as daemon (Linux):

curl -fsSL https://raw.githubusercontent.com/Sendspin/sendspin-cli/refs/heads/main/scripts/systemd/install-systemd.sh | sudo bash

With pip:

pip install sendspin

Install from source

git clone https://github.com/Sendspin-Protocol/sendspin.git
cd sendspin
pip install .

After installation, run:

sendspin

The player will automatically connect to a Sendspin server on your local network and be available for playback.

Updating

To update to the latest version of Sendspin:

If installed with uv:

uv tool upgrade sendspin

If installed with pip:

pip install --upgrade sendspin

If installed as systemd daemon:

The systemd daemon preserves your configuration during updates. Simply upgrade the package:

# Upgrade sendspin (the daemon installer uses uv by default)
uv tool upgrade sendspin

# Or if you installed with pip
pip install --upgrade sendspin

# Restart the service to use the new version
sudo systemctl restart sendspin

Your client name, audio device selection, and other settings in /etc/default/sendspin are preserved during the update.

Note: You do not need to uninstall and reinstall when updating. Your configuration (client name, audio device, delay settings) is stored separately and will be preserved.

Configuration Options

Sendspin stores settings in JSON configuration files that persist between sessions. All command-line arguments can also be set in the config file, with CLI arguments taking precedence over stored settings.

Configuration File

Settings are stored in ~/.config/sendspin/:

• settings-tui.json - Settings for the interactive TUI client
• settings-daemon.json - Settings for daemon mode
• settings-serve.json - Settings for serve mode

Example configuration file (TUI/daemon):

{
  "player_volume": 50,
  "player_muted": false,
  "static_delay_ms": 0,
  "last_server_url": "ws://192.168.1.100:8927/sendspin",
  "name": "Living Room",
  "client_id": "sendspin-living-room",
  "audio_device": "2",
  "audio_format": "flac:48000:24:2",
  "log_level": "INFO",
  "listen_port": 8927,
  "use_mpris": true,
  "use_hardware_volume": true,
  "hook_set_volume": "/usr/local/bin/set-avr-volume",
  "manufacturer": "Acme Corp",
  "product_name": "Living Room Speaker",
  "interface": "192.168.1.5"
}

Example configuration file (serve):

{
  "log_level": "INFO",
  "listen_port": 8927,
  "name": "My Sendspin Server",
  "source": "/path/to/music.mp3",
  "clients": ["ws://192.168.1.50:8927/sendspin", "ws://192.168.1.51:8927/sendspin"]
}

Available settings:

Setting	Type	Mode	Description
player_volume	integer (0-100)	TUI/daemon	Player output volume percentage
player_muted	boolean	TUI/daemon	Whether the player is muted
static_delay_ms	float	TUI/daemon	Extra playback delay in milliseconds
last_server_url	string	TUI/daemon	Server URL (used as default for --url)
name	string	All	Friendly name for client or server (--name)
client_id	string	TUI/daemon	Unique client identifier (--id)
audio_device	string	TUI/daemon	Audio device index, name prefix, or ALSA device name (--audio-device)
audio_format	string	TUI/daemon	Preferred audio format (--audio-format, e.g., flac:48000:24:2)
log_level	string	All	Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL
listen_port	integer	daemon/serve	Listen port (--port, default: 8927)
use_mpris	boolean	TUI/daemon	Enable MPRIS integration (default: true)
use_hardware_volume	boolean	TUI/daemon	Control hardware/system output volume instead of software volume (--hardware-volume true/false). Default: on for daemon (if available), off for TUI
hook_set_volume	string	TUI/daemon	Script to run for external volume control (--hook-set-volume). Receives the effective volume 0-100 as the last argument
hook_start	string	TUI/daemon	Command to run when audio stream starts
hook_stop	string	TUI/daemon	Command to run when audio stream stops
manufacturer	string	TUI/daemon	Manufacturer name reported in the client hello (--manufacturer)
product_name	string	TUI/daemon	Product name reported in the client hello (--product-name); defaults to auto-detected OS/platform name
interface	string	TUI/daemon	IP address of the network interface to use (--interface)
source	string	serve	Default audio source (file path or URL, ffmpeg input)
source_format	string	serve	ffmpeg container format for audio source
clients	array	serve	Client URLs to connect to (--client)

Settings are automatically saved when changed through the TUI. You can also edit the JSON file directly while the client is not running.

Server Connection

By default, the player automatically discovers Sendspin servers on your local network using mDNS. You can also connect directly to a specific server:

sendspin --url ws://192.168.1.100:8080/sendspin

List available servers on the network:

sendspin servers list

Client Identification

If you want to run multiple players on the same computer, you can specify unique identifiers:

sendspin --id my-client-1 --name "Kitchen"
sendspin --id my-client-2 --name "Bedroom"

• --id: A unique identifier for this client (optional; defaults to sendspin-<hostname>, useful for running multiple instances on one computer)
• --name: A friendly name displayed on the server (optional; defaults to hostname)

Audio Output Device Selection

By default, the player uses your system's default audio output device. You can list available devices or select a specific device:

List available audio devices:

sendspin audio-devices list

This displays all audio output devices with their IDs, channel configurations, and sample rates. The default device is marked.

Select a specific audio device by index:

sendspin --audio-device 2

Or by name prefix:

sendspin --audio-device "MacBook"

Or by raw ALSA device name (Linux):

sendspin --audio-device dmixer

This is useful for ALSA plugin devices (dmix, plug, etc.) that may not appear in the numbered PortAudio device list (though they may be shown in the ALSA devices section on Linux). For example, in a dual mono setup where two daemons share a single sound card via dmix, each daemon can target a different ALSA device that routes to a specific channel:

# Room 1: left channel via dmix
sendspin daemon --name "Living Room" --audio-device living_room

# Room 2: right channel via dmix
sendspin daemon --name "Kitchen" --audio-device kitchen

This requires an /etc/asound.conf with dmix and plug devices that route to the appropriate channels. See your ALSA documentation for details on configuring dmix.

This is particularly useful when running sendspin daemon on headless devices or when you want to route audio to a specific output.

Preferred Audio Format

By default, the player negotiates the best audio format with the server from the list of formats supported by your audio device (preferring FLAC over PCM). You can specify a preferred format to prioritize:

sendspin --audio-format flac:48000:24:2

The format string uses the pattern codec:sample_rate:bit_depth:channels:

• codec: flac (compressed, preferred) or pcm (uncompressed)
• sample_rate: Sample rate in Hz (e.g., 44100, 48000, 96000)
• bit_depth: Bits per sample (16 or 24)
• channels: Channel count (1 for mono, 2 for stereo)

The specified format is validated against the audio device on startup. If the device doesn't support it, the player will exit with an error.

System Volume Control

On Linux with PulseAudio/PipeWire, Sendspin can control your system output volume directly. Volume adjustments (keyboard shortcuts, server commands) change the system volume. The current system volume is read on startup — the player_volume and player_muted settings are only used when hardware volume is disabled.

Hardware volume is on by default in daemon mode and off by default in TUI mode. To override:

sendspin --hardware-volume true             # Enable for TUI
sendspin daemon --hardware-volume false     # Disable for daemon

If your real volume control lives on another device, you can hand volume changes off to a script instead:

sendspin daemon --hook-set-volume /usr/local/bin/set-avr-volume

The script receives the effective output volume as its last argument in the range 0-100. When the player is muted, Sendspin calls the script with 0 and keeps the last logical player_volume persisted separately so unmuting restores the previous level.

Because Sendspin cannot read back external device state from the hook, startup volume comes from the persisted player_volume and player_muted settings. Those settings are updated whenever Sendspin successfully applies a new volume through the hook. When hook_set_volume is configured, it takes precedence over PulseAudio/PipeWire hardware volume control.

Adjusting Playback Delay

The player supports adjusting playback delay to compensate for audio hardware latency or achieve better synchronization across devices.

sendspin --static-delay-ms 50

Note: A delay of 0ms works well in most cases. If audio is playing slightly too late, a small positive delay (e.g., 50ms) can help compensate for audio hardware latency. On compatible servers, delay can be configured remotely per player, so you shouldn't need to set this locally.

Daemon Mode

To run the player as a background daemon without the interactive TUI (useful for headless devices or scripts):

sendspin daemon

The daemon runs in the background and logs status messages to stdout. It accepts the same connection and audio options as the TUI client:

sendspin daemon --name "Kitchen" --audio-device 2

In daemon mode without --url, the client listens for incoming server connections and advertises itself via mDNS. The --name option (or name setting) is used as the friendly name in the mDNS advertisement, making it easy for servers to identify this client on the network.

Use --manufacturer and --product-name to override the device identity reported to the server in the client hello. This is useful when running the daemon in a container or on a custom device where the auto-detected OS name is not meaningful:

sendspin daemon --name "Living Room" --manufacturer "Acme" --product-name "Living Room Speaker"

Hooks

You can run external commands when audio streams start or stop. This is useful for controlling amplifiers, lighting, or other home automation:

sendspin --hook-start "./turn_on_amp.sh" --hook-stop "./turn_off_amp.sh"

Or with inline commands:

sendspin daemon --hook-start "amixer set Master unmute" --hook-stop "amixer set Master mute"

--hook-set-volume is separate from these stream lifecycle hooks. It is intended for external volume controllers and receives the effective output volume as its last argument.

Hooks receive these environment variables:

• SENDSPIN_EVENT - Event type: "start" or "stop"
• SENDSPIN_SERVER_ID - Connected server identifier
• SENDSPIN_SERVER_NAME - Connected server friendly name
• SENDSPIN_SERVER_URL - Connected server URL. Only available if client initiated the connection to the server.
• SENDSPIN_CLIENT_ID - Client identifier
• SENDSPIN_CLIENT_NAME - Client friendly name

Visualizer

The TUI includes a real-time audio spectrum visualizer that displays frequency data received from the server. This uses the experimental visualizer@_draft_r1 role. The spectrum data is computed on the server and sent via sendspin to the TUI.

Toggle it by pressing v in the TUI. Your preference is saved in settings and remembered on next launch.

Debugging & Troubleshooting

If you experience synchronization issues or audio glitches, you can enable detailed logging to help diagnose the problem:

sendspin --log-level DEBUG

This provides detailed information about time synchronization. The output can be helpful when reporting issues.

Network Interface Binding

On machines with multiple network interfaces (e.g., a home server with both a LAN and a WAN/internet interface), you can restrict Sendspin to a specific interface using --interface:

sendspin --interface 192.168.1.5
sendspin daemon --interface 192.168.1.5

The --interface option takes the IP address of the interface to use. This affects:

• mDNS discovery: only servers advertising on that interface will be found.
• Daemon listening mode (no --url): the incoming-connection server binds only to that IP, so servers on other interfaces (e.g., the WAN) cannot connect.

This is useful when you want Sendspin to be accessible only on your LAN, not on the internet-facing interface.

Install as Daemon (systemd, Linux)

For headless devices like Raspberry Pi, you can install sendspin daemon as a systemd service that starts automatically on boot.

Install:

curl -fsSL https://raw.githubusercontent.com/Sendspin/sendspin-cli/refs/heads/main/scripts/systemd/install-systemd.sh | sudo bash

The installer will:

• Check and offer to install dependencies (libportaudio2, uv)
• Install sendspin via uv tool install
• Prompt for client name and audio device selection
• Create systemd service and configuration

Manage the service:

sudo systemctl start sendspin    # Start the service
sudo systemctl stop sendspin     # Stop the service
sudo systemctl status sendspin   # Check status
journalctl -u sendspin -f        # View logs

Configuration: Edit /etc/default/sendspin to change client name, audio device, or delay settings.

Uninstall:

curl -fsSL https://raw.githubusercontent.com/Sendspin/sendspin-cli/refs/heads/main/scripts/systemd/uninstall-systemd.sh | sudo bash

Sendspin Party

The Sendspin client includes a mode to enable hosting a Sendspin Party. This will start a Sendspin server playing a specified audio file or URL in a loop, allowing nearby Sendspin clients to connect and listen together. It also hosts a web interface for easy playing and sharing. Fire up that home or office 🔥

# Demo mode
sendspin serve --demo
# Local file
sendspin serve /path/to/media.mp3
# Remote URL
sendspin serve https://retro.dancewave.online/retrodance.mp3
# Without pre-installing Sendspin
uvx sendspin serve /path/to/media.mp3
# Connect to specific clients
sendspin serve --demo --client ws://192.168.1.50:8927/sendspin --client ws://192.168.1.51:8927/sendspin

Multi-Worker Mode

For serving many concurrent listeners, use --workers to run multiple server processes behind a reverse proxy:

sendspin serve --demo --workers 4

This spawns 4 worker processes on consecutive ports starting from --port (default 8927), so ports 8927-8930. Place a reverse proxy (e.g., nginx, Caddy) in front with load balancing across these ports.

Note: --client is not supported with --workers.