Absolutely Love V V 3 but........

AKAGraphix wrote on 11/15/2001, 2:35 PM
Help!I am fairly new to Vegas Video having downloaded VV3 Beta. I had been using VF 1 and 2 which I loved. I regularly made short 5 to 7 minutes vids and printed to digital tape completely without problem. An awesome program with easy to use rendering. Both of my computers handled all aspects of production to DV tape. Render times were around 2 hours for these lengths of vids. The PROBLEM I am having with VV3 beta is that I simply can't render. I put together a 6 min vid of my son with a max of 5 tracks consisting of video and music. Nothing heavy duty as I am not up to that yet. When I went to render to tape I received this message: "Warning, Over 80% of the selected region has to be rendered. Do you wish to continue?" When I click "Yes" it starts to render one file at a time; 0001, 0002, and the render time that shows exceeds 30 hours!!! I try to render regular, not to tape and the time exceeds 10 hours. It never finshes, just locks up and I get a horrible error message with all kinds of stact faults! My computers are all up to the task. Help, anyone???? Thanks. kevin@akagraphix.com

Comments

FadeToBlack wrote on 11/15/2001, 2:49 PM
AKAGraphix wrote on 11/15/2001, 3:01 PM
That is what I selected. I have a Sony TRV20 hooked up as I always did with VF2. I selected:

Tools > Print to DV Tape > DV Template NTSC DV >
and then the default slections after that. The programs response is a quick check of the timeline and then the message: Over 80%.... blah balh.. I renders each of 256 files it says it needs to render. I count 53 files in my Media Pool. What gives?
AKAGraphix wrote on 11/15/2001, 3:08 PM
All my settings I posted: They are here: www.akagraphix.com/fault.htm

Thanks everyone.
FadeToBlack wrote on 11/15/2001, 3:21 PM
rgwarren wrote on 11/15/2001, 3:47 PM
So what! We're not talking about rendering 3 hours of footage. It's just six bloody minutes!

If the poor guy is having a problem you're dumb observations aren't going to help him. It shouldn't take 30 hours to render even if ALL six minutes of DV footage need to be re-rendered 10 times.

Let's all work to solve the problem not act like there is no problem. I find VV3 slow to render as well. Just like VV2. Rendering takes longer than I think it should as well.

It's what limits my use of VV2 to 4-5 minute projects.

I'm tired of 15 hour renders on my dual 2ghz machines as well.

The new dual processor aware codec doesn't seem all that aware. I'd call it more of a dual processor tolerant codec.

FadeToBlack wrote on 11/15/2001, 7:57 PM
SonyEPM wrote on 11/15/2001, 8:34 PM
The render time issue is likely the complexity of the Vegas project- meaning you have a filter or compositing or some kind of fx operation going on all over the place. If it says "over 80% of the project needs to be rendered" that means there's is something (FX, speed changes, compositing, resample,any number of other things) on at least 80% of the DV events.

Try setting video render quality to good rather than best, and uncheck "resample the frame rate of all video" if either of those have been swapped from the defaults, and amke sure your .avi render setting uses the NTSC DV template.

You can also send me (or GG) the project file and we can further diagnose.
db wrote on 11/15/2001, 9:20 PM
just in case in VV 3 preference ...put a check in the BOX "ignore 3rd party dv codec" ... as my system defaulted to another dv codec and the rendering were very slow ... after checking that box my renderings were about 2-3 times faster depending on the FX used ...
AKAGraphix wrote on 11/15/2001, 10:38 PM
After all the great replies from users and personal E-mails from the tech guys at SF, I decided to do a little investigative work. And, finally, I discovered the problem. Everytime I tried to render, the program crashed in the same spot. A complete and total lock up. I went through my time line and found a short video file I had with the FX applied of: Convolution Kernel > Emboss. That was it. I removed that FX and my render time dropped to a very acceptable 1 hour and 45 minutes. All went well and without a hitch. I am so freaking relieved. Thanks to all. Maybe a look at that FX by the tech department may be needed.

Best to all, K. Archer.
SonyEPM wrote on 11/15/2001, 11:06 PM
please send the crashing project file to:

vegasbeta@sonicfoundry.com

No repro here-
rgwarren wrote on 11/16/2001, 8:09 AM
Sorry GG, I reacted to your post because I felt it seemed you were just saying "it's going to have to render everything and that's slow". I didn't think that helped anything other than confim the obvious.

Rendering does still seem slow with VV3. It's one of my biggest wishes for VV3 that rendering get's faster.

However, the concept of a dual proc. codec isn't quite living up to it's name. Sure it's the best codec to date in terms of quality. But it really doesn't crank on the processors. My drives aren't being hit hard and the overall CPU usage while rendering is only 60%.

I think the codec could be much much faster. Having to wait a long time for short clips with a dual 2 gig Xeon machine is tough.

VV3 is pretty stable. Our mutual friend Douglas just finished an hour long piece of work using VV3. I would say it's pretty stable if he could pull that off.

Sorry if you were irritated by my post. Slow rendering irritates me.