One pro of using nested veggies is how the fx is applied to the clip

The same as precomposing in AE and in Boris its upstream and downstream

For example place a pic on the timeline and apply liner blur it will effect the surface but not the edge
Save that as a veg

Start a new project place the veg on the timeline and apply the linear blur the fx will effect the object as a whole blurring the entire pic
So nested veggies act as bins in Boris and precomps in AE

So multiple shadows can also be easier to compose from a single imported veg rather than creating a shadow for each object when dealing with multiple objects

Cons to using nested vegs:

1) Certain things don't appear correctly in preview, they come out OK in the render. Speed ramps are one thing I've noticed this happening with.

2) More things to keep track of. It would be very nice if Vegas let us store multiple sequences / comps in the one project file.

Bob.

Using Track Motion within the Nest makes easier for life in general, than having to keep track in the MAIN Veg.

Grazie

For example place a pic on the timeline and apply liner blur it will effect the surface but not the edge
Save that as a veg
Start a new project place the veg on the timeline and apply the linear blur the fx will effect the object as a whole blurring the entire pic

xfx -- I don't follow this. I see that the FX applied to the entire track will effect the entire track, whether the track has nested veg or not. What's this about effecting the "edge" ..?

It would be very nice if Vegas let us store multiple sequences / comps in the one project file.

Bob - Why can't you store multiple sequences / comps in one project? .. Seems there is no limit to the number of veg files or rendered sequences you can store in one project file. You must mean something different.

Using Track Motion within the Nest makes easier for life in general, than having to keep track in the MAIN Veg.

Grazie - Are you saying that creating track motion effects is best handled in a seperate veg and then inserted into the main project as a nested veg? I absolutely agree with that. Much easier to handle and make changes later too. I use to do this by rendering the track motion effect to an AVI and then using that in the main project -- but I think the nested veg is better and takes less time.

Xberk

Place a pic on the time line track one save this as nest test, now ..add linear blur to the pic [ or track ] it will effect the surface only

Import nest test veg place on track 2 and add linear blur…the linear blur will effect the entire pic in effect treating it as an object not just the surface but the edge also

Now you can compare the difference between the two, the nested fx applied and the direct fx
The same will apply to other fx’s

I have used nesting a lot and have found it to be very useful.

One Con: is that (I believe) audio in nested .veg files is only imported in stereo, so if a sub-project has a surround sound mix, it will be down-mixed to stereo.

Apart from that, can be a very useful tool for managing complex projects.

marks

"Seems there is no limit to the number of veg files or rendered sequences you can store in one project file."

They're not stored in the project, the project references them. For example if MyMovie is split into 5 scenes each with it's own veg file then I have Scene1.veg ...Scene5.veg. I nest all of these into MyMovie.veg. I now have 6 veg files and I need all of them to create MyMovie.
In other NLEs Scene1,2 etc can be sequences in the one proj file, I only need one proj file to create MyMovie.

Bob.

I like the IDEA of nesting, but whenever I've used it, I end up forgetting something that I applied in the original veg that doesn't carry over. For example, if you apply fx to the Project Media in the original veg, those fx don't apply to the events in the nested veg. I'm not even sure if you apply fx to a track whether that carries forward into the nested veg. Also, when I'm archiving at the end of a project (via either Veggie Toolkit or Ultimate S), I get confused about what items are in the current veg or the nested veg, and I'm never quite sure if all of the events were archived. There are so many details to remember in any particular project that I ended up just having a system where I copy/paste events from a veg into my full project veg rather than nest it.