-
Notifications
You must be signed in to change notification settings - Fork 109
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 support for Spotify playlist management #22
Comments
Was thinking of adding this feature.
Right now I assume any playlist that you create would have to only include spotify items in order for it to sync to spotify. I'm guessing this feature might also require additions to pyspotify which I could do as needed. Planning to read through some of the code at which point I'll have something more intelligent to say on this topic. |
👍 |
Currently getting 'Playlist with scheme "spotify" can't add track with scheme "spotify"' error in ncmpcpp, which does not make sense. |
Please don't hijack unrelated issues. On Fri, Feb 19, 2016, 16:32 Cysioland notifications@github.com wrote:
|
But it is related, because Mopidy-Spotify currently can't manage playlists,
hence this message.
|
Any update about this one? |
Not now, spotify will close libspotify, which is used by this project, until 2017 or it is closed already (#110) |
There are no changes required to libspotify (or pyspotify) to implement this feature as they already have full support for modifying playlists. The changes required to implement this feature are in mopidy-spotify/mopidy. If I remember correctly the main blocker is some sensible generic handling when tracks come from multiple backends, as per @peterlvilim's comment above. So, no update here sadly. |
I think ideally you could add tracks from multiple sources to a playlist in mopidy, and it would sync only those tracks that are from spotify back to the spotify playlist, no? |
Is there anything going on with this? |
I don't know of anyone working on it.
We need to start using the Web API for most playlist stuff so that probably
includes this. Although since you can't edit the Spotify owned playlists
(the ones seemingly now incompatible with libspotify) that might not
technically be the case. But doing everything the same way does have value.
…On 5 Aug 2017 11:10 a.m., "Emil Lynegaard" ***@***.***> wrote:
Is there anything going on with this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5DqOjFKsVZiTdG1BWyjPbeZYFaBFYRks5sVD-sgaJpZM4Cft-l>
.
|
To understand that correctly - does that mean that as things are right now, it will never be possible to add tracks to a playlist that was created directly in Spotify? As in have playlist changes made both in Spotify and with Mopidy be synced. |
No, I'm referring to Spotify playlists owned by the Spotify account. Such
as toplists, new releases etc.
…On 5 Aug 2017 11:48 a.m., "Emil Lynegaard" ***@***.***> wrote:
Although since you can't edit the Spotify owned playlists...
To understand that correctly - does that mean that as things are right
now, it will never be possible to add tracks to a playlist that was created
directly in Spotify? As in have playlist changes made both in Spotify and
with Mopidy be synced.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5DqCSJg40z-aXGPt_70umDhasVwYVGks5sVEhfgaJpZM4Cft-l>
.
|
Ah of course - alright, so eventual support for editing one's own spotify playlists should be possible then. |
Moved from mopidy/mopidy#42:
The text was updated successfully, but these errors were encountered: