11/5/2022 0 Comments Fat princess pc emulator![]() PBP -> CSO2 with bigger block size -> CSO -> ZSO Is ZSO even ment for the biggest compression?įrom my test with available formats from best compression to worst: This may change thou, since they seem proud of the CHD support. I'm more pessimistic, complicated features are the first to be handwaved away.Īnyway, CHD is bad for now for retroarch anyway because the metadata database and their scanner is not ready to accept CHD checksums, internal or external (even the internal checksums are different from the raw cue/bin because they're of a 'sum' of the involved files, not only the 'first track' or whatever hack RA is using - they previously used cues and gdi and of course this failed alot since many gdi are indistinguishable due to dumping group bad idea, so i'd actually prefer the CHD approach). The devs thought that since the format specifies that the format should support parent/clone relationships this wasn't needed. Emulators still need to implement reading chd, but that's much easier. FAT PRINCESS PC EMULATOR PATCHand they nixed my proposal on their chdman issue report page to add 'reversible hardpatch' to their format (basically, do the boring work of integrating a 'patch update' tool that takes a binary patcher, patches the underlying bytes, and creates a reversal patch to add as header for the next 'patch update' and recompress that again).īig advantage of such schemes is that they don't depend on lazy/dead emulators implementing softpatching to work (reimplementing the wheel every time), while still being easy to update. Pity it doesn't work anywhere else (including retroarch, except, ofc, the MAME core). ![]() ![]() ![]() One 'advantage' of CHD is that chdman and mame are supposed to have support for a form softpatching (parent-clones relationships, where clones store different files/sectors). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |