Hello,

I'm an OGG newbie.

Using CDex 1.70b2 and its supplied OGG encoder, I'm averaging about 1 minute for each 2m 30s track. Is this a typical rate of ripping for OGG? Using LAME and newer schemes I can rip the same song in about 10 seconds.

Pentinum 2.8Ghz D875PBZ
2GIG RAM DDR400
74GIG WD Raptor boot drive
400 GIG WD data drive

Thanks!

Try Lancer !

Yep, use Lancer.

Let's see... 2m30s = 150s

On my PC (AthlonXP Barton 2400+) Lancer encodes at 24x that means...

Slightly more than 6 seconds

Prepare to be amazed! (by lancer)

I have been using Lancer for some time and am really impressed by it. However, I want to know what the patch in the downloads section is for. Does it improve encoding in any way?

Thanks in advance
audiomars

It's a patch against the original source so it can have the Lancer changes.

@Firon: Thanks for the info. So, I take it that I do not need to download the patch if I am going to use the oggenc.exe that has been already compiled and available for download?

audiomars

Nope, you can download binaries that have been compiled from the patched sources.

@kjonlee, thanks a lot for the info. I have downloaded and am using the precompiled binaries but there was always a thing on the back of my mind if I should do something with the patch too. I am not a programmer and really did not know what to do with the files after expanding the archive contaning the patch for my OS

audiomars

Thanks for the replies.

Solved the problem. I'm using an iriver IMP-550 which only allows for 96-256 ogg bitrates. So, trying to be clever I managed the bitrates between 96 and 256 with 160 being a mid-point. This method came about from using an IMP-350 with has restrictions of 96-160 and using the -q settings resulted, occasionally, in rates outside of the supported range and odd scratching artifacts.

On a hunch I tried the -q settings again -- bingo! fast speeds and player is supporting the varied bitrates (q5 and q6).