Hi Joerg...

I read over my e-mail and felt I had left something out, sorry.  

Both the working and non-working CDs were made using cdrecord.  

The working CD was made using the inf2cdtext.pl PERL script to 
make a cdtext.dat file. Then, I used cdrecord and this file to 
create a working CD.  

Something like:
cdrecord -dev=0,0,0 -v -dao textfile=cdtext.dat *.wav

The non-working CD was made using just cdrecord.

Something like:
cdrecord -dev=0,0,0 -v -dao -text  *.wav

Do you think this is consistent with a buggy CDROM drive?

                ...thanks, [EMAIL PROTECTED]


> >About: creating CD's with CD-TEXT (cdtext) data using cdrecord, cdda2wav
> >and inf2cdtext.pl 
>       ^^^^^
>       You don"t need this anymore. 
>       Cdrecord does understand and convert the tags from the .inf files.
> 
> >The cdda2wav program pulls ISRC records from CDs (along with many other
> >types of information), but then adds "-" to the field to make it easier
> 
> Partially right/wrong:
> 
> While the '-' is missing in the ISRC data in the subchannel data inside
> a track, it _is_ present in the CD_text field in the TOC of the CD.
> 
> >to read.  These fields end up in the audio_xx.inf files. Both cdrecord
> >(which can use the audio_xx.inf files directly) and inf2cdtext.pl (which
> >can use the audio_xx.inf files to create a single cdtext.dat file which
> >cdrecord can use instead of reading each audio_xx.inf files) do not take
> >these "-" out of the ISRC fields.  I don't believe this is a problem on
> >my cdtext capable console player, but programs like xmcd appear to find
> >the problem and not play the CD.
> 
> This is how all commercial CD's that I am aware of look like.
> 
> >Joerg, it looks like you already have code to remove the "-" in the ISRC
> >field in cdrecord.  So I am assuming this is the direction you want to
> >go instead of removing the code in cdda2wav which adds the "-"
> >characters to the ISRC fields.  This change appears to activate your
> >code:
> 
> Why should I make the CDs created with cdrecorc look different from
> commercial CD's?
> 
> 
> >I should add that I have been adding the following line to the last
> >audio_xx.inf file (it can probably be added to any audio_xx.inf file) in
> >order to make cdrecord produce a CD which looks to have proper cdtext
> >data (it might be necessary, but I haven't arranged a test to make
> >sure):
> 
> >Albumperformer= 'Various Artists'
> 
> This is just missing code in cdda2wav. Cdrecord will eventually
> add automatically such a tag if all tracks contain the same information.
> 
> >Then I used the command:
> 
> >cdrecord -dev=0,0,0 -v -dao -text  *.wav
> 
> >However, after all this, I still wasn't able to make a playable CD.  My
> >console CD player reads all the cdtext data and displays it.  But, only
> >the first track is playable in the normal sense.  The second track
> >plays, but the CD timer stays at 00 seconds.  Subsequent tracks can not
> >be found by skipping to their beginnings.  The only way to listen to the
> >whole CD is to let the console player play through all tracks in
> >sequence.
> 
> This looks like you writer has buggy firmware and thus creates broken
> sub-channel data.
> 
> >But here is what bugs me. Using the following command:
> 
> >cdrecord -vv -toc -dev 0,0,0
> 
> >I can get a dump of the cdtext.dat file from both the working and
> >non-working CD.  Both cdtext.dat files turn out to be the same!  Joerg,
> >at this point, I am lost.  If you have any suggestions as to what to
> >test next I would be willing to try them.
> 
> If the CD-Text is identical, then the writer is buggy.
> 
> J�rg
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to