Date: Mon, 28 Jan 2002 21:03:33 +0100 From: Martin Faxér <gmh003532@brfmasthugget.se> To: Lars Eggert <larse@ISI.EDU> Cc: multimedia@FreeBSD.org Subject: Re: BCP: CD ripping Message-ID: <20020128210333.6e58aabf.gmh003532@brfmasthugget.se> In-Reply-To: <3C559C46.7000502@isi.edu> References: <3C558EE3.5060708@isi.edu> <20020128191513.77360a03.gmh003532@brfmasthugget.se> <3C559C46.7000502@isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi. Well, I don't see any reason for not using cdda2wav if it both works better and runs faster. :-) I wonder if those errors you are getting are due to the CD being faulty and cdda2wav doing better error correction or if it's a bug in dagrab. I've never had any problems with such errors... You could try with some other CD's and see if you still get the same kind of errors; if you do, I guess a PR would be appropriate. Martin Faxér On Mon, 28 Jan 2002 10:45:26 -0800 Lars Eggert <larse@ISI.EDU> wrote: > Martin Faxér wrote: > > > Personally, I'd say that ``dagrab'' has worked very well for me, for > > ripping the audio tracks into .WAV's. > > > That's ripit's default, but it doesn't always work for me. I see a > number of errors like these: > > acd0: READ_CD - MEDIUM ERROR asc=02 ascq=00 error=04 > or > dagrab: read raw ioctl failed at lba 44750 length 12: Input/output error > > cdda2wav doesn't produce (or detect) these errors, and seems faster. Any > reason not to use that? > > > Thanks, > Lars > > -- > Lars Eggert <larse@isi.edu> Information Sciences Institute > http://www.isi.edu/larse/ University of Southern California > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020128210333.6e58aabf.gmh003532>