Veg files, why the big render time ? at DVinfo.net

Paul Kellett · June 9th, 2009, 05:16 AM

Ok i just did a little experiment, i have a 4 min project which i rendered from hd>sd/mpeg2,
the render took 12 mins which is ok for a 4 min project with a few light effects.
However when i open a new blank copy of vegas and drag the saved veg file, (same project,) to the timeline it renders to a single track in a few seconds, that's no problem but when i come to render this into mpeg2 it takes over 2 hours.

Also when looking at the task manager i notice that my processor is only working at about 30%, whereas when i'm render a project (not a veg) the processor is always at nearly 100%.

All this is not a problem for me as such because i don't render seperate veg files often, i just want to know why the long render time happens, it's just my thirst for knowledge.

Thanks, Paul.

Edward Troxel · June 9th, 2009, 06:46 AM

First of all, dragging a VEG file to the timeline doesn't "render it to a single track". Instead, it NESTS it. It does create a separate file to help speed up preview rates.

When you then render, it has to go through the complexity of rendering the nested VEG and making sure it's properly transformed to the current timeline settings. The different CPU usage would be related to the difference between rendering the project separately and rendering it nested.

Bill Ravens · June 9th, 2009, 07:33 AM

Paul...
Vegas uses a very archane terminology. When they use the term "render", they mean "export". Every other NLE I know uses the term "export" to create a new video output. Render, most commonly, means conform to the timeline. Exporting and rendering are two entirely different animals, one requires minimal CPU processing while the other is pretty processor intensive.

June 9th, 2009, 05:16 AM	#1
Paul Kellett Trustee Join Date: Nov 2007 Location: Bristol UK Posts: 1,273	Veg files, why the big render time ? Ok i just did a little experiment, i have a 4 min project which i rendered from hd>sd/mpeg2, the render took 12 mins which is ok for a 4 min project with a few light effects. However when i open a new blank copy of vegas and drag the saved veg file, (same project,) to the timeline it renders to a single track in a few seconds, that's no problem but when i come to render this into mpeg2 it takes over 2 hours. Also when looking at the task manager i notice that my processor is only working at about 30%, whereas when i'm render a project (not a veg) the processor is always at nearly 100%. All this is not a problem for me as such because i don't render seperate veg files often, i just want to know why the long render time happens, it's just my thirst for knowledge. Thanks, Paul. __________________ Round 2 GH5,FZ2000 Last edited by Paul Kellett; June 9th, 2009 at 05:18 AM. Reason: .

June 9th, 2009, 06:46 AM	#2
Edward Troxel Sponsor: JET DV Join Date: Dec 2001 Location: Southern Illinois Posts: 7,953	First of all, dragging a VEG file to the timeline doesn't "render it to a single track". Instead, it NESTS it. It does create a separate file to help speed up preview rates. When you then render, it has to go through the complexity of rendering the nested VEG and making sure it's properly transformed to the current timeline settings. The different CPU usage would be related to the difference between rendering the project separately and rendering it nested. __________________ Edward Troxel [SCVU] JETDV Scripts/Scripting Tutorials/Excalibur/Montage Magic/Newsletters

June 9th, 2009, 07:33 AM	#3
Bill Ravens Join Date: Nov 2001 Location: santa fe, nm Posts: 3,264 Images: 10	Paul... Vegas uses a very archane terminology. When they use the term "render", they mean "export". Every other NLE I know uses the term "export" to create a new video output. Render, most commonly, means conform to the timeline. Exporting and rendering are two entirely different animals, one requires minimal CPU processing while the other is pretty processor intensive.