[sciurius]

@Mike: "As far as synchronizing collections and setlists, that's already handled if you check the "Sync groups" option."

I think I did not express myself correctly. What I meant was to limit the sync to songs that belong to a selected collection. But I already came to the conclusion that that would be pointless.

I consider synchronizing to be something that happens between devices that have more or less identical song collections[1]. For example, I make a backup on the master device and restore that on the slave device. After that, when I make changes to the master, I can sync them to the slave and/or vice/versa.

So the songs on both the master and slave will have the same properties and these can be used to identify songs that have non-unique names. For example, the properties name, collection, source and key are very likely to uniquely identify a particular song. But it would also be possible to generate an unique id (uuid) when creating a song, and use that id to find matches.

In addition, it would be nice if I could say: copy (not sync) the complete database from this device to the slave. This would be equivalent to (but much easier than) making a full backup on the master, copy it to shared storage, and restore from the shared storage on the client. When you assign master and slave a uuid you can verify that the client has a sync of the master, and therefore you can use song uuid for matching. You may even disallow synching with an unknown client.

[1] An exception may be the physical file paths but there's already a path mapping facility.