RightThere Posted February 19, 2017 Posted February 19, 2017 (edited) FILE "Quake2.bin" BINARY TRACK 01 MODE1/2352 INDEX 01 00:00:00 TRACK 02 AUDIO PREGAP 00:02:00 INDEX 01 40:34:18 TRACK 03 AUDIO INDEX 00 44:03:08 INDEX 01 44:05:05 TRACK 04 AUDIO INDEX 00 46:22:60 INDEX 01 46:24:57 TRACK 05 AUDIO INDEX 00 48:56:69 INDEX 01 48:58:66 TRACK 06 AUDIO INDEX 00 51:50:30 INDEX 01 51:52:27 TRACK 07 AUDIO INDEX 00 54:27:22 INDEX 01 54:29:19 TRACK 08 AUDIO INDEX 00 58:04:34 INDEX 01 58:06:31 TRACK 09 AUDIO INDEX 00 61:10:50 INDEX 01 61:12:47 TRACK 10 AUDIO INDEX 00 63:48:43 INDEX 01 63:50:40 TRACK 11 AUDIO INDEX 00 65:50:46 INDEX 01 65:52:43 FILE "Quake2.bin" BINARY TRACK 01 MODE1/2352 INDEX 01 00:00:00 TRACK 02 AUDIO INDEX 01 40:36:18 TRACK 03 AUDIO INDEX 01 44:07:05 TRACK 04 AUDIO INDEX 01 46:26:57 TRACK 05 AUDIO INDEX 01 49:00:66 TRACK 06 AUDIO INDEX 01 51:54:27 TRACK 07 AUDIO INDEX 01 54:31:19 TRACK 08 AUDIO INDEX 01 58:08:31 TRACK 09 AUDIO INDEX 01 61:14:47 TRACK 10 AUDIO INDEX 01 63:52:40 TRACK 11 AUDIO INDEX 01 65:54:43 The first one was created via Imgburn 2.5.7.0 (not via the PC I'm having the driver issue on) and the second was created via AnyBurn 3.5, 64-bit portable (on the PC with my driver issue). Is there any functional difference between the two bin/cue file pairs? Is this kind of difference normal for bin/cue files between Imgburn and other similar applications? If so, does that mean the two file pairs are, for all intents and purposes, the same? Edited February 19, 2017 by RightThere
LIGHTNING UK! Posted February 19, 2017 Posted February 19, 2017 It's not normal for programs that attempt to create an accurate cue, no. ImgBurn does, AnyBurn doesn't appear to. I don't think burning each of those would result in identical looking discs (and that's just taking the basic TOC into consideration), so I wouldn't say they're the same.
Recommended Posts