I'm using Audiograbber's line-in sampling function to record FM and DAB radio. Audiograber offers a choice of five VBR methods using the Lame.dll encoder...Default, Old, New, MTRH, and ABR.

With lameEnc.dll ver 1.28 (9/5/2003) Engine 3.90, I'm assuming the 'Default' method will be --alt-preset standard...could somebody please confirm this is a correct assumption ?

Thanks

ß

Hi, this is a little bit OT but there is no reason for using Audiograbber, it has NO error correction and no safe mode! If you want to use the lame.dll, there is a CD Ripper calles CDex which can use the lame.dll with real alt-presets and it has a jitter correction and supports Paranoia Extraction mode.

Your assumption "may" be correct, but I believe their are compromises to using the lame.dll. Its better to import the lame executable and select "external" encoder in AudioGrabber.

The reasons for using AudioGrabber are that its probably the single most popular and user-friendly ripper to use that doesn't need the so called error correction and "safe mode", (whatever the hell that is), that the other boutique rippers like EAC or Cdex require.

Just use AudioGrabber and enjoy the music.

Dex

CDex and EAC require nothing, it's just an additional function of these programs whose importance is huge! I made the fault to use Audiograbber for a long time and didn't listen to my ripped mp3s very often until I found the first MP3's which were corrupted beacause I didn't use a program with jitter correction. And that is very disguting. It's just a tip not to use Audiograbber, just believe me

PS: When using safe mode you can be 100% sure that the Ripped audio data is coorect. Just use it

[quote=FuRaL,Jul 30 2003, 03:21 PM] The reasons for using AudioGrabber are that its probably the single most popular and user-friendly ripper to use that doesn't need the so called error correction and "safe mode", (whatever the hell that is), that the other boutique rippers like EAC or Cdex require.

Just use AudioGrabber and enjoy the music.

Dex [/QUOTE]
CDex and EAC require nothing, it's just an additional function of these programs whose importance is huge! I made the fault to use Audiograbber for a long time and didn't listen to my ripped mp3s very often until I found the first MP3's which were corrupted beacause I didn't use a program with jitter correction. And that is very disguting. It's just a tip not to use Audiograbber, just believe me

PS: When using safe mode you can be 100% sure that the Ripped audio data is coorect. Just use it [/quote]
He isn't ripping CDs, reread the origonal quote.

[quote=music_man_mpc,Jul 30 2003, 03:29 PM] [QUOTE=FuRaL,Jul 30 2003, 03:21 PM] The reasons for using AudioGrabber are that its probably the single most popular and user-friendly ripper to use that doesn't need the so called error correction and "safe mode", (whatever the hell that is), that the other boutique rippers like EAC or Cdex require.

Just use AudioGrabber and enjoy the music.

Dex [/QUOTE]
CDex and EAC require nothing, it's just an additional function of these programs whose importance is huge! I made the fault to use Audiograbber for a long time and didn't listen to my ripped mp3s very often until I found the first MP3's which were corrupted beacause I didn't use a program with jitter correction. And that is very disguting. It's just a tip not to use Audiograbber, just believe me

PS: When using safe mode you can be 100% sure that the Ripped audio data is coorect. Just use it [/QUOTE]
He isn't ripping CDs, reread the origonal quote. [/quote]
You're right, thats why I wrote that it's a little bit OT.. I'm sorry, i didn't want to change to a cd ripper discussion

As I re-read my comments, (in the light of a new day), they seem a bit harsh.

In my personal experience, I've had problems with EAC and CDex that I haven't had in AudioGrabber. Which is why I tend to use it more. But, this "jitter correction" thing sounds interesting. Could you, (or anyone), give an example of a CD or situation where it would be needed? What kind of artifacts or anomolies would I listen for to know if I was having "jitter" related problems?

Thanks, Dex

Edit: Ooops . . . noted my harshness but forgot to apologize!
Sorry FuRaL66, didn't mean to snap at ya.

It depends on how bad the damage is on the source CD. Ususally scratches are the problem, however a dirty CD can be just as difficult to extract tracks from error free.

To test this yourself just find a CD with moderate to alot of scratches on it, actually many CD's without alot of scratches won't rip error free in a program that doesn't use jitter correction, secure ripping as EAC uses, or Paranoia Full that CDex uses.

Rip a bad track or section of a track (one with errors) in EAC and CDex to separate .wav files. Now rip the same track or section with AG and listen to them. Notice which one does or doesn't have errors, and which errors are the least annoying to listen to.

Thanks Andavari; I'll try this test when I get home, but first I'll have to go to a pawn shop and buy a cheap scratched CD. All mine are as fresh as the day I bought them.

Dex

britannica,

In Audiograbber, if you go to the setting panel where you select the bitrate method, click on the "?" at the top right of the window, then click on the drop down window for Method. You get a tip window describing the different variable bitrate methods. This is pretty much the same as is in the Audiograbber help file:

"LAME 3.89 and higher can do VBR encoding in a few different ways and the following methods are available:

· Default, the default method for the dll. This is the same the old method in LAME 3.89.
· Old, the old and commonly used method.
· New, a new method which is still a bit experimental.
· MTRH, a mix between the old and new method.
· ABR (Average), the encoder makes the file at the bitrate specified and uses more bits for complex parts of the music."

Thanks - this is what gave rise to my original question.

Is the 'Default' VBR method for lameEnc.dll ver 3.90.3 the --alt-preset standard settimg ?

The reason I ask is that using the external encoder and APS I sometimes get recording errors reported by AG when using other apps (multitasking), but when using the dll I don't.

Perhaps the dll uses less Windows and/or cpu resource ?

As for the other points raised. I've used CDex a couple of years now for ripping - but haven't got hyper-critical hearing.

Audiograbber is certainly the most useful tool for recording and on-the-fly encoding I've tried and tested over several years.

I guess Messer is OK too but he abandoned the project a couple of years ago.

ß