Okay, your system is impressive; but what's in the nested VEG?

BTW, bumping up the Dynamic RAM Preview setting isn't going to help Vegas' performance. It's memory that Vegas sets aside for when you want to render a section to memory (Shift+B or Tools -> Build Dynamic RAM Preview), and that is the only time it uses it (as far as I know ;). In fact, by bumping up that setting, you're giving Vegas less memory to use for regular tasks.

Rob

yes i am waiting...and the hit is huge...i have tried tis before...always given up...am trying to see if I can actually use the feature (more quickly than sloooooooooooowwww in draft preview)

i see...OK i changed it back...any other tweaks?

At least when using regular DV files I don't feel any performance drop for playbacking the nested veg file. This is on a X2 4.200+ with 1 GB of Ram.

Marco

I feel a HUGE hit both in playback and rendering time (sometimes rendering time takes 6 times as long) when using nested files. Im just gonna start doing 1 huge 40 minute project again :<

If you open up the nested veg file and prerender it, you should see a really big improvement. One user reported that prerenders in a nested veg don't get blown away easily like they do on the master timeline. For my own part, I do a "render to new track" inside the nested veg file. Be aware, though, that unless you use uncompressed avi, the new (rendered) track in the nested veg file won't have an alpha channel.

More discussion here. Disregard the last post in that thread. He was forgetting that we were only talking about the alpha channel in cases where you do a "render to new track."

so if i do a complex edit with 3D + FX in one project and then render to new track uncompressed, i can use the project as a veg and it will speed up my preview + render time in the master project?

then when i go to do the final render I just turn off the "render to new track"- track , in the veg and I will have no generation loss + faster renders in the master project?

Im just done using nested projects till they fix perfomance hits and doing one big project, I hate prerendering because it generally disrupts my work having to stop and do extra render steps when my system is easily capable of doing 40 minute projects on a single timeline :(

i understand...only reason im looking at it agian is because you cant parent a parent motion- which is another limitation...so i am forced to bring in a veg and parent motion that.

hen when i go to do the final render I just turn off the "render to new track"- track , in the veg and I will have no generation loss + faster renders in the master project?

No reason to turn off the "render to new track" track. Just the opposite, you would solo it. Then when the master render is done, it won't have much work to do. Overall, instead of a performance hit, this is a huge render speed booster (for the master render, not considering the "render to new track" that was done inside the nested veg. If you rendered to uncompressed avi, I wouldn't be too concerned about generation loss on rendering that avi into something new.

An example where I used this.. I had a slide show with Spice transitions, pan/crop and track motion. It was a long slow render and difficult to preview. So I rendered the thing on its own to a new track.

This slide show was one small piece of a bigger project. Thereafter I could preview the master project without stalling on the timeline where the nested veg file goes.

And the render of the master project would have gotten an "out of memory" error if I hadn't farmed out the piece with the slide show. Because this was a rather complex project.

yes but if you are paranoid and want to turn off the render track do you still see a render speed improvment because of the 3D issue?