Beta version 1.7.0

[Admin]

Similarity 1.7.0 build 1307 (Beta version) (Updated 2012.04.03)

Download

- New image comparing algorithm, first implementation, finds only resized,colored duplicates, not similar images



- New grouping mechanism in Image results, all groups are builded even if one pair suitable.



- New automark field in Images, folder priority, you can select folders what more preferable for deletion



- Groups identifier and real-time sorting (new duplicate pairs added already sorted) (Updated 2012.04.03)



- Executable size reduced from 1302 build. (Updated 2012.04.03)

- Minor fixes (options saving, folder browsing)

[hsei]

The new Feature "image duplicates" is quite nice even in the current beta stadium.
Some remarks:
- sorting by click on row header does not work
- folder list for deletion priority is inadequate: When you have folder trees (as usual), resorting half of the list is much too tedious. A click on a directory with the option a) keep all files in tree b) remove duplicates in this tree would be sufficient. To be effective, parent directories of (more than one) subdirectories with duplicates should be listed, too.
- the new group list feature with the ability to expand/collapse may be useful in some cases, but the default view should be "expanded" because I want to know what is in the group and e.g. has been marked automatically.
- to list all duplicate groups may be useful in some cases since similarity is not necessarily transitive, but only if there are more than two duplicates. If there are only two duplicates it is sufficient to list them only once (A <sim> B => B <sim> A)
- a similarity score of almost 100% should not be given if images are "almost identical" but have very different size. At least for JPEG images, size is a strong indicator of quality (compression ratio). Sometimes it may be an option to delete the larger image with the same origin, but not without any warning.

[Admin]

Thanks for your message,
1) Sorting not implemented yet
2) this not simple, all folders on bottom selected to delete, where can duplicates in folders what you doesn't selected by your method, and system stores all your selection of priority.
3) we set groups more visible in next builds, but now you don't need to expand specific file, all groups shown by different background color.
4) scores method will changed in future this is first version

[hsei]

ad 2) To do this, you need a standard treeview window and the possibility to select a root directory in it.
After that you select whether all files in that tree have to be preserved or if files in that tree may be deleted.
Now you can search through your groups and mark those files that may be deleted or exclude those files from marking that should be preserved.
This can be done by a simple substring comparison of the full file paths vs. the selected root directory.
Under the assumption that folder was the top priority, the other criteria might then be applied to the remaining files.
Of course at least one file per group should be kept.
ad 4) Compression ratio should be a criteria in the priority list (if not included in score calculation).
Size is an indicator for that, too, but only if resolution is identical.

[rocco]

As to me, I'm not sure if you're going the right way. Similarity was always meant to be music duplicates searching tool, even site name is "music-similarity". Why did you decided to implement image searching? Maybe it would be a better solution to make a separate app for image dupes? Also with all the new features file size got 2.6 times bigger than previous version. Personally I will stick with 1.6.4 version, even if it will be no more supported. Either way thanks for what you did so far.

[Admin]

As to me, I'm not sure if you're going the right way. Similarity was always meant to be music duplicates searching tool, even site name is "music-similarity". Why did you decided to implement image searching? Maybe it would be a better solution to make a separate app for image dupes? Also with all the new features file size got 2.6 times bigger than previous version. Personally I will stick with 1.6.4 version, even if it will be no more supported. Either way thanks for what you did so far.

It's only beta, we know about executable size and trying to resolve problem, we using Intel libraries for speedup and problem in them.
We added image comparing beacuse too many request for such feature, this is not very hard because we didn't do complex algorithms, and you always can disable image comparing via Options.