Nesting Veg Files: are there any "gotchas"?

Jay-Hancock wrote on 5/2/2006, 9:24 AM
I am a hobbyist, so I don't work with an editing staff. Still, I find this feature is becoming a life saver.

I'm working on a wedding video with tons of stuff in it. Multi-cam PIPs (that move), masks and overlays, effects clips and targa sequences, slide shows using zoom and pan, and plenty of Spices. Normally I would never use this much stuff in a video but this is a special case...

Doing a preview at good or best is impossible. Render to RAM is really slow (brings my fast PC to its knees). This is where the veg file nesting really is helping me. Fortunately I can break the project down into pieces and work on them in isolation. Render to RAM is now quite useful.

I am saving markers to the media via trimmer so that I can promote them later from the scripts menu, but I don't know if this feature can actually promote media markers from a nested veg all the way up to a master timeline.

Other than that one, are there any "gotchas" I should look out for / be aware of with nested veg files? I've seen posts about crashes and things, but that's not what I'm wondering about. I'm interested if there are any procedural tips to avoid difficulties you wouldn't experience without nesting veg files.

Comments

johnmeyer wrote on 5/2/2006, 10:29 AM
I am saving markers to the media via trimmer so that I can promote them later from the scripts menu, but I don't know if this feature can actually promote media markers from a nested veg all the way up to a master timeline.

Starting with Vegas 6.0c, there is a ".cs" script called "Promote Media Markers.cs" that does exactly this. Any markers that were rendered into a media file using the "include markers" switch in the Render As dialog will be extracted and put on the timeline. This also works with markers that are "embedded" in the VEG file. Of course, if you move the markers in your original project, you will have to run the script again to extract the new locations.