[Non Volatile Human]

I read it, but I feel like it's missing something. It means that I need to have an idea of the data present in each *.bin archive and as such pick the appropriate disk size (or take into account the size of the whole game). e.g. if I know that all the archives/*.bin files will be at most 45GB big, I should choose the BD 50 disk size?

why not choose ~unlimited so that the need to merge is made irrelevant, as all the data would be on one disk, and that disk would contain all of the archives/*.bin files?

And if in "developer mode" I choose "Disk spanning using CLS-Diskspan.dll" in the "Game1" tab, would I need to adjust the disk sizes in the "General" tab?

And if I add the game from the Database, would I need to touch anything at all afterward? Or does using the Database automate everything so that I would just have to save my preset, re-launch DiskSpan GUI in its normal mode, and press "compress"?