3+ hours render for 53min Rendered Project?

Grazie wrote on 5/3/2006, 3:06 PM
I have done this countless times - A Project consisting of 12 pre-rendered files with the audio set down 3dB.

Total runtime = 53 minutes plus.

Attempted a PTT but it was proceeding at a snail's pace, through the "pre-render" sequence. I thought - "Hello, what's all this then?"

Tried twice, with the same result.

I then decided to render to a New Track and would then PTT from that.

I started at 8:15pm thinking it would only take something like an hour, plus minutes. It is still going at 11:00pm. By the looks of things it wont finish for another 30 minutes. That would be at least 3.5 hours to render to a new track a project that has 12 pre-rendered files totalling 53 minutes.

NOT GOOD!

Any thoughts?

Grazie

Comments

Grazie wrote on 5/3/2006, 3:50 PM
I have NOT done this before ! ! !

Answer:

1/- I was telling Vegas to render an original 16:9 project to 4:3 ! !

2/- I had picked up a GLOW Fx for one of the pre-rendered pieces that was some 10 minutes long ! !

OK, having an non-active (I unchecked the Fx to test) GLOW on an EVENT slows stuff up? Yes? Why?

Grazie
Dan Sherman wrote on 5/3/2006, 4:37 PM
Well, at least you achieved a render, long as it might be.
My machine's been shutting down only minutes into renders and the work's backing up.
Can't find the problem, but suspect it is hardware related and not the fault of Vegas.
Had no luck tracing the problem afer calling in smarter minds than mine (which is not saying a great deal).
But my pea brain suspects it is upgrade time, as I've tried everything else under the sun inlcuding numerous re-installs, driver changes ad infinitum.
Looking at an AMD dual core, and it looked back and winked!
Grazie wrote on 5/3/2006, 4:48 PM
Oh dear . . You looked at the cooling systems? Dust free . .? Fans and CPU fins visible? - About as far as my PC acumen goes. - Grazie
Dan Sherman wrote on 5/3/2006, 5:25 PM
Looked at all that stuff
fldave wrote on 5/3/2006, 5:36 PM
Probably hardware. New memory may be a cheap test. Or run Memtest utility to see if your memory is shot.

I'm still using my dual Pentium III 1Ghz system sometimes for targeted HDV renders using Vegas 6d. Runs fine.
Dan Sherman wrote on 5/3/2006, 7:20 PM
Not to hijack your thread here Grazie.
But really,---memory may be shot?
No one has ever suggested that.
I wonder if that's my problem,------the computer that is.
I know my memory is shot.
So that could slow down renders and maybe even cause crashing and renders that stop?
Dan Sherman wrote on 5/3/2006, 7:21 PM
Not to hijack your thread here Grazie.
But really,---memory may be shot?
No one has ever suggested that.
I wonder if that's my problem,------the computer that is.
I know my memory is shot.
So that could slow down renders and maybe even cause crashing and renders that stop?
johnmeyer wrote on 5/3/2006, 7:45 PM
You mentioned using a Glow fX. I assume you saw my thread about the increase in render times for various fX, but if not, here it is:

Results of render times for ALL Vegas fX

Some of these suckers can seriously slow down your render.
rs170a wrote on 5/3/2006, 8:34 PM
I know my memory is shot.

It most certainly could.
Check the Rendering Issue thread for more ideas and software test suggestions.

Mike
Grazie wrote on 5/3/2006, 10:41 PM
I assume you saw my thread about the increase in render times for various fX

Yup - I even posted in it, which I assume you saw too! Great work John.

Anyway, why should it slow down a render even when it isn't even activate? I checked and unchecked. Unchecked was faster but it wasn't until I actually removed/deleted it did it speed through this section. Now if this can be corroborated it would indicate that some of the extra render time is added as a result of the command being applied but NOT checked/activated. Interesting? I think so.

Grazie
dand9959 wrote on 5/4/2006, 8:05 AM
I had the same problem start on my machine...and it is indeed the power supply overheating. (Unfortunately, this machine is an off-the-shelf buy, with a "custom" power supply...which means its form factor is unlike other PS...so they're forcing me to get the same - discontinued - PS at three times the cost. Screw 'em)

So...when I work on that machine, I remove the chasis cover AND get a portable fan to blow into the chasis. Works great. (You need the external fan because once you remove the cover, the "factory designed" airflow cooling is disrupted.)
Former user wrote on 5/4/2006, 8:42 AM
It seems to me I remember this issue being brought up in reference to Version 4. That even though an effect is not active, it is part of the render.

Dave T2
MRe wrote on 5/4/2006, 11:52 AM
"It seems to me I remember this issue being brought up in reference to Version 4. That even though an effect is not active, it is part of the render."

Now when you mentioned it I also remembered that Spot warns against using "idle" effects on long events in his excellent Vegas4 Editing Workhop -book. I think he recommends to split the event in parts and use the effect only where its needed. Sorry Spot, if my brain fails me here...
Grazie wrote on 5/4/2006, 2:44 PM
" . . split the event in parts and use the effect only where its needed. Sorry Spot, if my brain fails me here... "

This I did. AFTER having applied the FX!! Soooo... the Fx was still"dormant" within one section of the Event. Be warned .. it is toooo easily done .

Grazie