View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009818 | MMW v4 | Synchronization | public | 2012-10-12 17:17 | 2012-10-13 09:06 |
Reporter | Ludek | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
Target Version | 4.1 | ||||
Summary | 0009818: Enforce use of sync mask for files already on the device should be enabled by default | ||||
Description | Currently, if you go to Device->Options->File Locations the checkbox [ ] Enforce use of sync mask for files already on the device is unchecked by default, which means that if user changes the destination masks then only new tracks are synced to the new locations and already synced tracks remain in its old place. I guess that the default behaviour should be that all tracks should be moved according to the current destination mask. i.e. the checkbox should be enabled by default | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
I'm a little reluctant, because that means that MM would make changes to the users tracks without the user necessarily being aware. Also, I believe that it was left disabled by default so that sync operations don't always re-sync all files when the only change is the sync destination (a single change could trigger hours and hours of synchronization). What's the downside of not doing this, from a functional perspective? Also, to confirm: the function only move tracks that match the auto sync list criteria (ie it doesn't move tracks that aren't on the sync list or those not in the library)? |
|
OK, thinking about it further, you seem to be true. So most probably we should leave it as is, resolving for now... The downside of the current default is related to 0006343 where it makes problems when using the <Auto Number> mask on playlists. Because the mask doesn't take effect for tracks already on the device or when playlists are re-ordered. |