Hi, ok, I think I know where the problem lies.
The problem is that MM5<>MMA sync was not designed for MMA sync with multiple MM5 instances and what happens here is that:
1) The previously synced playlists from MMA to the work computer are also auto-added to the sync-list from the work computer to the MMA therefore in the log I see also copying back (MM5 -> MMA) playlists like
\Playlists\All Collections.m3u
\Playlists\Added from Galaxy A12 on 2021-12-06.m3u
\Playlists\Chorus-Bridge Counterpoints.m3u
BTW: Uploading the file '\Playlists\All Collections.m3u ' took more than 2000 seconds!! This is quite curious, there wasn't MTP error but it seemed to stuck for such a long time (for some reason). I remember that such a freeze can happen when a file is deleted on Android and it internally refreshes the content somehow making the transfer protocol to freeze (+ also Windows Explorer is frozen)
2) The main problem causing mixing the track is calling CheckTrackIsPaired during the sync where MM5 is trying to find whether the track exists based on MMW.track.ID in the MMA's database and if it does not exists then it updates the MMW.track.id in the MMA's DB based on the track path.
BUT because you sync also with another instance of MMW then the MMW.track.id can get totally mismatched !
This issue is tracked as
https://www.ventismedia.com/mantis/view.php?id=9941 for a long time in Mantis, but has never been implemented.
So unless #9941 is implemented then I am afraid that the only workaround is to not sync MMA with multiple MMW instances, and either:
- sync just with home computer and manually copy the content to the work computer from MMA (i.e. not sync with work computer)
- or sync just with the work computer and manually copy the content to the MMA from the home computer (i.e. not sync with work computer)
Hi, ok, I think I know where the problem lies.
The problem is that MM5<>MMA sync was not designed for MMA sync with multiple MM5 instances and what happens here is that:
1) The previously synced playlists from MMA to the work computer are also auto-added to the sync-list from the work computer to the MMA therefore in the log I see also copying back (MM5 -> MMA) playlists like
\Playlists\All Collections.m3u
\Playlists\Added from Galaxy A12 on 2021-12-06.m3u
\Playlists\Chorus-Bridge Counterpoints.m3u
BTW: Uploading the file '\Playlists\All Collections.m3u ' took more than 2000 seconds!! This is quite curious, there wasn't MTP error but it seemed to stuck for such a long time (for some reason). I remember that such a freeze can happen when a file is deleted on Android and it internally refreshes the content somehow making the transfer protocol to freeze (+ also Windows Explorer is frozen)
2) The main problem causing mixing the track is calling CheckTrackIsPaired during the sync where MM5 is trying to find whether the track exists based on MMW.track.ID in the MMA's database and if it does not exists then it updates the MMW.track.id in the MMA's DB based on the track path.
BUT because you sync also with another instance of MMW then the MMW.track.id can get totally mismatched !
This issue is tracked as https://www.ventismedia.com/mantis/view.php?id=9941 for a long time in Mantis, but has never been implemented.
So unless #9941 is implemented then I am afraid that the only workaround is to not sync MMA with multiple MMW instances, and either:
- sync just with home computer and manually copy the content to the work computer from MMA (i.e. not sync with work computer)
- or sync just with the work computer and manually copy the content to the MMA from the home computer (i.e. not sync with work computer)