doc: Formal documentation for CHD

[chyyran]

Following my research on the format for https://github.com/SnowflakePowered/chd-rs

I will be quite busy so I'm not sure when I can wrap this up but putting this as a draft for now.

Rendered

cc @cuavas

[mikehyrus]

Good question. Could this process also work with DVD and Blu-ray CHD procedures in the future?

[chyyran]

Sorry, I’m not exactly sure what you mean by process.

[galibert]

Bluray is not on the plan yet, dvd will only be a specific metadata and a fixed chunk/sector size (2048). So just a couple of lines to add to the doc once it's done.

[cuavas]

Thanks, I’ll hopefully get a chance to look at this some time later in the week.

[chyyran]

There is really nothing much here, just header specs for now. I intend to document the rest of it but that is depending on my available bandwidth.

On Sun, Aug 14, 2022 at 7:01 AM Vas Crabb @.***> wrote:

Thanks, I’ll hopefully get a chance to look at this some time later in the week.

— Reply to this email directly, view it on GitHub https://github.com/mamedev/mame/pull/10222#issuecomment-1214338810, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHUIN2HVTQJSK2ZHPY65HLVZDGXBANCNFSM56PCZKDA . You are receiving this because you authored the thread.Message ID: @.***>

[ajrhacker]

If you ever return to this, it might also be useful to document the chdman tool, or at least add a sentence or two to docs/source/tools/othertools.rst summarizing what it does.

[chyyran]

That could possibly be done in another PR, since I never really examined the inner workings of chdman (I only looked at chd.cpp and codecs as well as libchdr) I don’t feel like I can contribute much there.

[rb6502]

Hi @chyyran! Were you ever going to finish this and take it out of draft?

[chyyran]

Ah, yeah its been some time hasn’t. I put this down for a bit and am currently preoccupied with other projects so I’m happy to close this out for tracking hygiene and reopen when I’m ready to continue.