Any help is appreciated
Full Version: Random EAC/Lame problem
First time user of mp3 player and software....I followed a couple of websites as far as configuring EAC/Lame and proceeded to rip and compress some 40-50 CDs. I have set the configuration to create mp3 files and delete the wav files. Most worked just fine but a handful have not created mp3 files and left the wav files in the folder? Any help is appreciated
Any help is appreciated
Just a bad guess, but hey, might be worth a try...
Maybe surround the %s and %d each with quotation marks... ? Maybe there are characters or strings in some filenames that Lame doesn't like... ?
Maybe surround the %s and %d each with quotation marks... ? Maybe there are characters or strings in some filenames that Lame doesn't like... ?
Possibly the old "LAME 3.90.3 with invalid genre" as well.
I'm not sure how this would manifest itself.
I'm not sure how this would manifest itself.
My guess being your new to EAC is that you didn't realize those tracks probably didn't rip correctly/fully.
When EAC encounters a read error in which after it exhausted all it's retries still cannot get a identical re-read
of the data will give up and go on to the next track. (Of course all this depends on how you've set up EAC)
Tracks that are not fully ripped will not be compressed and EAC leaves the wav file that was extracted up to the point it gave up.
When EAC encounters a read error in which after it exhausted all it's retries still cannot get a identical re-read
of the data will give up and go on to the next track. (Of course all this depends on how you've set up EAC)
Tracks that are not fully ripped will not be compressed and EAC leaves the wav file that was extracted up to the point it gave up.
Or maybe you've set up EAC to extract and compress simultaneously (different tracks of course), and have closed EAC before all compressing has been completed?
QUOTE (Acid8000 @ Jul 10 2005, 03:10 PM)
Or maybe you've set up EAC to extract and compress simultaneously (different tracks of course), and have closed EAC before all compressing has been completed?
This would be my guess. If this is the case, you can resume encoding by just opening EAC again.
QUOTE (teleguise @ Jul 9 2005, 09:14 PM)
My guess being your new to EAC is that you didn't realize those tracks probably didn't rip correctly/fully.
When EAC encounters a read error in which after it exhausted all it's retries still cannot get a identical re-read
of the data will give up and go on to the next track. (Of course all this depends on how you've set up EAC)
Tracks that are not fully ripped will not be compressed and EAC leaves the wav file that was extracted up to the point it gave up.
When EAC encounters a read error in which after it exhausted all it's retries still cannot get a identical re-read
of the data will give up and go on to the next track. (Of course all this depends on how you've set up EAC)
Tracks that are not fully ripped will not be compressed and EAC leaves the wav file that was extracted up to the point it gave up.
I did notice several beeps during the EAC session (not present on good rips)...is that an indication of problems?
I made a point not to shut EAC down until the Lame session finished?
QUOTE (teleguise @ Jul 10 2005, 10:14 AM)
My guess being your new to EAC is that you didn't realize those tracks probably didn't rip correctly/fully.
When EAC encounters a read error in which after it exhausted all it's retries still cannot get a identical re-read
of the data will give up and go on to the next track. (Of course all this depends on how you've set up EAC)
Tracks that are not fully ripped will not be compressed and EAC leaves the wav file that was extracted up to the point it gave up.
When EAC encounters a read error in which after it exhausted all it's retries still cannot get a identical re-read
of the data will give up and go on to the next track. (Of course all this depends on how you've set up EAC)
Tracks that are not fully ripped will not be compressed and EAC leaves the wav file that was extracted up to the point it gave up.
EXAcTLY!!! okRon, check out the leftover wav files and see if they play til the end of the song
QUOTE
EXAcTLY!!! okRon, check out the leftover wav files and see if they play til the end of the song
wav files play just fine all the way thru...??
Copy LAME.EXE into the directory where the problem WAVs are. Start a Command Prompt session; navigate to that directory then run lame %1 %2 test.mp3, where %1 is the settings you use in EAC to encode (e.g. --preset standard) and %2 is one of the trouble WAVs' file name, enclosed in quotation marks if it contains spaces. If LAME gives you error message, you will see it there because the window will stay open until you close it manually.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.