How to insert (nested?) projects into timeline without rendering

gary-o wrote on 10/17/2020, 11:10 AM

Hello,

I have a number of projects that I'd like to assemble on the timeline, one after the other, so that I can tweak the individual events.

I thought that this is what nested projects is all about, but when I import a project into the timeline, all the video events collapse into a single track. How do I prevent that from happening so that I get exactly the same layout as in the (nested?) project?

Each project looks a bit like the one on the left. When I import/insert the other project, it looks like the one on the right. I'd like all the imported projects to look like the one on the left.

How do I do that?

Thanks :)

Comments

jetdv wrote on 10/17/2020, 11:35 AM

Yes, nesting will collapse the entire project into a single event. If you want to copy the full project, you'd need to have Vegas open twice, copy from the original project, and the paste into the combined project. However, you would looks things like track motion and effects, etc...

Even if nested, you can still edit the original project and the changes will show up in the combined project.

gary-o wrote on 10/17/2020, 7:26 PM

Thanks, but that isn't practical. I would have to open up hundreds of separate instances of Vegas in order to individually copy and paste the different projects onto the timeline.

All I want to do is select all the projects in Explorer and drag/import them en masse into the timeline.

Is there some way to "uncollapse" each of the (nested) projects, also en masse so I view them across the whole timeline?

DougT wrote on 10/17/2020, 7:55 PM

No, it will the nested project will always appear as one file. Jetdv's answer is the only way to edit individual

walter-i. wrote on 10/18/2020, 2:30 AM

No, it will the nested project will always appear as one file. Jetdv's answer is the only way to edit individual

That makes sense - at least in the way I think and work.
I therefore nest in order to maintain an overview and to be able to work with smaller units on large projects.
If I have to change something in a sub-project, I only make the change in one part without running the risk of "shooting" the others.
Just as an example - if you were to use Auto Ripple incorrectly only once, the misery would be complete with your hundreds of project files.

Automation can make life a lot easier - but you can destroy a lot with a single push of a button !!!!!!