View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012691 | MMW v4 | Synchronization | public | 2015-03-30 15:16 | 2015-03-31 23:54 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 4.1.6 | ||||
| Target Version | 4.1.7 | ||||
| Summary | 0012691: Send to (Synchronize) is confusing | ||||
| Description | Users using the Send to (synchronize) function seem to: - end up with duplicates (http://www.mediamonkey.com/forum/viewtopic.php?f=26&t=80330 ) - missing album art (http://www.mediamonkey.com/forum/viewtopic.php?f=26&t=80330 ) - tracks being synchronized needlessly ( http://www.mediamonkey.com/forum/viewtopic.php?f=21&t=80361 ) This is probably because this function actually doesn't update the sync database in the same manner as Auto-sync does. Possible approaches: 1) change the functionality so that when this function is used with an Android device, it updates all aspects of the device exactly as Auto-sync does 2) Change the wording to Send to (Device). However, this isn't a great solution either--as users will no doubt still experience sync problems. I suspect that this functionality may be the root cause of many Android sync problems that are being reported. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Send to (synchronize) is updating database etc. same way as the Auto-Sync, the only difference is that the tracks aren't added on sync-list (es expected) and might be re-copied (as expected) And if a user change the sync masks (target paths) then they will result in duplicates on re-sending (as expected) |
|
|
I do not see the bug here but rather feature. From my tests Only thing I would add is that even user initiate sync with using send too MMW sync it to device like Auto sync is executed (Conversions, naming, etc. based on profile) but like Auto Sync is executed/set to sync only these selected files as that way duplicates will be ignored as MMW will not sync paired files. As files already on device will not be in expected folder, maybe just maybe it could be wise to add single Playlist on device named "Manually Synched" to gather all tracks that were synched that way. I'm suggesting this as ther was number of requests to make possible that user can flag some tracks to be in auto-sync directly from MMW library and not explicitly set in Device sync profile. Also maybe an additioonal option "Manually synched" check box in Sync to device that will comply newly created playlist and allow user to exclude them in next autosync. Ludek, Rusty am I getting this correcly in thinking that this approach would not stray from current design and make things more clear and easier to track and manage. |
|
|
I agree that eliminating the '(Synchronize)' appendix would be less confusing. i.e. just Send to -> [My Device] instead of current Send to -> [My Device] (Synchronize) The fact that it uses settings from the profile when sending (Auto-Conversions, target path configurations, etc.) is OK, because these are under the 'Options' tab on the device profile (indicating that it is general device settings). It is also correct that the things configured on the 'Auto-Sync (-->Device)' and 'Auto-Sync (-->Library)' are not applied when using "Send to", i.e. no file deletions, no metadata sync for files on the sync list etc. As for the Peke's idea of adding another option for creating a playlist for manually synced files (to be auto-added on sync list). I think it would unnecessarily complicated the UI further. And I don't see a need for this, because user can create a playlist anytime, add it to sync list and then he can use 'Send To -> Playlist' instead of 'Send to -> [My Device]' But based on the forum posts I have an impression that there is lack of the documentation for the users. We could add a summary dialog showing at the end of sync (like in MMA) e.g. "Copied 6 tracks" etc. but it probably wouldn't help much, better choice would be to add a synchronization Wizard or a better documentation. So this is more about issues like 0011490 (lack of documentation) |
|
|
SEND TO behavior framework for Devices: 1. Instead of "Send to -> [My Device] (Synchronize)" put it as "Send to -> [My Device] (Copy)" which is correct description for the behavior and function 2. As there is no way to tell where user will SEND TO selected tracks user just select "Send to -> [My Device] (.....)" Profile settings should apply like Auto-Sync is set only to sync Selected tracks (ignoring Delete Content that is not on sync list) 3. Under "Auto-Sync (-->Device)" -> Collections we should add "Manually synched" Check box so that those manually synche files would not be deleted if "Delete Other files and Playlists ...." is selected. Which will act like single static playlist (Created also on device)containing files that user either D&D to device or used Send to. By adding this user will have direct access to files he manually Synched to device (Like Ringtones or few favorite tracks) 4. In case that user wants to manually sync Large Number of files MMW Should suggest to Create new Static Playlist and add it to Auto-Sync list as this is not normal behavior for large number of files and Send To is not designed for using to sync to device but rather Send single or few tracks to device. 5. profile settings should be always applied 6. even user manually send track to device MMW should check for for existing track on device and not sync if exists and avoid duplicates More clarification on Above points in relation to existing reply 0012691:0042388: 1. Simple "Send to -> [My Device]" is not descriptive enough as it can be understanded as MOVE also 2. Not once in past few months I have fixed sending of FLAC using Send (or Copy/Paste) to iPod Which results in Copy of FLAC track with Full Long path onto "/ipod_control/Music/" which render track non playable and user complain (often request refund) last one was observing issues described in 0012688 made 27GB of non usable tracks which would be all avoided if profile settings were applied and tracks wer normally converted named. 3. As pointed in 0012691:0042388 "...user can create a playlist anytime, add it to sync list and then he can use 'Send To -> Playlist' instead of 'Send to -> [My Device]'" which I end in Suggesting to users even for example on 64GB sync list it can take time to Sync few tracks that user want to sync Manually and not interfere with regular Auto-sync (like only single Podcast episode from podcast he is evaluating without setting whole podcast to be sync, but if he/she likes it than an whole podcast can be added later). So instead of "Create playlist -> Send to playlist -> Auto Sync" user would only do "Send to -> [My Device] (Copy)" and track would be positioned itself where it should be and be easily managable/excluded from next Sync under "Auto-Sync (-->Device)" -> Collections we should add "Manually synched" istead of going thrum process of Managing Playlist, than excluding playlists from Sync Profile, than Do Auto-Sync. Also Simple tooltip "Manually Sync represent all tracks that were at some point manually synched to device and selecting this option will ensure that these tracks are always synched to device. Reffer to list in order to manage them" should clear any doubts what the function mean. And under Listing there should be "[x] Create corresponding playlist on device to reflect manually synched tracks" this also eliminates of need for Summary dialog and sync wizard on Send To. 4. As pointed of lack of documentation users often make mistake select 1000 of tracks and use SEND TO -> [DEVICE] to do a actual sync that results of hour of syncing without any means to manipulate and handle duplicates 5. Although Android devices do not suffer that behavior (large number of formats supported and Scan storage processes) Apple devices like iPod Classic suffer due the namings, lack format support and high dependencies on device SQLite library, but can be also the case for Car head units, GPS navigations, ...) 6. If user is heavily dependent on Manual sync of tracks it is very very Easy that in Manually Sync track selection there is a bunch of duplicates |
