View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018598 | MMW 5 | Sync | public | 2021-11-29 19:42 | 2022-09-14 14:39 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 5.0.2 | ||||
| Target Version | 5.2 | ||||
| Summary | 0018598: MediaMonkey to MediaMonkey Sync | ||||
| Description | Users with multiple PCs would like to have all MediaMonkey installs in Sync. This would involve: 1) Sync media files bi-directional 2) Sync metadata changes bi-directional 3) Sync Playlists bi-directional (where AutoPlaylists remain AutoPlaylists). | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=33&t=100823 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This is something that should be done with MMS as Middle man eg. Init Master MM5.DB on MMS and all other MM5 installations should import that one and add own. I personally think that this is something for MMS not MM5. Assigning to Jiri for review. |
|
|
Martin is actually suggesting that MMW<-->MMW sync should be possible _without_ MMS running on a separate server (MMS could be run transparently on the MMW server, but that's a technical issue--the point is that users are asking for the possibility of syncing MMW instances). |
|
|
I'm with Peke on this one, having MMS for this purpose makes things easier to develop, but also to understand (how to resolve various sync-conflicts, etc.). The functionality could evolve to satisfy Rusty's point, but I'd definitely start simply with MMS (which should actually already work, at least somewhat, more testing needed). |
|
|
BTW: The MMS sync already works with multiple MM5 instances (including auto-playlists) -- at least it worked once I implemented it several years ago ;-) |
