View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019087 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2022-05-19 21:42 | 2026-08-21 13:19 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | feedback | Resolution | reopened | ||
| Product Version | 5.0.4 | ||||
| Target Version | 2027 | Fixed in Version | 2027 | ||
| Summary | 0019087: Duplicate Manager | ||||
| Description | Placeholder--This functionality needs to be specced. Currently duplicate management is a very complex/manual process. MM should have a single tool that allows the user to: - Easily find all duplicates via a combination of existing hash (exact duplicates) and artist/title matching + fingerprinting to help automate the process for finding duplicates that are either similar sounding (different versions) or are missing track metadata. - Visually display possible duplicates in a manner that makes it obvious which items are possible duplicates (e.g. grouping them) - Facilitate selection of which items to retain and which to reject - Automatically recommend which files to retain and which to reject (e.g. via rules based on bitrate, volume leveling, etc.) - Automatically recommend which metadata to retain (e.g. most recently updated track OR merge of metadata OR selection of metadata, TBD) - Allow play history of deleted entries to be merged with the retained entries (e.g. last played should be the most recent date, played # should be the sum of all played # values). - Allow playlists to be automatically updated with the retained entries Additionally, it should be able to handle cases in which the duplicates actually exist AND/OR cases in which there are duplicate database entries (even if the tracks do not exist) Note: usecases could involve: - finding duplicates within a set of selected tracks - finding whether a set of tracks already contains duplicates elsewhere in the library | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3515 | ||||
| related to | 0019083 | feedback | rusty | MMW 5 | Media Properties: Changing Media Drive letter to existing Drive letter create duplicate |
| related to | 0016154 | new | petr | MMW 5 | Use audio fingerprints to detect duplicates |
| related to | 0005800 | new | MMW v4 | Duplicate Content Node Issues | |
| related to | 0005498 | new | MMW v4 | Duplate analysis should occur as a background process & be enabled by default | |
| related to | 0000839 | new | MMW v4 | Files to Edit: Duplicates -- add intelligence to exclude similar but different files | |
| related to | 0000231 | new | MMW v4 | Simplify Duplicate Tracks functionality | |
| related to | 0022117 | resolved | Ludek | MMW 5 | CUE files are shown under 'Duplicate content' node |
| related to | 0021601 | closed | Ludek | MMW 5 | Ability to easily copy file tags and artwork between files |
|
|
What about to add 'Remove duplicates...' as the first item to the context menu for these nodes: Files to Edit -> Duplicate Titles/Artists Files to Edit -> Duplicate Titles Files to Edit -> Duplicate Content Selecting a node (or selection of files) -> right-click -> Remove duplicates... would show dialog like this: -------------------------------- Do you wish to remove 115 duplicates from your library? (o) Delete from the database only ( ) Delete from the database and drive [x] Create database backup [x] Retain files with higher bitrate / quality [x] Join metadata (in case of conflict prefer those with newer timestamp) -------------------------------- Left assigned to me for implementation, then wording can be adjusted by Rusty. |
|
|
Mostly implemented in 3514, just 'Import missing metadata' feature is a to-do.. |
|
|
Implemented in 3515 Added 'Manage Duplicates' to both context-menu and tracklist selection context-menu for these nodes: Files to Edit -> Duplicate Titles/Artists Files to Edit -> Duplicate Titles Files to Edit -> Duplicate Content Resolved for testing. |
|
|
Tested 3520 and this is a really great start! Here's some initial feedback: 1) It's not obvious how to access the functionality a) Right-clicking on any of the duplicates node doesn't display 'Manage duplicates' unless the user has focused on the node beforehand (this is a regression that applies generally to all nodes--right-clicking on them no longer works). b) If the user visits a duplicates nodes, they have to 'Select All', and then use the context menu to access a function that they may not realize exists. It would be preferable if the toolbar displayed a 'Manage duplicates' icon (by the same logic that the playlists node contains playlist management icons) that would apply to all tracks in the view unless more than 1 track is selected. c) We may even want to consider adding this to the Tools menu (following Auto-tag). Thoughts? 2) Text tweaks: a) This action selects duplicates to delete from your library base on the following criteria: --> Choose which of the duplicates to delete based on the following criteria: b) Change the 'OK' button to 'Delete...' 3) Similarity: can you clarify how this is implemented? Is it based on audio fingerprinting for the duplicate content node and on metadata for the other two nodes? If so: - How/when are fingerprints calculated (i.e. I know that hashes can be calculated on scan, but afaik fingerprints were never calculated for my collection previously)? - How is similarity calculated based on metadata? Note: One of the goals of the feature was to eliminate the need/complexity for multiple duplicates nodes. If my understanding of the current design is correct, it continues to reinforces the need for multiple nodes, and we should discuss whether it would make sense to change this. 4) Quality & Format preference order: can you roughly describe the implementation? e.g. is 'format preference' subordinate to 'quality'? 5) Often, there are identical tracks in different locations. Currently, MM will recommend deletion of tracks from one location for some duplicates and from another location for other duplicates (making the library a mess). The spec had indicated using 'Location is in', but a better approach would be to apply the approach you used for format preferences. e.g. [ ] Location preference order _D:/Music,D:/Temp/Download,//NAS/Music,___________________________________________ [Configure...] Note: this preference should follow and be subordinate to Quality&Format preference order 6) 'Import missing metadata' is unclear since it isn't a criterion, and doesn't obviously do anything. Suggested changes: a) Change to 'Copy missing metadata from deleted tracks' b) Move it to the bottom-left (same level as OK/Cancel) c) Highlight copied metadata so that it's visible (same as how this is done in the Tag from filename dialog) 7) Do you think it would be useful to be able to use headers for sorting? e.g. I wanted to see all 'Beatles' duplicates together. The issue is the all dups in a group may not have the same value, so which track would be used for sorting purposes? |
