Igir show and tell megathread!

[emmercm]

I created the "personal usage" documentation page to show off how I personally use igir with my own ROM collection. But that page only shows one person's needs, when so many other use cases could be solved with igir.

I would love to see how you use igir with your own ROM collection!

Some information that would be helpful to include:

• The entire set of commands and options used, including if you have to run igir multiple times
• Your process for initially sorting your collection
• Your process for incrementally updating your collection
• What devices (flash cards, emulation handhelds, etc.) you use with your collection

To keep discussions clear, please use separate comments for separate use cases, and make use of the "reply" feature to respond to someone's use case. Thank you!

[tnvu]

I'm still figuring out my workflow, but for now.

1. I have the ROMs I want to organize.
2. I run them through igir move zip test clean report
3. I torrentzip the output from igir.
4. I take the output of igir and import them into ROMVault (I like the interface better and it's a little more proven). This step tends to be fast since the files are (usually) properly prepared.

I especially like that there is command line support, parallel processing, and more supported file formats (rar, etc). I also like that it's opensource and makes it easy for me to find where potential problems might be. Also the developer is super responsive!

[emmercm]

Thank you for the message! I'd love to dig in on a few points:

• Is there a reason you prefer TorrentZip? Is it because of the first-class support in RomVault? I see the value for people joining MAME torrents, but I'm less sure about general collection sorting.
• What features do you use in RomVault after Igir has sorted your ROMs?

[tnvu]

I use TorrentZip primarily because of the first-class support in RomVault. It just makes my collection consistent with a lot of what's out there. I can checksum the zip and get the result without having to unpack it and then compare the file. It saves a step.

As for RomVault, post Igir... it's primarily the UI. Being able to visually see what's going on is pretty convenient. I know Igir isn't designed with that type of UI functionality in mind, so it's just a little easier to use than scanning through fixDATs.

The secondary use is to verify the work done by Igir. It caught #1001 when I noticed it was recompressing the zips produced by Igir. Just a sanity check to run it against a second, more mature tool.