audio noise - bad source disc?

2001-02-01 Thread Fernan Aguero
It happened both using cdrdao and cdda2wav + cdrecord, with two different audio source discs. In some tracks, suddenly, the music is replaced by a repetaing noise (like a chack-chack-chack or a door-knocking sound) and then the music resumes again. In another disc, the first two tracks are just

RE: audio noise - bad source disc?

2001-02-01 Thread Karl-Heinz Herrmann
On 31-Jan-01 Fernan Aguero wrote: The question: is there any way to play a ripped cdrdao 'data.bin' or the *.wav files generated by cdda2wav so i can see if I can avoid burning the bad tracks? I know that I should be able to play .wav files, but my selection of multimedia utilities (the

Re: audio noise - bad source disc?

2001-02-01 Thread Karl-Heinz Herrmann
On 01-Feb-01 [EMAIL PROTECTED] wrote: Did you check if cdparanoia follows the right rules for track boundaries? You should extract with both programs and check for identical length of the audio files first. Note that you should do this with a CD that does _not_ start at +2:00 seconds

Re: audio noise - bad source disc?

2001-02-01 Thread Fernan Aguero
Thanks Karl and 'schunn' ([EMAIL PROTECTED]) for your replies. I played the .wav files generated by cdda2wav and the noises are all there in the .wav files. Thus, the burning was OK, the audio extraction from the CD was the problem. now that I think of it, I started using cdda2wav based on the

Re: audio noise - bad source disc?

2001-02-01 Thread Karl-Heinz Herrmann
On 01-Feb-01 Fernan Aguero wrote: As Karl said, cdparanoia (which is what cdrdao uses to rip audio data to disc) does correction and verification. Perhaps this is why I had never noticed a similar problem before (or perhaps it was just luck). You can use both: cdda2wav to get the *.inf files

Re: audio noise - bad source disc?

2001-02-01 Thread schilling
From: Karl-Heinz Herrmann [EMAIL PROTECTED] On 01-Feb-01 Fernan Aguero wrote: As Karl said, cdparanoia (which is what cdrdao uses to rip audio data to disc) does correction and verification. Perhaps this is why I had never noticed a similar problem before (or perhaps it was just luck). You