Persistent IDs in the database
Track entries and playlists have no persistent IDs in the Rhythmbox database, which means third-party apps cannot reliably find a song after e.g. its file has been renamed/moved.
Assigning "persistent" IDs to each track or playlist would be a way to make third-party apps resilient to such renamings. I'll try to implement this myself and make an MR, unless you think that would be a bad idea?
Context: I'm developing StarSync, a tool that I may well be the only one to use, which syncs media players to Android devices.
It currently supports iTunes (and uses iTunes' PersistentID
s to keep track of playlists and songs), and now I've moved to Linux, I'd like to make StarSync support Rhythmbox.
I can achieve almost what I want through D-Bus, through which Rhythmbox exposes DB entries...but their D-Bus paths are not persistent, and they change everytime Rhythmbox restarts. I'd like to improve this