Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What do you mean not encode properly? Do they not encode at all and are un-playable, or do they just sound a bit crap? (e.g. do they skip or something?)
If you can play the mp3, rip the wav first (if you haven't already done so) and play it. If that doesn't play correctly, it might be a scratch/fingerprint/dust on the cd causing the ripper to have synch problems. You might have to select a few options to put some error-checking on (if you're lucky you'll have C2 support).
What program were you using to convert the CD anyway?
what prog are you using to do the encoding? there are a few buggy mp3 encoders out there - have you tried using a different rate (160 instead of 128)? sometimes that helps.
ok... i just re-read the thread, and i think i missunderstood the problem here - is the mp3 encoder badly encoding the wav, with beeps and skips and stuff, or is it just failing to encode the file altogether?
if the file info only comes up, then, first instinctual guess here: there's something wrong with the way grip or notlame parses the filenames or detects the EOF. i'll try using them when i get home to my linux box and mess around with them if i can find them.
I can record .wav files, but when I try to convert them to mp3 files using notlame, I end up with a 128 byte file with no MP3 music (it seems to contain just the ID3 tag information).
My mp3 settings in grip are as follows:
MP3 Executable: /usr/bin/notlame
MP3 Command line: -v -V 0 %f %o
MP3 file firmat: ~/mp3/%a/%d/%n.mp3
I can successfully convert the file to mp3 in a terminal window by typing /usr/bin/notlame -v -V 0 <musicfile>.wav <musicfile>.mp3, but when grip tries to do the same command - 128 bytes only.
I've tried replacing the ~ with an explicit /home/jeff path, but get the same response. Can anybody shed some light on why the file is not getting written, or advise on how I can get more diagnostic information on the failure
Now I've discovered the reason why.
I added two additional tags to the MP3 command line.
The MP3 command line now reads
-v -V 0 -p --nohist %f %o
I think the key was the --nohist option, which prevents the notlame program from attempting to display a histogram of the VBR encoding. As grip does not open a terminal window in which to display the histogram, this is probably what caused grip to drop off.
Perhaps a similar effect is causing the problems seen by shadowhacker?
What is this notlame stuff? LAME is the best around and easy to use. You can get it with a gtk+ gui also if that's how you like doing things. Just curious as i've never heard of Grip...
As I understand it, notlame is based upon the lame MP3 encoding engine, compiled without GTK frame analyzer support.
Using grip (part of the Red Hat 7.2 distribution), I can quickly convert my CDs to .wav files. Once the first track is ripped, grip calls up notlame to convert them to mp3 files, finally deleting the original .wav files.
grip works very well, and I've found that I can quickly rip several CDs, leaving grip to batch process them to MP3 files overnight. It certainly works better than musicmatch which runs under wine, and is a processor hog.
I'd recommend going into the options of grip and setting 'nice' values reasonably high. This keeps grip and notlame as background processes, so your other apps don't get unduly slowed down. I use a value of 14 for the ripper, and 10 for the MP3 encoder, and that seems to work reasonably well.
Jeff
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.