DiscImageCreator

[Kalamari5662]

I get an error but it still continues which is weird.

[Enker]

The ANSI build is crashing on CD-TEXT CDs with these two versions:
20130222
20130203

[sarami]

The ANSI build is crashing on CD-TEXT CDs with these two versions:
20130222
20130203

fixed

[Enker]

I found some CCD file issues:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

[TRACK 1]
MODE=0
INDEX 0=0
INDEX 1=30

Here are the .ccd files: http://www.mediafire.com/?z3idm72x26751d8

[Nexy]

That's a bug in CloneCD

[sarami]

I found some CCD file issues:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

I don't write "FLAGS" in ccd file at the present.
Fix at the next release.

[TRACK 1]
MODE=0
INDEX 0=0
INDEX 1=30

Here are the .ccd files: http://www.mediafire.com/?z3idm72x26751d8

I don't know a specification in detail about a disc including "INDEX 0" to "TRACK 1".
need or not "INDEX 0" in "TRACK 1"?

in case of clonecd
don't write "INDEX 0" in "TRACK 1". in cue & ccd file.
in case of CDRWIN
write "INDEX 0" in "TRACK 1" in cue file.

[Enker]

I agree with Nexy, the missing INDEX 0 for Track 1 is a bug with CloneCD. The .cue files here on redump don't have an INDEX 0 for Track 1 when INDEX 1 is >00:00:00. This should be fixed.

I noticed that the last track for my disc is being underdumped. The last 30 sectors are lost with DiscImageCreator and not with other tools.

[sarami]

I found some CCD file issues:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

I noticed that the last track for my disc is being underdumped. The last 30 sectors are lost with DiscImageCreator and not with other tools.

fixed

[Enker]

Thanks! I tested it and everything is working fine

I sent a message to iR0b0t about the redump .cue file issue.

[Nexy]

All tools just assume when burning, that track 1 has a pre gap of 2:00. Dunno why this is, or if you can even burn the real pre gap even if you dumped it in dao mode.

The cue/ccd is there to recreate the TOC on the original disc, if subs are burned too they can of course conflict with TOC like on many discs. Quite interesting how firmwares get around these inconsistencies. Protections could however check for these non-standard conditions... but rainbow books specs are rarely followed to the letter.