DiscImageCreator: Wrong LEAD-OUT in .cue file with multisession cd-rom / PX-760A drive
Version Latest, 20220301
Describe the bug With my drive/pc it seems all multisession cd-roms get an invalid .cue file when dumped with DIC. DIC says it’s succesfully dumped and indeed all goes well, but the .cue / .bin files generated have file table problems when opened with IsoBuster or PowerIso. When dumped with ImgBurn, although it’s not readed in raw mode, the cue/bin are functional. It seems to be related with LEAD-OUT
This is the .cue file generated by DIC:
REM SESSION 01
FILE "TOVENARY (Track 1).bin" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00
REM LEAD-OUT 01:30:00
REM SESSION 02
REM LEAD-IN 01:00:00
REM PREGAP 00:02:00
FILE "TOVENARY (Track 2).bin" BINARY
TRACK 02 MODE2/2352
INDEX 01 00:00:00
This is the .cue file generated by ImgBurn for the same cd-rom:
FILE "tovenarij.bin" BINARY
REM SESSION 01
TRACK 01 AUDIO
INDEX 01 00:00:00
REM LEAD-OUT 03:24:40
REM SESSION 02
TRACK 02 MODE2/2352
INDEX 01 05:56:40
This is the DIC .cue editted to make it open succesfully again:
REM SESSION 01
FILE "TOVENARY (Track 1).bin" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00
REM LEAD-OUT 03:24:40
REM SESSION 02
REM LEAD-IN 01:00:00
REM PREGAP 00:02:00
FILE "TOVENARY (Track 2).bin" BINARY
TRACK 02 MODE2/2352
INDEX 01 00:00:00
So when using the LEAD-OUT value from ImgBurn it all works again. I’m not very technical at this but I hope this report is useful to help improving DIC
Screenshots
This is how it looks when opening with the original cue file from DIC (file table problems):

This is after fixing the LEAD-OUT manually to match imgburn’s cuefile:

Disc title Tovenarij! (Hybrid disc) cd-rom
URL https://archive.org/details/TOVENARY
Log file Log: logs.zip
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 33 (16 by maintainers)
I might also add that I (in IsoBuster) was the very first person ever to support multi-session CUE+ISO/IMG/BIN files and as such I set/created the standard … So … when I say it’s wrong … it’s wrong ! LOL