Loading Profile...
EMPLOYEE
How does dupeGuru determine file priority?
How does dupeGuru decide which file gets to go in the reference position of the duplicate group? Is it possible to change that?
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?By default, the biggest file is the file that's going to get the reference position (the file that is going to be kept). It is not possible to change the way dupeGuru prioritize this file during the scan, but it is easy to re-prioritize files after the scan using a the Power Marker and the Delta Values together.
The Power Marker mode makes dupeGuru hide the reference files, and the Delta Values mode makes dupeGuru display certain values (size, modification time, duration (in ME), etc..) relative to the reference file. For example, if a dupe is 100kb and the reference file is 150kb, the size column in delta mode will show 50kb. If the dupe is 150kb and the reference 100kb? -50kb.
Therefore, if for example you want to have only the files with the latest modification date to be kept, you would sort by modification date (under delta values mode). Then it will be easy to select all files that have a positive delta (it means that their modification date is higher than the reference's), and then use Make Selected Reference.
It might look complex, but once you get the hang of it, it's easy and logical (sort and process).
The company says
this answers the question
-
Inappropriate?When DupeGuru Music Edition has candidates for duplicate files, I've thought of one thing that makes a big difference in weighing which should be the reference. If their quality is the same or nearly so, the more deeply nested items should be given greater precedence. The logic behind it is that files buried deeply in subdirectories have a greater relative weight of "intelligence" attached to them through user organization/categorization.
Some MP3s have a few extra seconds of silence while others have perhaps an artist or album image embedded in them, but when the primary consideration is sound quality, a few bytes more or less have little bearing on the choice of reference. Bit rate and duration are much more important, and when they match then levels of nesting in the directory tree could play a part.
As an example, I keep new unsorted files just a level or two below the root, while audio collections go fairly deeply. This is not something that is easily sorted in a columnar fashion since it's an alphabetic sort method, and sorting on that alone would invalidate more important file attributes.
I’m unsure
1 Comment Add a comment
This answers the question
-
There is a thread here about prioritization where I'm trying to put together all possible rules for a smarter prioritization. It would be nice if you would comment there instead.
