cdrtools-support Mailing List for cdrecord (Page 3)

Highly portable CD/DVD/BluRay command line recording software

Brought to you by: fbrosson, schily

cdrtools-support — Cdrtools user support

You can subscribe to this list here.

2014	Jan	Feb	Mar	Apr	May	Jun	Jul (4)	Aug (3)	Sep	Oct	Nov (2)	Dec (1)
2015	Jan (3)	Feb	Mar (3)	Apr	May (5)	Jun	Jul	Aug	Sep	Oct (23)	Nov (5)	Dec (6)
2016	Jan (22)	Feb (20)	Mar	Apr	May (4)	Jun (4)	Jul	Aug (7)	Sep (1)	Oct	Nov (2)	Dec (1)
2017	Jan	Feb	Mar (8)	Apr	May	Jun	Jul	Aug (1)	Sep	Oct	Nov	Dec (1)
2018	Jan (1)	Feb (1)	Mar (1)	Apr	May	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec (1)
2019	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (3)	Dec
2021	Jan (6)	Feb (3)	Mar (2)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec

Flat | Threaded

<< < 1 2 3 4 5 6 > >> (Page 3 of 6)

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Joerg S. <Joe...@fo...> - 2016-02-24 10:31:49

Ron Stordahl <ron...@ya...> wrote:

> To do this, you could add
>
>      INDEX 00 05:00:14
>
> before INDEX 01 for track 2 and so on...----------------------
>
> So following your recommendation I created this Cue Sheet:
> FILE "..\Large.wav" WAVE
>   TRACK 01 AUDIO
>     INDEX 01 00:00:00
>   TRACK 02 AUDIO
>     INDEX 00 05:00:14
>     INDEX 01 05:02:14
>   TRACK 03 AUDIO
>     INDEX 00 10:28:14
>     INDEX 01 10:30:14
>   TRACK 04 AUDIO
>     INDEX 00 16:18:01
>     INDEX 01 16:20:01
>   TRACK 05 AUDIO
>     INDEX 00 24:21:00
>     INDEX 01 24:23:00
>   TRACK 06 AUDIO
>     INDEX 00 34:52:00
>     INDEX 01 34:54:00
>   TRACK 07 AUDIO
>     INDEX 00 44:17:01
>     INDEX 01 44:19:01
>   TRACK 08 AUDIO
>     INDEX 00 48:21:03
>     INDEX 01 48:23:03

This is a correct cue sheet.

> That Cue sheet produces the identical warning message:
> 01:38.34: > Sending CUE sheet...
> 01:38.34: >  01 00 00 01 00 00 00 00
> 01:38.34: >  01 01 00 00 00 00 00 00
> 01:38.34: >  01 01 01 00 00 00 02 00
> 01:38.34: >  01 02 00 00 00 05 02 0E
> 01:38.34: >  01 02 01 00 00 05 04 0E
> 01:38.36: >  01 03 00 00 00 0A 1E 0E
> 01:38.36: >  01 03 01 00 00 0A 20 0E
> 01:38.36: >  01 04 00 00 00 10 14 01
> 01:38.36: >  01 04 01 00 00 10 16 01
> 01:38.36: >  01 05 00 00 00 18 17 00
> 01:38.36: >  01 05 01 00 00 18 19 00
> 01:38.37: >  01 06 00 00 00 22 36 00
> 01:38.37: >  01 06 01 00 00 22 38 00
> 01:38.37: >  01 07 00 00 00 2C 13 01
> 01:38.37: >  01 07 01 00 00 2C 15 01
> 01:38.37: >  01 08 00 00 00 30 17 03
> 01:38.37: >  01 08 01 00 00 30 19 03
> 01:38.39: >  01 AA 01 01 00 37 3A 40
> 01:38.39: > cdrecord: WARNING: Drive returns wrong startsec (0) using -150
> 01:40.08: > Writing pregap for track 1 at -150
> 01:40.08: > Starting new track at sector: 0
> The burn continues successfully to completion.
> The test was done with the ASUS drive using a CD-RW disc.

This warning message is unrelated to the cue sheet but related to just another 
firmware bug in your drive.


BTW: I asked the author of EAC about how he interprets cue sheets.

His reply was that he interprets them exactly the same way as I do:

-	If INDEX 00 is missing, INDEX 00 == INDEX 01

-	The CUE format does not allow to include a INDEX 00 and a INDEX 01
	line with the same time values.

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-23 18:20:32

Joerg
The Cue Sheet immediately below is exactly the format of  Example #1 on the Example Cue Sheets page of the CDRWin documentation:
FILE "..\Large.wav" WAVE
  TRACK 01 AUDIO
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    INDEX 01 05:02:14
  TRACK 03 AUDIO
     INDEX 01 10:30:14
  TRACK 04 AUDIO
    INDEX 01 16:20:01
  TRACK 05 AUDIO
    INDEX 01 24:23:00
  TRACK 06 AUDIO
    INDEX 01 34:54:00
  TRACK 07 AUDIO
    INDEX 01 44:19:01
  TRACK 08 AUDIO
    INDEX 01 48:23:03
Are you saying this is not a legal Cue Sheet?
That Cue Sheet returns this message:
00:49.08: > Sending CUE sheet...
00:49.08: >  01 00 00 01 00 00 00 00
00:49.08: >  01 01 00 00 00 00 00 00
00:49.08: >  01 01 01 00 00 00 02 00
00:49.08: >  01 02 00 00 00 05 04 0E
00:49.08: >  01 02 01 00 00 05 04 0E
00:49.09: >  01 03 00 00 00 0A 20 0E
00:49.09: >  01 03 01 00 00 0A 20 0E
00:49.09: >  01 04 00 00 00 10 16 01
00:49.09: >  01 04 01 00 00 10 16 01
00:49.09: >  01 05 00 00 00 18 19 00
00:49.09: >  01 05 01 00 00 18 19 00
00:49.11: >  01 06 00 00 00 22 38 00
00:49.11: >  01 06 01 00 00 22 38 00
00:49.11: >  01 07 00 00 00 2C 15 01
00:49.11: >  01 07 01 00 00 2C 15 01
00:49.11: >  01 08 00 00 00 30 19 03
00:49.11: >  01 08 01 00 00 30 19 03
00:49.11: >  01 AA 01 01 00 37 3A 40
00:49.13: > cdrecord: WARNING: Drive returns wrong startsec (0) using -150
00:50.83: > Writing pregap for track 1 at -150
00:50.84: > Starting new track at sector: 0
The burn continues successfully to completion.

You have suggested making changes to the Cue Sheet thus:
---------------------
If you have other drives that don't accept this cue sheet, I recommend you to 
create a legal cue sheet and use it.

To do this, you could add

     INDEX 00 05:00:14

before INDEX 01 for track 2 and so on...----------------------

So following your recommendation I created this Cue Sheet:
FILE "..\Large.wav" WAVE
  TRACK 01 AUDIO
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    INDEX 00 05:00:14
    INDEX 01 05:02:14
  TRACK 03 AUDIO
    INDEX 00 10:28:14
    INDEX 01 10:30:14
  TRACK 04 AUDIO
    INDEX 00 16:18:01
    INDEX 01 16:20:01
  TRACK 05 AUDIO
    INDEX 00 24:21:00
    INDEX 01 24:23:00
  TRACK 06 AUDIO
    INDEX 00 34:52:00
    INDEX 01 34:54:00
  TRACK 07 AUDIO
    INDEX 00 44:17:01
    INDEX 01 44:19:01
  TRACK 08 AUDIO
    INDEX 00 48:21:03
    INDEX 01 48:23:03

That Cue sheet produces the identical warning message:
01:38.34: > Sending CUE sheet...
01:38.34: >  01 00 00 01 00 00 00 00
01:38.34: >  01 01 00 00 00 00 00 00
01:38.34: >  01 01 01 00 00 00 02 00
01:38.34: >  01 02 00 00 00 05 02 0E
01:38.34: >  01 02 01 00 00 05 04 0E
01:38.36: >  01 03 00 00 00 0A 1E 0E
01:38.36: >  01 03 01 00 00 0A 20 0E
01:38.36: >  01 04 00 00 00 10 14 01
01:38.36: >  01 04 01 00 00 10 16 01
01:38.36: >  01 05 00 00 00 18 17 00
01:38.36: >  01 05 01 00 00 18 19 00
01:38.37: >  01 06 00 00 00 22 36 00
01:38.37: >  01 06 01 00 00 22 38 00
01:38.37: >  01 07 00 00 00 2C 13 01
01:38.37: >  01 07 01 00 00 2C 15 01
01:38.37: >  01 08 00 00 00 30 17 03
01:38.37: >  01 08 01 00 00 30 19 03
01:38.39: >  01 AA 01 01 00 37 3A 40
01:38.39: > cdrecord: WARNING: Drive returns wrong startsec (0) using -150
01:40.08: > Writing pregap for track 1 at -150
01:40.08: > Starting new track at sector: 0
The burn continues successfully to completion.
The test was done with the ASUS drive using a CD-RW disc.

Are there additional changes needed to modified Cue Sheet?
Ron Stordahl

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Joerg S. <Joe...@fo...> - 2016-02-23 11:13:49

Ron Stordahl <ron...@ya...> wrote:

> Joerg
> I realize that you probably did mean -vv rather than  -VV, as the later generated an enormous amount of debug data.  However since I did run both I am providing links to both just in case.
> Writing E-CD to ASUS here are the relevant documents:
> Debug logs with cdrecord -vv  :  http://www.dxspots.com/cd/cdrtfe_log-vv.7zDebug logs with cdrecord -VV : http://www.dxspots.com/cd/cdrtfe_log_uppercase-VV.7zThe CUE sheet used : http://www.dxspots.com/cd/E-CD_test/Test_Files/Large/Special_Cues/Large_minimal.cue
> Complete test set and results : http://www.dxspots.com/cd/E-CD_test.7z
> Here is the Large_minimal.cue
> REM Large-minimal.cue is the minimal cue sheet for the large test wave file.
> FILE "..\Large.wav" WAVE
>   TRACK 01 AUDIO
>     INDEX 01 00:00:00
>   TRACK 02 AUDIO
>     INDEX 01 05:02:14
>   TRACK 03 AUDIO
>      INDEX 01 10:30:14
>   TRACK 04 AUDIO
>     INDEX 01 16:20:01
>   TRACK 05 AUDIO
>     INDEX 01 24:23:00
>   TRACK 06 AUDIO
>     INDEX 01 34:54:00
>   TRACK 07 AUDIO
>     INDEX 01 44:19:01
>   TRACK 08 AUDIO
>     INDEX 01 48:23:03
> Excerpts from cdrtfe_log-vv.txt:
> 00:50.29: > Start: Disc Image
> 00:50.29: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -vv -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test/Test_Files/Large/Special_Cues/Large_minimal.cue
> 01:02.42: > Sending CUE sheet...
> 01:02.42: >  01 00 00 41 00 00 00 00
> 01:02.42: >  01 01 00 00 00 00 00 00
> 01:02.43: >  01 01 01 00 00 00 02 00
> 01:02.43: >  01 02 00 00 00 05 04 0E
> 01:02.43: >  01 02 01 00 00 05 04 0E
> 01:02.45: >  01 03 00 00 00 0A 20 0E
> 01:02.45: >  01 03 01 00 00 0A 20 0E
> 01:02.45: >  01 04 00 00 00 10 16 01
> 01:02.46: >  01 04 01 00 00 10 16 01
> 01:02.46: >  01 05 00 00 00 18 19 00
> 01:02.46: >  01 05 01 00 00 18 19 00
> 01:02.46: >  01 06 00 00 00 22 38 00
> 01:02.46: >  01 06 01 00 00 22 38 00
> 01:02.46: >  01 07 00 00 00 2C 15 01
> 01:02.48: >  01 07 01 00 00 2C 15 01
> 01:02.48: >  01 08 00 00 00 30 19 03
> 01:02.48: >  01 08 01 00 00 30 19 03
> 01:19.06: >  01 AA 01 01 00 37 3A 40

Looks OK, except that the index 0 positions for track 2 ff
are invalid according to the red book.

> 01:19.06: > SAO startsec: -11077
> 01:19.06: > Writing lead-in...
> 01:19.06: > Lead-in write time:   21.262s (00:00:21.262)
> 01:19.25: > Writing pregap for track 1 at -150
> 01:19.25: > Starting new track at sector: 0
> 01:49.31: > Track 01:   50 of   50 MB written (fifo 100%) [buf 100%]  10.8x.
> 01:49.33: > Track 01: Total bytes read/written: 53305728/53305728 (22664 sectors).
> 01:49.33: > Starting new track at sector: 22664

Didn't you write that the drive rejects this?

If you have other drives that don't accept this cue sheet, I recommend you to 
create a legal cue sheet and use it.

To do this, you could add

     INDEX 00 05:00:14

before INDEX 01 for track 2 and so on...

see also the official cue sheet documentation from CDRWin.

> Note that with the Large_minimal.cue the the message appears:
>
> 01:19.25: > Writing pregap for track 1 at -150
> 01:19.25: > Starting new track at sector: 0
> 150 frames is 2 seconds.  Did you intend for that to be 'minus 150'?  It seems to me it should be 'plus 150'.

NO, what cdrecord does is 100% correct: the time 00:00.00 is sector -150 and the 
time 00:02.00 is sector 0. See Red Book...

> My limited understanding is that without a PREGAP statement the default is to impose a pregap of 2 seconds of digital silence generated by cdrecord, however CD players start playing at index 01 so that 2 seconds is not actually seen by a typical cd player.

This is not documented in the cdrwin documentation.

Note that your cue sheet explicitely tries to avoid INDEX 00
and this can only be achieved by sending INDEX 00 with the same
time stamp as INDEX 01. If your drive does not accept this, you are lost 
because you try to get something illegal that is not granted to work.


> This is described about half way down this page:  http://www.pcnineoneone.com/howto/cdburnadv4.html
> If one uses the PREGAP statement, it is additive (I am not sure about this!).  So if I wrote:
> PREGAP 00:01:00INDEX 01 00:00:00
> The effect would be 1+2 seconds of PREGAP...maybe.
> I could try writing with CDRWin and then read the disc using cdrtfe debug data prove this one way or the other.
> I am just speculating and you are the expert so I hope the data I am providing is helpful.
> I am hoping that the problems start with the pregap processing, but it seems strange the all 9 drives write what appears to be the correct E-CD with CD-RWs, but some (too many really) fail with CD-Rs.

If CDRWin behaves different than cdrecord for this, then CDRWin does not follow 
it's own documentation.

>From the original documentation:

Rules: 
 
All index numbers must be between 0 and 99 inclusive. The first index must 
be 0 or 1 with all other indexes being sequential to the first one. The 
first index of a file must start at 00:00:00. 
 
INDEX 0 Specifies the starting time of the track "pregap". 
 
INDEX 1 Specifies the starting time of the track data. This is the only 
index that is stored in the disc's table-of-contents. 

-------

I interpret this in a way that the absense of INDEX 00 enforces INDEX 00 == 
INDEX 01

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-23 00:43:25

Joerg
I realize that you probably did mean -vv rather than  -VV, as the later generated an enormous amount of debug data.  However since I did run both I am providing links to both just in case.
Writing E-CD to ASUS here are the relevant documents:
Debug logs with cdrecord -vv  :  http://www.dxspots.com/cd/cdrtfe_log-vv.7zDebug logs with cdrecord -VV : http://www.dxspots.com/cd/cdrtfe_log_uppercase-VV.7zThe CUE sheet used : http://www.dxspots.com/cd/E-CD_test/Test_Files/Large/Special_Cues/Large_minimal.cue
Complete test set and results : http://www.dxspots.com/cd/E-CD_test.7z
Here is the Large_minimal.cue
REM Large-minimal.cue is the minimal cue sheet for the large test wave file.
FILE "..\Large.wav" WAVE
  TRACK 01 AUDIO
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    INDEX 01 05:02:14
  TRACK 03 AUDIO
     INDEX 01 10:30:14
  TRACK 04 AUDIO
    INDEX 01 16:20:01
  TRACK 05 AUDIO
    INDEX 01 24:23:00
  TRACK 06 AUDIO
    INDEX 01 34:54:00
  TRACK 07 AUDIO
    INDEX 01 44:19:01
  TRACK 08 AUDIO
    INDEX 01 48:23:03
Excerpts from cdrtfe_log-vv.txt:
00:50.29: > Start: Disc Image
00:50.29: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -vv -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test/Test_Files/Large/Special_Cues/Large_minimal.cue
01:02.42: > Sending CUE sheet...
01:02.42: >  01 00 00 41 00 00 00 00
01:02.42: >  01 01 00 00 00 00 00 00
01:02.43: >  01 01 01 00 00 00 02 00
01:02.43: >  01 02 00 00 00 05 04 0E
01:02.43: >  01 02 01 00 00 05 04 0E
01:02.45: >  01 03 00 00 00 0A 20 0E
01:02.45: >  01 03 01 00 00 0A 20 0E
01:02.45: >  01 04 00 00 00 10 16 01
01:02.46: >  01 04 01 00 00 10 16 01
01:02.46: >  01 05 00 00 00 18 19 00
01:02.46: >  01 05 01 00 00 18 19 00
01:02.46: >  01 06 00 00 00 22 38 00
01:02.46: >  01 06 01 00 00 22 38 00
01:02.46: >  01 07 00 00 00 2C 15 01
01:02.48: >  01 07 01 00 00 2C 15 01
01:02.48: >  01 08 00 00 00 30 19 03
01:02.48: >  01 08 01 00 00 30 19 03
01:19.06: >  01 AA 01 01 00 37 3A 40
01:19.06: > SAO startsec: -11077
01:19.06: > Writing lead-in...
01:19.06: > Lead-in write time:   21.262s (00:00:21.262)
01:19.25: > Writing pregap for track 1 at -150
01:19.25: > Starting new track at sector: 0
01:49.31: > Track 01:   50 of   50 MB written (fifo 100%) [buf 100%]  10.8x.
01:49.33: > Track 01: Total bytes read/written: 53305728/53305728 (22664 sectors).
01:49.33: > Starting new track at sector: 22664
02:21.95: > Track 02:   55 of   55 MB written (fifo 100%) [buf 100%]  10.3x.
02:21.96: > Track 02: Total bytes read/written: 57859200/57859200 (24600 sectors).
02:21.96: > Starting new track at sector: 47264
02:56.76: > Track 03:   58 of   58 MB written (fifo 100%) [buf 100%]  10.8x.
02:56.76: > Track 03: Total bytes read/written: 61709424/61709424 (26237 sectors).
02:56.78: > Starting new track at sector: 73501
03:44.83: > Track 04:   81 of   81 MB written (fifo 100%) [buf 100%]   9.8x.
03:44.83: > Track 04: Total bytes read/written: 85198848/85198848 (36224 sectors).
03:44.84: > Starting new track at sector: 109725
04:47.62: > Track 05:  106 of  106 MB written (fifo 100%) [buf 100%]  10.2x.
04:47.62: > Track 05: Total bytes read/written: 111308400/111308400 (47325 sectors).
04:47.63: > Starting new track at sector: 157050
05:43.84: > Track 06:   95 of   95 MB written (fifo 100%) [buf 100%]  10.5x.
05:43.86: > Track 06: Total bytes read/written: 99668352/99668352 (42376 sectors).
05:43.86: > Starting new track at sector: 199426
06:08.13: > Track 07:   41 of   41 MB written (fifo 100%) [buf 100%]  10.3x.
06:08.13: > Track 07: Total bytes read/written: 43046304/43046304 (18302 sectors).
06:08.15: > Starting new track at sector: 217728
06:53.29: > Track 08:   76 of   76 MB written (fifo 100%) [buf 100%]  10.3x.
06:53.29: > WARNING: padding up to secsize (by 1340 bytes).
06:53.29: > Track 08: Total bytes read/written: 80051332/80052672 (34036 sectors).
06:53.31: > Writing  time:  355.493s (00:05:55.493)
06:53.31: > Average write speed  10.0x.
06:53.31: > Min drive buffer fill was 100%
07:48.58: > Fixating...
07:48.58: > Fixating time:   55.270s (00:00:55.270)
07:48.59: > cdrecord: fifo had 9328 puts and 9328 gets.
07:48.59: > cdrecord: fifo was 0 times empty and 9257 times full, min fill was 96%.
07:48.59: > BURN-Free was 15 times used.
07:48.59: > 
07:48.61: > Execution completed.   
Note that with the Large_minimal.cue the the message appears:

01:19.25: > Writing pregap for track 1 at -150
01:19.25: > Starting new track at sector: 0
150 frames is 2 seconds.  Did you intend for that to be 'minus 150'?  It seems to me it should be 'plus 150'.

My limited understanding is that without a PREGAP statement the default is to impose a pregap of 2 seconds of digital silence generated by cdrecord, however CD players start playing at index 01 so that 2 seconds is not actually seen by a typical cd player.

This is described about half way down this page:  http://www.pcnineoneone.com/howto/cdburnadv4.html
If one uses the PREGAP statement, it is additive (I am not sure about this!).  So if I wrote:
PREGAP 00:01:00INDEX 01 00:00:00
The effect would be 1+2 seconds of PREGAP...maybe.
I could try writing with CDRWin and then read the disc using cdrtfe debug data proving this one way or the other.
I am just speculating and you are the expert so I hope the data I am providing is helpful.
I am hoping that the problems start with the pregap processing, but it seems strange the all 9 drives write what appears to be the correct E-CD with CD-RWs, but some (too many really) fail with CD-Rs.

Hopefully the answer is to attack this one step at a time.  I will help in any way I am able.

Thank you,
Ron Stordahl

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-22 21:00:12

Should that option be -vv or -VV.   I have run with -vv and it didn't object, but perhaps it didn't give me all the info.  I found -VV in the howto

Ron
 

    On Monday, February 22, 2016 9:58 AM, Joerg Schilling <Joe...@fo...> wrote:
 

 Ron Stordahl <ron...@ya...> wrote:

> Joerg
>
> You asked: "What is the reason for creating hand written CUE sheets?:"
> I don't know of any other way to do so.  These are all original discs, not extracted from other cds.  With CDRWin there was a GUI to create a binary file of CD-Text information, which was then referenced in the CUE file for the audio session.  The only way I know how to accomplish this is to create a text CUE sheet.
>
> If there is another way to do this I would be interested in knowing.
> Further testing of CUE files, I have created a minimal cue file:
> REM Large-minimal.cue is the minimal cue sheet for the large test wave file.
> FILE "Large.wav" WAVE
>   TRACK 01 AUDIO
>     INDEX 01 00:00:00
>   TRACK 02 AUDIO
>     INDEX 01 05:02:14
>   TRACK 03 AUDIO
>      INDEX 01 10:30:14
>   TRACK 04 AUDIO
>     INDEX 01 16:20:01
>   TRACK 05 AUDIO
>     INDEX 01 24:23:00
>   TRACK 06 AUDIO
>     INDEX 01 34:54:00
>   TRACK 07 AUDIO
>     INDEX 01 44:19:01
>   TRACK 08 AUDIO
>     INDEX 01 48:23:03
> From the debug log:
> The cdrecord command:
> 00:39.64: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test/Test_Files/Large/Large-minimal.cue
>
> Note that Oliver said his program makes no changes to the CUE sheet, but simply passes it to cdrecord as shown above.  Incidentally Large-minimal.cue is a protected file just to be sure.
>
>
> This minimal cue file causes cdrecord to report the same 'CUE sheet not accepted...':
>
> 00:46.99: > Sending CUE sheet...
> 00:47.10: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
> 00:47.10: > cdrecord: WARNING: Drive returns wrong startsec (0) using -150
> 00:51.72: > Writing pregap for track 1 at -150

Please send the raw cue sheet as send to the drive by cdrecord.

This is printed by cdrecord if you use cdrecord -vv

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
      joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Joerg S. <Joe...@fo...> - 2016-02-22 15:58:21

Ron Stordahl <ron...@ya...> wrote:

> Joerg
>
> You asked: "What is the reason for creating hand written CUE sheets?:"
> I don't know of any other way to do so.  These are all original discs, not extracted from other cds.  With CDRWin there was a GUI to create a binary file of CD-Text information, which was then referenced in the CUE file for the audio session.  The only way I know how to accomplish this is to create a text CUE sheet.
>
> If there is another way to do this I would be interested in knowing.
> Further testing of CUE files, I have created a minimal cue file:
> REM Large-minimal.cue is the minimal cue sheet for the large test wave file.
> FILE "Large.wav" WAVE
>   TRACK 01 AUDIO
>     INDEX 01 00:00:00
>   TRACK 02 AUDIO
>     INDEX 01 05:02:14
>   TRACK 03 AUDIO
>      INDEX 01 10:30:14
>   TRACK 04 AUDIO
>     INDEX 01 16:20:01
>   TRACK 05 AUDIO
>     INDEX 01 24:23:00
>   TRACK 06 AUDIO
>     INDEX 01 34:54:00
>   TRACK 07 AUDIO
>     INDEX 01 44:19:01
>   TRACK 08 AUDIO
>     INDEX 01 48:23:03
> From the debug log:
> The cdrecord command:
> 00:39.64: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test/Test_Files/Large/Large-minimal.cue
>
> Note that Oliver said his program makes no changes to the CUE sheet, but simply passes it to cdrecord as shown above.  Incidentally Large-minimal.cue is a protected file just to be sure.
>
>
> This minimal cue file causes cdrecord to report the same 'CUE sheet not accepted...':
>
> 00:46.99: > Sending CUE sheet...
> 00:47.10: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
> 00:47.10: > cdrecord: WARNING: Drive returns wrong startsec (0) using -150
> 00:51.72: > Writing pregap for track 1 at -150

Please send the raw cue sheet as send to the drive by cdrecord.

This is printed by cdrecord if you use cdrecord -vv

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-18 20:03:35

Joerg

You asked: "What is the reason for creating hand written CUE sheets?:"
I don't know of any other way to do so.  These are all original discs, not extracted from other cds.  With CDRWin there was a GUI to create a binary file of CD-Text information, which was then referenced in the CUE file for the audio session.  The only way I know how to accomplish this is to create a text CUE sheet.

If there is another way to do this I would be interested in knowing.
Further testing of CUE files, I have created a minimal cue file:
REM Large-minimal.cue is the minimal cue sheet for the large test wave file.
FILE "Large.wav" WAVE
  TRACK 01 AUDIO
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    INDEX 01 05:02:14
  TRACK 03 AUDIO
     INDEX 01 10:30:14
  TRACK 04 AUDIO
    INDEX 01 16:20:01
  TRACK 05 AUDIO
    INDEX 01 24:23:00
  TRACK 06 AUDIO
    INDEX 01 34:54:00
  TRACK 07 AUDIO
    INDEX 01 44:19:01
  TRACK 08 AUDIO
    INDEX 01 48:23:03
>From the debug log:
The cdrecord command:
00:39.64: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test/Test_Files/Large/Large-minimal.cue

Note that Oliver said his program makes no changes to the CUE sheet, but simply passes it to cdrecord as shown above.  Incidentally Large-minimal.cue is a protected file just to be sure.


This minimal cue file causes cdrecord to report the same 'CUE sheet not accepted...':

00:46.99: > Sending CUE sheet...
00:47.10: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
00:47.10: > cdrecord: WARNING: Drive returns wrong startsec (0) using -150
00:51.72: > Writing pregap for track 1 at -150
00:51.73: > Starting new track at sector: 0
01:36.81: > Track 01:   50 of   50 MB written (fifo 100%) [buf  90%]  10.5x.
01:36.81: > Track 01: Total bytes read/written: 53305728/53305728 (22664 sectors).
01:36.83: > Starting new track at sector: 22664
02:09.62: > Track 02:   55 of   55 MB written (fifo 100%) [buf  90%]  10.3x.
02:09.62: > Track 02: Total bytes read/written: 57859200/57859200 (24600 sectors).
02:09.64: > Starting new track at sector: 47264
02:44.61: > Track 03:   58 of   58 MB written (fifo 100%) [buf  90%]  10.5x.
02:44.61: > Track 03: Total bytes read/written: 61709424/61709424 (26237 sectors).
02:44.63: > Starting new track at sector: 73501
03:32.91: > Track 04:   81 of   81 MB written (fifo 100%) [buf  90%]  10.1x.
03:32.93: > Track 04: Total bytes read/written: 85198848/85198848 (36224 sectors).
03:32.93: > Starting new track at sector: 109725
04:36.03: > Track 05:  106 of  106 MB written (fifo 100%) [buf  90%]   9.7x.
04:36.04: > Track 05: Total bytes read/written: 111308400/111308400 (47325 sectors).
04:36.04: > Starting new track at sector: 157050
05:32.55: > Track 06:   95 of   95 MB written (fifo 100%) [buf  90%]  10.5x.
05:32.55: > Track 06: Total bytes read/written: 99668352/99668352 (42376 sectors).
05:32.56: > Starting new track at sector: 199426
05:56.95: > Track 07:   41 of   41 MB written (fifo 100%) [buf  90%]  10.3x.
05:56.96: > Track 07: Total bytes read/written: 43046304/43046304 (18302 sectors).
05:56.96: > Starting new track at sector: 217728
06:42.33: > Track 08:   76 of   76 MB written (fifo 100%) [buf  90%]  10.3x.
06:42.33: > WARNING: padding up to secsize (by 1340 bytes).
06:42.33: > Track 08: Total bytes read/written: 80051332/80052672 (34036 sectors).
06:42.34: > Writing  time:  355.368s (00:05:55.368)
06:42.34: > Average write speed   9.4x.
06:42.34: > Min drive buffer fill was 90%
06:42.36: > Fixating...
07:02.73: > Fixating time:   20.389s (00:00:20.389)
07:02.84: > cdrecord: fifo had 9328 puts and 9328 gets.
07:02.84: > cdrecord: fifo was 0 times empty and 9086 times full, min fill was 90%.
07:02.86: > 
07:02.86: > Execution completed.
Can you tell me what changes to make to the CUE sheet to avoid this problem.  It may not be what is causing the failures when using CD-R rather than CD-RW disc (keep in mind that all of the drives successfully write the Large E-CD test when using CD-RW discs).
Maybe if the CUE sheet issue is corrected, other problems with CD-Rs will go away.  One can hope!

OH..one more thing.  Can you enable posting to the forum directly via the web?  My other sourceforge forums all allow direct posting via the web.  cdrtools-support is the only one I am subscribed to that does not have that option enabled.
Some strange things are going on for posting via e-mail.  My prior posting had attachments..and for some reason the entire text was somehow turned into a html attachment rather than being displayed.  Also I never did get the posting sent to me via e-mail.  I have that option turned on in the mailman set up, but something isn't working as expected.  This is the reason I am providing web links for files which I would otherwise attach.


Thank you
Ron Stordahl

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Joerg S. <Joe...@fo...> - 2016-02-18 17:48:03

Ron Stordahl <ron...@ya...> wrote:

> I send the message below and it was rejected as being 78694 bytes in length, which is beyond the 40kb limit. 

Your first mail did repeat the old text and thus was too large.

> Yet the message was only 5,925 characters in length and had no attachments.  So I am sending it as a separate message.
> =================
> Lets start with the CUE sheet.  It is in E-CD_Test.7z as it is part of the test dataset.  But here it is:
>
> REM Large.cue to be used with CDRTFE (http://cdrtfe.sourceforge.net/cdrtfe/index_en.html) includes inline CD-Text commands
> REM This is the first step of the process of creating an Enhanced-CD (CD-DA + CD-Rom Mode 2 Form 1)
> REM The next line enables CDRTOOLS processing of ARRANGER, COMPOSER & MESSAGE
> REM CDRTOOLS
> REM Commands DATE & GENRE are unsupported in CDRTOOLS as far as I know. I would like them!

These names are not part of the CD-Text standard, but rather part of the CDDB 
protocol.

> REM DATE 1999
> REM GENRE Classical
> CATALOG 1234567890123
> ARRANGER "TestCD Album Arranger"
> COMPOSER "TestCD Album Composer"
> SONGWRITER "TestCD Album Songwriter"
> MESSAGE "TestCD Album Message"
> TITLE "TestCD Album Title"
> PERFORMER "TestCD Album Performer"
> FILE "Large.wav" WAVE
>   TRACK 01 AUDIO
>     TITLE "TestCD Track 1 Title"
>     PERFORMER "TestCD Track 1 Performer"
>     COMPOSER "TestCD Track 1 Composer"
>     SONGWRITER "TestCD Track 1 Songwriter"
>     ARRANGER "TestCD Track 1 Arranger"
>     MESSAGE "TestCD Track 1 Message"
>     ISRC ABCDE0000001

"AB" is no legal 2-char country code. It may be that a drive does not accept it.

If there are problems, it helps to see what kind of MMC CUE sheet cdrecord makes 
from this text.

In general, the CDR-WIN CUE sheet system is seen typically less useful than the 
*.inf notation.

What is the reason for creating hand written CUE sheets?

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Joerg S. <Joe...@fo...> - 2016-02-18 17:42:27

Ron Stordahl <ron...@ya...> 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:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Oliver V. <ker...@us...> - 2016-02-17 23:44:02

Am 17.02.2016 um 23:28 schrieb Ron Stordahl:
> Perhaps cdrtfe is mangling the cue sheets in some manner

no, cdrtfe does not change the cue sheet. It just takes the filename of 
the cue sheet which the user has selected, creates the cdrecord 
commandline according to the project's settings and then executes this 
commandline.

Oliver

[Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-17 22:28:42

Attachments: Large_added_pregap.cue Large.cue

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

[Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-17 20:08:10

I send the message below and it was rejected as being 78694 bytes in length, which is beyond the 40kb limit. 

Yet the message was only 5,925 characters in length and had no attachments.  So I am sending it as a separate message.
=================
Lets start with the CUE sheet.  It is in E-CD_Test.7z as it is part of the test dataset.  But here it is:

REM Large.cue to be used with CDRTFE (http://cdrtfe.sourceforge.net/cdrtfe/index_en.html) includes inline CD-Text commands
REM This is the first step of the process of creating an Enhanced-CD (CD-DA + CD-Rom Mode 2 Form 1)
REM The next line enables CDRTOOLS processing of ARRANGER, COMPOSER & MESSAGE
REM CDRTOOLS
REM Commands DATE & GENRE are unsupported in CDRTOOLS as far as I know. I would like them!
REM DATE 1999
REM GENRE Classical
CATALOG 1234567890123
ARRANGER "TestCD Album Arranger"
COMPOSER "TestCD Album Composer"
SONGWRITER "TestCD Album Songwriter"
MESSAGE "TestCD Album Message"
TITLE "TestCD Album Title"
PERFORMER "TestCD Album Performer"
FILE "Large.wav" WAVE
  TRACK 01 AUDIO
    TITLE "TestCD Track 1 Title"
    PERFORMER "TestCD Track 1 Performer"
    COMPOSER "TestCD Track 1 Composer"
    SONGWRITER "TestCD Track 1 Songwriter"
    ARRANGER "TestCD Track 1 Arranger"
    MESSAGE "TestCD Track 1 Message"
    ISRC ABCDE0000001
REM CDRTFE complains with just presence of INDEX 01 00:00:00, but makes some internal adjustment which
REM 'corrects' it and produces an identical indexed disc as CDRWin.  However I would like to know what
REM command I should enter so it does the same, but without complaint.  
REM I tried a pregap of 00:02:00 with the result that the first track is prefixed by 4 seconds of silence.
REM I tired a pregap of 00:00:00 which was unaccepted and the program halted.
REM Without the PREGAP statement the disc is generated correctly with a 2 second automatic pregap, just as
REM is done by CDRWin. I also tried index 00 00:02:00 and this fails with a program halt.
REM As such I proceed with INDEX as below, creating a correct audio session with an automatic pregap of 2 seconds.
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    TITLE "TestCD Track 2 Title"
    PERFORMER "TestCD Track 2 Performer"
    COMPOSER "TestCD Track 2 Composer"
    SONGWRITER "TestCD Track 2 Songwriter"
    ARRANGER "TestCD Track 2 Arranger"
    MESSAGE "TestCD Track 2 Message"
    ISRC ABCDE0000002
    INDEX 01 05:02:14
  TRACK 03 AUDIO
    TITLE "TestCD Track 3 Title"
    PERFORMER "TestCD Track 3 Performer"
    COMPOSER "TestCD Track 3 Composer"
    SONGWRITER "TestCD Track 3 Songwriter"
    ARRANGER "TestCD Track 3 Arranger"
    MESSAGE "TestCD Track 3 Message"
    ISRC ABCDE0000003
    INDEX 01 10:30:14
  TRACK 04 AUDIO
    TITLE "TestCD Track 4 Title"
    PERFORMER "TestCD Track 4 Performer"
    COMPOSER "TestCD Track 4 Composer"
    SONGWRITER "TestCD Track 4 Songwriter"
    ARRANGER "TestCD Track 4 Arranger"
    MESSAGE "TestCD Track 4 Message"
    ISRC ABCDE0000004
    INDEX 01 16:20:01
  TRACK 05 AUDIO
    TITLE "TestCD Track 5 Title"
    PERFORMER "TestCD Track 5 Performer"
    COMPOSER "TestCD Track 5 Composer"
    SONGWRITER "TestCD Track 5 Songwriter"
    ARRANGER "TestCD Track 5 Arranger"
    MESSAGE "TestCD Track 5 Message"
    ISRC ABCDE0000005
    INDEX 01 24:23:00
  TRACK 06 AUDIO
    TITLE "TestCD Track 6 Title"
    PERFORMER "TestCD Track 6 Performer"
    COMPOSER "TestCD Track 6 Composer"
    SONGWRITER "TestCD Track 6 Songwriter"
    ARRANGER "TestCD Track 6 Arranger"
    MESSAGE "TestCD Track 6 Message"
    ISRC ABCDE0000006
    INDEX 01 34:54:00
  TRACK 07 AUDIO
    TITLE "TestCD Track 7 Title"
    PERFORMER "TestCD Track 7 Performer"
    COMPOSER "TestCD Track 7 Composer"
    SONGWRITER "TestCD Track 7 Songwriter"
    ARRANGER "TestCD Track 7 Arranger"
    MESSAGE "TestCD Track 7 Message"
    ISRC ABCDE0000007
    INDEX 01 44:19:01
  TRACK 08 AUDIO
    TITLE "TestCD Track 8 Title"
    PERFORMER "TestCD Track 8 Performer"
    COMPOSER "TestCD Track 8 Composer"
    SONGWRITER "TestCD Track 8 Songwriter"
    ARRANGER "TestCD Track 8 Arranger"
    MESSAGE "TestCD Track 8 Message"
    ISRC ABCDE0000008
    INDEX 01 48:23:03

Note that I had experimented with the pregap statement to avoid the warning message.  I documented that as excerpted from the CUE Sheet above:
REM CDRTFE complains with just presence of INDEX 01 00:00:00, but makes some internal adjustment which
REM 'corrects' it and produces an identical indexed disc as CDRWin.  However I would like to know what
REM command I should enter so it does the same, but without complaint.  
REM I tried a pregap of 00:02:00 with the result that the first track is prefixed by 4 seconds of silence.
REM I tired a pregap of 00:00:00 which was unaccepted and the program halted.
REM Without the PREGAP statement the disc is generated correctly with a 2 second automatic pregap, just as
REM is done by CDRWin. I also tried index 00 00:02:00 and this fails with a program halt.
REM As such I proceed with INDEX as below, creating a correct audio session with an automatic pregap of 2 seconds.
What I will do is add PREGAP 00:02:00 immediately prior to INDEX 01 00:00:00 and then rerun, beginning with the LG_E60N.  Earlier when I did this I noted that it results in an actual pregap of 4 seconds.  If that results in 4 seconds of silence at the beginning of a sound recording that would be a problem.
I will note that the CUE Sheet definition appears to have originated with Jeff Arnold author of CDRWin.  It is documented in the help file for that program.  PREGAP appears to be optional, when not included a pregap of 2 seconds prior to the first audio track is automatically inserted.
https://en.wikipedia.org/wiki/Cue_sheet_%28computing%29#Cue_sheet_syntax shows many examples of CUE Sheets, all without a PREGAP statement.
Keep in mind that all 9 drives successfully write the Large E-CD using CD-RW discs.
I will include the PREGAP 00:02:00 statement and retest. 

If that is source the problem finding that out will be an important step.
Ron Stordahl

[Cdrtools-support] Problems Creating Enhanced-CDs - short posting

From: Ron S. <ron...@ya...> - 2016-02-17 00:05:33

I am concerned that my posting was too large..and it looks like it may have bounced.

Here is a copy of it as a download:
http://204.221.76.52/cd/Analysis_20160216.txt

Ron Stordahl

[Cdrtools-support] Problems creating Enhanced-CDs - updated

From: Ron S. <ron...@ya...> - 2016-02-16 23:52:14

This file, Analysis_20160216.txt and Collected_Notes.txt are available at:

    http://204.221.76.52/cd/Analysis.7z
    
The complete test set (including the Analysis) is at:

    http://204.221.76.52/cd/E-CD_Test.7z
    
The files excerpted in the analysis below are found at:

    http://204.221.76.52/cd/Edited_Debug_Logs.7z
    
A PDF file describing the testing procedure is at:

    http://204.221.76.52/cd/E-CD_Test_Procedure.pdf
    
Joerg

I have done as you requested, providing for each failing burn an analysis of the debug logs with my comments
about things that don't seem right.

There is a bit of guessing involved, as I don't completely understand the details of the reports generated by cdrecord -v with the many reporting options.

I tried to pick out the anomalies by comparing a run with CD-R to an otherwise identical run with CD-RW.  All 9 drives tested successfully burn the E-CD when using CD-RW.  I think this is the best I can do in comparing failing vs successful
burns.  I used a diff line program WinMerge to make the comparisions.

The files which contain all the debug data are contained in http://204.221.76.52/cd/Edited_Debug_Logs.7z
They are edited to make the timestamps all 00:00.00: to facilitate comparison.  The unedited debug logs are
in the full test set http://204.221.76.52/cd/E-CD_Test.7z in the appropriately named folders.

This an overwhelming amout of test data, however I felt it would be best to provide it all at once. 

I am sure you are a very busy person, so please review this when time allows.  I am in no hurry.

Since all the tested drives will successfully burn the large E-CD with CD-RW's, a work-around is to use CD-RW
and if needed to image the multisession CD-RW onto a CD-R. A program, ImgBurn, will do that successfully in a single step, even to those drives which fail to create the E-CD in my testing.

Thanks for giving this your attention as time allows.

I could have attached the smaller files as attachments, but I don't know if attachments are allowed.

Ron Stordahl


The 5 failing drives are (Short ID - Long ID):

LG_E60N = "LG HL-DT-ST DVD-RAM GSA-E60N Rev 1r00"
Phillips = "Phillips PLDS DVE+-RW DH-16AAS Rev JD12"                                    
Plextor = "Plextor PX-891SAF Rev 1rT2"
Samsung = "Samsung TSSTcorp CDDVDW SE-218GNRSBD Rev TS00 USB 2015"
Sony = "Sony DVD RW DRU-830A_SS22"

The numbers starting at column 1 are line numbers in the associated files.
Lines without line numbers are comments.

The 'diff' program used is WinMerge.  Use CTRL+Shift+C to copy with line numbers.

In the file names:
LRF indicates Large E-CD on CD-R Failed
LRWS indicates Large E-CD on CD-RW Successful

Test drive: ASUS
===================

Comparison of ASUS_LRS (Large, CD-R, Successful) vs ASUS_LRWS (Large, CD-RW, Successful):
**********

There are no significant differences other than things directly related to R vs RW.  Addresses nearly identical. The E-CD was created successfully in both cases
   
**********

Test drive: LG_E60N
====================

Comparison of LG_E60N_LRF (Failed using a CD-R disc) vs LG_E60N_LRWS (Succeeded using a CD-RW disc):
**********

File: LG_E60N_LRF.txt (Failed):

539: 00:00.00: > Start: Disc Image
540: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

616: 00:00.00: > Sending CUE sheet...
617: 00:00.00: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
618: 00:00.00: > cdrecord: Input/output error. write_g1: scsi sendcmd: no error
619: 00:00.00: > CDB:  2A 00 FF FF D1 B7 00 02 9F 00

cdrtfe message: cdrecord: Could not write Lead-In.  Could not proceed.

----------

File: LG_E60N_LRWS.txt (Successful):

534: 00:00.00: > Start: Disc Image
535: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

621: 00:00.00: > Sending CUE sheet...
622: 00:00.00: > cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
623: 00:00.00: > SAO startsec: -11077
624: 00:00.00: > Writing lead-in...
625: 00:00.00: > Lead-in write time:   19.609s (00:00:19.609)
626: 00:00.00: > Writing pregap for track 1 at -150

Comment: Writing continues with the E-CD being successfully written.

**********

Test drive Phillips
====================

Comparison of Phillips_LRF.txt (Failed using a CD-R disc) vs Phillips_LRWS.txt (Succeeded using a CD-RW disc):
**********

File: Phillips_LRF.txt (Failed):

549: 00:00.00: > Start: Disc Image
550: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 speed=10 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

876:  00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

936: 00:00.00: > disk status:              incomplete/appendable
937: 00:00.00: > session status:           incomplete/appendable

Comment:  Line 937 seems to indicate a problem.

 949: 00:00.00: > Track  Sess Type   Start Addr End Addr   Size
 950: 00:00.00: > ==============================================
 951: 00:00.00: >     1     1 Audio  0          22663      22664         -1
 952: 00:00.00: >     2     1 Audio  22664      47263      24600          0
 953: 00:00.00: >     3     1 Audio  47264      73500      26237      22664
 954: 00:00.00: >     4     1 Audio  73501      109724     36224      47264
 955: 00:00.00: >     5     1 Audio  109725     157049     47325      73501
 956: 00:00.00: >     6     1 Audio  157050     199425     42376     109725
 957: 00:00.00: >     7     1 Audio  199426     217727     18302     157050
 958: 00:00.00: >     8     1 Audio  217728     251763     34036     199426
 959: 00:00.00: >     9     2 Audio  263164     1166727    903564     229128
 960: 00:00.00: >
 961: 00:00.00: > Last session start address:         263164
 962: 00:00.00: > Last session leadout start address: 1166728
 963: 00:00.00: >
 964: 00:00.00: > Execution completed.

Comment:  Line 959 seems to indicate a problem.

Message:  Not enough space on this disc.  MiByte available (without indicating any number before MiByte)

Comment:  Could not proceed to write CD-ROM session.
----------

File Phillips_LRWS.txt (Successful):

540: 00:00.00: > Start: Disc Image
541: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 speed=10 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Large/Large.cue

911: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

982: 00:00.00: > disk status:              incomplete/appendable
983: 00:00.00: > session status:           empty

 995: 00:00.00: > Track  Sess Type   Start Addr End Addr   Size

 996: 00:00.00: > ==============================================
 997: 00:00.00: >     1     1 Audio  0          22663      22664         -1
 998: 00:00.00: >     2     1 Audio  22664      47263      24600          0
 999: 00:00.00: >     3     1 Audio  47264      73500      26237      22664
1000: 00:00.00: >     4     1 Audio  73501      109724     36224      47264
1001: 00:00.00: >     5     1 Audio  109725     157049     47325      73501
1002: 00:00.00: >     6     1 Audio  157050     199425     42376     109725
1003: 00:00.00: >     7     1 Audio  199426     217727     18302     157050
1004: 00:00.00: >     8     1 Audio  217728     251763     34036     199426
1005: 00:00.00: >     9     2 Blank  263164     359846     96683     229128
1006: 00:00.00: >
1007: 00:00.00: > Last session start address:         0
1008: 00:00.00: > Last session leadout start address: 251764
1009: 00:00.00: > Next writable address:              263164
1010: 00:00.00: > Remaining writable size:            96683
1011: 00:00.00: >
1012: 00:00.00: > Execution completed.

Comment:  Program proceeded to write the CD-ROM session successfully.

**********

Test drive: Plextor
====================

Comparison of Plextor_LRF.txt (Failed using a CD-R disc) vs Plextor_LRWS.txt (Succeeded using a CD-RW disc):
**********

File Plextor_LRF.txt (Failed):

551: 00:00.00: > Start: Disc Image
552: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

882: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

943: 00:00.00: > disk status:              incomplete/appendable
944: 00:00.00: > session status:           incomplete/appendable

Comment:  Line 944 seems to indicate a problem.

 956: 00:00.00: > Track  Sess Type   Start Addr End Addr   Size
 957: 00:00.00: > ==============================================
 958: 00:00.00: >     1     1 Audio  0          22661      22662         -1
 959: 00:00.00: >     2     1 Audio  22664      47261      24598          2
 960: 00:00.00: >     3     1 Audio  47264      73498      26235      22666
 961: 00:00.00: >     4     1 Audio  73501      109722     36222      47266
 962: 00:00.00: >     5     1 Audio  109725     157047     47323      73503
 963: 00:00.00: >     6     1 Audio  157050     199423     42374     109727
 964: 00:00.00: >     7     1 Audio  199426     217725     18300     157052
 965: 00:00.00: >     8     1 Audio  217728     251761     34034     199428
 966: 00:00.00: >     9     2 Audio  263164     1166727    903564     229130
 967: 00:00.00: > 
 968: 00:00.00: > Last session start address:         263164
 969: 00:00.00: > Last session leadout start address: 1166728
 970: 00:00.00: > 
 971: 00:00.00: > Execution completed.
 
Comment:  Line 966 seems to indicate a problem.
 
Message:  Not enough space on this disc.  MiByte available (without indicating any number before MiByte)

Comment:  Could not proceed to write CD-ROM session. 

----------

File Plextor_LRWS.txt (Successful):

543: 00:00.00: > Start: Disc Image
544: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 speed=10 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Large/Large.cue

918: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

990: 00:00.00: > disk status:              incomplete/appendable
991: 00:00.00: > session status:           empty

1003: 00:00.00: > Track  Sess Type   Start Addr End Addr   Size
1004: 00:00.00: > ==============================================
1005: 00:00.00: >     1     1 Audio  0          22661      22662         -1
1006: 00:00.00: >     2     1 Audio  22664      47261      24598          2
1007: 00:00.00: >     3     1 Audio  47264      73498      26235      22666
1008: 00:00.00: >     4     1 Audio  73501      109722     36222      47266
1009: 00:00.00: >     5     1 Audio  109725     157047     47323      73503
1010: 00:00.00: >     6     1 Audio  157050     199423     42374     109727
1011: 00:00.00: >     7     1 Audio  199426     217725     18300     157052
1012: 00:00.00: >     8     1 Audio  217728     251761     34034     199428
1013: 00:00.00: >     9     2 Blank  263164     359846     96683     229130
1014: 00:00.00: > 
1015: 00:00.00: > Last session start address:         0
1016: 00:00.00: > Last session leadout start address: 251762
1017: 00:00.00: > Next writable address:              263164
1018: 00:00.00: > Remaining writable size:            96683
1019: 00:00.00: > 
1020: 00:00.00: > Execution completed.

Comment:  Program proceeded to write the CD-ROM session successfully.

**********

Test drive: Samsung
====================

Comparison of Samsung_LRF.txt (Failed using a CD-R disc) vs Samsung_LRWS.txt (Succeeded using a CD-RW disc):
**********

File Samsung_LRF.txt (Failed):

569: 00:00.00: > Start: Disc Image
570: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

900: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

961: 00:00.00: > disk status:              incomplete/appendable
962: 00:00.00: > session status:           empty

1508: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -xa -v -tao /cygdrive/C/Users/RON_ST~1/AppData/Local/Temp/image.iso

1568: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1569: 00:00.00: >       359847             2048         0x00  Formatted Media
1570: 00:00.00: > Blocks total: 359847 Blocks current: 96683 Blocks remaining: 7465
1571: 00:00.00: > Starting to write CD/DVD/BD at speed 24 in real TAO mode for single session.

1592: 00:00.00: > Reading TOC of Disc. Please wait ...
1593: 00:00.00: > Comparing 28 files with the source files ...
1594: 00:00.00: > 
1595: 00:00.00: > Error! File not found         : d:\AUTORUN.INF
1596: 00:00.00: > Error! File not found         : d:\Dummy01.fil
1597: 00:00.00: > Error! File not found         : d:\Dummy02.fil
1598: 00:00.00: > Error! File not found         : d:\Dummy03.fil
1599: 00:00.00: > Error! File not found         : d:\Dummy04.fil
1600: 00:00.00: > Error! File not found         : d:\Dummy05.fil
1601: 00:00.00: > Error! File not found         : d:\Dummy06.fil
1602: 00:00.00: > Error! File not found         : d:\Dummy07.fil
1603: 00:00.00: > Error! File not found         : d:\Dummy08.fil
1604: 00:00.00: > Error! File not found         : d:\Dummy09.fil
1605: 00:00.00: > Error! File not found         : d:\Dummy10.fil
1606: 00:00.00: > Error! File not found         : d:\Dummy11.fil
1607: 00:00.00: > Error! File not found         : d:\Dummy12.fil
1608: 00:00.00: > Error! File not found         : d:\Dummy13.fil
1609: 00:00.00: > Error! File not found         : d:\Dummy14.fil
1610: 00:00.00: > Error! File not found         : d:\Dummy15.fil
1611: 00:00.00: > Error! File not found         : d:\Dummy16.fil
1612: 00:00.00: > Error! File not found         : d:\Dummy17.fil
1613: 00:00.00: > Error! File not found         : d:\Dummy18.fil
1614: 00:00.00: > Error! File not found         : d:\Dummy19.fil
1615: 00:00.00: > Error! File not found         : d:\Dummy20.fil
1616: 00:00.00: > Error! File not found         : d:\Dummy21.fil
1617: 00:00.00: > Error! File not found         : d:\Dummy22.fil
1618: 00:00.00: > Error! File not found         : d:\Dummy23.fil
1619: 00:00.00: > Error! File not found         : d:\Dummy24.fil
1620: 00:00.00: > Error! File not found         : d:\Dummy25.fil
1621: 00:00.00: > Error! File not found         : d:\E-CD_Test_Test_Procedure.pdf
1622: 00:00.00: > Error! File not found         : d:\ShellRun.exe
1623: 00:00.00: > 
1624: 00:00.00: > 28 error(s) found.

Comment: Windows does not see the CD-ROM session it appears.

1637: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -toc -v

1692: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1693: 00:00.00: >       352382             2048         0x00  Formatted Media
1694: 00:00.00: > first: 1 last 9
1695: 00:00.00: > track:   1 lba:         0 (        0) 00:02:00 adr: 1 control: 0 mode: -1
1696: 00:00.00: > track:   2 lba:     22664 (    90656) 05:04:14 adr: 1 control: 0 mode: -1
1697: 00:00.00: > track:   3 lba:     47264 (   189056) 10:32:14 adr: 1 control: 0 mode: -1
1698: 00:00.00: > track:   4 lba:     73501 (   294004) 16:22:01 adr: 1 control: 0 mode: -1
1699: 00:00.00: > track:   5 lba:    109725 (   438900) 24:25:00 adr: 1 control: 0 mode: -1
1700: 00:00.00: > track:   6 lba:    157050 (   628200) 34:56:00 adr: 1 control: 0 mode: -1
1701: 00:00.00: > track:   7 lba:    199426 (   797704) 44:21:01 adr: 1 control: 0 mode: -1
1702: 00:00.00: > track:   8 lba:    217728 (   870912) 48:25:03 adr: 1 control: 0 mode: -1
1703: 00:00.00: > track:   9 lba:    263164 (  1052656) 58:30:64 adr: 1 control: 4 mode: -1
1704: 00:00.00: > track:lout lba:    352382 (  1409528) 78:20:32 adr: 1 control: 4 mode: -1
1705: 00:00.00: > 
1706: 00:00.00: > Execution completed.

Comment: Line 1703 shows "4 mode: -1", whereas for successful burn CD-RW shows "4 mode: 2" (see below) 

Comment: Beyond this point things look normal to me.

Comment: The burn is unsuccessful.  Windows does not see the CD-ROM session.

----------

File Samsung_LRWS.txt (Successful):

555: 00:00.00: > Start: Disc Image
556: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

925: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

996: 00:00.00: > disk status:              incomplete/appendable
997: 00:00.00: > session status:           empty

1538: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -xa -v -tao /cygdrive/C/Users/RON_ST~1/AppData/Local/Temp/image.iso

1606: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1607: 00:00.00: >       359849             2048         0x00  Formatted Media
1608: 00:00.00: >       359849             2048         0x00  Reserved (0)
1609: 00:00.00: >       295264               32         0x10  Reserved (0)
1610: 00:00.00: > Blocks total: 359849 Blocks current: 96685 Blocks remaining: 7467
1611: 00:00.00: > Starting to write CD/DVD/BD at speed 10 in real TAO mode for single session.


1632: 00:00.00: > Reading TOC of Disc. Please wait ...
1633: 00:00.00: > Comparing 28 files with the source files ...
1634: 00:00.00: > 
1635: 00:00.00: > 0 error(s) found.

Comment: Successful verify of files in CD-ROM session with source files.

1648: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -toc -v

1711: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1712: 00:00.00: >       352382             2048         0x00  Formatted Media
1713: 00:00.00: >       352382             2048         0x00  Reserved (0)
1714: 00:00.00: >       295264               32         0x10  Reserved (0)
1715: 00:00.00: > first: 1 last 9
1716: 00:00.00: > track:   1 lba:         0 (        0) 00:02:00 adr: 1 control: 0 mode: -1
1717: 00:00.00: > track:   2 lba:     22664 (    90656) 05:04:14 adr: 1 control: 0 mode: -1
1718: 00:00.00: > track:   3 lba:     47264 (   189056) 10:32:14 adr: 1 control: 0 mode: -1
1719: 00:00.00: > track:   4 lba:     73501 (   294004) 16:22:01 adr: 1 control: 0 mode: -1
1720: 00:00.00: > track:   5 lba:    109725 (   438900) 24:25:00 adr: 1 control: 0 mode: -1
1721: 00:00.00: > track:   6 lba:    157050 (   628200) 34:56:00 adr: 1 control: 0 mode: -1
1722: 00:00.00: > track:   7 lba:    199426 (   797704) 44:21:01 adr: 1 control: 0 mode: -1
1723: 00:00.00: > track:   8 lba:    217728 (   870912) 48:25:03 adr: 1 control: 0 mode: -1
1724: 00:00.00: > track:   9 lba:    263164 (  1052656) 58:30:64 adr: 1 control: 4 mode: 2
1725: 00:00.00: > track:lout lba:    352382 (  1409528) 78:20:32 adr: 1 control: 4 mode: -1
1726: 00:00.00: > 
1727: 00:00.00: > Execution completed.

Comment: Line 17243 shows "4 mode: 2", whereas for unsuccessful burn CD-R shows "4 mode: -1" 

Comment: The burn successfully created the Large E-CD.

**********

Test drive: Sony
====================

Comparison of Sony_LRF.txt (Failed using a CD-R disc) vs Sony_LRWS.txt (Succeeded using a CD-RW disc):
**********

File Sony_LRF.txt (Failed):

167:           "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -prcap

181:           Write Performance:
182:           START LBA:         0
183:           End LBA:      359834

467:           "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -silent -v

521:             ATIP start of lead in:  -11849 (97:24/01)

Comment:  For successful burn, Sony_LRWS.txt, above line is -11077

522:             ATIP start of lead out: 359847 (79:59/72)

527:               Capacity  Blklen/Sparesz.  Format-type  Type
528:               16763814             2048         0x00  No Media Present or Unknown Capacity

542:           last start of lead in: -11849
543:           last start of lead out: 359847

562: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Test_Files/Large/Large.cue

630: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
631: 00:00.00: >     16763814             2048         0x00  No Media Present or Unknown Capacity
632: 00:00.00: > Blocks total: 359847 Blocks current: 359847 Blocks remaining: 108083
633: 00:00.00: > Starting to write CD/DVD/BD at speed 40 in real SAO mode for multi session.

640: 00:00.00: > SAO startsec: -11849

Comment: For the successful burn with CD-RW this was -11077

1030: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -prcap -v

1040: 00:00.00: > Write Performance:
1041: 00:00.00: > START LBA:         0
1042: 00:00.00: > End LBA:      359834

Comment:  For the successful burn with CD-RW this was 166

1492: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 driveropts=burnfree -xa -v -tao /cygdrive/C/Users/RON_ST~1/AppData/Local/Temp/image.iso

1552: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1553: 00:00.00: >       251764             2048         0x00  Formatted Media
1554: 00:00.00: > Blocks total: 359847 Blocks current: 96683 Blocks remaining: 7465
1555: 00:00.00: > Starting to write CD/DVD/BD at speed 40 in real TAO mode for single session.

1576: 00:00.00: > Reading TOC of Disc. Please wait ...
1577: 00:00.00: > Comparing 28 files with the source files ...
1578: 00:00.00: > 
1579: 00:00.00: > Error! File not found         : d:\AUTORUN.INF
1580: 00:00.00: > Error! File not found         : d:\Dummy01.fil
1581: 00:00.00: > Error! File not found         : d:\Dummy02.fil
1582: 00:00.00: > Error! File not found         : d:\Dummy03.fil
1583: 00:00.00: > Error! File not found         : d:\Dummy04.fil
1584: 00:00.00: > Error! File not found         : d:\Dummy05.fil
1585: 00:00.00: > Error! File not found         : d:\Dummy06.fil
1586: 00:00.00: > Error! File not found         : d:\Dummy07.fil
1587: 00:00.00: > Error! File not found         : d:\Dummy08.fil
1588: 00:00.00: > Error! File not found         : d:\Dummy09.fil
1589: 00:00.00: > Error! File not found         : d:\Dummy10.fil
1590: 00:00.00: > Error! File not found         : d:\Dummy11.fil
1591: 00:00.00: > Error! File not found         : d:\Dummy12.fil
1592: 00:00.00: > Error! File not found         : d:\Dummy13.fil
1593: 00:00.00: > Error! File not found         : d:\Dummy14.fil
1594: 00:00.00: > Error! File not found         : d:\Dummy15.fil
1595: 00:00.00: > Error! File not found         : d:\Dummy16.fil
1596: 00:00.00: > Error! File not found         : d:\Dummy17.fil
1597: 00:00.00: > Error! File not found         : d:\Dummy18.fil
1598: 00:00.00: > Error! File not found         : d:\Dummy19.fil
1599: 00:00.00: > Error! File not found         : d:\Dummy20.fil
1600: 00:00.00: > Error! File not found         : d:\Dummy21.fil
1601: 00:00.00: > Error! File not found         : d:\Dummy22.fil
1602: 00:00.00: > Error! File not found         : d:\Dummy23.fil
1603: 00:00.00: > Error! File not found         : d:\Dummy24.fil
1604: 00:00.00: > Error! File not found         : d:\Dummy25.fil
1605: 00:00.00: > Error! File not found         : d:\E-CD_Test_Test_Procedure.pdf
1606: 00:00.00: > Error! File not found         : d:\ShellRun.exe
1607: 00:00.00: > 
1608: 00:00.00: > 28 error(s) found.

Comment:  Verify fails as Windows does not see the CD-ROM session to do a file verify

1621: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -toc -v

1676: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1677: 00:00.00: >       354631             2048         0x00  Formatted Media
1678: 00:00.00: > first: 1 last 8
1679: 00:00.00: > track:   1 lba:         0 (        0) 00:02:00 adr: 1 control: 0 mode: -1
1680: 00:00.00: > track:   2 lba:     22664 (    90656) 05:04:14 adr: 1 control: 0 mode: -1
1681: 00:00.00: > track:   3 lba:     47264 (   189056) 10:32:14 adr: 1 control: 0 mode: -1
1682: 00:00.00: > track:   4 lba:     73501 (   294004) 16:22:01 adr: 1 control: 0 mode: -1
1683: 00:00.00: > track:   5 lba:    109725 (   438900) 24:25:00 adr: 1 control: 0 mode: -1
1684: 00:00.00: > track:   6 lba:    157050 (   628200) 34:56:00 adr: 1 control: 0 mode: -1
1685: 00:00.00: > track:   7 lba:    199426 (   797704) 44:21:01 adr: 1 control: 0 mode: -1
1686: 00:00.00: > track:   8 lba:    217728 (   870912) 48:25:03 adr: 1 control: 0 mode: -1
1687: 00:00.00: > track:lout lba:    251764 (  1007056) 55:58:64 adr: 1 control: 0 mode: -1
1688: 00:00.00: > 
1689: 00:00.00: > Execution completed.

Comment:  In the successful burn there is a 9th Data track, not present here.

1822: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

1893: 00:00.00: > last start of lead in: 258514
1894: 00:00.00: > last start of lead out: 359847
1895: 00:00.00: > 
1896: 00:00.00: > Track  Sess Type   Start Addr End Addr   Size
1897: 00:00.00: > ==============================================
1898: 00:00.00: >     1     1 Audio  0          22661      22662         -1
1899: 00:00.00: >     2     1 Audio  22664      47261      24598          2
1900: 00:00.00: >     3     1 Audio  47264      73498      26235      22666
1901: 00:00.00: >     4     1 Audio  73501      109722     36222      47266
1902: 00:00.00: >     5     1 Audio  109725     157047     47323      73503
1903: 00:00.00: >     6     1 Audio  157050     199423     42374     109727
1904: 00:00.00: >     7     1 Audio  199426     217725     18300     157052
1905: 00:00.00: >     8     1 Audio  217728     251761     34034     199428
1906: 00:00.00: >     9     2 Blank  263164     352379     89216     229130
1907: 00:00.00: >    10     2 Data   352532     1166727    814196     263316
1908: 00:00.00: > 
1909: 00:00.00: > Last session start address:         352532
1910: 00:00.00: > Last session leadout start address: 1166728

Comment: The above differs significantly from the successful burn with CD-RW.

2142:           "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -silent -v

2208:           disk status:              incomplete/appendable
2209:           session status:           incomplete/appendable

Comment:  In the successful burn both lines are reported as 'complete'.

----------

File Sony_LRWS.txt (Successful):

167:           "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -prcap
 
181:           Write Performance:
182:           START LBA:         0
183:           End LBA:           0

448:           "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -silent -v

503:             ATIP start of lead in:  -11077 (97:34/23)
504:             ATIP start of lead out: 359849 (79:59/74)

516:               Capacity  Blklen/Sparesz.  Format-type  Type
517:                 359849             2048         0x00  Unformated or Blank Media
518:                 295264             2048         0x00  Reserved (0)
519:                 295264               32         0x10  Reserved (0)

534:           last start of lead in: -11077
535:           last start of lead out: 359849
536:           

554: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 speed=10 driveropts=burnfree -v -multi -pad -text -dao cuefile=/cygdrive/C/Users/Ron_Stordahl/Documents/E-CD_Test_Test/Large/Large.cue

630: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
631: 00:00.00: >       359849             2048         0x00  Unformated or Blank Media
632: 00:00.00: >       295264             2048         0x00  Reserved (0)
633: 00:00.00: >       295264               32         0x10  Reserved (0)
634: 00:00.00: > Blocks total: 359849 Blocks current: 359849 Blocks remaining: 108085
635: 00:00.00: > Starting to write CD/DVD/BD at speed 10 in real SAO mode for multi session.

642: 00:00.00: > SAO startsec: -11077

1080: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -prcap -v

1090: 00:00.00: > Write Performance:
1091: 00:00.00: > START LBA:         0
1092: 00:00.00: > End LBA:         166

1547: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" gracetime=5 dev=0,0,0 speed=10 driveropts=burnfree -xa -v -tao /cygdrive/C/Users/RON_ST~1/AppData/Local/Temp/image.iso

1615: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1616: 00:00.00: >       251764             2048         0x00  Formatted Media
1617: 00:00.00: >       295264             2048         0x00  Reserved (0)
1618: 00:00.00: >       295264               32         0x10  Reserved (0)
1619: 00:00.00: > Blocks total: 359849 Blocks current: 96685 Blocks remaining: 7253
1620: 00:00.00: > Starting to write CD/DVD/BD at speed 10 in real TAO mode for single session.

1641: 00:00.00: > Reading TOC of Disc. Please wait ...
1642: 00:00.00: > Comparing 28 files with the source files ...
1643: 00:00.00: > 
1644: 00:00.00: > 0 error(s) found.

1657: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -toc -v

1720: 00:00.00: >     Capacity  Blklen/Sparesz.  Format-type  Type
1721: 00:00.00: >       352596             2048         0x00  Formatted Media
1722: 00:00.00: >       295264             2048         0x00  Reserved (0)
1723: 00:00.00: >       295264               32         0x10  Reserved (0)
1724: 00:00.00: > first: 1 last 9
1725: 00:00.00: > track:   1 lba:         0 (        0) 00:02:00 adr: 1 control: 0 mode: -1
1726: 00:00.00: > track:   2 lba:     22664 (    90656) 05:04:14 adr: 1 control: 0 mode: -1
1727: 00:00.00: > track:   3 lba:     47264 (   189056) 10:32:14 adr: 1 control: 0 mode: -1
1728: 00:00.00: > track:   4 lba:     73501 (   294004) 16:22:01 adr: 1 control: 0 mode: -1
1729: 00:00.00: > track:   5 lba:    109725 (   438900) 24:25:00 adr: 1 control: 0 mode: -1
1730: 00:00.00: > track:   6 lba:    157050 (   628200) 34:56:00 adr: 1 control: 0 mode: -1
1731: 00:00.00: > track:   7 lba:    199426 (   797704) 44:21:01 adr: 1 control: 0 mode: -1
1732: 00:00.00: > track:   8 lba:    217728 (   870912) 48:25:03 adr: 1 control: 0 mode: -1
1733: 00:00.00: > track:   9 lba:    263164 (  1052656) 58:30:64 adr: 1 control: 4 mode: 2
1734: 00:00.00: > track:lout lba:    352596 (  1410384) 78:23:21 adr: 1 control: 4 mode: -1
1735: 00:00.00: > 
1736: 00:00.00: > Execution completed.

1901: 00:00.00: > "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -v

1982: 00:00.00: > last start of lead in: 716730
1983: 00:00.00: > last start of lead out: 1166730
1984: 00:00.00: > 
1985: 00:00.00: > Track  Sess Type   Start Addr End Addr   Size
1986: 00:00.00: > ==============================================
1987: 00:00.00: >     1     1 Audio  0          22661      22662         -1
1988: 00:00.00: >     2     1 Audio  22664      47261      24598          2
1989: 00:00.00: >     3     1 Audio  47264      73498      26235      22666
1990: 00:00.00: >     4     1 Audio  73501      109722     36222      47266
1991: 00:00.00: >     5     1 Audio  109725     157047     47323      73503
1992: 00:00.00: >     6     1 Audio  157050     199423     42374     109727
1993: 00:00.00: >     7     1 Audio  199426     217725     18300     157052
1994: 00:00.00: >     8     1 Audio  217728     251761     34034     199428
1995: 00:00.00: >     9     2 Data   263164     352593     89430     229130
1996: 00:00.00: > 
1997: 00:00.00: > Last session start address:         263164
1998: 00:00.00: > Last session leadout start address: 352594

2215:           "C:\Program Files (x86)\cdrtfe\tools\cdrtools\cdrecord" dev=0,0,0 -minfo -silent -v

2291:           disk status:              complete
2292:           session status:           complete
**********

Re: [Cdrtools-support] Can't write dvd-rw disk with cdrecord

From: Joerg S. <Joe...@fo...> - 2016-02-10 11:17:37

????? ??????? <art...@ya...> wrote:

> I can't write dvd-rw disk with cdrecord. dvd+rw-tools work perfectly
> fine, but I don't want to use both tools to record cd/dvd when I can
> only one. I'am using OpenBSD 5.8

Hi Artur,

It seems that you are suffering from a similar kernel bug as recently discovered 
on Linux.

	Is this device connected via USB-3?

Background:

the kernel reports a DMA residual count that is equal to the expected transfer 
count and there is no other (real) SCSI error reported.

Given that cdrecord decently evaluates all possible error states, it stops 
writing because of this error reported by the kernel.

If dvd+rw-tools work for you, then this is most likely a result of ignoring the 
error codes in dvd+rw-tools.

You can tell cdrecord to ignore this specific error situation by adding the 
option:

	scgopts=ignore-resid

to your command line.

Note that you need to upgrade your outdated cdrecord first, in order to be able
to do so.


> First I blank dvd with:
> $cdrecord -v -dev=/dev/rcd0c -blank=all
> Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
> Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE 
> Supported modes: PACKET SAO LAYER_JUMP
> Drive buf size : 751616 = 734 KB
> Current Secsize: 2048
> WARNING: Phys disk size 1 differs from rzone size 2297888! Prerecorded disk?
> WARNING: Phys start: 196608 Phys end 196608
> Starting to write CD/DVD/BD at speed 2 in real BLANK mode for single session.
> Last chance to quit, starting real write    0 seconds. Operation starts.
> Blanking entire disk
>
> Blanking time: 1752.884s
>
> Then I reload disk and writing with:
> $cdrecord -v -dev=/dev/rcd0c -dao /path/to/image.iso
> drecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd5.8) Copyright (C) 1995-2010 J?rg Schilling                                                       [37/85]
> TOC Type: 1 = CD-ROM
> scsidev: '/dev/rcd0c'
> devname: '/dev/rcd0c'
> scsibus: -2 target: -2 lun: -2
> Using libscg version 'schily-0.9'.
> SCSI buffer size: 61440
> atapi: 0
> Device type    : Removable CD-ROM
> Version        : 0
> Response Format: 2
> Capabilities   : 
> Vendor_info    : 'HL-DT-ST'
> Identifikation : 'DVDRAM GU61N    '
> Revision       : '1.00'
> Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
> Current: DVD-RW sequential recording
> Profile: DVD-R/DL sequential recording 
> Profile: DVD-R/DL layer jump recording 
> Profile: 0x0018 
> Profile: DVD+R/DL 
> Profile: DVD+R 
> Profile: DVD+RW 
> Profile: DVD-RW sequential recording (current)
> Profile: DVD-RW restricted overwrite (current)
> Profile: DVD-RAM 
> Profile: DVD-R sequential recording 
> Profile: DVD-ROM 
> Profile: CD-RW 
> Profile: CD-R 
> Profile: CD-ROM 
> Profile: Removable Disk 
> Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
> Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE 
> Supported modes: PACKET SAO LAYER_JUMP
> Drive buf size : 751616 = 734 KB
> cdrecord: Warning: Cannot read drive buffer.
> cdrecord: Warning: The DMA speed test has been skipped.
> FIFO size      : 4194304 = 4096 KB
> Track 01: data   586 MB        
> Total size:      586 MB = 300348 sectors
> Current Secsize: 2048
> Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 1998148
> Reducing transfer size from 61440 to 32768 bytes.
> Starting to write CD/DVD/BD at speed 2 in real SAO mode for single session.
> Last chance to quit, starting real write    0 seconds. Operation starts.
> Waiting for reader process to fill input buffer ... input buffer ready.
> BURN-Free is ON.
> Turning BURN-Free off
> Starting new track at sector: 0
> Track 01:    0 of  586 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error
> CDB:  2A 00 00 00 00 70 00 00 10 00
> status: 0x0 (GOOD STATUS)
> resid: 32768
> cmd finished after 0.002s timeout 200s

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

[Cdrtools-support] Can't write dvd-rw disk with cdrecord

From: Артур И. <art...@ya...> - 2016-02-10 02:43:23

I can't write dvd-rw disk with cdrecord. dvd+rw-tools work perfectly
fine, but I don't want to use both tools to record cd/dvd when I can
only one. I'am using OpenBSD 5.8

First I blank dvd with:
$cdrecord -v -dev=/dev/rcd0c -blank=all
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE 
Supported modes: PACKET SAO LAYER_JUMP
Drive buf size : 751616 = 734 KB
Current Secsize: 2048
WARNING: Phys disk size 1 differs from rzone size 2297888! Prerecorded disk?
WARNING: Phys start: 196608 Phys end 196608
Starting to write CD/DVD/BD at speed 2 in real BLANK mode for single session.
Last chance to quit, starting real write    0 seconds. Operation starts.
Blanking entire disk

Blanking time: 1752.884s

Then I reload disk and writing with:
$cdrecord -v -dev=/dev/rcd0c -dao /path/to/image.iso
drecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd5.8) Copyright (C) 1995-2010 J�rg Schilling                                                       [37/85]
TOC Type: 1 = CD-ROM
scsidev: '/dev/rcd0c'
devname: '/dev/rcd0c'
scsibus: -2 target: -2 lun: -2
Using libscg version 'schily-0.9'.
SCSI buffer size: 61440
atapi: 0
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'HL-DT-ST'
Identifikation : 'DVDRAM GU61N    '
Revision       : '1.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: DVD-RW sequential recording
Profile: DVD-R/DL sequential recording 
Profile: DVD-R/DL layer jump recording 
Profile: 0x0018 
Profile: DVD+R/DL 
Profile: DVD+R 
Profile: DVD+RW 
Profile: DVD-RW sequential recording (current)
Profile: DVD-RW restricted overwrite (current)
Profile: DVD-RAM 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R 
Profile: CD-ROM 
Profile: Removable Disk 
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE 
Supported modes: PACKET SAO LAYER_JUMP
Drive buf size : 751616 = 734 KB
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
FIFO size      : 4194304 = 4096 KB
Track 01: data   586 MB        
Total size:      586 MB = 300348 sectors
Current Secsize: 2048
Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 1998148
Reducing transfer size from 61440 to 32768 bytes.
Starting to write CD/DVD/BD at speed 2 in real SAO mode for single session.
Last chance to quit, starting real write    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is ON.
Turning BURN-Free off
Starting new track at sector: 0
Track 01:    0 of  586 MB written.cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error
CDB:  2A 00 00 00 00 70 00 00 10 00
status: 0x0 (GOOD STATUS)
resid: 32768
cmd finished after 0.002s timeout 200s

write track data: error after 229376 bytes
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error
CDB:  00 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 0.000s timeout 200s
Writing  time:   12.940s
Average write speed  34.4x.
Fixating...
cdrecord: Input/output error. flush cache: scsi sendcmd: retryable error
CDB:  35 00 00 00 00 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 0.000s timeout 1000s
Trouble flushing the cache
cdrecord: Cannot fixate disk.
Fixating time:    0.000s
cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: retryable error
CDB:  1E 00 00 00 00 00
status: 0x0 (GOOD STATUS)
cmd finished after 0.009s timeout 200s
cdrecord: fifo had 135 puts and 8 gets.
cdrecord: fifo was 0 times empty and 1 times full, min fill was 94%.

In dmesg I see:
cd0(ahci0:4:0): Check Condition (error 0x70) on opcode 0x28
    SENSE KEY: Media Error

Here is with -atip:
$ cdrecord -v -dev=/dev/rcd0c -atip
Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-openbsd5.8) Copyright (C) 1995-2010 J�rg Schilling
TOC Type: 1 = CD-ROM
scsidev: '/dev/rcd0c'
devname: '/dev/rcd0c'
scsibus: -2 target: -2 lun: -2
Using libscg version 'schily-0.9'.
SCSI buffer size: 61440
atapi: 0
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   : 
Vendor_info    : 'HL-DT-ST'
Identifikation : 'DVDRAM GU61N    '
Revision       : '1.00'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: DVD-RW sequential recording
Profile: DVD-R/DL sequential recording 
Profile: DVD-R/DL layer jump recording 
Profile: 0x0018 
Profile: DVD+R/DL 
Profile: DVD+R 
Profile: DVD+RW 
Profile: DVD-RW sequential recording (current)
Profile: DVD-RW restricted overwrite (current)
Profile: DVD-RAM 
Profile: DVD-R sequential recording 
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R 
Profile: CD-ROM 
Profile: Removable Disk 
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE 
Supported modes: PACKET SAO LAYER_JUMP
Drive buf size : 751616 = 734 KB
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
Current Secsize: 2048
book type:       DVD-RW, Version 1.1x (3.2)
disc size:       120mm (0)
maximum rate:    Not specified (15)
number of layers:1                                                                                                                                       [4/284]
track path:      Parallel Track Path (0)
layer type:      Rewritable Area (2)
linear density:  0.267 �m/bit (0)
track density:   0.74 �m/track (0)
phys start:      196608 (0x30000) 
phys end:        496955
end layer 0:     0
bca:             0
phys size:...    300348
copyr prot type: 0
region mgt info: 0
last rma sector: 0
application code:64
physical code:   214
last rec address:16621272
part v./ext code:2/1
ind wr. power:   13
wavelength code: 6
write str. code: 07 88 65 0D
Manufacturer:   'RITEKW01'
rzone size:         40
rzone number:       1
border number:      1
ljrs:               0
track mode:         4 copy: 0
damage:             0
reserved track:     0 blank: 0 incremental: 0 fp: 0
data mode:          1
lra valid:          1
nwa valid:          1
rzone start:        0
next wr addr:       96
free blocks:        2298400
blocking factor:    16
rzone size:         2298496
last recorded addr: 79
read compat lba:    0

    Capacity  Blklen/Sparesz.  Format-type  Type
     2297888             2048         0x00  Unformated or Blank Media
     2297888             2048         0x00  Reserved (0)
     2297888               16         0x10  Reserved (0)
     2297888               16         0x15  Reserved (0)
WARNING: Phys disk size 300348 differs from rzone size 2298496! Prerecorded disk?
WARNING: Phys start: 196608 Phys end 496955

I suspect that problem with bad media/manufacturer, but dvd+rw-tools circumvent
this somehow.

Thank you!

Re: [Cdrtools-support] Problems creating Enhanced-CDs

From: Joerg S. <Joe...@fo...> - 2016-02-05 10:22:39

Ron Stordahl <ron...@ya...> wrote:

> Using cdrtfe CDRTools Frontend, for Windows, I have performed extensive tests on 9 CD writers in writing Enhanced-CDs.
> The details may be read on the cdrtfe sourceforge discussion forum at http://sourceforge.net/p/cdrtfe/discussion/help/thread/cca48c3b/
> I am speculating the issue may be in cdrecord.
>  Any help would be appreciated.

If you don't describe your problem, it is hard to help you.

The term "enhanced cd" is not a technical term for one of the CD variants.

If you like help, please send the following information:

-	What exactly do you like to do and what did not work?

-	what version of cdrtools did you use?

-	what command line with which program from the cdrtools failed?

-	the log from the command above and the error message.
	If cdrecord failed, send the output from "cdrecord -atip" for the
	used media and the output from "cdrecord -v ..." from the cdrecord call
	that was used for writing.

-	Send a log of the state of the medium from before starting to write.
	This information can be retrieved via: "cdrecord -v -minfo"

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

[Cdrtools-support] Problems creating Enhanced-CDs

From: Ron S. <ron...@ya...> - 2016-02-04 22:48:09

Using cdrtfe CDRTools Frontend, for Windows, I have performed extensive tests on 9 CD writers in writing Enhanced-CDs.
The details may be read on the cdrtfe sourceforge discussion forum at http://sourceforge.net/p/cdrtfe/discussion/help/thread/cca48c3b/
I am speculating the issue may be in cdrecord.
 Any help would be appreciated.

Ron Stordahl

Re: [Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Joerg S. <Joe...@fo...> - 2016-01-19 10:38:42

Tao Wang <twa...@gm...> wrote:

> We generalized the API we need, such as 'scsi_read()' and
> 'scsi_write()',  then, implemented those API for Linux and Windows
> separately.
>
> Here is the implementation:
> https://github.com/asalamon74/pktriggercord/blob/master/pslr_scsi_linux.c
> https://github.com/asalamon74/pktriggercord/blob/master/pslr_scsi_win.c
>
> So, basically, we use '/sys/class/scsi_generic' with 'ioctl()'  for
> Linux, and 'DeviceIoControl()' with 'IOCTL_SCSI_PASS_THROUGH_DIRECT'
> for Windows.

For a limited usage, this may look OK but this way, you only support two platforms.
If this is to support a camera, I believe there would be people on many more 
platforms that could be interested in support.


> There are 2 driver candidates I might look into if I'm going to
> implement my own OSX kernel driver.
>
> The first one is the blog written by Joel Reymont:
>
> http://wagerlabs.com/blog/2008/02/04/writing-a-mac-osx-usb-device-driver-that-implements-scsi-pass-through/
>
> And here is the code for it:
>
> https://github.com/wagerlabs/seaforth24
>
> Another one is 'OS-X-SAT-SMART-Driver' written for 'smartmontools':
>
> https://github.com/kasbert/OS-X-SAT-SMART-Driver

Interesting, thank you!

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Tao W. <twa...@gm...> - 2016-01-19 03:20:58

On 18 January 2016 at 23:42, Joerg Schilling
<Joe...@fo...> wrote:
>
>
> Libscg is the most portable solution you may find.
>
> OS X is the only non-orthogonal OS in the list of supported OS. Note that
> libscg supports aprox. 30 different OS types.
>
> Does your project already work on more than one platform?
> If yes, how does it implement this feature?

We generalized the API we need, such as 'scsi_read()' and
'scsi_write()',  then, implemented those API for Linux and Windows
separately.

Here is the implementation:
https://github.com/asalamon74/pktriggercord/blob/master/pslr_scsi_linux.c
https://github.com/asalamon74/pktriggercord/blob/master/pslr_scsi_win.c

So, basically, we use '/sys/class/scsi_generic' with 'ioctl()'  for
Linux, and 'DeviceIoControl()' with 'IOCTL_SCSI_PASS_THROUGH_DIRECT'
for Windows.

> BTW: If you ever write an own driver or if you find somebody who did or who is
> willing to do this for you, please keep me informed as I would be interested to
> use this for better OS X support in libscg.
>
> Jörg

There are 2 driver candidates I might look into if I'm going to
implement my own OSX kernel driver.

The first one is the blog written by Joel Reymont:

http://wagerlabs.com/blog/2008/02/04/writing-a-mac-osx-usb-device-driver-that-implements-scsi-pass-through/

And here is the code for it:

https://github.com/wagerlabs/seaforth24

Another one is 'OS-X-SAT-SMART-Driver' written for 'smartmontools':

https://github.com/kasbert/OS-X-SAT-SMART-Driver

I hope these will help.

Best Regards,
Tao Wang

Re: [Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Joerg S. <Joe...@fo...> - 2016-01-18 12:47:59

Joerg Schilling <Joe...@fo...> wrote:

> Tao Wang <twa...@gm...> wrote:
>
> > I don't think there is a similar device type for a camera under scsi
> > category, and plus the problem, I think maybe the best way to support
> > sending those vendor specific SCSI commands to camera on OS X is to write
> > my own kernel driver for it. It's a little bit too much for this project I
> > think.

BTW: If you ever write an own driver or if you find somebody who did or who is 
willing to do this for you, please keep me informed as I would be interested to 
use this for better OS X support in libscg.

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Joerg S. <Joe...@fo...> - 2016-01-18 12:42:50

Tao Wang <twa...@gm...> wrote:

> I don't think there is a similar device type for a camera under scsi
> category, and plus the problem, I think maybe the best way to support
> sending those vendor specific SCSI commands to camera on OS X is to write
> my own kernel driver for it. It's a little bit too much for this project I
> think.
> Currently the project can work on Linux/Windows, not OS X. I was hoping
> that I can find a more portable solution to support all those 3 platforms.
> It seems that I cannot use 'libscg' for this purpose.

Libscg is the most portable solution you may find.

OS X is the only non-orthogonal OS in the list of supported OS. Note that 
libscg supports aprox. 30 different OS types.

Does your project already work on more than one platform? 
If yes, how does it implement this feature?

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

Re: [Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Tao W. <twa...@gm...> - 2016-01-18 12:22:23

Hi, Jörg,

For OS X, Here is the 'ioreg -l' output for the camera:

    +-o PENTAX K-3@14300000  <class AppleUSBDevice, id 0x100000a10,
registered, matched, active, busy 0 (6 ms), retain 23>

        {

          "sessionID" = 14016892056132

          "iManufacturer" = 1

          "bNumConfigurations" = 1

          "idProduct" = 356

          "bcdDevice" = 256

          "Bus Power Available" = 900

          "USB Address" = 3

          "bMaxPacketSize0" = 9

          "iProduct" = 2

          "iSerialNumber" = 3

          "bDeviceClass" = 0

          "Built-In" = No

          "locationID" = 338690048

          "bDeviceSubClass" = 0

          "bcdUSB" = 768

          "USB Product Name" = "PENTAX K-3"

          "PortNum" = 3

          "non-removable" = "no"

          "IOCFPlugInTypes" =
{"9dc7b780-9ec0-11d4-a54f-000a27052861"="IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle"}

          "bDeviceProtocol" = 0

          "IOUserClientClass" = "IOUSBDeviceUserClientV2"

          "IOPowerManagement" =
{"DevicePowerState"=0,"CurrentPowerState"=3,"CapabilityFlags"=65536,"MaxPowerState"=4,"DriverPowerState"=3}

          "Device Speed" = 3

          "USB Vendor Name" = "RICOH IMAGING COMPANY, LTD."

          "idVendor" = 9723

          "IOGeneralInterest" = "IOCommand is not serializable"

          "USB Serial Number" = "4860600"

          "IOClassNameOverride" = "IOUSBDevice"

        }

I don't think there is a similar device type for a camera under scsi
category, and plus the problem, I think maybe the best way to support
sending those vendor specific SCSI commands to camera on OS X is to write
my own kernel driver for it. It's a little bit too much for this project I
think.
Currently the project can work on Linux/Windows, not OS X. I was hoping
that I can find a more portable solution to support all those 3 platforms.
It seems that I cannot use 'libscg' for this purpose.

Anyway, thanks for your help.

Best Regards,
Tao Wang





On 18 January 2016 at 21:46, Joerg Schilling <
Joe...@fo...> wrote:

> Tao Wang <twa...@gm...> wrote:
>
> > Hi,
> >
> > I'm looking for a cross-platform SCSI communication solution for an open
> > source project, which communicate with Pentax camera via USB (Mass
> Storage)
> > SCSI Pass-through Interface, using 'F0' vendor specific SCSI commands.
> > Someone referenced me to 'libscg', which included in 'cdrtools' project.
>
> libscg is the oldest SCSI generic implementation (it turns 30 this summer)
> and
> it was initially created to send vendor unique commands.
>
> libscg allows to send any command on any target platform as long as the OS
> in question does not prevent this.
>
> > May I ask, what is the current state of 'libscg'? Can I use it for
> sending
> > vendor specific SCSI command cross-platform? Does it support current
> Linux
> > kernel 4.x? OS X 10.11? and Windows 10? Where should I start if I want to
> > use libscg in the project? Thanks.
>
> There recently have been reports about some USB-SCSI related kernel bugs in
> Linux (in special when you are using USB-3), but otherwise  it is known to
> work.
> If you have specific problems on Linux, you need to ask the kernel people
> for
> help.
>
> Regarding OS X, the SCSI subsystem from Apple is a bit ideosyncratic and
> the
> clean interface from early development versions (thatwas taken from Next
> Step)
> has unfortunately been replaced by something that does not work in a
> universal
> way. In other words: OS X does not implement device type independent SCSI
> kernel structures.
>
> You will need to find out whether there is a similar interface for your
> device
> type as it exists for CD-ROM type devices, where the names are:
>
> IOCompactDiscServices/0 or IODVDServices/0 or IOBDServices/0
>
> (replace /0 by any valid instance number).
>
> I recommend to check the Apple device tree for matches...
>
> Let me explain the problem here: Even though a CD-ROM drive is if course
> also
> using the USB<->SCSI mass storage interface, it may be that the OS X
> kernel will
> not give you access to your device.
>
> Jörg
>
> --
>  EMail:jo...@sc...                    (home) Jörg Schilling D-13353
> Berlin
>        joe...@fo... (work) Blog:
> http://schily.blogspot.com/
>  URL:  http://cdrecord.org/private/
> http://sourceforge.net/projects/schilytools/files/'
>

Re: [Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Joerg S. <Joe...@fo...> - 2016-01-18 10:46:35

Tao Wang <twa...@gm...> wrote:

> Hi,
>
> I'm looking for a cross-platform SCSI communication solution for an open
> source project, which communicate with Pentax camera via USB (Mass Storage)
> SCSI Pass-through Interface, using 'F0' vendor specific SCSI commands.
> Someone referenced me to 'libscg', which included in 'cdrtools' project.

libscg is the oldest SCSI generic implementation (it turns 30 this summer) and 
it was initially created to send vendor unique commands.

libscg allows to send any command on any target platform as long as the OS 
in question does not prevent this.

> May I ask, what is the current state of 'libscg'? Can I use it for sending
> vendor specific SCSI command cross-platform? Does it support current Linux
> kernel 4.x? OS X 10.11? and Windows 10? Where should I start if I want to
> use libscg in the project? Thanks.

There recently have been reports about some USB-SCSI related kernel bugs in 
Linux (in special when you are using USB-3), but otherwise  it is known to work.
If you have specific problems on Linux, you need to ask the kernel people for 
help.

Regarding OS X, the SCSI subsystem from Apple is a bit ideosyncratic and the 
clean interface from early development versions (thatwas taken from Next Step) 
has unfortunately been replaced by something that does not work in a universal 
way. In other words: OS X does not implement device type independent SCSI 
kernel structures. 

You will need to find out whether there is a similar interface for your device 
type as it exists for CD-ROM type devices, where the names are:

IOCompactDiscServices/0 or IODVDServices/0 or IOBDServices/0

(replace /0 by any valid instance number).

I recommend to check the Apple device tree for matches...

Let me explain the problem here: Even though a CD-ROM drive is if course also 
using the USB<->SCSI mass storage interface, it may be that the OS X kernel will 
not give you access to your device.

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'

[Cdrtools-support] Can I use libscg to send vendor specific SCSI command cross-platform?

From: Tao W. <twa...@gm...> - 2016-01-18 03:23:41

Hi,

I'm looking for a cross-platform SCSI communication solution for an open
source project, which communicate with Pentax camera via USB (Mass Storage)
SCSI Pass-through Interface, using 'F0' vendor specific SCSI commands.
Someone referenced me to 'libscg', which included in 'cdrtools' project.

May I ask, what is the current state of 'libscg'? Can I use it for sending
vendor specific SCSI command cross-platform? Does it support current Linux
kernel 4.x? OS X 10.11? and Windows 10? Where should I start if I want to
use libscg in the project? Thanks.

Best Regards,
Tao Wang

2 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 2 3 4 5 6 > >> (Page 3 of 6)