"Richard A. Smith" wrote:
>
> I have a few questions on cdrdao
>
> #1 If I place the drivers file in "/var/share/cdrdao/" or whereever it claims to
> put it the program dies with "Illegal Instruction." Leaving it out so that it
> uses the internal table works fine.
Do you have an Intel CPU? I've got some reports that my pre compiled
binaries contain some Intel optimized code (I'm not sure why) that
fails on AMD CPUs. Maybe you can try to recompile the package on your
host and check if the crash still occurs.
I checked the code if there is bug in the driver table reading function
but it looks OK to me.
> #3 DAE is very slooooow. Much slower than cdparanoia.
Cdrdao reads the sub-channel data in addition to the main channel
audio data. Maybe this slows down the extraction process. Especially,
if you get lots of CRC errors, your drive is probably not able to
retrieve the sub-channel data correctly. BTW, the CRC errors are only
related to the sub-channel data so there's no real need to correct them
since it does not have an effect to the audio data.
You could try to run with options '--driver generic-mmc:0x30 --fast-toc'
to avoid the sub-channel reading, but it won't detect pre-gaps in index
marks this way. It's also worth trying to use options
'--driver generic-mmc:0x10' or '--driver generic-mmc:0x13' to select
different sub-channel reading modes.
> #4 CD-Text info in the TOC must be positioned as the next to last block before
> the source statement. Anywhere else generates an error. The documentation
> dosn't mention this. The examples do show it correctly which is how I figured it
> out.
For track specifications the man page says that a CD-TEXT block may
follow the sub-channel flag settings. This means that it comes before
data source definitions. Do you think I should point out this more
explicitly? However, I just noticed that the description for the location
of the global CD-TEXT data block is misleading.
> #5 My Global PERFORMER statement don't seem to be honored. If I leave the
> PERFORMER statement out of the track cd-text info block I get an error. A
> gcdmaster created file also adds these statements even if "disable performer" is
> selected. The documentation suggests that if they are not declared the global
> will be used.
I decided to not have such a magic automatism to avoid unwanted results
caused by a missing entry for a track. Unfortunately, I missed to update
the documentation.
> #6 The cd that I burned last night has some isolated artifacts and wierd audio
> anomalities yet I never received a buffer underflow. 93% was the smallest buffer
> fill and a sucessful burn was reported.
>
> However, it was burned at 6x while I was doing other things on the machine. 6x is
> pushing the limits of my ISA SCSI card. (8x dies) I am going to try a reburn at
> 4x tonight but I would have thought that I would have received a buffer underflow
> or some other error. Is is possible to muck up a recording without a buffer
> underflow?
Usually, the source audio data is already corrupted. Did you check that?
Otherwise it might have been a temporary problem with the CD-R media.
Andreas
--
Andreas Mueller Tel: +49 89 67808848
Ramsmeierstr. 1 email priv: [EMAIL PROTECTED]
85579 Neubiberg, Germany work: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
