View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001583 | MMW v4 | Synchronization | public | 2004-11-09 03:23 | 2004-11-10 14:04 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Fixed in Version | 2.3 | ||||
| Summary | 0001583: Auto-Synchronization - Duplicates: should copy one of each | ||||
| Description | When the user Auto-Synchronizes and there are duplicates among the files to be copied, the following message occurs: 1) "The following, which are slated for synchronization have duplicate path and filenames and will not be copied:" The text and associated functionality should be changed to: "The following tracks have duplicate path and filenames, and only one of each set will be copied." 2) The duplicate files are not separated in any way. What should happen is that there should be some divider between the sets of files that are in duplicate. 3) It would be nice if there were checkboxes or radio buttons to the left of the tracks so that the user could select _which_ of the tracks should be copied. In this case, the wording should be changed to: "The following tracks have duplicate path and filenames, and only the selected one of each set will be copied." | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I don't think that this would improve the process mainly for the following reason (and actually I have at least one other reason): - This is a kind of an error message, although we let user to continue he should fix either the mask, or the selection of tracks or their metadata (or all of this) in order to proceed properly. For example if user doesn't have artist and title filled in for several tracks, all of them can result in the following filename: P:\Unknown\Unknown - Unknown.mp3. It such case there doesn't make sense to export one of such tracks, I think it's more logical to not export anything and fix metadata (by user). |
|
|
But in the following cases, which I expect will be most common, it would be far more beneficial if the app copied at least one of the tracks: a) if the user has Beatles-Help! and Beatles-Help! (one of them is live the other isn't) b) if the user has Beatles-She Loves Me and Beatles-She Loves Me (actual dups) |
|
|
If this should be at least a bit useful, the setting you propose would have to persist and I don't see a way how to do it (output masks can change, etc.). I still believe that the best solution is to only warn user about duplicates and let him do necessary changes in used masks (e.g. if user exports using Location node, this situation cannot happen). |
|
|
I see. Sounds like a not easily solved problem that definitely isn't worth the effort. |
