With some time on my hands, I've been trying to recreate some SEGA CD chds, and seem to have hit a snag. My steps, which have worked for most of them, are:
- get the sha (using sha1sum) of the "pre-files" (cue, bin, wav, etc)
- make sure they match what is in the segacd.xml (via the source comments for each game)
chdman createcd -i "input.cue" -o "output.chd"
- check the "Data SHA1:" of the created chd with
chdman info -i "output.chd"
to the sha1 value found in the xml (or run the chd through clrmamepro)
Unfortunately a few of the created chd files do not match the values in the xml. Going through the history of the segacd.xml file on git, I noticed that the chd files I am having issue with were all updated in commit 022430913cda3521a010046357061a2cc408b8f2 (10/16/2016: "Fix most of the faulty sha1.")
. I noticed that all the sha1 values I am getting with my created chd files match the previous sha1 values that were edited via this commit of the segacd.xml file.
I do not see any reference on how these new sha1 values were obtained, and I'm a beginner when it comes to chdman so I'm not sure if I am missing a command line switch or I have to insert certain metadata into the chd? Thanks for any input.
As an example:
I get: Dracula Unleashed (USA) (Disc 1).chd Data SHA1: a622e34eece3b778be5db57e286f660dfa6eb24f
Currently in xml: <disk name="dracula unleashed (usa) (disc 1)" sha1="307c0779dace5d95f3e7a0ccee18c00356ca2362"/>
What was edited by commit 0224309...: <disk name="dracula unleashed (usa) (disc 1)" sha1="a622e34eece3b778be5db57e286f660dfa6eb24f"/>
Ubuntu 18.04, self compiled .221 with TOOLS (though I was experiencing the same issue with .220)