View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011378 | MMW v4 | Synchronization | public | 2013-10-17 14:17 | 2014-03-05 08:20 |
Reporter | Ludek | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | 4.0 | ||||
Fixed in Version | 4.1 | ||||
Summary | 0011378: Files with same metadata are skipped during synchronization | ||||
Description | This is a a long standing behaviour, but was hardly noticed until we added the new log message in course of 0006219:0037812 : 'File %s was skipped, because it points to the same device location (%s) as file %s' I've just tested it with my iTouch 5 and MM reported sync problems (see attached screenshot). I have songs with same metadata, one song is from LIVE concert and the other is album song, MM auto-synchronizes only one of them in that case. Using "Send to -> Device" all songs are copied. 1) For Apple devices the log shouldn't be shown in such a cases, because mask config is not shown for iOS devices at all and MM respects the Apples file structure (a non human readable form). 2) Eventually all songs should be synced to Apple devices in such a case. Althought it is debatable, because it would result in dups when navigating the device (might be undesirable), so I would rather leave it as is for now, because user can use "Send to device" if he wants to have dups on iPhone, or tag the songs properly (e.g. add '(live in Vienna)' appendix to the album name). | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 1665 | ||||
has duplicate | 0011913 | closed | Ludek | Duplicate Titles fail to sync to Apple devices |
related to | 0011772 | closed | Ludek | Some tracks that MM mistakenly considers as duplicates fail to sync |
child of | 0011321 | closed | Ludek | Playlist contains duplicates when more tracks point to the same location on the device |
child of | 0006219 | closed | Ludek | Synchronization errors should be logged |