I've never used that feature, but I've heard about it. How does a nested .veg reference media? I've run into problems in the past where I accidentally drag in a file from outside the project folder I'm working, and later forget about it, and open the project in the future and that file is missing because it was moved.

For all my serious edits I use more than one "nested veg", sometimes only nested vegs.
I do that to keep my timelines easy and not too much and big so I keep the oversight.

Here I use a part of a total of 6 nested vegs, this is nr 3 with in it another nested veg with a part of the titel. Look how easy it works:

😨 My head is spinning; I would get so confused trying to figure that out.

I would get so confused trying to figure that out.

What? That your head is spinning?😉
Nested vegs exists already as long as I know the program from VPro 8 on till now. It works very simpel: make a projectfile from one or two simple edits and click that one in the Vegas explorer, wait a little moment and drag it to the timeline as a "nested veg".

Thanks, I watched the video. Noted where he said at 1:54 that it's wise to use the same save location as the master project. So it doesn't really seem like the nested feature could serve as a template to use in other projects right? What I was trying to do was have a template that I could just insert into any project, and edit it without running into project media location issues and such...

It's over my head anyways, I can't think of any reason I'd need to use nested projects; I don't work with other editors. Why else would you use that feature instead of having everything in one timeline?

@joelsonforte.br We were talking here about nested vegs and NOT nested timeline.

@j-v aren't they they same thing, according to the video? nested veg is how vegas handles nested timeline?

I don't know. I never used nested timelines because they need too much settings and mouseclicks.

If you want to have all the media included, you can create a package which will do just that. Watch again at the 6:05 mark. It's explained.

As for using nested timelines, it can streamline everything for you. When I have a project that will have many tracks, I work in segments and then nest. Now, just one track used, but the nest can be edited. @j-v shows how it will be used.

Another video about nested timelines.....

Thanks, I watched the video. Noted where he said at 1:54 that it's wise to use the same save location as the master project. So it doesn't really seem like the nested feature could serve as a template to use in other projects right? What I was trying to do was have a template that I could just insert into any project, and edit it without running into project media location issues and such...

It's quite easy to accomplish that, just save all your template.veg's in a separate folder called "T E M P L A T E S" and point that folder as a "favorite" folder in the Vegas explorer. This folder becomes easy accessible in every Vegas project and those template.veg's can also be used as nested veg's in any Vegas project by dragging them from the Vegas explorer into the timeline, like every other event.

Those templates can be intros, outros, overlay animations like lowerthirds etc.

@MikeLV “Advisable does not mean mandatory. It will also work if it is saved elsewhere. But for the sake of logical organization it is recommended to save in the same location as the master project.”

The above is important. I haven’t yet used the newer nesting, but last year I used the “classical” nesting in a few projects, it really saved so much time and extra work. I left all of my add in .veg's in their respective locations because for my use case that made sense, they were full projects in their own right. Just imagine the add in veg as simply another piece of media that you add into your project, its that simple.

If you were to say modify your add in nested project, then when you reuse it in another project or projects it just takes a little longer to load the first time as vegas makes its adjustments.

Its a really wonderful tool to have, not to be overlooked.

Thanks @Reyfox

I think Vegas nesting is very awkward. I would much prefer multiple timelines like Premiere and After Effects. I also think it would easier if Vegas could just allow you to save the graphics as the OP originally requested.

I don't know if it's awkward or not. I guess it depends on what you are used to. I've used nested timelines in a consumer editor too, which was easier. But learning the way Vegas does it, and after doing it a few times, then it becomes less problematic. But yeah, it is a little more "complex".

@3POINT Ok, I've created a template folder, added it to favorites, and added the image to that folder. I started a new Vegas project, set up my text media how I want it. So you're saying that I just need to drag this new .veg file into my project folder, and click the open nested timeline button, and I can edit the template file without a problem? Then on the next project, I just edit the same template file again?

There's no need to import that template.veg into your project folder. You can directly drag it from the Vegas explorer (from you template folder) to the timeline of your project where you need that template. Just drag it on a video track and use it as overlay, underlay or as a single event. If you decide to edit the template.veg, just right click the template.veg event on the timeline and choose to edit it in a seperate Vegas instance. After closing and saving the edited template.veg, all Vegasprojects where you used this template.veg will be automatically updated.

all Vegasprojects where you used this template.veg will be automatically updated.

 

This last comment is very important. If you change that veg (update graphic, image, etc) it will be changed in all other projects that use that template.veg. so you need to create a NEW template.veg if you are revising graphics that you don't want revised in other projects.

Hmm, well that's no good. It really doesn't serve as a template then. i.e. the changes don't get saved to the project I'm working on. My use case couldn't be any simpler. I have an image on one track, and some legacy text on the track above. The image is the same for every project, but of course the text changes in each project. So you're saying if I drag in the template veg file, make changes to the text, save it. Do another project, bring the same template veg into the new project, make changes to the text. Then if I go back to the first project, it's going to have the text from the new project.

If you constantly have to create a new template for every project, then what good is the nested veg feature? I still fail to see its use.

If I do a "save as" on the main project, and choose the copy media, will it then copy the veg and image file, and no longer reference the template veg file?

@Former user and @MikeLV Simply create a copy of the template with a different name and use that copy. Changes will only affect the copy.

If I'm going to end up having multiple copies of this "different" template veg file, then why don't I just copy it, and the image file to the project folder I'm working on, over and over? Having one "source template" doesn't really work since every time I make a new project, it's going to be changing it. This goes back to what I originally said about copying events between two instances of Vegas, but instead, just copy the veg file and image file.

Hmm, well that's no good. It really doesn't serve as a template then. i.e. the changes don't get saved to the project I'm working on. My use case couldn't be any simpler. I have an image on one track, and some legacy text on the track above. The image is the same for every project, but of course the text changes in each project.

I wouldn't say that's the purpose of a template. For a same background image, you don't need a template. A template could be a lower third animation, an intro/outro, a slideshow with effects, a complete project etc. Like you name every project different, you should give also different names to different versions of your template. A template is nothing else than a project inside your project.