Page 8 of 15
Re: [DONE] Discussing the multisession cue
Posted: Sun May 26, 2019 2:51 am
by Jackal
Ok, according to this document, the area between Session 1 and 2 should always be:
http://web.mit.edu/kolya/sipb/afs/root. … ADME.multi
REM LEAD-OUT 01:30:00
REM SESSION 02
REM LEAD-IN 01:00:00
REM PREGAP 00:02:00
(= 11400 sectors total)
and subsequent sessions should have:
REM LEAD-OUT 00:30:00
REM SESSION 0?
REM LEAD-IN 01:00:00
REM PREGAP 00:02:00
(= 6900 sectors total)
It would be nice to confirm this from an official document (Philips' "Multisession Compact Disc Specification")
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 3:00 am
by F1ReB4LL
sarami wrote:Jackal wrote:is DIC really measuring the LEAD-IN and LEAD-OUT length, or are they predetermined?
LEAD-OUT length = 1st LBA of lead-in of 2nd session - 1st LBA of lead-out of 1st session
LEAD-IN length = 11400 - 150 - LEAD-OUT length
Why not to read that area and measure the lead-out/lead-in/pregap sizes according to subs? Plextor allows to read all those sectors, I guess?
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 3:22 am
by sarami
F1ReB4LL wrote:sarami wrote:Jackal wrote:is DIC really measuring the LEAD-IN and LEAD-OUT length, or are they predetermined?
LEAD-OUT length = 1st LBA of lead-in of 2nd session - 1st LBA of lead-out of 1st session
LEAD-IN length = 11400 - 150 - LEAD-OUT length
Why not to read that area and measure the lead-out/lead-in/pregap sizes according to subs? Plextor allows to read all those sectors, I guess?
I get it from subch. From 1st 0xaa to 1st 0x00 and 0xa0 is lead-out length.
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 5:29 am
by F1ReB4LL
sarami wrote:I get it from subch. From 1st 0xaa to 1st 0x00 and 0xa0 is lead-out length.
I've misunderstood your "LEAD-IN length = 11400 - 150 - LEAD-OUT length" formulas, then

I've thought you just assume the lead-out/lead-in sizes.
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 7:13 am
by sarami
http://www.mediafire.com/file/eq80y20l9 … st.7z/file
changed: LEAD-IN length = 1st LBA of 1st track of 2nd session - 1st LBA of lead-in of 2nd session
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 11:47 am
by Jackal
What about the pregap then? It has to be included somehow
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 12:15 pm
by iR0b0t
Maybe make it like follows(?):
REM SESSION 01
FILE "dump (Track 1).bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
REM LEAD-OUT 01:30:00
REM SESSION 02
REM LEAD-IN 01:00:00
FILE "dump (Track 2).bin" BINARY
TRACK 02 MODE2/2352
INDEX 01 00:00:00
REM INDEX 01 00:02:00
FILE "dump (Track 3).bin" BINARY
TRACK 03 AUDIO
INDEX 00 00:00:00
INDEX 01 00:01:74
To comment the real INDEX 01 and make it work like that.
Or even more accurate:
REM INDEX 00 00:00:00
REM INDEX 01 00:02:00
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 12:19 pm
by Jackal
That looks ugly.. why not just go with REM PREGAP 00:02:00? Everybody keeps ignoring this solution.
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 12:24 pm
by iR0b0t
One of the reasons i don't want to have it is because the database currently supports two cuesheet styles, without "PREGAP" (our standard one) and with "PREGAP" which is available as an alternative variation.
If i bring in additionaly "REM PREGAP 00:02:00" for both styles it will be super ugly.
And yes, my last suggestion is a little bit "ugly" if you want to call it that, but it would serve its purpose and i feel its a better (more appropriate) solution.
Re: [DONE] Discussing the multisession cue
Posted: Mon May 27, 2019 12:55 pm
by Jackal
We never use the normal "PREGAP" command, so I guess you can remove support for it?