Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add two way sync with playlist #1956

Open
mybuntu-git2 opened this issue Nov 9, 2023 · 1 comment
Open

Add two way sync with playlist #1956

mybuntu-git2 opened this issue Nov 9, 2023 · 1 comment
Labels
Feature Request Feature Request Stale Issue with no activity for the last 30 days

Comments

@mybuntu-git2
Copy link

Requested Feature

Create a spotdl sync_remove command to remove tracks from playlists in Spotify, through api.

I know this can be done by having spotdl check the songs directory if it contains all music, but such setup forces us to make a massive scan every time and creates dependencies with other systems (music streamers, beets, antivirus, mounts, cached files) which I’d like to keep separate

Possible implementation

This will enable the following process flow:
Spotdl sync saves and overwrite .spotdl playlist file (existing functionality)
spotdl sync downloads the content and pipes results to a log (existing functionality)
with awk we gather the list of downloaded songs and remove them from the playlist (I deliver the code in shell)
with the new command we sync_remove them from the Spotify playlist, keeping in the Spotify playlist the tracks that were not found.

This also makes the Spotify playlist usable by a sequence of downloaders, e.g.
at 1AM we sync with spotdl, we expunge what is found, the rest is fed to lidarr at 2AM.

If this is set up I can also post a working spotdl_sync_remove.sh shell code that everyone can save in crontab as well as the script for the scenario above (including lidarr-prowlarr docker if required)

with this setup, whenever I open Spotify I can clearly see what has been found already and what instead has not been found, and is undergoing a more extensive search.

There are hints to the api call here:
Link

@mybuntu-git2 mybuntu-git2 added the Feature Request Feature Request label Nov 9, 2023
Copy link

stale bot commented Dec 15, 2023

This issue has been automatically marked stale because there hasn't been any activity for the last 30 days.

@stale stale bot added the Stale Issue with no activity for the last 30 days label Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Feature Request Stale Issue with no activity for the last 30 days
Projects
None yet
Development

No branches or pull requests

1 participant