Templates

Phil_P wrote on 10/26/2024, 3:06 AM

Hi all,

When I am working in my DAW, I have a number of templates for various tasks. e.g. Composing / Scoring for movies. Voice Over. Songwriting etc.

You set up a project how you like it and then save it as a template, which when starting a new project, you can choose a template to use, and choose the location and name of the project etc.

Loading a template when starting a project, all plugins (and instruments) and various other settings, (mixer routing / channel naming etc.) will be part of the template. It is a very quick way to get started on certain projects. (As an example, In Cubase and Nuendo scoring template, I have over 200 tracks which have everything assigned and ready, and all tracks are disabled so that the project loads quicky and then tracks can be enabled at will.)

Anyway, I have been using Vegas for a while, but it has only recently started occurring to me that having a template system would be very convenient.

For example, I have written various scripts that I can apply when starting a new Vegas project. But some things just are not possible with scripting. And my workflow would be greatly improved if I didn't have to set up all these things every time starting a new project.

I would like to be able to:

Have certain plugins and FX packages (audio and video) already assigned to certain tracks.
Track naming and colouring
Track heights and zoom factor
A certain workspace (view) set per project (depending on the project type my main view is different)
Obviously, all other project settings that are already possible
And of course, many other things.

So how do you guys deal with this kind of workflow? Is there some way to do this that I have missed?

Are we limited to making a blank, dummy project and saving that, as a kind of template?

I thought it might be interesting to discuss this, ether with solutions or as possible useful feature request.

Cheers,

Comments

EricLNZ wrote on 10/26/2024, 3:14 AM

Are we limited to making a blank, dummy project and saving that, as a kind of template?

My understanding is yes, at the moment it is. Does doing this provide you with everything you need?

Phil_P wrote on 10/26/2024, 3:44 AM

My understanding is yes, at the moment it is. Does doing this provide you with everything you need?

Well, I guess some of it, but not all of it.

Opening a blank project is not really the same thing as loading a template which will then give options to save in a new location and so on.

Usually, templates will be a separate entry in the menu (and welcome screen, if there is one)

I mean, it is kind of standard thing in most complex editing applications. I was wondering how you guys deal with this.

Attaching an example of Cubase for ref:

Dexcon wrote on 10/26/2024, 4:12 AM

Are we limited to making a blank, dummy project and saving that, as a kind of template?

That's what I've been doing for years. All tracks named and with track VFX or audio vst plugins where necessary, Project Properties specific for the project.

Track colors are decided by the colors globally set in Options/Preferences/Display so are not project specific, and the workspace layout is going to be the last workspace layout used - but easy enough to change via the View menu with 3 clicks to choose preset window layouts (maximum custom layouts though).

Phil_P wrote on 10/26/2024, 4:33 AM

Hi @Dexcon

Yup I get it. And I understand that if you have been doing this for years, you are Ok with it.

But it still isn't the same as having an actual template system.

For example, what if you have assets that are part of the dummy project. You save the newly created project to a new location. There are a few (albeit small - but every second counts) hoops to jump though in order to make sure everything remains as it should. And certain tools and program settings need to be changed depending on the workflow required.

I mean, there are many reasons why most editors have a template system.

Imagine you have 10 or 20 different workflows. Different video project types. Colour correction. Dialogue editing. etc. etc.

With a proper template system, the templates for those would be listed and easily viewable, separate from the actual projects list. (No need to search for them, if they have dropped off the recent projects list for example).

You could then simply click the template to open it
It would ask where you want to save the new project that is based on that template etc.
And ALL settings would be part of that template.
Including view, certain settings and editing setting. etc.

Anyway, for now I guess I was correct in my assumption that using dummy projects is the only way. So personally, I think it would be a useful addition.

Cheers :-)