Here’s a picture
(I’ve chosen it but it’s not appeared here, if it doesn’t appear when I post this I hope there’s an editing function. I’m not good at this kind of thing!) Anyway.
DupeGuru’s kept one file from what it thinks is each group of the same files. The problem is, it doesn’t seem to have realised some of the others in the group marked for deletion have different extensions to the file it’s keeping. I want it to keep one file from each sub-group of different extensions, so for instance if I’ve got three files named Thisfile.abc, three named Thisfile.def and 3 named Thisfile.ghi, it keeps one of each extension group. Right now it’s keeping one copy of Thisfile.abc and marking for deletion ALL of the .def and .ghi files, even though they only share the same name, NOT the same extension.
Is there a way of telling DupeGuru to keep one file from EACH extension subgroup? The files might be the same name and within the same size range, but they are different and the system needs one file of each extension type to make the main file usable. They’re virtual instruments, so flute.abc would be the software instrument the package loads up, flute.def would be the samples associated with that instrument and flute.ghi would be the articulation settings the software would use when you asked it to. So the same main name, similar sizes but different extensions. That’s why I need DupeGuru keeping one of each extension type.
How do I make it count different extension types as different files, so it keeps one of each of the subgroups along with the blue one from the main group, so I end up with a collection of sets, flute.abc/flute.def/flute.ghi, oboe.abc/oboe.def/oboe.ghi and so on? I messed up downloading the orchestra bigtime so I’ve ended up with a LOAD of copies of different instrument sets! But I need one complete set of each instrument.
Hope the above is clear and hope the picture I’ve chosen turns up when I post this.
Yours respectfully,
Chris.
