View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0016063 | MMA | Synchronization | public | 2019-10-27 22:26 | 2024-09-30 23:37 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 2.0.1 | Fixed in Version | 2.0.1 | ||
| Summary | 0016063: Sync: Enforce Mask do not work | ||||
| Description | If User Sync WiFi while Using Enforce Mask for existing, then Mask is not enforced. Only New syncs have correct mask. Attached picture with: - Sync settings and Mask from MY MMW - Track Properties/path Mask before WiFi Sync - Confirming that after WiFi Sync all is in sync - Log ID Sent after confirming that Track Properties/path is same eg. Track path not enforced | ||||
| Additional Information | BUC-687-40284 https://www.mediamonkey.com/forum/viewtopic.php?f=12&t=95238 https://www.mediamonkey.com/forum/viewtopic.php?t=105928 | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1203 | ||||
| duplicate of | 0012027 | closed | martin | MMW v4 | WiFi Sync: option 'Enforce use of sync mask for files already on device' doesn't take effect |
| related to | 0013350 | closed | martin | MMA | Implement sync progress and sync result activities using ORM and data binding |
| has duplicate | 0019986 | resolved | martin | MMA | Enforce Mask on WiFi for existing files should be low priority in background |
| related to | 0020942 | closed | martin | MMA | Force files to resync whenever the source files have changed |
|
|
I) If possible do it in background after sync is done so that user can continue using device? II) Maybe add similar dialog to one we use for skipping scan on device startup as it stress the device? IIa) Also it could be wise to add battery watch so that it starts when charging to optimize battery usage? |
|
|
1)MMW has to add "Enforce" flag to DeviceConfig.xml 2)when the flag is set, MMA has to rescan the entire library track by track and for each track compare old path with a new path (path depends on track metadata) 3)If paths differ, then track should be added to the list to confirm by a user. After confirmation, old tracks should be deleted and new tracks will be downloaded to new paths(and with new filename). 4)This is not a trivial operation and should be postponed to 2.0.x version. Also, 0013350 will be useful for this issue. |
|
|
Fixed in build 2.0.1.1200 |
|
|
Why tracks are re downloaded, wouldn't MOVE file be better solution? FYI functionality is Verified in 1201 |
|
|
Files are moved under normal circumstances, however files were re-downloaded in specific cases. Fixed in build 2.0.1.1203 |
|
|
Re verified 1214 |
