In reply to the issue posted here: https://github.com/saramibreak/DiscImag … issues/121
DIC dumps multisession .cue with these lines added:
REM LEAD-OUT 01:30:00
REM SESSION 02
REM LEAD-IN 01:00:00
REM PREGAP 00:02:00
These lines are added with the intention to document the disc layout and to describe data that isn't there.
So the REM LEAD-OUT, REM LEAD-IN and REM PREGAP lines are describing missing blocks the same way as PREGAP (without REM) did before we came up with this. They are describing a length and not a relative address.
When I look at previous definitions of REM LEAD-OUT, they are also describing a length: https://github.com/libyal/libodraw/blob … m-lead-out (but a couple lines below there's a typo where it says "The REM LEAD-OUT command is used to specify the LBA corresponding to an MSF.", where they actually meant REM MSF)
It wasn't meant to be a functional implementation. These lines are stored in the database. As soon as you download the .cue from the redump site, these lines are omitted. So you end up with a cuesheet that only has the REM SESSION 02 line.
Which leads to the problem that was described before here: http://forum.redump.org/post/94441/#p94441
To have somewhat functional .cue's using old definitions, I proposed to add the PREGAP 02:32:00 after the REM SESSION 2 to downloaded .cue's. This fix was never implemented and since then, user7 got in contact and IsoBuster implemented some changes that I'm unaware of.
To summarize, there are a couple different solutions:
1. Add the REM LEAD-OUT 01:30:00, REM LEAD-IN 01:00:00, REM PREGAP 00:02:00 into the redump .cue downloads, and have tool authors interpret these lines as a missing block, similar to PREGAP.
2. Add the PREGAP 02:32:00 line to redump .cue downloads. Tell people to use redump .cue instead of the one produced by DIC.
3. Keep everything as is, but have tool authors interpret multi-bin .cue with only the SESSION 02 line (= .cue as currently downloaded) as missing a 02:32:00 block between the sessions and hardcode a fix.
