Comments

Chienworks wrote on 9/9/2003, 6:18 AM
In a brief phrase, it's the ability to import an entire .veg file project as an event in another project.
taliesin wrote on 9/9/2003, 6:57 AM
In some cases (for example CineStream) a nested timeline means, you can have a very complex timeline, but it needs just a mouse-click to make this whole timeline a single clip which can be used in another timeline.
Now - if you wanna make changes to what was a timeline before, just double-click that single clip and it becomes the timeline it was before.
This is a VERY timesaver in complex projects.

Marco
TheHappyFriar wrote on 9/9/2003, 7:48 AM
In Premiere Pro the nested timelines means you could have multiple timeline's in 1 project. They are set up with tabs for the different timeline's. However, I don't know if this would be extreamily useful in Vegas. You can have multiple instances of Vegas open, unlike Premiere where you can only have 1 instance open at once (and if you need to copy things between multiple projects, multiple timeline's would help). I'm not sure if any other major NLE can have only 1 copy open at a time (Avid, Final Cut Pro, etc.).
PeterWright wrote on 9/9/2003, 8:22 AM
Here's one way nested timelines would be very useful in Vegas.

A single event, in say Timeline B, which represents another timeline, maybe a 15 track opening sequence from Timeline A, will be updated realtime as you make alterations to the original 15 track nested timeline.

Having multiple instances of Vegas doesn't do this.
Sol M. wrote on 9/9/2003, 6:57 PM
I'm curious as to why you would rather have multiple instances of a program open when working on a single project, than multiple timelines within one instance?

I guess I'm just a stickler for efficiency, but it would seem that one would have to do a lot more mouse-movin' to work on the multiple instances than if all the timelines/sequences were in one single interface.

Also, is there any sort of peformance hit with multiple instance of Vegas open?
rmack350 wrote on 9/10/2003, 12:03 AM
In addition, I contend that a nested timeline could lend itself to background prerenders. This is because a nested timeline would be less likely to be altered. I suppose you could have a lock feature on the nested timeline-meaning it was definitely ready for a prerender. Might be better because all that prerendering will eat up disk space.

Rob MAck
rmack350 wrote on 9/10/2003, 12:11 AM
Of course multiple instances of Vegas use more memory.

One reason to have multiple instances open is that one can render while you work in the other. There is an inherent performance hit but not really a productivity hit if you use dual processors or an HT processor. You're getting that render done and you can still work. That's good!

The mouse-movin isn't so bad because you aren't usually doing a lot of work in both instances at once.

No one is suggesting replacing multiple instances with multiple timelines in the same project. Both would have their uses.

Rob Mack