Hello. I am need of a bit of help to get ripping to ogg with EAC.

Firstly, in 'parameter passing scheme' in compression options, I take it that should be 'ogg vorbis encoder?' Seems likely, but thought I'd better ask.

Also what should I put in 'additional command line options?' I am happy to start with quality level 5, but also getting tags added would be good.

Many thanks.

Yup.

I leave that field blank. EAC knows how to pass the info it knows (quality level, title, artist, track number, etc). If you put anything in that box, you need to put everything in that box. I've just never felt the need to add extra comments.

Thanks for reply Peter. One question: if you leave that field blank, what quality setting is used?

Select the Quality setting in the Bitrate window(!!).

thanks john33. I feel a bit silly now, have I gone red???

Two things...

-1- The only time you'd want to specify the quality setting in Additional Command Line Options is to use a fractional setting (i.e., -q 3.75 or -q 5.50).

-2- @john33 (or anyone else who may know): Will tag info EAC passes to the encoder be written as Vorbis comments if the encoder is oggenc (or oggenc2)? I know it can do ID3 tags (of various versions) but I never saw references to it being able to pass tags to be written as Vorbis comments.

Is 'Quality 5 (Medium)' generally accepted as transparent when using GT3b1 (oggenc2.exe) encoder? I know its subjective, but I havent done much experimenting with ogg so far.

For many people that is a setting that provides transparency, yes. -q 5 to -q 6 are the most common (lowest) settings I've noticed people claiming transparency with.

Then there are people like me (with seemingly less sensitive hearing than average) for whom something like Post 1.0 CVS -q 4.25 is transparent. We're the same people who score lots of 5.0's on 64kbps listening tests.

I'm not sure how to feel about that, but at least I like my filesizes!

Think I'll stick with q5 then ScorLibran. Like you, filesize is of importance and from what I've read, this tuned version should perform even better than the 'official' version at q5.

Cheers

One more thing to keep in mind, concerning filesizes.

Garf's changes to the GT3b1 encoder improved quality settings 5 through 10, though it has a "partial effect" for 4.01 to 4.99 as well. However, GT3b1 encodes at higher bitrates per each of these -q settings than Post1.0CVS. For example, -q 5 with GT3b1 = 180kbps nominal bitrate, while -q 5 with Post1.0CVS = 160kbps nominal. It's been explained that even if the bitrates were "equalized" (manually) that GT3b1 would still give generally better sound quality (IIRC the improvement was most noticible with reduction of pre-echo).

Nominal bitrates for GT3b1 are higher by 20kbps for all quality settings 5.00 and higher. Increases in bitrate above those of Post1.0CVS for quality 4.01 to 4.99 are incremental. For instance, GT3b1 -q 4.01 creates a slightly larger file than Post1.0CVS -q 4.01, and that difference increases as you go up in -q until it levels off at a difference of 20kbps at 5.00 and up.

I know this is probably more detail than you wanted, but just know that you'll have somewhat larger files with GT3b1 than you would using an equal -q setting with Post1.0CVS.

Thanks for the explanation there. I wasn't aware of that but slightly larger files are ok for me as long as quality is increased. At the moment I only use Lame APS, which as you know are usually about 200-220kb on average (which gives me quite acceptable file sizes). Thanks for all the help everyone.

To be honest, I only rip to wavs. I have no experience as to whether you can use the placeholders for vorbis tags in the command line.

@ ScorLibran

Hmm, I tried to encode with EAC in q 8.5 but GT3b1 always encodes only in q 8.
I only added -q 8.5 in the aditional command line box. I wonder why the parameter isn't given to the encoder.