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.
This PR aims at adding support for Smart Shuffle. It is very early stages as some reverse engineering is required.
Spotify introduced the concept of signals and lenses. For Smart Shuffle we send a
reset
signal to the playlist with theenhance
lense. The result is a list of ~310 tracks for a ~210 tracks playlist, but it is not clear where they should go. There is a suspicious metadata key calledshuffle.distribution
that may play a role in this. I have also noticed that the shuffle seed has been added to the session state.There might be some refactoring required to handle the "injection" of tracks inside the current tracks list. Perhaps something similar to how the queue works?