Devices
Every open lodesong of yours (a tab, another browser, another computer) joins one playback session, like Spotify Connect. One of them plays; the others are remotes.
One session across devices
- Press play anywhere and that device takes over: the one that was playing stops, the rest follow it.
- Remotes show the same song, queue and progress. Play, pause, next, previous, seeking, picking a song, "play next" and "add to queue" all go to the device that plays.
- The device picker (speaker icon in the player bar, shown once there are two devices) lists them with the playing one checked; pick one to move playback there, from where it was. "playing on chrome on mac" shows next to the controls while another device plays.
- Remotes don't count plays, scrobble or show the old "continue from your other browser" offer, so nothing is counted twice.
- A device that drops (a laptop closing) leaves the session paused where it was; any device picks it up.
It is per account and needs nothing set up. ONE_SESSION=off on the server goes back to every tab playing on its own
(configuration). The server passes the session over a WebSocket, so a reverse proxy in front must
allow WebSockets (deploy).
Phones use a Subsonic app against Navidrome directly (Arpeggi, Substreamer, Symfonium…). Those can't be remote controlled; the queue hands off through Navidrome instead: sync.
Stream quality
Settings → playback → stream quality picks what this browser asks Navidrome for. It is kept per device, not synced.
| plays | |
|---|---|
| auto (the default) | songs kept on this device (keep offline, or already in the offline cache) as they are; every other song as Opus 192 (MP3 320 in a browser that can't play Opus) |
| original | the file as it is, never transcoded |
| mp3 320 | an MP3 at up to 320 kbps |
| opus 192 | Opus at up to 192 kbps |
| opus 96 | Opus at up to 96 kbps, for a slow or metered connection |
A transcode is about a fifth of a FLAC's size, so a song starts sooner away from home. Navidrome does the converting;
it keeps a cache of converted songs (ND_TRANSCODINGCACHESIZE, 100 MB unless you raise it), so a song played again
doesn't wait for ffmpeg.
Only the original file can come from the offline cache, so auto and the transcodes don't precache the next songs. Choose original to keep that, or use keep offline on an album or playlist: those songs play from the cache, as they are. A song the browser can't play (ALAC in Firefox, say) is retried as an MP3 320 transcode whatever you picked.
Subsonic apps like Arpeggi ask Navidrome directly, not lodesong. If an app has no quality setting, give its player a transcoding profile and a maximum bit rate in Navidrome's players list; that applies unless the app asks for the original format.
Now playing in your terminal
A line above the prompt of Claude Code or OpenCode: the song, the artist, the progress, the device, the synced lyric line, and ⏮ ⏸ ⏭ for whichever player of yours is playing. A song playing in another Subsonic app (your phone) shows too, without the buttons.
-
In lodesong: settings → sync → now playing in your terminal → connect. It shows one line,
/lodesong connect https://your-player <token>, once. -
Claude Code:
/plugin marketplace add FindMalek/lodesong /plugin install lodesong-now-playing@lodesongthen paste the line from step 1.
/lodesongplays or pauses,/lodesong next,/lodesong prev,/lodesong offdisconnects. -
OpenCode (2.x): point
~/.config/opencode/cli.jsonat the plugin folder of a lodesong clone, with the URL and the token from step 1 as options:{ "plugins": [ { "package": "/path/to/lodesong/integrations/opencode", "options": { "url": "https://your-player", "token": "<token>" } } ] }/music,/music next,/music prev.
The token is a sign-in of its own: it shows under settings → account → sessions as "terminal · now playing", and signing it out there disconnects the terminal. It can only read what's playing and play, pause or skip.
The endpoints, for anything else that wants them (a status bar, a stream deck), all with
Authorization: Bearer <token>:
GET /api/remote/now | { song, position, playing, device, line, controllable } |
POST /api/remote/toggle · next · previous | to the playing device; 409 when none of yours plays |
Troubleshooting
First stop: https://<your lodesong>/api/health. It says, per configured server, whether lodesong reaches it, how fast, and what it is.
Your phone
lodesong and Arpeggi share one thing on the server: the Subsonic play queue (what's queued, which song is current, and how far into it). Each browser saves under its own client name, lodesong@<id>, so the app can tell its own saves from the phone's.