20min video in 20min.Lucky you.

I'd suggest updating your processor, Mobo and Ram if you want faster speeds. Get a MoBo that supports DDR Ram, with at least a gig of DDR Ram and a minimum of a 2.5ghz processor. Then you will see your rendering times decrease.

thx for your reply but there are not card for accelerate that ?

Lots of people have asked questions in this forum over the past years about how long it takes to encode MPEG2. Because they are rendering from the timeline, some of their projects may include dozens of effects that require rendering. This rendering may take longer than encoding.

I propose that it would be useful if we all took ten minutes of DV AVI, put it on the Vegas timeline, and then encoded it with one of the default templates such as the "DVD NTSC video stream" template. No other programs or processes should be running during the test. We could then report on our processor type (e.g., single Pentium P4 running at 2,8 GHz), O/S (Win XP SP1), and RAM memory (512 MByte). This would give a common set of benchmarks that everyone could use.

For me, with the paramters I just gave, it takes 14.3 minutes to encode a 10 minute AVI clip to MPEG2 (actually, I need to amend that -- this is using the DVD Architect template, which doesn't encode audio, and I'm running the browser writing this message while the encode is taking place).

At the risk of repeating myself, this is without any rendering whatsoever (no transitions, titles, fades, fx, etc.).

If people are interested in this idea, I'll do the test exactly and report back the results.

In order to be accurate we all need to start with the same source file. One everyone already has, or could make. For example one of the color bars images that come with Vegas, then extent it out to exactly the same length. I would suggest exactly one minute.

Actually I did do this "test" with a few forum members well over a year ago. Forget who with or even if he is still here. Anyhow once you build the project you need to reboot, again to be more accurate before you render. Again, back when I did the origianal test I had a AMD system and the other guy had the latest Intel CPU. The results were somewhat difference than expected in part because I rebooted first thereby maxing out system resources and he didn't.

Rebooting is a good idea. I think, however, that if we are going to use generated media, then the media should not be static, like color bars. Perhaps someone could create a simple title sequence. We could all download the VEG file, generate the AVI, and then encode the resulting AVI file. A little complicated, I guess, but a static file, like color bars, wouldn't give the MPEG encoder much to do.

Actually, maybe the encoder doesn't care whether each frame is the same as the last.

Try encoding to DV PAL Avi FIRST( I assume it's a PAL project...) and THEN encode the new avi to MPEG2...I have found this to be more time efficient in practise ...