View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008808 | MMW v4 | Synchronization | public | 2011-12-05 05:02 | 2013-06-20 13:40 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.1 | ||||
| Target Version | 4.1 | Fixed in Version | 4.1 | ||
| Summary | 0008808: Improved bi-di sync implementation | ||||
| Description | For MM 4.1, we should improve the bi-di sync implementation so that MM has an accurate representation of all device contents. See #8677 for summary of compromises in initial implementation. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1607 | ||||
| related to | 0008705 | closed | jiri | MMA | Synchronization UI |
| parent of | 0009106 | closed | Ludek | MMW v4 | Track matching based on metadata |
| parent of | 0010097 | closed | jiri | MMA | Sync can delete unexpected tracks |
| related to | 0001350 | closed | rusty | MMW v4 | Portable Device: Bidirectional Synchronization |
| related to | 0010958 | closed | Ludek | MMW v4 | Files copied from device -> PC are recopied when deleted in device |
| related to | 0011279 | closed | marek | MMA | Bidi sync can be confusing |
|
|
Most notably http://www.ventismedia.com/mantis/view.php?id=8677#c29226 b) should be implemented and c) be reverted. |
|
|
Note that recent discussions over IM revealed that even b) isn't such a good idea. The most significant problem is that it requires the playlist then to be also created on the device. We suggested the following implementation together with Ludek: d) In case some tracks are synced from a device to PC a new node below Playlists in Auto-Sync dialog for the device is added: [x] Individually selected tracks {or some much better wording} This node would list all the tracks that were anytime in the past synced from the device. User could uncheck them individually or all of them and they would disappear from this node then (after Okaying the change). |
|
|
OK, just the 'Individually selected tracks' isn't really a good wording, because it should indicate the tracks synced from the device. So something like 'Files synced from the device' would be better. |
|
|
Note that futher conclude is that only the tracks with different metadata should be copied back to PC. i.e. If a track with the same metadata exists on the PC, then it is just added to the 'Synced from device' node. Otherwise it is copied to PC and added to 'Synced from device' node (issue 0009106). |
|
|
Fixed in build 1600. |
|
|
Verified 1605 |
|
|
The 'Synced from Device' functionality is quite confusing as it's unclear what it represents, why it's automatically created, why the tracks in it get selected in the auto-sync list, and how it relates to the 'Auto sync --> Library' functionality. Comment from Jiri: Actually, do we have to change anything? We are probably in agreement now that the new node isn't really needed to be visible to the user - i.e. all the related handling will only be internal, transparent to the user. However, this seems to be the only change needed. As for metadata sync, it probably can remain as it has always been - i.e. always working, regardless of bi-di sync setting. We could consider a switch for this in the future, but it probably ins't really needed. Ludek's response: We can hide the node, but then a) user will not see which tracks were synced from device b) the tracks will be internally presented on sync-list, but user has no chance to remove them from the sync-list Maybe as Rusty previously suggested, we should just move the node from [Library-->Device] to [Device-->Library] tab? Comment from Rusty: Assuming that Jiri was referring to the cases where MM currently automatically adds tracks to a hidden auto-sync list because bi-di sync is enabled, but auto-sync isn't; i.e. for the following cases: case b: bi-di sync enabled for track on device, track exists in library, is not enabled on users auto-sync list case d: bi-di sync enabled for track on device, track doesn't exist in library We could deal with Ludek's objections as follows: Re. objection a): - Ensure that default settings are such that tracks that are _newly added_ to the library, but not those that are on the hidden auto-sync list because they fit into case b i) appear in the 'Recently added' auto-playlist ii) trigger creation of new playlists if the existing 'Create new playlists...' option is enabled (e.g. 'Added from {Device Title} on 2012-11-14' ) - Ensure that the default settings are such that 'Confirm updates (recommended)' is enabled by default, and that when enabled, if the user declines to have tracks copied to the device, then the tracks aren't added to the hidden auto-sync list Re. objection b): - Ensure that tracks are removed from the hidden auto-sync list whenever the user removes tracks from the 'Auto-sync-->Library' list. i.e. if the user changes the config of the 'Auto-sync-->Library' list, then the hidden auto-sync list should be 'recalculated' If we go this route, then the only UI/String specific changes that are required are: 1) removal of the 'Synced from device' node 2) new string for newly created playlists ('Added from {Device Title} on 2012-11-14') Conclusion from Ludek: OK, we can go this way, but there are still some usability tweaks (probably not a big deal though): - the tracks originally on the device and in MM library will be still invisible to user - user can remove the tracks from sync list just by deselecting whole folder (there is no way to remove a track individually) - user cannot deselect them in MMA These usability tweaks are not probably a big deal so if also Jiri agree then we should go this way. |
|
|
Resolved in 1607. |
|
|
Verified 1615 |
|
|
Closing all other issues are reassigned accordingly |
