Jump to content

CUE sheet troubles with raw audio files


baguvix

Recommended Posts

Hi, this is my first post here since I've never had any problems with ImgBurn :) Thanks for that!

However now I've run into a little snag.

 

I have been creating cue sheets for discs of the following layout which worked great:

Session 1 - Audio Track 1 - Audio Track n - Lead Out - Session 2 - Data Track.

 

Now I would like to combine all audio tracks (.raw files) into one big .raw file (by just copying all files together) and create a working cue sheet for that; I would have expected that using the combined lengths of the previous audio tracks as "INDEX 01" would get me what I wanted but for some reason the disc length comes out wrong.

 

I suspect it's either because of wrong LBAs/MSFs or because of the .raw file, declared as BINARY - I've read I could just install a direct show filter for .raw audio and change the BINARY to... something else, but even if that would work that's not really an option as this is all supposed to be part of a program I'm writing and I don't want the users to have to install extra stuff.

 

Working CUE (79:59:00):

SESSION 01

FILE "track04.raw" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00

FILE "track05.raw" BINARY
TRACK 02 AUDIO
INDEX 01 00:00:00

FILE "track06.raw" BINARY
TRACK 03 AUDIO
INDEX 01 00:00:00

FILE "track07.raw" BINARY
TRACK 04 AUDIO
INDEX 01 00:00:00

FILE "track08.raw" BINARY
TRACK 05 AUDIO
INDEX 01 00:00:00

FILE "track09.raw" BINARY
TRACK 06 AUDIO
INDEX 01 00:00:00

FILE "track10.raw" BINARY
TRACK 07 AUDIO
INDEX 01 00:00:00

FILE "track11.raw" BINARY
TRACK 08 AUDIO
INDEX 01 00:00:00

LEAD-OUT 00:11:08

SESSION 02

FILE "data.bin" BINARY
TRACK 09 MODE2/2352
INDEX 01 00:00:00

 

NON working CUE (with 2 secs gap for each track) (80:01:67):

SESSION 01

FILE "audio.raw" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00

TRACK 02 AUDIO
INDEX 01 01:54:31

TRACK 03 AUDIO
INDEX 01 02:36:56

TRACK 04 AUDIO
INDEX 01 03:56:50

TRACK 05 AUDIO
INDEX 01 04:17:53

TRACK 06 AUDIO
INDEX 01 04:32:54

TRACK 07 AUDIO
INDEX 01 04:43:55

TRACK 08 AUDIO
INDEX 01 05:01:18

LEAD-OUT 00:11:08

SESSION 02

FILE "data.bin" BINARY
TRACK 09 MODE2/2352
INDEX 01 00:00:00

 

NON working CUE (without gaps) (79:47:67):

SESSION 01

FILE "audio.raw" BINARY
TRACK 01 AUDIO
INDEX 01 00:00:00

TRACK 02 AUDIO
INDEX 01 01:52:31

TRACK 03 AUDIO
INDEX 01 02:32:56

TRACK 04 AUDIO
INDEX 01 03:50:50

TRACK 05 AUDIO
INDEX 01 04:09:53

TRACK 06 AUDIO
INDEX 01 04:22:54

TRACK 07 AUDIO
INDEX 01 04:31:55

TRACK 08 AUDIO
INDEX 01 04:47:18

LEAD-OUT 00:11:08

SESSION 02

FILE "data.bin" BINARY
TRACK 09 MODE2/2352
INDEX 01 00:00:00

 

Lengths:

track04.raw 19.829.712 bytes, 8431 2352byte blocks, 01:54:31 (with 2 secs gap), 01:52:31
track05.raw 7.114.800 bytes, 3025 2352byte blocks, 00:42:25 (with 2 secs gap), 00:40:25
track06.raw 13.745.088 bytes, 5844 2352byte blocks, 01:19:69 (with 2 secs gap), 01:17:69
track07.raw 3.358.656 bytes, 1428 2352byte blocks, 00:21:03 (with 2 secs gap), 00:19:03
track08.raw 2.295.552 bytes, 976 2352byte blocks, 00:15:01 (with 2 secs gap), 00:13:01
track09.raw 1.589.952 bytes, 676 2352byte blocks, 00:11:01 (with 2 secs gap), 00:09:01
track10.raw 2.735.376 bytes, 1163 2352byte blocks, 00:17:38 (with 2 secs gap), 00:15:38
track11.raw 1.959.216 bytes, 833 2352byte blocks, 00:13:08 (with 2 secs gap), 00:11:08
audio.raw 52.628.352 bytes, 22376 2352 byte blocks, 05:00:26 (with 2 secs gap), 04:58:26
Lead Out (in cue) = last "old" audio track length without 2 secs gap = 00:11:08
data.bin 766.749.648 Bytes, 325999 2352byte blocks, 72:28:49 (with 2 secs gap), 72:26:49

 

I'm pretty sure the 2 secs gap per track are wrong but I tried it anyway and the output from that is closer to the value I'm looking for... which is just confusing me more.

 

Alternatively I suppose I could convert all the audio tracks to wav files, stick them together and reference that via "WAVE" but I haven't yet looked into that.

 

And is there an explanation of ImgBurn's cue support, e.g. what filetypes and "commands" it supports (and what exactly that "lead out xx:yy:zz" in the cue means again)?

 

Any pointers in the right direction would be greatly appreciated as I'm completely stuck but would really like to add this "feature"... in the meantime I'll get fitshaced. Cheers!

 

EDIT: I thought it might be easier for any helpful people if they had all the files I was talking about, so I recreated all of the above mentioned files filled with 0s, rar'd them and uploaded that to MultiUpload (size ~5kb): http://www.multiupload.com/MKX8DTDG97

Edited by baguvix
Link to comment
Share on other sites

Your CUE file for a single audio.raw track should look as follows:

 

REM SESSION 01
 FILE "audio.raw" BINARY
   TRACK 01 AUDIO
     INDEX 01 00:00:00
   TRACK 02 AUDIO
     INDEX 01 01:52:31
   TRACK 03 AUDIO
     INDEX 01 02:32:56
   TRACK 04 AUDIO
     INDEX 01 03:50:50
   TRACK 05 AUDIO
     INDEX 01 04:09:53
   TRACK 06 AUDIO
     INDEX 01 04:22:54
   TRACK 07 AUDIO
     INDEX 01 04:31:55
   TRACK 08 AUDIO
     INDEX 01 04:47:18
 REM LEAD-OUT 04:58:26
REM SESSION 02
 FILE "data.bin" BINARY
   TRACK 09 MODE2/2352
     INDEX 01 00:00:00

 

You had the LEAD-OUT bit wrong, that's all.

 

It uses the LEAD-OUT to know how much data there is in the last INDEX.

 

i.e. LEAD-OUT value - (minus) last INDEX value = size of INDEX.

 

Your LEAD-OUT value was smaller than the INDEX value and that's why it didn't work. It just meant the last index was calculated as having a size of 0.

 

I've added a check/prompt for such issues now - not that it should ever really be needed if the CUE files are created properly (i.e. by the software itself)

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.