feat: support starting playback at a position via POST /player/play#335
Merged
devgianlu merged 1 commit intoJul 21, 2026
Merged
Conversation
Add an optional `position` (milliseconds) to the play request so a context can be started at a specific position within the selected track, completing the existing `skip_to_uri` (which track) with where in the track. This mirrors the position handling Spotify Connect transfers already use internally. When a position is given the track is loaded paused and seeked before unpausing, so no audio plays from 0:00 while it loads — and since loadContext returns once the track is loaded, no client-side polling is needed to time the seek. Purely additive: a new request field plus seek/resume orchestration in the existing play handler using the existing seek()/play() helpers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019FHWG4ossSBydy7jbVFWho
Author
|
Thanks!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Up for another one? Essentially just exposing the ability to start a song at a specific position over the API.
Add an optional
position(milliseconds) to the play request so a context can be started at a specific position within the selected track, completing the existingskip_to_uri(which track) with where in the track. This mirrors the position handling Spotify Connect transfers already use internally.When a position is given the track is loaded paused and seeked before unpausing, so no audio plays from 0:00 while it loads — and since loadContext returns once the track is loaded, no client-side polling is needed to time the seek.
Purely additive: a new request field plus seek/resume orchestration in the existing play handler using the existing seek()/play() helpers.