Save a template?

Comments

3POINT wrote on 3/13/2020, 11:41 PM

@joelsonforte.br Yes I would suggest making a copy and opening that. But I still think multiple timelines is superior to nesting.

As an example. A complex animated lowerthird background can be made up by multiple timelines. When you need that same lowerthird background several times in your project, you have to copy/paste those multiple timelines each time at the several locations on your timeline, which makes your project unnecessary complicated. Better to make a separate lowerthird background project and use that as your lowerthird template. You just drag that lowerhird background template.veg at the several locations in the timeline of your project. The overexposed text can be changed on a separate track above each lowerthird background in the project itself. Also when you decide to change afterwards the lowerthird background (colors, animation etc) you can easily edit the lowerthird background.veg and all the lowerthirds backgrounds in your project are updated.

Former user wrote on 3/13/2020, 11:49 PM

I think you are getting timelines confused with Tracks. A timeline can be a project, a graphic, etc and can contain multiple tracks but is entered into another timeline as one element. The original timeline can be altered and it is automatically updated whereever it appears. If you have used After Effects, then you understand.

joelsonforte.br wrote on 3/14/2020, 12:23 AM

It must be recognized that the native nesting system in Premiere and After Effects is better than the native nesting system in Vegas. Premiere and After in addition to the typical nesting of events also have the Make Subsequence feature in which it is possible to create several subsequences of the same nesting and edit each one individually without affecting the others.

Vegas native nesting system can improve. An Proof that this, is that the developers of the Vegasaur have created a feature that allows using in Vegas a nesting system as efficient as the nesting system of Premiere and After.

However, I realize that many Vegas users are not interested and do not want to learn or invest in this feature. This too makes it difficult to get official developers to take this feature more seriously and invest in it.

3POINT wrote on 3/14/2020, 4:17 AM

@Former user Indeed, I mixed up timelines and tracks.

@joelsonforte.br I'm not familiar with Premiere but with PowerDirector, a non pro NLE, where nesting is quite easy. The nesting feature of Vegas can and should improve, that's my opinion.

MikeLV wrote on 3/14/2020, 11:29 AM

I guess for me, the expected behavior, or what would have worked better is if I drag in the template veg into the project, make the changes I want and when I save it, it should copy the data to the current project folder. Then repeat the process when the next project comes up. But I guess that does't happen.

MikeLV wrote on 3/14/2020, 12:08 PM

I decided to play around with this template issue this morning. I started a new project, didn't save it. Brought in my video footage, and dragged in the template .veg file that is saved in a template folder. I then did a save as for the project, and clicked the copy media check box. I watched my project folder to see what would get copied. Only the template .veg file got copied, but NOT the image file associated with that veg. Why?

The next thing I notice when I right click on the .veg event on the timeline, there are two options in the right click menu. One to edit in Vegas, and the other to open the nested timeline. If you click Edit in Vegas, it opens a second instance of Vegas (don't know what the reason for this option is?).

If I click open nested timeline, and I make a change and save the file, the .veg file that got copied to my project folder is the one that gets edited, NOT the one in the template folder. And this is what I want to happen, so that's a good thing!

But I still wonder why Vegas didn't copy the image file associated with the template veg into the new project folder like it does the veg itself? If that image were to get deleted or renamed in the template folder, then it would become disconnected from my project. I expected the image to get copied along with the veg, but this is better than nothing.