Ok, I have a question for those of you who do nested projects. Because nearly all of my work is long form single recording, I've really not had a need to nest. I just finished a big project and I think nesting would have made my life MUCH easier, so let me lay out a scenario and ask a question.

Let's assume I am making a movie with 30 scenes. I create one .veg per scene. I create 3 .veg files for Act1 (scene 1 - 9), Act2 (scene 10-19), and Act3 (scene 20-30). And then I create a master .veg file comprised of just the 3 acts.

My question is this:

If I make a change to say, scene 3, scene 15, and scene 22, and I then open up my master .veg file, will those changes automatically flow up, or do I need to open each of the "act" .veg files to register those changes?

Perrone, I was pretty sure they would but I ran a quick test to be sure and yes, they will automatically update the next time you open your master veg file.

Thanks Mike,

That will save me EONS of time the next time I build a large multi-scene project. Actually, it will save me a lot of disk space too as I prevent the intermediate render files also. And generational loss.

You're welcome Perrone.
I started using nested vegs on some of my projects a few years ago and it made my life SO much easier :-)

I got SLAUGHTERED on my most recent project (doing final renders now) because of last minute changes in the project. Typos that weren't caught in the proof, color changes, etc. Things that would have been trivial in a nested project, but require tedious re-work, and rendering in non-nested projects.

This is the last time I'll do a project this way.

Perrone,

I do every big project nested these days for the reasons you mentioned.

I would not render work until you are actually wrapping things. I made that mistake in my last project and it caused me unending greif (I was mixing m2t files and cineform avi files.) Just a thought about an easy mistake that caused me greif that is easy to avoid.