[DONE] Discussing the multisession cue (Page 1 of 6)

The only logical solution I can think of is to keep the track checksums only in db and implement the REM LEAD-IN/REM LEAD-OUT commands similar to PREGAP/POSTGAP ones.

Like:

REM LEAD-OUT 00:03:55
REM SESSION 02
REM LEAD-IN 00:02:00

(so the virtual drive or some converter could generate the proper amount of empty sectors there).

What's the point? You need to add an empty PREGAP after the first LEAD-IN, then, since the first track always has some omitted pregap after the lead-in. Lead-in and lead-out always exist, it's an axiom, you don't need any additional commands to show that.

http://forum.redump.org/post/69075/#p69075

I think 'REM LEAD-IN' and 'REM LEAD-OUT' don't need in multi-session's cue of multi-track (redump'org) format.
1. Because multi-session's cue of multi-track format doesn't have lead-in area and lead-out area.

2. Because Dreamcast's cue doesn't have 'REM LEAD-IN' and 'REM LEAD-OUT'. (Admin and mod defined only REM SINGLE-DENSITY AREA and REM HIGH-DENSITY AREA. Actually, GD-ROM has lead-out after the last track of single-density area and lead-in before first track of high-density area.)

3. With only 'REM SESSION 01' and 'REM SESSION 02', IsoBuster can recognize that multi-session's cue of multi-track is multi-session.

But IsoBuster needs 'REM LEAD-OUT' because IsoBuster's bin has the lead-out area of 1st session and lead-in area of 2nd session.

I see, then should we add 'REM LEAD-IN' and 'REM LEAD-OUT' and 'REM SEGA-LOGO' etc in dreamcast's cue?

This is how we've been dealing with multisession discs so far:

http://redump.org/disc/39048/
http://redump.org/disc/10299/
http://redump.org/disc/48363/

So what's wrong with using the IsoBuster "standard"? it contains all the relevant information for a functional image? It seems overkill to define lead-out etc, when all other dumps have them excluded.

Oops yeah, so IsoBuster seems to use:

REM SESSION 01
(cuesheet for session 1)
REM LEAD-OUT [MSF]
REM SESSION 02
(cuesheet for session 2)

Would this be sufficient for our purposes? I would leave out the REM LEAD-IN because it's not part of the IsoBuster standard and the only purpose anyway is to bridge the gap, which is what LEAD-OUT does also.

Do we have a consensus on what's needed?

Erm. IsoBuster allows to map the sessions with their lead-ins/lead-outs only inside a single bin+cue image, it doesn't support split tracks. We need to do the custom stuff in any case. And my idea stated above is to show the amount of inserted generated sectors. Like the PREGAP 00:02:00 and POSTGAP 00:05:00 commands => REM LEAD-OUT 00:03:00 and REM LEAD-IN 00:02:00 (or something similar to not to conflict with native IsoBuster commands).

Yeah. It basically shows where the last session of the first track ends with the REM LEAD-OUT command. And the next track entry shows where the first track of the next session begins. The actual lead-out sectors of the first session/lead-in sectors of the second session/pregap are 'just there' undescribed.

But if we want these to be split to tracks, we need to describe how many lead-out sectors to generate and how many lead-in sectors to generate.

The current REM LEAD-OUT "standard" is used to define the address in the bin _image_ (not track), where the last track of the session ends. And, since we don't use the single bin images, we need 2 new commands to show the CD emulator/burner/whatever_other_tool to insert the needed amount of lead-out and lead-in sectors to fill the gap between tracks.

I'd like to know if the TOC/subchannels of multisession discs (and/or rainbow books) really have a "RUN-OUT", "LEAD-OUT" and "LEAD-IN" marked between sessions. If they do, then I wonder why IsoBuster omitted the LEAD-IN.

Uploaded test version
- added: Lead-out length of 1st session in _disc.txt (needs /ms flag)
- fixed: incorrect 'REM SESSION' position.

Logs
http://www.mediafire.com/file/33yj4wjky … og.7z/file

It seems old isobuster supports it. https://forum.daemon-tools.cc/showthread.php?t=6281
But latest version doesn't output it.

FILE "CD.iso" BINARY

REM ORIGINAL MEDIA-TYPE: CD
CATALOG 4943674011599

  REM SESSION 01        (*)
    TRACK 01 AUDIO
      ISRC JPWP09906010
      INDEX 01 00:00:00
         REM LBA: 0
    TRACK 02 AUDIO
      ISRC JPWP09906020
      INDEX 01 03:35:47
         REM LBA: 16172
    TRACK 03 AUDIO
      ISRC JPWP09906030
      INDEX 01 06:42:30
         REM LBA: 30180
    TRACK 04 AUDIO
      ISRC JPWP09906040
      INDEX 01 08:41:55
         REM LBA: 39130
    TRACK 05 AUDIO
      ISRC JPWP09906050
      INDEX 01 11:28:17
         REM LBA: 51617
    TRACK 06 AUDIO
      ISRC JPWP09906060
      INDEX 01 14:15:62
         REM LBA: 64187
    TRACK 07 AUDIO
      ISRC JPWP09906070
      INDEX 01 17:23:67
         REM LBA: 78292
    TRACK 08 AUDIO
      ISRC JPWP09906080
      INDEX 01 22:08:10
         REM LBA: 99610
    TRACK 09 AUDIO
      ISRC JPWP09906090
      INDEX 01 24:38:62
         REM LBA: 110912
    TRACK 10 AUDIO
      ISRC JPWP09906100
      INDEX 01 27:34:52
         REM LBA: 124102
    TRACK 11 AUDIO
      ISRC JPWP09906110
      INDEX 01 29:52:25
         REM LBA: 134425
    TRACK 12 AUDIO
      ISRC JPWP09906120
      INDEX 01 32:10:72
         REM LBA: 144822
    TRACK 13 AUDIO
      ISRC JPWP09906130
      INDEX 01 34:32:62
         REM LBA: 155462
    TRACK 14 AUDIO
      ISRC JPWP09906140
      INDEX 01 37:32:67
         REM LBA: 168967

  REM LEAD-OUT 41:01:67 (*)
  REM SESSION 02        (*)
    TRACK 15 MODE2/2352
      INDEX 01 43:33:67
         REM LBA: 196042

REM (*) SESSION commands are not supported by all applications

REM Generated by IsoBuster 4.3.0.00 (https://www.isobuster.com)