CyberGonzo

Hi All, I addressed this CUE 'issue' in IsoBuster 5.0 to the best of my knowledge. Without having read the details in this thread, issues exist(ed) because the LEAD-OUT entry...

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 wonder what would need to change for the img/ccd/sub to be parsed correctly, or for the cuesheet with the merged bin (img) to be parsed correctly. Can you...

> Currently, IsoBuster is unable to parse the file system correctly based on the img/ccd/sub that is produced by DIC from a multisession disc. In other words, what would need...

Thank you, I will have a look as soon as I can. Question, why the two CUE variants ? A CUE for a single *.img container and a CUE for...

I'm going to have a look tomorrow, to try and figure things out. For my understanding, is the *.ccd in its current form, as generated by DIC, actually properly supported...

OK, I've done my analysis based on the counting crows' CD images and here are the results. I'm trying to be as objective as possible without pointing fingers. This stuff...

1. CUE + multiple BIN files: ``` REM SESSION 01 FILE "Counting Crows - Hard Candy (Track 01).bin" BINARY TRACK 01 AUDIO ISRC USIR10211155 INDEX 01 00:00:00 FILE "Counting Crows...

2. CUE + single IMG file: Counting Crows - Hard Candy_img.cue ``` FILE "Counting Crows - Hard Candy.img" BINARY REM SESSION 01 TRACK 01 AUDIO ISRC USIR10211155 INDEX 01 00:00:00...

3. CCD + single IMG file: The IMG file is correct and created in a way that is expected for CCD files (see 2. last paragraph) However the CCD file...