You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Is it possible to remove or rename files from ibroadcast when I delete or rename it from local beets collections?
Thanks.
The text was updated successfully, but these errors were encountered: