igir like RomVault

[21millStreets]

Hello everybody,

I wonder if one day, igir will get the ability to change ROMs to adapt the DAT files like ROM Vault (or other).
Sorry about my technical speech and my low 8-bit English, I hope you will understand my concern :)

Love you.

[emmercm]

Hi @21millStreets, I'm not sure I understand the request. Are you asking igir to:

• Modify ROMs in some new way during writing?
• Modify input DATs in some new way?
• Create output DATs of some new type?

[21millStreets]

Thanks for your answer.

Well, I will explain how I use RomVault to point what I would like to see coming into igir.

With RomVault, I get a DAT file, for example: SG-1000.
Then I put it on a RomVault folder, select my SG-1000 ROMs folder, and launch the scan.

After a while, sometimes even if my roms are (or was) "good", I have to fix them. Actually, I do not understand exactly why, so I cannot be more specific here. But the button is Find fixes and then, Fix ROMs. And it's this exactly function I miss with igir to definitely drop RomVault.

Sorry I was a little bit in the move last time, I hope you will understand what I mean :)

[emmercm]

I'm assuming that RomVault only indicates your collection needs to be "fixed" after you download a new DAT version?

I don't like the "fix" nomenclature that other ROM managers use, I find it non-descriptive and confusing. There is typically nothing "wrong" with your ROMs, it's just that they don't match the DAT 100%, likely because the DAT changed the name of some file.

Assuming that is indeed the case, you can igir move --dat DATs/ --input ROMs/ --output ROMs/ to re-organize your collection according to some updated DATs. The input and output directories are allowed to be the same, and there should be a help example demonstrating this.

[21millStreets]

Hmmm OK I wasn't sure it was changing name of some file and YES, it's confusing :)

I will try your command, thanks a lot to take some time, I love igir !

[emmercm]

Awesome, thank you @21millStreets!

[github-actions[bot]]

🔒 Inactive discussion lock

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Comment generated by the GitHub Lock Issues workflow.