Releases: dotjarden/pixeltui
Release list
v0.5.5
Full Changelog: v0.5.4...v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0 — downloads at full speed, genre stations
Downloads: ~400× faster
Full-file transfers of YouTube tracks were throttled by the CDN to ~32 KB/s — a 4-minute song took minutes to download to a client. The server now relays whole-file requests as sequential ranged chunks in one continuous response; the same track measures 13.4 MB/s (0.3s total). Playback streaming is unchanged. Clients need no update to benefit.
Genre stations
GET /api/station?tag=<last.fm tag> — an engine-built station for any tag, seeded from your own most-played artists in that genre when possible (Last.fm's tag chart as fallback), with the same multi-seed blend, affinity, and discovery level as everything else. Cached per tag for an hour.
CLI
pixeltui devices— table of paired companion devices (id, name, paired, last seen)pixeltui devices revoke <id>— unpair from the command line
Scrobbling
- Liking a track now also submits Last.fm
track.love(from the TUI and from companion clients), when scrobbling is configured
v0.4.0 — companion server grows up
The companion-app server reaches feature parity with the TUI, gets first-class tunnels, and the recommendation engine now powers clients end to end.
Server / companion API
- Play reporting — clients record plays into the shared
history.jsonland scrobble through the server (POST /api/played,POST /api/nowplaying), so phone listening feeds Recently Played, stats, recommendations, and Last.fm/ListenBrainz exactly like TUI plays - Shared history & stats —
GET /api/history(cross-device Recently Played, covers stored with each listen) andGET /api/stats(plays, uniques, time listened, top artists/tracks over any window) - Daily mixes —
GET /api/mixes: up to 4 engine-built mixes from your last 90 days, grouped by dominant Last.fm tag, rebuilt daily - Multi-seed recommendations —
/api/recommendaccepts repeatedseed=Artist|Trackparams (the TUI's blended-station behavior);exclude=mutes artists on radio and recommendations - Live sync — the server watches the library files, so edits made in the TUI broadcast to connected clients over SSE
- Resilient addressing —
/api/sourceslists every address the server answers on (tunnel + LAN) so paired clients can follow address changes;/healthreports the server version - Official album art for library tracks that never stored a cover; album pages fall back to the first track's art; transient lyrics failures are no longer cached for a day
Tunnels
pixeltui serve --tunnel cloudflare|ngrok|tailscale— auto-publish with the public URL baked into the pairing QR; child tunnels torn down with the server- New
serverconfig block (addr,name,public_url,tunnel) plus a "Companion server" step inpixeltui setupandPIXELTUI_SERVE_*env overrides - Startup banner shows public and LAN addresses with remote-access hints
CLI
pixeltui update [version]— install a specific tagged release (also your rollback path)