First render glitch with Vegas in--EVER!

Jay Gladwell wrote on 5/12/2004, 5:17 AM
Yesterday, I just finished editing a program that is 105 minutes long with 5.1 audio and a total of 15 tracks. I started the render to .avi at 4:30p.m. yesterday. When I went to bed at 11:30p.m. it show that the render was 68% complete. When I awoke at 7a.m. it show 77% rendered. At 8a.m. it showed 77% rendered. I canceled the render and looked at what it had done. Not even a quarter of the program had been rendered!

Any ideas as to what might have happened? Any ideas to what I can do to prevent this from happening again?

I bought Vegas Video 3.0 when it was first released. Upgraded to Vegas+DVD when it was released. Again, upgraded to Vegas+DVD Production Suite last month within a hour of its release. I guess if you use a product long enough, sooner or later, you'll run into a problem with it. This is my first! Not a complaint, mind you, just an observation. [sigh]

Any suggestions would be greatly appreciated!

J--

Comments

RafalK wrote on 5/12/2004, 5:21 AM
Hey, it happened to me. Turnes out I was out of disk space.
Jay Gladwell wrote on 5/12/2004, 5:25 AM
Thanks for the suggestion, but that was the first thing I checked. I had plenty of space left--over 50% of a 150GB drive!

J--
farss wrote on 5/12/2004, 5:31 AM
Maybe it needs space elsewhere for temp files and that ran out?
I've noticed that Vegas seems to use more than just the source and destination drives during renders at times.
Mind you I never try running long complex renders, I always split them up and stitch them back together. Not so much out of concern over things going pear shaped but if I want to change a small part hopefully I don't have to redo the whole render again.
Jay Gladwell wrote on 5/12/2004, 6:00 AM
Good point! I'll give that a try.

J--
Grazie wrote on 5/12/2004, 6:19 AM
Any luck yet? G
Jay Gladwell wrote on 5/12/2004, 6:21 AM
Grazie, right now it's rendering the ac3 file. Will let you know how the video portion turns out after trying Farss' suggestion. Thanks for asking! ;o)

J--
Jay Gladwell wrote on 5/12/2004, 6:41 AM
Well, the .ac3 file hung up at 77%, too!

I've found a logical point where I can divide the project into two halves. I'm rendering part A now as an .avi file. Then will do part B and join the two back together. Will then attempt to render an mpeg2 file in prep for DVDA. Hopefully, this will take care of the problem. [fingers crossed]

J--
JJKizak wrote on 5/12/2004, 7:22 AM
You have to have something at the 77% point that V5 doesn't like. Some of the things that clobbered me were not enough memory but you will get a message stating that fact. Also a still photo that is too big say around 3000 x 3000 will choke it. Credit rolls, Gausian noise, compositing will slow it down to a crawl. Do you have any still photos in the video?

JJK
Frenchy wrote on 5/12/2004, 7:37 AM
VideoC:

Is your pc overheating?

Frenchy
Jay Gladwell wrote on 5/12/2004, 8:32 AM
James, there are several still throughout the video, but none so big as to choke the program. Even if that were the case, how would that have affected the render of the .ac3 file?

Still, once the part A render is complete--and if your thesis is correct, it should--I'll check to see what's at that 77% point in the video. Thanks for the suggestion!

J--
Jay Gladwell wrote on 5/12/2004, 8:34 AM
Phil, I'm not getting any kind of indicators that are saying it's over heating. It's got four exhaust fans plus a heat sink fan that are, in theory, supposed to prevent that from happening.

J--
johnmeyer wrote on 5/12/2004, 8:35 AM
Are you rendering using a script? There has been a BUG in Vegas for some time (since 4.0) that has not been fixed in 5.0. I just ran into it yesterday. If you render using a script, and have the script render first the MPEG and then the AC3, it hangs up on the AC3 file. The solution is to re-boot, open the project in Vegas, and then immediately render the AC3 file, directly from the Render As dialog.

In my experience, the problem always seems to happen when rendering the AC3 file. Sometimes it completely hangs, other times it takes hours to render an AC3 file which normally should render in minutes.

Jay Gladwell wrote on 5/12/2004, 8:53 AM
Wow, John, I wish it were that simple. I'm not smart enough to use scripts! I've been rendering the old-fashioned way all along. So I'm really stumped.

I'm leaning toward James' suggestion, that being there is something at the 77% point that Vegas doesn't cotton to that's causing the problem.

Thanks for your input. Your knowledge and expertise with Vegas has always been greatly appreciated.

J--
HPV wrote on 5/12/2004, 9:11 AM
What drive is your temp audio going to? Is there any blank audio/no audio sections on the timeline? If so, try putting in a 0db audio event or an audio event turned down to 0db.

Craig H.
Jay Gladwell wrote on 5/12/2004, 9:16 AM
Thank you, Craig, I will look into that for certain!

J--
RafalK wrote on 5/12/2004, 9:41 AM
VC, I remembered one more time this happened to me. A client gave me their little JVC digital video capture camera which catches things in ASF ( I think ) format and there was something with those files that was crashing Vegas during render. It seemed like the last frame would stretch forever. I think at that time, my workaround was to render only about 90% of the clip and it seemed that as long as the last frame was not being rendered , things worked. Go figure.
Jay Gladwell wrote on 5/12/2004, 11:00 AM
Thanks, Rafal, for the insight. I'll add that to my list of things to try!

J--

P.S. And I thought my cat was a couch potatoe!
Jay Gladwell wrote on 5/12/2004, 12:36 PM
Well, part A was rendered without any problems after 5 hours, 40 minutes. I looked at the 77% mark in the overall piece (before splitting into two parts), and there was nothing there but original picture (with color correction) and audio.

So now part B is rendering. I'm hoping for the best at this point, just to get the project out of my hair. Then I'll take the original edit file apart and see what happened, if I can find it at all.

J--
BrianStanding wrote on 5/12/2004, 12:43 PM
I had a similar problem with an early (public beta, maybe?) version of V4. I eventually opened a second instance of Vegas and copied all the events into a new project and saved with a different name. Worked fine thereafter.

Never did find out what the hang up was. The (then) Sonic Foundry guys just chalked it up to "corrupted files."
Jay Gladwell wrote on 5/12/2004, 1:39 PM
Thanks, Brian. In the back of my mind, which isn't too far from the front, I've been hoping that was the case. But...

When you copied/saved the old file under a new name, why did that not save the apparent corruption with it? Just wondering!

J--
Jay Gladwell wrote on 5/12/2004, 5:52 PM
Finally... it's done!

Never did figure out what the problem was, though. Thanks to everyone who provided input and made suggestions!

J--
BJ_M wrote on 5/12/2004, 6:06 PM
i dont know if it has any bearing on your problem .. but i have had the same sort of thing happen in v5 now twice -- and both times it was stuck at about 58% i seem to recall -- but instead of rendering project, i rendered region (after setting a region in the project) and it rendered totally normal ..

there was nothing after the project in the timeline - i checked completly ..
wobblyboy wrote on 5/12/2004, 7:17 PM
I tried a render to Quicktime and it blew up at 77%, would just go on and on until I had to stop it. I checked default for Quicktime and discovered that video format was set to "none". I picked a video format and it would render fine. I have never had a problem rendering to MPEG.