The first stable release. The player speaks Sendspin 1.0.0-rc1, as 0.4.0 did. It now runs on
Windows, installs as a .deb, .rpm or Arch package, and comes with a terminal remote.
Nothing breaks for CLI users. Every flag, config key, control-socket message, state-file
format and exit code from 0.4.0 still works the same way. The few visible changes are listed
under "Worth knowing".
New features
sendspin-cli tui, a terminal remote for the running player. It attaches over the
control socket likestatusdoes, and it never plays audio or gets an identity of its own.
When a server starts pairing, the screen shows the 6-digit code in large digits. A pairing
window asks Y/N, and the outcome stays on screen for 3 s. The rest of the time it shows what
is playing and drives it with the Python TUI's keys: space, ←/→, ↑/↓ for this player,[/]
for the group,m/M,r,x,g,,/.,pto show the pairing token, andq. It
needs a terminal, and exits 1 without one. See
Using the TUI. (#120)- New subcommands, added for the TUI.
player-vol <0-100>andplayer-mute on|offset
this player's own level, which the server is told about and the player remembers.voland
mutestill address the group, and under--fixed-volumethe new two are refused with
exit 2.status-kvprints status askey=valuelines for scripts, starting with
version=1, with documented keys that are never renamed.statusgainslast pairing:,
and showsalbum:,group:andcodec:once they are known. Every control exchange,
including connect, is now bounded to 3 s, so a wedged player cannot hang a subcommand.
(#120) - Windows. The player runs on Windows 10 1809 or later at parity with Linux and macOS:
control socket, state, hooks, mDNS and-z. The control socket and the state file stay private to
the user who runs it. Releases carry a Windows zip, linked against the static CRT so it runs
on a clean install.get_started_windows.ps1installs per user with no administrator
rights, asks for a name and an output (or takes-Nameand-Output), and starts the
player at logon.uninstall_windows.ps1removes it, with-Purgeto drop config and state.
See Getting Started on Windows.
(#95, #102, #103, #104, #117) .deb,.rpmand Arch packages. Each release now has
sendspin-cli-<version>-<leg>.{deb,rpm,pkg.tar.zst}for linux-x86_64, arm64 and armv7, and
a.deband an Arch package for armv6, with no rpm. They hold the same binary as the
tarballs but install to/usr. They create thesendspin-cliaccount and install the unit
without enabling or starting it. Don't mix a package with a/usr/localtarball install on
one machine. See Packages for which
package fits which release, and how to verify and install it. (#124)- A guided Linux install, and an uninstaller.
get_started_linux.shasks for a name and
an output device (or takes--nameand--output), writes them, and starts the service.
It works piped fromcurl. It installs missing runtime libraries through
apt-get/dnf/pacmanas part of the plan it shows.--user-serviceruns the player
undersystemctl --userinstead of the system unit.uninstall_linux.shremoves either
mode, and keeps config and state unless you pass--purge. (#79) - The installers offer unpaired access, on by default. On a fresh install, both
get-started scripts ask
Let any server on your network play here without pairing first? [Y/n]and write
allow-unpaired.--allow-unpaired/--no-allow-unpaired(-AllowUnpaired/
-NoAllowUnpairedon Windows) answer it up front, and--yeswritestrue. A config that
already sets the key is left alone. The binary's own default is still
allow-unpaired = false. (#123) --alsa-mixer <card:control>drives a hardware mixer for volume and mute instead of
scaling the stream in software, mapped over the control's dB range. The player reports the
mixer's level at startup, and reports changes made in alsamixer or with a hardware knob.
--alsa-mixer-curve spec|cubicpicks the curve:cubictracks alsamixer's slider. A mixer
that cannot be opened falls back to software gain. The flag needs an ALSA output and is
refused with--fixed-volume. Thanks to @TermeHansen. (#96)--release-devicecloses an ALSA or PortAudio output when a stream ends and reopens it
at the next one. Squeezelite, AirPlay or Spotify can then share an exclusivehw:DAC with
the player between streams. It is off by default: another app may hold the device when a
stream starts. (#100)--keep-output-alive <s>keeps an ALSA output running on silence for up to<s>
seconds after the last audio. This helps an HDMI or S/PDIF receiver that swallows the start
of the next stream while it re-locks. The default0stops the output at once, as before,
and--release-deviceoverrides it. Thanks to @tho22. (#109, #127)portaudio:<host api>:<name>picks one of the copies of a device that Windows lists
once per host API, e.g.-o portaudio:directsound:Speakers.-lprints the prefix to type
(mme,directsound,wasapi,alsa,coreaudio, …). A name that already resolves still
resolves the same way. An ambiguous bare name is refused with each copy listed. (#103)statusprintspaired servers: N, the number of stored pairings, whether or not a
server is connected. (#105)--pairing-token-endpoint <address>:<port>serves the pairing token over HTTP on one
internal address, e.g.172.30.32.1:8930on Home Assistant OS, so a server on the same host
can pair without a code. It answers only peers on that address's own subnet, and only until
a server pairs. It refuses a wildcard address. This needs a server that does local pairing
through the_ohf_local_pairing@v1role. That role name is still provisional, and Music
Assistant support is in progress (music-assistant/server#7371). Off by default. (#110)
Fixed issues
- A busy ALSA device no longer loses the whole stream. An open that fails because another
process holds the device now logsOutput device '…' is busy (held by another process)
instead of blaming the format. The player retries in the background after 2, 4, 8, 16 and
30 s, then starts again from 2 s. When the device frees up it logs
Output device '…' is free -- playingand playback resumes within the stream. When the stream ends it stops retrying, so an idle player never grabs a device that
another player has just released. (#127) - PulseAudio and PipeWire can suspend the sink between streams. The player's stream is
corked (Pulse) or paused (PipeWire) at stream end, instead of left running. (#127) - The default state directory is created when
~/.local/statedoesn't exist yet. On a
fresh system every write of the state file used to fail, so the player forgot its identity,
pairings and volume across restarts. Missing parents of the default path are now created at
0700. An explicit--state-dirstill needs its parent to exist. (#118) -o portaudioand--input portaudioon big-endian hosts. PortAudio's sample formats
are native-endian, so on such a host every 16-, 24- and 32-bit sample was byte-reversed and
played as noise. Samples are now swapped on the way in and out. (#119)- A format change mid-stream no longer desyncs. The sink is reopened in the format each
write carries, once the old format's audio has played out. (#122) - Linux playback no longer hard-corrects while the time daemon slews the clock. Every
sink and source now timestamps on the library's clock, which readsCLOCK_MONOTONIC_RAWon
Linux. (#94) statuskeeps showing a pairing attempt that starts with the connection. It used to
readpairing: noneduring the exchange. An attempt that the server cancels is now
forgotten too. (#115)
Worth knowing
- New installs through the get-started scripts let unpaired servers play, unless you
answer no or pass--no-allow-unpaired. Unattended--yesinstalls on a host with no
config are included. Existing configs are not changed. (#123) statusno longer printstrust: unknown. A connected session is alwayspairedor
unpaired. (#115)--name,--product-nameand--manufacturerover 64 bytes of UTF-8 are cut at a
character boundary, with a warning. Astream/startin a format the player didn't
advertise ends that stream. (#122)- Log wording. A busy ALSA device ends a stream with
Stream ended: N bytes discarded, because '…' was busy. A refused format ends one with
Stream ended: N bytes discarded, because '<sink>' refused their format.
Stream updated: <rate> / <ch> / <bits>is new. A log watcher that matches "refused" no
longer sees busy devices. (#122, #127)
Under the hood
- sendspin-cpp is pinned to
v0.10.0, and the CLI uses none of its deprecated APIs.
Upstream changes that reach the player with the pin: time-sync bursts run at most 10 s
apart; aserver/activatethat drops theplaybackactivity ends the running stream; and
--buffer-msand--output-delayalready sit inside the library's new limits.
(#94, #101, #115, #122) - Building offline with vendored sources, through
FETCHCONTENT_SOURCE_DIR_<NAME>and
FETCHCONTENT_FULLYDISCONNECTED=ON, is documented for distro packagers. (#127) - The README follows the Python CLI's layout, and the pairing docs lead with the code
rather than the token. Thanks to @maximmaxim345. (#107, #112) - CI runs the Linux installer on clean Debian trixie and bookworm, installs and removes
the packages on Debian, Ubuntu, Fedora and Arch, and checks that the Windows binary imports
no Visual C++ runtime. macOS builds onmacos-15, and the armv7 dependency install
survives a lagging mirror. (#99, #102, #116, #124, #125, #128)
Full changelog: v0.4.0...v1.0.0
What this build is
sendspin-cli 1.0.0. The version of the sendspin-cpp library it is linked against
is pinned at build time and printed on the second line of sendspin-cli --version,
alongside this one on the first.
Installing, verifying SHA256SUMS and the macOS Gatekeeper situation are in the
wiki — Installation,
or Getting Started on a Raspberry Pi
for the two 32-bit ARM archives. Each archive also carries its own BUILD-INFO.txt,
with the install command already filled in for its platform. The .deb, .rpm and
.pkg.tar.zst packages install the same binary under /usr; see
Packages.
The macOS binary and the .pkg around it are unsigned — ad-hoc signed, which is
the minimum an arm64 Mach-O needs to execute at all, and carries no developer identity
— so Gatekeeper refuses them until you say otherwise. Said here rather than only behind
a link because it is worth knowing before you download; what to do about it is under
the macOS installation guide.
The Windows zip is unsigned as well, so SmartScreen may warn the first time it runs.
Getting Started on Windows
has a guided installer that checks the zip against SHA256SUMS before installing it.
- README — what it is, how to run
it, and how to contribute - Contributors — development,
testing, CI, and release guidance - Roadmap — what is still owed,
item by item