rusty wrote: ↑Mon Sep 18, 2023 4:48 pm
When you initiate the WiFi Sync operation after a couple of months, does MMA find and recognize the MMW Server? OR does the sync fail and then you're forced to sync to a 'New server' (even though it's the same server except that the client or server have a different IP address)?
MMA recognises the MMA server w/o requiring any assistance.
Also it is just tracks|albums that disappear from the Sync Tree in "Sync List (Library->Device)" in D&S tab. I also synced a playlist. The playlist remains recognised as being synced.
Barry4679 wrote: ↑Sat Sep 16, 2023 7:51 am
Or was it the MM5 File>ManageDatabases>Rebuild that I accidentally triggered a few weeks ago when researching something for someone on the forum? ... A DB Rebuild shouldn't wipe out the sync status should it?
I am now convinced that a db "rebuild" is what triggers this problem.
I have just triggered another rebuild, and the sync tree is empty again, except for the playlist that I had synced.
There should be a rebuild step which conserves the sync status during a rebuild process. Maybe it is a bug, because the status of playlists seems to be protected.
IMO there should also be a procedure to recover the sync status if it becomes confused at the MMW end.
The target location contains a database describing the contents that it received via sync.
It doesn't seem a large stretch to get that db from the device, and then rebuild the MMW db sync flags via a track ID match, or tag match.
It is a lot of work to transcode and sync a large collection, especially to a network location. It would be better if that work can be better protected.