rycieos / ensemble

Playlist syncing and updating across different playlist types and systems.

ensemble

ensemble's Issues

Dynamic playlists

Many music clients support dynamic playlists, adding tracks from rules about artist, album, genre, etc. While this works for one client, such dynamic playlists are not portable, and do not generate basic playlist types for other clients to use. While it would be harder to configure them, building playlists for ensemble would allow basic playlist types to be generated from the library to work on all platforms.

New target doesn't get old playlists

If a new target is created, old playlists will not get propagated to them. A work around is touching all the playlists in an old target to force an update.

Ideally this could be discovered automatically, but otherwise having some sort of force flag would work too.

Not possible to have a local profile

Some programs support finding files relative to a directory. Currently, there is no way to have ensemble write playlists with relative filenames. While a profile exists where this is the case (local), it is not checked for changes, which defeats the point.

Deleting a playlist will not update nor remove other copies

If a client deletes a playlist from one of the profile directories, it will not be deleted by the client or ensemble. It will also not cause an update, leaving the other copies of the playlist stale, and if another copy is updated, the deleted copy will be re-made with the new changes, which is probably not the desired outcome.