binmerge VS mame

You need to merge the "Track #" bin files into one; one game needs to have one bin and one cue file. You can use CDMage, cdfix, BinMerger, or just binmerge to do that. Then you can convert to PBP.

If you only have 1 bin file, you can use binmerge to split the tracks.

You can use binmerge to put many bin into one bin: https://github.com/putnam/binmerge

If you want to split the bin file back to multiple bin files, you can use binmerge.

No idea where the pre-merged set exists online- but if you'd like to curate your own set I'd recommend binmerge, and you can auto-generate the cue files here.

Yeah, that would be cool, but then the .bin file usually needs to be split into separate tracks (using binmerge) so I'd need to modify that the work with the streams too in some way. And the .cue file needs to be handled too, so it all gets a bit awkward, and I'm thinking it might be better to make the program support .chd files directly using one of the .chd-reading libraries 🤔

Would be nice to add Binmerge functionality so you can also reverse the process completely for CD-ROM multi-tracks. I learned the hard way that GD-ROMs are not reversible yet.

Yes, there are many challenges in reverse engineering these classic games. This is a good example.

https://www.youtube.com/watch?v=objL2hGAEgU

Living in L.A. in the 90's, I remember Pack Mann in Pasadena had this one.

http://www.arcaderestoration.com/games/3330/Gals+Panic+II.as...

The ROM dump's been done but people seem to be stuck on the RLE encoding. It's hard to say what kind of wizardry is needed in this case.

https://github.com/mamedev/mame/issues/5816

There's a good start at it in the tree ( https://github.com/mamedev/mame/blob/master/src/mame/yamaha/... ) but it's missing the sound generation which is kind of the important part :-)

> As requested by users, you can finally use delta CHD files for clone systems and software items. This allows for major disk space savings in some cases when you have multiple versions of a system or software item.

FWIW, this is commit https://github.com/mamedev/mame/commit/d1172bf710f2a7b1777ed...

The GitHub Actions workflow bgfxshaders.yml will rebuild the shaders and then zip them up as an artefact. If you push your shader changes to GitHub and let the workflow run, you can grab the rebuilt shades from there.

Note that the process of getting the MSYS64/MinGW build environment set up is simple enough that we have automated CI builds for it on GitHub Actions without needing any custom actions of our own.

I assume they’re free vend because they’re MAME based?