I'm new to VP. I've read about nesting, but that only allows access to the imported file as a single event. I'd like to be able to import the project with the tracks to retime events based on the current project.

Scenario :

Titles project , Main Movie project , Credits project .

I want to stick all 3 pieces together to make 1 complete seamless presentation .

The above will require 4 Vegas sessions running , concurrently .

Open Vegas session 1 . Viewing Vegas Explorer , Drag the 3 .veg project files onto 3 time line tracks . 1 .veg for each track .

while in session 1 , viewing Vegas Explore , right click Titles.veg , to open context menu and click "Edit in Vegas" this launches another session of Vegas , with Full tracks onto the time line . Using Vegas Session 1 again , launch Main Movie.veg and Credits.veg . You now have 4 Vegas sessions running .

Session 1 will be the final composite . You can now continue to edit at the Track Level in the other 3 sessions . Be sure to "Save" to the same .veg file name so that Session 1 will "get the update" changes . Session 1 continues to Pole the .veg files . When session 1 finds a change in a .veg file , session 1 will then update itself , to reflect those changes made to any track level editing performed in sessions 2 3 4 .

it might be a good idea to manually make copies of those 3 .veg files before doing this because in order for the track level edits to be seen by main session 1 , the 3 .vegs will need to be overwritten , as you edit them .

If you want to import one project with the tracks into inside another project just simply copy all the events from that project and paste inside the other.

What fan-boy is describing is a real strength for Vegas - one of many ways that multiple instances can really improve workflow. I almost always have another instance open, if nothing else than to use to hold possible clips, etc.

Nesting veg files in the timeline is basically like working with comps & pre-comps inside after effects, only you have to wait for the veg's "proxy" to re-render whenever you make changes to it (but that usually doesn't take too long). You will also see project markers & names from the source veg file as well, which can help when trying to line things up or re-time.

Copying from one open project to another doesn't copy everything - I tested this on one of the template files and the animation was not copied - perhaps the animation was on the track rather than the events.

Thanks for explaining the multi-instance approach, I would not have figured that out. My purpose for asking about this is a scenario similar to fan-boy's example. Personally I'd prefer the option to put everything in a single file where I can directly see and modify the relationships between the various tracks and events.

Copy/pasting from one instance to another instance works only for the selected events, settings in the tracklist like trackmotion or trackfx are not copied/pasted.