Internal Memory

[marcelr]

How much internal memory should one look for when doing encoding jobs using TMPGenc ? Would more mean faster ? How long does it take to encode a 750 mb avi file to mpg2 svcd format approx. ?
Thank you.

[bugster]

How much internal memory should one look for when doing encoding jobs using TMPGenc ? Would more mean faster ? How long does it take to encode a 750 mb avi file to mpg2 svcd format approx. ?
Thank you.

512Mb is more than enough for TmpGenc. As for how long it will take, you might as well ask how long is a piece of string?
What is your source, how long is the movie, how fast is your cpu? All these (and more) have a big impact on encoding time.

[ZippyP.]

Conversion is CPU intensive and doesn't rely on memory for speed. Within limits, and depending on what the computer is doing at the same time (surfing etc.), changing the amount of ram won't speed up conversion times. As bugster said, 512 MB sems to be the optimum amount of ram beyond which, in windows anyway, things won't speed up much.

Some people report conversion times of about 1.5 hours for a 2 hour movie on the low end. On the high end, the skies the limit. If you want an estimate of conversion time you'd have to answer these questions: CPU type and speed? Conversion program? Video length (not size)? CBR or VBR? Any filtering? With my setup I can do a 2 hour movie conversion (CBR, no filters, TMPGEnc) in about 3 hours. Your results may vary.

[Gazorgan]

When I upgraded from 256 MB of 133 SDRAM to 512 MB DDR 266 I gained Nothing in encoding speed.

I gained in games, and certain applications that can use a lot of cache. But generally speaking encoding is a CPU thing (that's why celerons can encode so well). The other difference (primarily between Athlon's, PIII's, and PIV's) is the SSE, SSE2, MMX, MMX2 instruction sets (Athlons don't do MMX2 and P's don't do SSE's ?) that make a slight difference to the CPU speed rule.