"Richard A. Smith" wrote:
>
> On Mon, 04 Sep 2000 21:51:27 +0200, Andreas Mueller wrote:
>
> >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.
>
> Ah.. thats probally it.. I have an AMD. I will get the source and try a compiled
>version
> tonight.
Can you please check where the faulty code is located (maybe a stack
trace is enough). I guess it is a library which is statically linked
to the cdrdao executable because I'm always compiling without special
Intel optimizations.
> >> #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
>
> Its on a TEAC R58S. How would one go about figuring out if it has issues with
>sub-channel
> reading?
Just by trying the driver options I mentioned.
> So I gather from this that cdparanoia dosen't read sub-channel data?
Right.
> The man page doesn't
> say anything about it. Also the man page of cdparanoia seems to suggest to me that
>by
> default its in a "full paranoia" mode as I only see options to disable various
>checking
> and not to enable it. Is this the case?
Yes.
> Ahh.. that explains things... Also I noticed if you use gcdmaster to create
>cd-text info
> from scratch it indeed does not add the performer info if disable is selected. But
>if you
> have a PERFORMER statment in the file when loaded an then selecting disable performer
> still writes performer statements.
The idea of the CD-TEXT table entry dialog is just to add the CD-TEXT
data to the project that was entered in this dialog.
Disabling the performer entries has just the effect that
hitting the TAB key directly jumps to the next title field. It does
not mean that the performer data will not be used. If you want to
enter the performer just once you'll have to enter the global performer
and then use the 'Fill Performer' button to add it to the track
performer fields.
> In addition, gcdmaster does not create a LANGUAGE MAP block either.
It does but you have to select the language in the 'Disk Info'
dialog.
> If a LANGAGE MAP is not specified cdrdao will not write any cd-text info. It also
>dosen't give any error or
> warnings or such. The only way to see if CD-TEXT info is being written is to enable
>the
> advanced debugging output.
That's really a problem. I'll add a warning message for that.
My idea was to be able to easily switch off the CD-TEXT data writing
by setting the language to 'Undefined' without the need to remove
it completely.
> How hard would it be to add a --verify option that went back and double checked the
>audio
> stream so I can play with various modes and see what works best?
I've no idea how to let a program determine if audio data is OK :)
I think the algorithms of cdparanoia try to do something like that
but I'm not familiar with it. Would be an interesting option.
> My sucessfull burn used mode 1 (jitter correction only) for the read and then burned
>at 4x
> and created what seems to be my first flawless CD-TEXT CD.
Can you verify if the CD-TEXT data is OK? Do you have a consumer
CD-player with CD-TEXT capabilities?
Regards,
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]
