Skip to content

Qobuz Connect: the renderer screen stays empty when a session is handed over paused - #794

Open
Gjuju wants to merge 1 commit into
moode-player:developfrom
Gjuju:contrib/qobuz-metadata-fallback
Open

Gjuju wants to merge 1 commit into
moode-player:developfrom
Gjuju:contrib/qobuz-metadata-fallback

Conversation

@Gjuju

@Gjuju Gjuju commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

The Qobuz app can hand a session over PAUSED: the daemon loads the track and
waits for a play command, so no TrackStarted is emitted. TrackStarted is the
only writer of the metadata cache, and the cache is truncated when a session
ends — so the renderer screen has nothing to show until playback is started by
hand.

The daemon knows the track the whole time, so ask it through its local API
rather than giving up. A daemon that answers nothing leaves the variables
untouched and the caller skips exactly as before.

This also restores the daemon's API address, which the pibuz rename dropped
from this script along with its last user.

Traced on x86_64 with pibuz 2.4.1 and debuglog on:

15:02:46  PLAYSTATE=stopped  CLIENT DISCONNECTED  Update cache: skipped
15:02:56  CLIENT CONNECTED
15:02:58  PLAYSTATE=loading  Cover URL: empty     Update cache: skipped
15:02:58  PLAYSTATE=paused   Cover URL: empty     Update cache: skipped

qbzmeta.json was 0 bytes throughout, while pibuz status reported the track
and its position.

🤖 Generated with Claude Code

@Gjuju Gjuju changed the title Qobuz Connect: show the track when the session is handed over paused Qobuz Connect: two cases where the renderer screen stays empty Sep 10, 2026
@Gjuju
Gjuju force-pushed the contrib/qobuz-metadata-fallback branch 8 times, most recently from 1efecae to 457ed6f Compare September 17, 2026 14:14
@Gjuju Gjuju changed the title Qobuz Connect: two cases where the renderer screen stays empty Qobuz Connect: the renderer screen stays empty when a session is handed over paused Sep 17, 2026
TrackStarted is the only writer of the metadata cache, and the cache is
truncated when a session ends. The Qobuz app hands a session over PAUSED: the
daemon loads the track and waits for a play command, so no TrackStarted is
emitted and the renderer screen stays empty until playback is started by hand.

The daemon knows the track the whole time, so ask it through its local API
rather than giving up. A daemon that answers nothing leaves the variables
untouched and the caller skips exactly as before.

This also restores the daemon's API address, which the pibuz rename dropped
from this script along with its last user.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Gjuju
Gjuju force-pushed the contrib/qobuz-metadata-fallback branch from 457ed6f to e6f913d Compare September 19, 2026 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant