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
------------------------------------------------------------------------------
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
