Over 8 hours to render 1.2 hour project!!

blk_diesel wrote on 11/4/2006, 9:28 AM
It actually topped out at 14 hours estimate. Only a couple of fades and 1-2 transitions. What in the world is going on? I captured the footage in DV mode from a FX1, so I used the NTSC dvdA widescreen template. This is the second project I used V7 to do, the last time the render was only 2.5 hours.

Comments

riredale wrote on 11/4/2006, 12:28 PM
In the past if a render was taking forever it was often because of accidentally setting something that required the laborious rendering of every frame. For example, check that video level is at 100%, and that the Opacity line at the top of the video clip on the timeline has not been accidentally pulled down.
rs170a wrote on 11/4/2006, 2:32 PM
Also check that you didn't accidentally turn on anything at the track level (Track FX) or master output (Video Output FX).

Mike
blk_diesel wrote on 11/4/2006, 2:33 PM
I checked those. I even used the last template because this project is only 5 minutes longer than the last, but I'm still getting an estimate of 12 hours. I also checked to make sure the avi was captured as DV. I don't know what's next. The opacity level is 100% (I can see the picture in preview when rendering).
rs170a wrote on 11/4/2006, 2:37 PM
If you accidentally knocked the opacity (or anything else) down to 99%, you wouldn't notice it on preview as it's so small a change.

Mike
blk_diesel wrote on 11/4/2006, 2:40 PM
"Also check that you didn't accidentally turn on anything at the track level (Track FX) or master output (Video Output FX)."

Do you mean on the rendering setting? If so, I tested it with the template I used last week which rendered the video in 2.5 hours because the projects are only 5 minutes different. The estimate was still rising at 7 hours when I cancelled.

blk_diesel wrote on 11/4/2006, 2:43 PM
"If you accidentally knocked the opacity (or anything else) down to 99%, you wouldn't notice it on preview as it's so small a change."

I checked it by putting the cursor at the top of the timeline and get the message that "opacity is 100%".
rs170a wrote on 11/4/2006, 2:56 PM
Don't know what else to suggest then as those are the usual culprits.
Hopefully someone else has another idea.

Mike
winrockpost wrote on 11/4/2006, 3:01 PM
check your project poperties,, and i have to ask,, magic bullet ?
blk_diesel wrote on 11/4/2006, 3:07 PM
check your project properties,, and i have to ask,, magic bullet ?

What's a magic bullet? As far as properties, anything in particular I should check? The only difference between this project and the one I did last week is that I shot this video in HDV with a Sony FX1 and the last was shot with a GL-2. It has to be something with this veg because the template from the last shoot is also giving crazy render estimates.
winrockpost wrote on 11/4/2006, 3:29 PM
magic bullet is a render hog plg for vegas,, project properties , just check and make sure you have it set correctly for what your fx1 footage is,, but no matter what it is set at i'm not sure it would result in an 8 hr render,, hmm, great help-- sorry
good luck
fldave wrote on 11/4/2006, 4:44 PM
Set your Dynamic RAM down to 0 in Preferences\Video. If you are using most of your RAM here, then it forces your render to use the disk paging file instead.
Tim L wrote on 11/4/2006, 4:51 PM
Another "long render" thing I've read about is accidentally having compositing mode set to 3d instead of the normal "Source Alpha". Check the compositing mode on all your video tracks.

Tim L
Laurence wrote on 11/4/2006, 5:26 PM
I made the "Source Alpha" mistake not too long ago. It increased my render time an absolutely incredible amount: maybe twenty times longer! Yeah, check for that!
blk_diesel wrote on 11/4/2006, 5:36 PM
I checked the alpha and it's set to Source Alpha. I'm going to redo the project in V6 and see if it helps. It's not much editing at all, I just have to set the markers. I'm thinking it has something to do with the HVD to DV capture.
fldave wrote on 11/4/2006, 7:45 PM
You should simply have a DV avi file, nothing HDV about it. Project properties set to DV, correct? Not HDV?
blk_diesel wrote on 11/4/2006, 7:56 PM
Yep, everything set to DV. I don't know what's causing the long render.
John_Cline wrote on 11/4/2006, 8:37 PM
What are the properties of the clip itself that is causing the long render?
MH_Stevens wrote on 11/5/2006, 6:34 AM
Is 8h to render 1.2h that unusual? With my 3.2G I always have a render ratio of 8:1. That's with Cineform .avi to DV for DVD Architect.


blk_diesel wrote on 11/5/2006, 8:13 AM
"What are the properties of the clip itself that is causing the long render?"

I have no idea, this is a first for me. The entire render took over 14 hours. I did have an error message this morning about no virtual memory. However, the render was finished by then.
bevross wrote on 11/5/2006, 1:57 PM
One other thing to check: any chance you were working off an external drive? I had crazy render times once when I thought I'd just leave my file on an external USB drive (usually I transfer over to internal drives). But, if your setups, drive-wise, were the same as when you had good times, then I guess that's not it.
JJKizak wrote on 11/5/2006, 3:04 PM
You might try this real simple thing---reboot, set your dynamic ram to 16.
JJK
busterkeaton wrote on 11/13/2006, 4:04 AM
"If you accidentally knocked the opacity (or anything else) down to 99%, you wouldn't notice it on preview as it's so small a change."

That's not the only place to change opacity. What you are looking at is the event level opacity. That is only telling you that clip is 100%. It could be another clip that has the opacity changed. Also you can also change opacity at the track level. If you will expand your track headers you will see opacity sliders for each track. There is a script here that checks for this sort of thing. I believe it's called audit. You may want to search the forum for that.
plasmavideo wrote on 11/13/2006, 6:38 AM
This is like a deja-vu. This is the crazy thing I've mentioned in another thread. I still have not figured it out either, and can find nothing out of order. Just saving a straight DV (no effects or transitions) timeline to a DV file takes much longer than realtime to do. And rendering to a mpg file takes forever! I cannot figure it out. I've started new veg files, reset all settings in Vegas to factory default and triple checked opacities, video bus effects, everything. It started after installing V7, but now happens within V6 as well. It is so peculiar. I was going to try installing Vegas on another "virgin" computer over the weekend to see what would happen, but had too many other commitments to get to it.
andremc wrote on 11/13/2006, 11:21 AM
Just had a similar situation over the weekend. Estimated render time was around 12 hours for a 2 hr project. Actual time was around 5 hours. Had another estimate of approx. 5 hours for a 1 hour project. Actual time 2 hrs. Both were DV .avi using V7.

I don't usually have these problems with shorter projects, & render time is ok - except mpeg-2 (like watching grass grow).

Maybe it's a bug where Vegas doesn't estimate times for larger renders properly. Was the actual render time 14 hrs?