[DONE] Discussing the multisession cue

[F1ReB4LL]

maybe it's time to make an additional topic to start discussing the multisession cue (or something xml-based) questions?

[F1ReB4LL]

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:

Code: Select all

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).

[F1ReB4LL]

Including the first session leadin and last session leadout, right?! (on multi sessional discs only)

the first session lead-in and last session lead-out would be too hard to measure.

The first session lead-out and the second session lead-in and first pregap are measureable (and their sizes are surely needed to at least convert such a stripped image into the "proper" iso-cue pair in IsoBuster format).

[F1ReB4LL]

I mean, REM LEAD-IN, REM LEAD-OUT, for those, without time values. But they have to be present.

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.

[iR0b0t]

I have seen some foreign multisessional cuesheet styles and they don't look correct to me.

To my understanding it should be as follows:

Code: Select all

REM SESSION 01
REM LEAD-IN
FILE "Himitsu - Original Sound Track (Japan) (Track 01).bin" BINARY
  TRACK 01 AUDIO
    ISRC JPWP09906010
    INDEX 01 00:00:00
FILE "Himitsu - Original Sound Track (Japan) (Track 02).bin" BINARY
  TRACK 02 AUDIO
    ISRC JPWP09906020
    INDEX 01 00:00:00
REM LEAD-OUT
REM SESSION 02
REM LEAD-IN
FILE "Himitsu - Original Sound Track (Japan) (Track 03).bin" BINARY
  TRACK 03 AUDIO
    ISRC JPWP09906030
    INDEX 01 00:00:00
REM LEAD-OUT

// one of the submissions: /viewtopic.php?t=13438

[sarami]

/viewtopic.php?p=43978#p43978

@sarami, do you have some thoughts?

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.

[F1ReB4LL]

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.

We need our own variants of these to show the amount of Lead-In and Lead-Out sectors to generate (similar to PREGAP and POSTGAP commands) - /viewtopic.php?p=48299#p48299

[sarami]

We need our own variants of these to show the amount of Lead-In and Lead-Out sectors to generate (similar to PREGAP and POSTGAP commands) - /viewtopic.php?p=48299#p48299

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

[F1ReB4LL]

No, dreamcast is a special case, it's not a multisessional disc, it's a disc with 3 independent areas and 3 independent TOCs (SD area, logo area, HD area). They don't need to be connected because the SD area's leadout always ends exactly at 24600, the ring area always starts at 24941 and ends at 38690 and the HD area always starts at 49850. These values cannot be changed, so you don't need the multisessional TOC with the sessions addresses in it. And you don't need to define the sessions, mirror zones and other stuff in cue, because these values should be precoded in the emulator.

And for the multisessional discs you always have the 'main' TOC where all the sessions are listed, so you need to fill the lead-out and lead-in gaps somehow to not to ruin the addressing.

[Jackal]

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

https://redump.info/disc/39048/
https://redump.info/disc/10299/
https://redump.info/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.