Music Assistant image with Jellyfin playback reporting #1
Loading…
Reference in a new issue
No description provided.
Delete branch "jellyfin-playback-reporting"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Builds the official Music Assistant release with a patch that makes its Jellyfin provider report playback to Jellyfin. Upstream (2.10.9 stable and the current dev branch) never reports plays, so nothing played through MA reached Jellyfin play counts or Harmonie.
What the patch does
Implements the provider's
on_playedhook (the one the Plex and Emby providers already use). Each track becomes a Jellyfin playback session under MA's existing Jellyfin login (james):/Sessions/Playingon the first report,/Sessions/Playing/Progressevery 30 s,/Sessions/Playing/Stoppedwith the real position at the end, skip or stop, andDELETE /UserPlayedItems/{id}when a track is marked unplayed. Jellyfin sets play count, last played and resume position itself, and Harmonie sees skips and listening time as well as completed plays. A failed report only logs a warning.Build
Daily, on push to main and by hand: latest stable upstream release ->
FROM ghcr.io/music-assistant/server:<version>->patch --fuzz=0(fails the build if it no longer applies) -> the test intests/runs inside the image against a fake Jellyfin server -> pushforgejo.mcy.space/music-assistant/music-assistant:<major.minor>.<run>.Tested locally (podman, 2.10.9)
Before merging
REGISTRY_TOKENmust be added as this repo's Actions secret (a PAT with write:package, read:package, write:repository); without it the push step fails.🤖 Generated with Claude Code
https://claude.ai/code/session_01CbPPc19ztjvWzSc5JPMH2B