Consider extracting to BIN/CUE instead of ISO

[bitsgalore]

BUT from the IsoBuster docs:

Cue-sheet files have limitations !! They're nice to get the track layout of a session, but they do not support Multi-Session discs. IsoBuster however adds features to the cue-sheet file so that Multi-session discs are supported as well. These entries are preceded by "REM" so that other applications (that do not support Multi-session cuesheet files) do not complain. However, if you load these cue-sheet files with IsoBuster again, you get the full potential of these added features and you can see all sessions again properly.

Experiment

Created bin/cue image of enhanced audio disc with IsoBuster. Generated cue sheet (note that command that are preceded by REM are IsoBuster-specfic and not part of the standard cue syntax):

FILE "no.bin" BINARY

REM ORIGINAL MEDIA-TYPE: CD

  REM SESSION 01        (*)
    TRACK 01 AUDIO
      ISRC USIR70200001
      INDEX 01 00:00:00
         REM LBA: 0
    TRACK 02 AUDIO
      ISRC USIR70200002
      INDEX 01 02:10:53
         REM LBA: 9803
    ::   ::
    ::   ::
    TRACK 17 AUDIO
      ISRC USIR70200017
      INDEX 01 31:08:34
         REM LBA: 140134

  REM LEAD-OUT 33:48:70 (*)
  REM SESSION 02        (*)
    TRACK 18 MODE2/2352
      INDEX 01 36:20:70
         REM LBA: 163570

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

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

Then opened the cue/bin file with cdEmu.

Result: this makes the audio session available, but not the data session. Also found this on the ImgBurn forum (from ImgBurn's author):

Virtual drive programs can't mount multisession BIN/CUE files so don't bother trying.

Also:

• AcetoneISO "can't mount correctly a multi-session image. Only the first track will be shown".
• ImgDrive supports multisession discs but only if they are in CCD, MDS or NRG formats, which are all proprietary formats.
• But this issue suggests that IsoBuster's extended bin / cue format should work in Cdemu (but it doesn't!). I've created a ticket here, so let's see what happens.

[0x6A7232]

Looks like Cdemu never fixed it, ticket is still open.