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

Remove or rename files from ibroadcast #6

Open
catap opened this issue Sep 18, 2021 · 2 comments
Open

Remove or rename files from ibroadcast #6

catap opened this issue Sep 18, 2021 · 2 comments

Comments

@catap
Copy link
Contributor

catap commented Sep 18, 2021

Is it possible to remove or rename files from ibroadcast when I delete or rename it from local beets collections?

Thanks.

@ctrueden
Copy link
Owner

@catap Good questions!

As written currently, when you rename a track in beets, that should bump the mtime, which should trigger beets-ibroadcast to delete your old track and reupload the new version the next time you run beet ibroadcast <query> with a matching query. I haven't tested it, though. Curious to hear whether you have success with that.

As for deleting: there is currently no mechanism to delete a track from iBroadcast in response to the track being deleted from beets. One way we could accomplish that would be to listen for item_removed and delete the iBroadcast track in response.

If the event-based approach works well for deleting, we could potentially also use it for renaming or other metadata updates—the after_write function looks promising for that.

I don't have time to implement these changes now, but we can leave this issue open as a reminder. And of course, PRs are welcome any time if you have the time and interest to work on such things.

@catap
Copy link
Contributor Author

catap commented Sep 19, 2021

@ctrueden thanks to make this clear. I can try to implement it, but I have no idea when I'll have time to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants