Vegasaur's creating nested timeline VS Vegas Pro 17's

lan-mLMC wrote on 8/12/2019, 4:53 AM

Vegasaur can copy tracks and tracks'fx and marks. If tracks have been copy to nested timeline, the original track fx will transfer to the nested timeline reasonably.

Vegas Pro 17 only can create event nested timeline and creating event nested timeline will make marks disappear.

And that, I find the Vegas Pro 17's swithcing between the main project and nestedline is equal to that using menu "File-Open-project1" and "File-Open-project2". It just use a one-click to simplify "File-Open-project1" and "File-Open-project2". There is a great difference between VEGAS Pro17 and some other NLE like Premiere, Edius, AfterEffects and so on......

Comments

Marco. wrote on 8/12/2019, 5:12 AM

Yes, it is different from the way nested timelines work in other NLE and each has its own pros and cons. So you would use it in a different way.
I do it in the way to have several small nested projects which all come together in one big parent project. Thus the way I work is other way round as you mentioned. I would not use markers etc. inside the parent project before the work in the nested projects is done. And the markers used in the nested projects will immediately transfer to the parent project.

The Vegas Pro concept also offers collaborated editing on the nested projects which all come together to the parent, quick isolation of nested projects by re-naming, it can be used for grouping and group-global use of FX and FX processing gain one more step (regarding the signal flow) as it can be used as output fx both in the nested as well in the parent project.

There are some more subtle differences which can be used to utilize that Vegas Pro nesting in a helpful way. I'm still exploring this feature.

lan-mLMC wrote on 8/12/2019, 8:38 AM

Yes, it is different from the way nested timelines work in other NLE and each has its own pros and cons. So you would use it in a different way.
I do it in the way to have several small nested projects which all come together in one big parent project. Thus the way I work is other way round as you mentioned. I would not use markers etc. inside the parent project before the work in the nested projects is done. And the markers used in the nested projects will immediately transfer to the parent project.

The Vegas Pro concept also offers collaborated editing on the nested projects which all come together to the parent, quick isolation of nested projects by re-naming, it can be used for grouping and group-global use of FX and FX processing gain one more step (regarding the signal flow) as it can be used as output fx both in the nested as well in the parent project.

There are some more subtle differences which can be used to utilize that Vegas Pro nesting in a helpful way. I'm still exploring this feature.

I think the maybe it is the VEGAS Pro's source code that restricts VEGAS Pro's qualitative leap.

halcyon00 wrote on 4/25/2020, 2:49 AM

Resurrecting this thread for questions re Vegasaur. It seems that the default nesting feature on VP17 b421 disregards track compositing modes, audio curves and volumes and perhaps another things when creating nested projects. Is there a way around this with Vegasaur?

lan-mLMC wrote on 4/25/2020, 5:03 AM

track compositing modes, audio curves and volumes

Vegasaur can. https://vegasaur.com/download/Vegasaur