[DONE] Sega Dreamcast: Multi-Cue > GDI (Page 2 of 3)

I think it would be better to skip dual cuesheets completely and stick to the single cue with the proposed improvements? It's just way more practical. Multi session discs should have a similar solution.

As a start i began with this single-cue file alternative:
http://redump.org/disc/57702/

If it looks good to you i will update all remaining functions and all GD-ROM cuesheets.

As a backup i would still keep the gdi downloads, but if you think its completely pointless i will discard those.

If you want to conform to the standards that are already set by IsoBuster with multisession discs, and have the best compatibility with other tools, the cuesheet should be like this:

edit: Because the HD area apparently starts with Track03, we no longer need to think about Multi-Cue or other alternatives.

The start address of the first Track03 sector is 10:02:00.

When we use a normal single cuesheet (with or without REM), the problem is that normal applications place the Track03 start time relative to the previous tracks.

So in order to get the correct sector addressing, a PREGAP will needs to be calculated based on the length of the previous 2 tracks.

Example: http://redump.org/disc/52815/

10:02:00 minus the combined length of the LD tracks (17:07) = 09:42:68

With this cuesheet, IsoBuster correctly loads the Track03 filesystem and other applications like CDmage have the correct sector addressing:

What do you guys think about this implementation?

It would require some extra coding, but it maintains the existing "standards" for .cue.

Actually, Track03 is shown with the correct size and starting address.

The only problem is that the Track02 end address aligns with Track03, but when you browse outside of the data range, it gives read errors.

I don't think this is a problem, it's merely a restriction of the .cue standard.

I only suggested it because it's the only way to make IsoBuster detect the filesystem of Track03. But for emulators etc. we could stick to REM SINGLE-DENSITY AREA and REM HIGH-DENSITY AREA.

You still need the PREGAP line, even with separate cue's, because otherwise you would be pointing Track03 to start at sector 150 instead of 45.150.

So, I think this solution still stands?

Or tell us what the benefit would be of having 2 .cue's, like this?

I don't think setting a PREGAP line is the right solution.

We could stick to a single cue example and make other REM lines, stating the next LBA starting address, which also could allow us to dump and link other inaccessible disc areas like security rings and gaps between multiple sessions.

It could look like that:

REM SINGLE-DENSITY AREA START LBA *here number*
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
REM HIGH-DENSITY AREA START LBA *here number*
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 3).bin" BINARY
  TRACK 03 MODE1/2352
    INDEX 01 00:00:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 4).bin" BINARY
  TRACK 04 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (Track 5).bin" BINARY
  TRACK 05 MODE1/2352
    INDEX 00 00:00:00
    INDEX 01 00:03:00

Anything between Track2 end sector and REM HIGH-DENSITY AREA START LBA would be emulated as a GAP without having to set any pregap values and would not require extra FILE lines.

REM SECURITY AREA START LBA *here number*
FILE "Official Sega Dreamcast Magazine Vol. 11 - February 2001 (USA) (*here anything*).bin" BINARY
  TRACK ?? MODE1/2352
    INDEX 01 00:00:00

Not sure how to solve the "TRACK ?? MODE1/2352" part at this point, but there is probably a solution for that too. At this point its not a requirement.

For inserting, yes.
For generating, no.

We don't dump them at this point, and besides of that not all leadout sectors will be dumpable. Not sure if we ever will have them included. Maybe its better to concentrate on GD topic right now

A separator is not really needed. Anything between "REM" and traling "START LBA NUMBER" is to be treated as a plain comment or a COMMAND, which will be recognized if its called "SESSION NUMBER" or "LEAD-IN" or "LEAD-OUT" or whatever commands you want to have there.

You know that they start there because you are aware of that, but mounting tools do not know it.

So what? Your "START LBA"/"START MSF" commands won't teach the mounting tools to do that, you need to tell the devs to code the support. So they can simply write the code to put the "REM HIGH-DENSITY AREA" data at 45150. You're overcomplicating things.

"REM HIGH-DENSITY AREA" would be dreamcast exclusive, a global command would make more sense imho.

2xcues would be still dreamcast exclusive (without further REM commands)

Honestly, I would be fine with what you suggest @F1ReB4LL but in the end the emulaton / mounting devs have to adapt their tools to that. Independently of what they would accept, if I developed such a tool myself I would rather prefer a global command which can be used on any system, not just one.

Let the devs know and arrange an adaptation, if they decided something I will go by that, its not a big deal.