View Issue Details

IDProjectCategoryView StatusLast Update
0015849MediaMonkey 5Synchronizationpublic2020-08-05 00:01
ReporterLudek Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version5.0 
Target Version5.0Fixed in Version5.0 
Summary0015849: GPM sync: Split config for metadata syncing into two directions
DescriptionCurrently 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
TagsNo tags attached.
Fixed in build2191

Relationships

related to 0014983 closedLudek Cloud sync: further sync/scan sub-options 

Activities

Ludek

2019-07-30 11:37

developer   ~0054239

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.

Ludek

2019-07-30 11:39

developer   ~0054240

Last edited: 2019-08-06 14:50

View 2 revisions

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

peke

2020-08-05 00:01

developer   ~0059234

Verified 2262

Looks Ok for me now.