Request | Enhancement - Write to existing playlist file - external player playlist duplication

[data-tim]

Currently using --dont-persist=false will delete the existing file when the playlist is regenerated as part of a cron job or manual run.

This is nice because it doesnt create endless duplicates in Navidrome.

The issue currently is that with this current delete - regenerate playlist behaviour - syncing playlists to external players like Symfonium becomes impossible as these new regenerations are treated as different playlists and cant be "synced" to update existing playlists and importing them will just create a same name duplicate in the external player.

Is it possible to create a toggle to "write to existing playlist file" alongside --dont-persist options?

edit: need to add that this behaviour is observed when using custom playlists (Spot/Apple)

[dammitjeff]

Yes currently when a playlist is updated in place, it currently deletes the OLD labeled playlist, and creates a new one with the same name.

Are you saying that you'd want to have a single playlist have their songs removed/added in place, so the same url is used for the playlist no matter how often they're updated?

[data-tim]

@dammitjeff I mean as in the same playlist data file eg. the m3u, m3u8, nsp etc

[data-tim]

so the scenario: you can monitor a playlist thats updated weekly on a streaming platform and not end up with multiple slightly different copies of the playlist each week that you have to delete in your external player of choice (Symfonium in this case)

[R3trorage]

if you guys don't mind me hopping on the thread, I think a fix to this issue might be ussing the append.playlist function from the api instead of delete. that way instead of deleting the existing playlist it only refreshes the contents/songs.