Envelope-to: greg@gregfolkert.net Delivery-date: Wed, 23 Jun 2004 12:00:28 -0400 From: Greg Folkert Reply-To: greg@gregfolkert.net To: GripUser List Subject: [Grip-users] Habitual questions: suggestions for RIP/ENCODE issues Date: Wed, 23 Jun 2004 11:47:06 -0400 I am getting tired of people just sending an e-mail when the answers are in the archive. So I will be re-sending this message every time someone does that. I am not mad, just frustrated that people either: 1) look casually and miss it (how I don't know the answer has been given so many times it is pathetic) 2) DO NOT search or look at the archives, but say they do. 3) Are not able to search the EN-TAR-NET effectively, basic the searching skills of a slug. (many many many people fall into this category) 4) Just "WANT THE ANSWER NOW!" and demand the answer from other people usually kindly offering assistance. 5) Classify any search as a waste and just want the "primary developer" to answer all of their questions, as they rank up there in richness or brattyness or elitism (at least elitism, I can forgive that... /me being one :) 6) Some other unthoughtful reason, I haven't thought of. So as of Right now, here is the e-mail. I'll be pasting this as text to: http://www.gregfolkert.net/files/grip-haq-faq.txt I use 2.6.5 right now, have for a while. Settled on it for now. I've tried to use the "integrated" cd-paranoia. Failed Miserably every time, zero length MP3 and OGGs. Turned out it was the cd-paranoia that was not reading the devices properly... using flaky methods Switch to a good 2.6.5+ kernel on your distro. It will be worth it. Period. I have ended up using CDDA2WAV with the "paranoia" correction. I get .wav files that are as close to perfect as possible even from Severely scratched CDs. Yet, I get the speed of CDDA2WAV when the CD is in pristine or very good shape, even questionable shape. I never disable the paranoia checking. The only downside is that the "extra paranoia" is not used by CDDA2WAV, but I have yet to notice a discernible difference. Every problem I have seen come through this list with ripping/encoding problems (lately that is) has been a ripper reading device improperly. The encoding seems to work with no problems if the ripping works. Here are the IMPORTANT parts of my grip config. I mean important too. GRIP 2 grip_version 3.2.0 cd_device /dev/hda force_scsi ripexename /usr/bin/cdda2wav ripcmdline -D ATA:0,0,0 -l 128 -paranoia -H -g -x -t %t -O wav %w Explanations: cd_device Anecdotal... just there so GRIP doesn't complain and it can read the CD proper for the CDDB info. It could be a standard device definition (/dev/hda) or a devfs definition (/dev/blah/bla/bla/d0) or a udev device (which look like a standard device) force_scsi I find it is needed to make things work. ripexename The actual name and location of the ripper ripcmdline explanations: -D ATA:0,0,0 extremely important (set your 0,0,0 to the proper one for your machine) -l 128 buffers (bigger is better, 128 max will fail if larger) -paranoia important to get the error correction needed/wanted the only issue, extra paranoia is not enabled :( frown -H Eliminates the info and cddb files generation as GRIP does that automagically -g Formats status output from cdda2wav for easier GUI status parsing -x Sets the rip quality to MAXIMUM. This is always good as the encoder can always mixdown -t %t Track Number controlled by GRIP automagically -O wav Output format, wav is the (not the only though) accepted standard for the source format for encoding from. %w The output file name, controlled by GRIP again. Hopefully I will just send this out, time and time again to fix that same question "No ripping after a bit, but encodes just fine what it does rip, WTF?" Cheeries. -- greg@gregfolkert.net REMEMBER ED CURRY! http://www.iwethey.org/ed_curry Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup