Adding the project files (*.veg) to Vegas is one way of doing this but the problem is that your projects get flattened to one video track and a stereo audio track.
The recommendation is to have multiple copies of Vegas open and do copy/paste between projects.
Thanks Mike. Like you said, flattening doesn't give access to the elements and opening up two separate Vegas instances is a memory hog and a pain. Yeah I think Vegas should look into making this available.
Heck,
with the way Vegas points to things and does editing without destroying anything, I wouldn't be surprised if opening multiple instances only runs the program once and just points to the veg files for the content - you can only focus on one project at a time... (this speculation is completely mine, and I have no real basis for the statement)... (grin)
Here again, showing how little I know about what I understand in Vegas... (wink)
I think what you're asking for is for Vegas to support "sequences".
Would be nice, very nice but it could come at a cost.
The NLEs that do use sequences can be a bit harder to get your head around.
No. Run additional instances of Vegas - the extra overhead is not significant, unless you are previewing or rendering in separate instances at the same time !.
It'd be very nice to be able to do both. There are real advantages to being able to run multiple instances of Vegas (You can render in one while editing in another) but having "sequences" would allow you to associate several timelines with an overall project. Vegas has never really been able to deal with the "project" concept.