I think it's an awesome idea. Make it happen Cap'n!
...I had duplicate files. So after adding a file compare when a collision was detected I had exactly 0 collisions.
When I read through the thread my mind immediately went to duplicates; Many people are IR crazy and immediately load their library of them, not understanding that the factory cabs probably already contain many of them.
Cliff (
@FractalAudio) said the factory cabs wouldn't need to be included in the hash because they don't change, but, because of the possibility of this duplication, I think it'd be useful if they were, and that all the duplicates found were reported so that the user is at least aware that slots are being wasted. If they were summarized in a table and we could mark whether we want to keep or toss the duplicates, along with choices like "Keep 'em all", "Delete all non-factory duplicates", "Delete this duplicate", "Delete all other duplicates", "Print the list", "Open the pod-bay doors", etc., we'd have a great tool to reduce duplication and save wasted space.
And, if part of this was to point to the factory version but allow a custom name I think people would find another use for the hash since some of the factory names are pretty cryptic. Yeah, I know, use our ears but some people want to use their eyes.
I imagine this process could be similar to how the Editor walks the block and cab definitions when it encounters a new firmware, or can be triggered manually when the user has added additional IRs/Cabs.