Why is ripping /encoding so slow ?

[Panther96]

Used DVD2SVCD to rip a 1hr 55min DVD, took over 24 hours to rip, convert and encode !! Why so long ?

I'm using a PIII 850Mhz Processor, 256meg Ram, got 11gig HDD space and using CCE 2.5 to encode.

Surely it shouldn't take this long !

[deadpac]

How can you seriously ask this question when the answer is right in front of your eyes. The sheer turtle like nature of you computer should be an indication of why it takes that LONG.

I'm using a PIII 850Mhz Processor, 256meg Ram, got 11gig HDD space and using CCE 2.5 to encode.

Your entire computer is the bottleneck, taking into consideration the speed I'm assuming that it's a Celeron because I run a PIII 450mhz server box and I used to be able to encode 2 hour SVCD's in 16-19 hours, tried it a couple of times but couldn't stand the front fans had running in front of the two 60gig HD's I used for Uncompressed AVI caps and DVD rips on that 450 box.

Now thankfully I can encode 2hour movies in about well......2 hours. Ripping time is about 25 minutes for DVD's, capturing of course depends on the source. But in the end everything encoded at Playing time speeds x amount of playing time = x amount of encoding time. All on a stock box with stock cooling and stock components, nothing OC'd

I'm about to dump this whole OC methodology of increased performance, Don't see that much of a reason to OC since encoding time on my Koolance rig is about .92x playing time; DAMM the Nforce chipset and ASUS for such a paltry OC board.

[DVantrease]

Panther96, our specs are very similar (Duron 800mhz), and I've cut my DVD2SVCD time down to about 10 hours for a movie. The one step that uses most of the time is the CCE video encoding, which you may have set to do multiple passes (which does improve quality). I've found some 1-pass settings that give me very good results, and cuts several hours off encoding time. I'm at work now so don't have the link handy, but let me know if you're interested and I'll post them here.

[Mirror_Image]

This might give you an idea of why your CPU is so busy during encoding:

http://www.research.ibm.com/journal/rd/434/westerink.html

[FiEND]

thanks, i think my brain just exploded from that... I will stick to the basic rule of thumb - "1pass cbr bad, 2pass vbr good"

and i think 24 hours to rip/encode is fine if you are doing 2pass vbr with high quality motion search.