VEP Project Template?

[wing]

Lately while in working in Dorico, I've been using VEPro as my backup arsenal of alternate libraries outside of NotePerformer. I have created instances for Brass & Winds that I may or may not use, and save this as a server project which can be invoked as a template, basically.

However, every project has different needs which invariably results in me tweaking slight variations on mic positions or CC values with the instruments, that I would not want to be saved as a default for the template with other projects. So far I have made the mistake of saving over my template with settings which were specific to one project. Is there any way to create template server project files in VEP, which create new files (that will not save over the template)? Just like how you would in Dorico or in a DAW.

Or, if not, what is the best strategy for what I am trying to do? Would you just save a new server project file which is specific to that one Dorico project, for example?

Thanks!

[Dewdman42]

in MacOS you can always try to lock the project file so that VePro can't over write it. I don't think there is a convenient template feature though like in a lot of DAW's. Once you lock it, if you accidentally save, VePro will complain in an unfriendly way, but at least you won't accidentally write over it.

[wing]

@Dewdman42 said:

in MacOS you can always try to lock the project file so that VePro can't over write it. I don't think there is a convenient template feature though like in a lot of DAW's. Once you lock it, if you accidentally save, VePro will complain in an unfriendly way, but at least you won't accidentally write over it.

Thanks for your response, I'll try that.

I'm somewhat new to VEP and interfacing with Dorico, still lots to learn. I just noticed when opening a project in Dorico that it automatically loaded all the necessary instances in VEP for me – I was surprised to see this, as I assumed that I had to load a server project on the VEP side first to connect all those instruments.

It seems, similar to MIR Pro, that the settings are saved within the Dorico project file itself perhaps?

I suppose to simplify my question: if I load a Brass section template for use in a Dorico project, but decide to adjust the mic positions or maybe swap a trumpet for a different sample library, do I even need to save this anywhere (in the folder with the project)? Or can I just close it and those things will all be saved inside the Dorico project somehow?

In which case does making such changes to my instruments actually affect the original server project, or is it safe?

In short – given this scenario, what would you do?

Thanks!

[Dewdman42]

Take a look at running vepro decoupled. The default behavior must be coupled, which yes saves a bunch of stuff in your daw project and when you load up the project it causes vepro to load all the channels of instruments as saved in the daw project. That is convenient in some ways but most people don’t use vepro that way. It also increases the save time of your daw project significantly.

when decoupled the daw does t save anything related to the vepro project and it’s entirely on you to save or load vepro instances or server projects however you want. One more advantage is if you use a consistent vepro project then you can quickly switch dorico or daw documents around and vepro won’t reload anything.

[wing]

@Dewdman42 said:
Take a look at running vepro decoupled. The default behavior must be coupled, which yes saves a bunch of stuff in your daw project and when you load up the project it causes vepro to load all the channels of instruments as saved in the daw project. That is convenient in some ways but most people don’t use vepro that way. It also increases the save time of your daw project significantly.


when decoupled the daw does t save anything related to the vepro project and it’s entirely on you to save or load vepro instances or server projects however you want. One more advantage is if you use a consistent vepro project then you can quickly switch dorico or daw documents around and vepro won’t reload anything.

Oh ok, that seems to be why – noticing this to be the case for all my Dorico projects so far. Fortunately it hasn't been totally crazy with load/save times and I'm not bouncing back and forth with a DAW, but I can see some Dorico project files where I had versioned before and after the addition of VEP, and the jump in actual file size is quite significant, from around ~500KB to 8MB from that alone. Good to keep all this in mind – like I said lots still to learn! I appreciate your help.