Ron Stordahl <[email protected]> wrote: > With respect to the use of PREGAP in the Cue Sheet. It should be optional. > When not included prior to the first INDEX statement I understand that an > automatic pregap of 2 seconds is created prior to track 1. With CDRWin I > never do use a pregap statement and that is what I observe. > With my original 'Large.cue' I do not use a PREGAP statement and get > successful burns on all 9 drives with CD-RW discs and on 4 of 9 with CD-R > discs. > Without the PREGAP statement this is an excerpt of the debug log for LG_E60N > 00:48.75: > Sending CUE sheet... > 00:48.84: > cdrecord: CUE sheet not accepted. Retrying with minimum > pregapsize = 1. > 01:28.47: > cdrecord: Input/output error. write_g1: scsi sendcmd: no error > 01:28.47: > CDB: 2A 00 FF FF D1 B7 00 02 9F 00 > 01:28.48: > status: 0x2 (CHECK CONDITION) > 01:28.48: > Sense Bytes: 70 00 04 00 00 00 00 0E 00 00 00 00 09 00 00 00 00 00 > 01:28.48: > Sense Key: 0x4 Hardware Error, Segment 0 > 01:28.50: > Sense Code: 0x09 Qual 0x00 (track following error) Fru 0x0 > 01:28.50: > Sense flags: Blk 0 (not valid) > 01:28.50: > cmd finished after 39.624s timeout 200s > 01:28.50: > cdrecord: Could not write Lead-in. > 01:28.58: > SAO startsec: -11849 > 01:28.58: > Writing lead-in... > 01:28.58: > write CD-Text data: error after 0 bytes > 01:28.59: > Writing time: 39.873s (00:00:39.873) > 01:28.59: > cdrecord: fifo had 64 puts and 0 gets. > 01:28.59: > cdrecord: fifo was 0 times empty and 0 times full, min fill was > 100%. > 01:28.61: > > 01:28.61: > Execution completed. > I have added the PREGAP statement, using 'Large_added_pregap.cue', here is an > excerpt: > PREGAP 00:02:00 > INDEX 01 00:00:00 > With this added PREGAP statement thhis is an excerpt of the debug log for > LG_E60N > 00:48.48: > Sending CUE sheet... > 00:48.59: > cdrecord: CUE sheet not accepted. Retrying with minimum > pregapsize = 1. > 01:27.95: > cdrecord: Input/output error. write_g1: scsi sendcmd: no error > 01:27.95: > CDB: 2A 00 FF FF D1 B7 00 02 9F 00 > 01:27.97: > status: 0x2 (CHECK CONDITION) > 01:27.97: > Sense Bytes: 70 00 04 00 00 00 00 0E 00 00 00 00 09 00 00 00 00 00 > 01:27.97: > Sense Key: 0x4 Hardware Error, Segment 0 > 01:27.97: > Sense Code: 0x09 Qual 0x00 (track following error) Fru 0x0 > 01:27.98: > Sense flags: Blk 0 (not valid) > 01:27.98: > cmd finished after 39.358s timeout 200s > 01:27.98: > cdrecord: Could not write Lead-in. > 01:28.06: > SAO startsec: -11849 > 01:28.06: > Writing lead-in... > 01:28.06: > write CD-Text data: error after 0 bytes > 01:28.08: > Writing time: 39.608s (00:00:39.608) > 01:28.08: > cdrecord: fifo had 64 puts and 0 gets. > 01:28.08: > cdrecord: fifo was 0 times empty and 0 times full, min fill was > 100%. > 01:28.09: > > 01:28.09: > Execution completed. > The results are the same. > Perhaps cdrtfe is mangling the cue sheets in some manner..however I currently > do now know this. > I provided links to the cue sheets as I do not know if the mailing list > allows attachments. > But I will attach the cue sheets and perhaps they will be accepted. > Ron Stordahl
A track following error while trying to write is a problem at optical level. BTW: If you like to understand what happens, when there is no write error, it may be a good idea to use -vv. IIRC, this causes the MMC standard notation of the CUR sheet that is sent to the drive to be pronted. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Cdrtools-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdrtools-support
