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

[Feature request] Playlist update after import #753

Closed
anatosun opened this issue Feb 1, 2021 · 9 comments
Closed

[Feature request] Playlist update after import #753

anatosun opened this issue Feb 1, 2021 · 9 comments

Comments

@anatosun
Copy link

anatosun commented Feb 1, 2021

First, thank you for the great work. The playlist import feature is especially the one that made me migrate to this project.

Now, after importing a playlist with an m3u file, any change added to the playlist in Navidrome is not added to the original m3u. Of course, we have the ability to download the updated m3u file directly from the UI. Yet, having the original m3u file updated automatically could be useful when working with other softwares such as Rekordbox or Traktor to have them in turn update the playlists.

@deluan
Copy link
Member

deluan commented Feb 1, 2021

Thanks for trying Navidrome!

Originally I planned to implement a "two way sync", but there are some complications in implementing it and I decided not to do it. Take a look here: #105 (comment)

Maybe change the auto-sync flag from a boolean (auto import or not) to a combo: Off, Auto-import, Auto-Export). The sync would be unidirectional, but the user would be able to select which direction to sync. What do you think?

@anatosun
Copy link
Author

anatosun commented Feb 1, 2021

Oh yes now I see the difficulties around this feature implementation...

Changing the “direction” of the sync can be a solution indeed but we would need that option globally so to make a smooth and easy export feature, what do you think?

In my opinion, it would also be good to have the option to export it either in relative or absolute path.

@deluan
Copy link
Member

deluan commented Sep 9, 2021

Hey @fwicht , I'm revisiting old issues and found this that I completely forgot about (sorry). Here are my thoughts:

Changing the “direction” of the sync can be a solution indeed but we would need that option globally so to make a smooth and easy export feature, what do you think?

What do you mean by "global"? One flag to control the direction of all playlists sync in Navidrome? That would not be a very flexible option....

In my opinion, it would also be good to have the option to export it either in relative or absolute path.

The problem is: Relative to what? To the MusicFolder path?

@anatosun
Copy link
Author

Hey, @deluan, no worries!

What do you mean by "global"? One flag to control the direction of all playlists sync in Navidrome? That would not be a very flexible option....

  • What I meant by 'globally' was to give the user the possibility of exporting every playlists from his library with a single and global option.

The problem is: Relative to what? To the MusicFolder path?

  • As for 'relative', I probably meant relative to the m3u8 files themselves. This way the playlists could be exportable to any software on any system. For example, say you want to export your playlists to a DJ software like Rekordbox on your PC. Well, you could successfully download your playlists and import them into the software. If the path was the original one from the server (absolute), it would most likely not be recognised from the software.

I hope this clarify what I meant in the previous comment.

@github-actions
Copy link

github-actions bot commented Mar 7, 2023

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Navidrome team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

@github-actions github-actions bot added the stale label Mar 7, 2023
@Crazy-Ginger
Copy link

I am still be interested in this feature.
Manually syncing playlists is still really cumbersome and automating it would be a nice feature

My use case (if that's important to anyone):
When I have internet access on my devices I stream via the navidrome UI. However, when my internet goes down or I'm travelling with my laptop, I use a local player (Audacious, Foobar2000). It would be nice if these players used the same playlists I've created in Navidrome but I have to keep downloading the playlists from the web UI and manually altering file paths in VSCode.

Being able to sync a Playlists folder across all my devices would be very welcome

@github-actions github-actions bot removed the stale label Mar 8, 2023
@github-actions
Copy link

github-actions bot commented Sep 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Navidrome team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

@github-actions github-actions bot added the stale label Sep 5, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 5, 2023
@Jucgshu
Copy link

Jucgshu commented Nov 25, 2023

I too am interested in this feature. I tried with the API but I don't get consistent results around paths.

Thanks a lot for the work on Navidrome.

Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants