View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015849 | MMW 5 | Sync | public | 2019-07-30 11:31 | 2020-08-05 00:01 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0015849: GPM sync: Split config for metadata syncing into two directions | ||||
| Description | Currently we have config: "[x] Sync GPM metadata with the library" which means bi-directional sync. i.e. if you change a rating of a track in MM library then it is propagated to the cloud (GPM library) and vice-versa. But in case of GPM users are worried that the data on the Google's server/database could be corrupted or modified by Google services/uploaders and this data could get back to their perfectly tagged MM library. So they prefer only one direction (MM > GPM) metadata sync by default. Details at: https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=94858 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2191 | ||||
|
|
I can understand that specifically for GPM sync it is desired to split this config and make two configs (for each direction). Which doesn't make much sense for the other cloud types (OneDrive, Google Drive, Drop Box, MMS) where we explicitly use MM metadata storage databases and have full control over it. |
|
|
Thinking about it further we could just: 1) change the "[x] Sync GPM metadata with the library" into "[ ] Sync GPM metadata to the library" (disabled by default) 2) Move the checkbox above and under the '[ ] Scan GPM content to the local database' checkbox 3) Always sync the metadata in the MM > cloud direction => Implemented in 2191 |
|
|
Verified 2262 Looks Ok for me now. |
