Split from #304 (reporter: @am4c130d).
Current behaviour
Restore Session (local) returns to the correct track on startup, but playback begins from 00:00 rather than from the timestamp where the app last closed. Qobuz Connect mirrors this — it only exposes a track pointer, not an in-track offset.
Ask
Persist the last known playback position (millisecond offset inside the current track) together with the track id, and seek to it on session restore. From the original report:
I would like QBZ to save the track (if not the position in the track) and the complete queue […]
i.e. the position inside the track is the secondary ask, but the one that makes the feature feel complete.
Acceptance
Out of scope
- Remote / Qobuz Connect position restore (Qobuz's own protocol doesn't expose this; would be a separate upstream feature request)
Thanks @am4c130d.
Split from #304 (reporter: @am4c130d).
Current behaviour
Restore Session (local) returns to the correct track on startup, but playback begins from
00:00rather than from the timestamp where the app last closed. Qobuz Connect mirrors this — it only exposes a track pointer, not an in-track offset.Ask
Persist the last known playback position (millisecond offset inside the current track) together with the track id, and seek to it on session restore. From the original report:
i.e. the position inside the track is the secondary ask, but the one that makes the feature feel complete.
Acceptance
TrackStartedto downstream listeners (MPRIS, tray, etc.), so the UI never briefly displays00:00Out of scope
Thanks @am4c130d.