Jump to content

Invalid Field in Parameter List when Tracks go over 60 Min


Koi

Recommended Posts

Hi, I'm having an issue burning a bin/cue of a data/audio CD that I was provided (so its not a fresh rip I made).

 

I am getting "Failed to send Cue Sheet!" and "Reason: Invalid Field in Parameter List"

 

Through testing, I have found the burn won't happen if the last two tracks are in the cue (by deleting lines and running test writes)

 

I happened to notice these are the only two tracks that are over 60.

 

I am using 80Min/700MB media.

 

Here's the ImgBurn log...

 

I 16:24:32 ImgBurn Version 2.5.8.0 started!
I 16:24:32 Microsoft Windows 8 Enterprise x64 Edition (6.2, Build 9200)
I 16:24:32 Total Physical Memory: 33,548,452 KiB  -  Available: 16,064,304 KiB
I 16:24:32 Initialising SPTI...
I 16:24:32 Searching for SCSI / ATAPI devices...
I 16:24:32 -> Drive 1 - Info: HL-DT-ST DVDRAM GT80N 1.00 (D:) (USB 2.0)
I 16:24:32 Found 1 DVD±RW/RAM!
 
I 10:37:52 Operation Started!
I 10:37:52 Source File: E:\file.cue
I 10:37:52 Source File Sectors: 277,322 (MODE1/2048)
I 10:37:52 Source File Size: 634,431,136 bytes
I 10:37:52 Source File Volume Identifier: file
I 10:37:52 Source File File System(s): ISO9660, Joliet
I 10:37:52 Destination Device: [0:0:0] HL-DT-ST DVDRAM GT80N 1.00 (D:) (USB)
I 10:37:52 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.)
I 10:37:52 Destination Media Supported Write Speeds: 10x, 16x, 24x
I 10:37:52 Destination Media Sectors: 359,844
I 10:37:52 Write Mode: CD
I 10:37:52 Write Type: SAO
I 10:37:52 Write Speed: 10x
I 10:37:52 Lock Volume: Yes
I 10:37:52 Test Mode: Yes
I 10:37:52 OPC: No
I 10:37:52 BURN-Proof: Enabled
I 10:37:52 Write Speed Successfully Set! - Effective: 1,764 KB/s (10x)
E 10:37:52 Failed to send Cue Sheet!
E 10:37:52 Reason: Invalid Field in Parameter List
E 10:37:55 Operation Failed! - Duration: 00:00:02
I 10:37:55 Average Write Rate: N/A - Maximum Write Rate: N/A
 
And this is the cue...
 
FILE "FILE.BIN" BINARY
  TRACK 01 MODE1/2048
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    PREGAP 00:02:00
    INDEX 01 13:02:02
  TRACK 03 AUDIO
    INDEX 01 14:21:44
  TRACK 04 AUDIO
    INDEX 01 16:46:29
  TRACK 05 AUDIO
    INDEX 01 18:44:32
  TRACK 06 AUDIO
    INDEX 01 21:40:49
  TRACK 07 AUDIO
    INDEX 01 24:22:24
  TRACK 08 AUDIO
    INDEX 01 26:02:37
  TRACK 09 AUDIO
    INDEX 01 27:49:71
  TRACK 10 AUDIO
    INDEX 01 30:45:63
  TRACK 11 AUDIO
    INDEX 01 33:06:33
  TRACK 12 AUDIO
    INDEX 01 34:42:32
  TRACK 13 AUDIO
    INDEX 01 37:02:03
  TRACK 14 AUDIO
    INDEX 01 39:53:14
  TRACK 15 AUDIO
    INDEX 01 41:23:56
  TRACK 16 AUDIO
    INDEX 01 43:44:47
  TRACK 17 AUDIO
    INDEX 01 45:59:61
  TRACK 18 AUDIO
    INDEX 01 48:59:72
  TRACK 19 AUDIO
    INDEX 01 51:33:41
  TRACK 20 AUDIO
    INDEX 01 55:02:37
  TRACK 21 AUDIO
    INDEX 01 56:29:28
  TRACK 22 AUDIO
    INDEX 01 58:47:22
  TRACK 23 AUDIO
    INDEX 01 60:24:09
  TRACK 24 AUDIO
    INDEX 01 61:35:47
 
 
Link to comment
Share on other sites

I'm pretty sure I've never seen a bin file where there's a mix of 2048 and 2352 byte sectors in the same file. How did that even happen?! That's probably messing things up and the file is running out of data (assuming the program is using 2352 bytes for everything), which in turn makes the last few tracks have weird sizes (or no/negative size). Most drives will reject tracks less than 4 seconds in length.

 

Can you please go into 'Write' mode, load the CUE and then click the 'View Image Information' button in the 'Source' box. Take screenshots of that please (it scrolls and I'll need to see it all) and attach them in a reply. Thank you.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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