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
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Cdrtools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cdrtools-support
