/
/
# What does this implement/fix? Adds Spotify Soloist — Spotify's new official headless client — as a backend for the Spotify Connect provider, next to the existing go-librespot implementation. Spotify accounts created since late 2024 do not work with the reverse-engineered clients; Soloist gives those users a working Spotify Connect device in Music Assistant. - New setup choice between **Spotify Soloist (official, recommended)** and **go-librespot (community)**; existing installs stay on go-librespot untouched - Soloist setup includes a clear Terms-of-Service warning, an explicit consent step for downloading/updating the binary straight from Spotify's CDN, and a guided Soloist API key step (a Premium account is needed to create the key) - The Soloist backend manages the daemon (auto-refresh before the 90-day build expiry), captures its audio through a private PulseAudio pipe, and offers two volume modes: player-volume-only (default, cleanest audio path) or syncing the Spotify app volume - Spotify Connect now appears under Live Inputs in browse: starting it from Music Assistant resumes the last Spotify context and properly claims active device status, so the Spotify apps follow - Stopping playback (or clearing the queue) in Music Assistant releases the Spotify session, so the Spotify app no longer stays tethered to the device - One module per playback engine with a README each (plus a provider-level README covering the shared architecture); provider stage bumped to beta with Soloist added to the credits - Extensively live-tested end to end (pairing, metadata, pause/resume both ways, both volume modes, device switching, session release) against a real Soloist daemon and the real Spotify CDN **Related issue (if applicable):** - related issue n/a ## Types of changes <!-- Tick exactly one box. CI (.github/workflows/pr-labels.yaml) derives the label from the ticked box and applies it automatically; the release-notes generator uses that same label to slot this change into the next release notes. --> - [ ] Bugfix (non-breaking change which fixes an issue) — `bugfix` - [ ] New feature (non-breaking change which adds functionality) — `new-feature` - [x] Enhancement to an existing feature — `enhancement` - [ ] New music/player/metadata/plugin provider — `new-provider` - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) — `breaking-change` - [ ] Refactor (no behaviour change) — `refactor` - [ ] Documentation only — `documentation` - [ ] Maintenance / chore — `maintenance` - [ ] CI / workflow change — `ci` - [ ] Dependencies bump — `dependencies` ## Checklist - [x] The code change is tested and works locally. - [x] `pre-commit run --all-files` passes. - [x] `pytest` passes, and tests have been added/updated under `tests/` where applicable. - [ ] For changes to shared models, the companion PR in `music-assistant/models` is linked. - [ ] For changes affecting the UI, the companion PR in `music-assistant/frontend` is linked. - [x] I have read and complied with the project's [AI Policy](https://github.com/music-assistant/.github/blob/main/AI_POLICY.md) for any AI-assisted contributions. - [ ] I have [raised a PR against the documentation repository](https://github.com/music-assistant/music-assistant.io/blob/main/CONTRIBUTING.md) targeting the main or beta branch as appropriate.