Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Best practice when using Decoupled
Last post Thu, Oct 25 2018 by civilization 3, 9 replies.
Options
Go to last post
Posted on Fri, Oct 12 2018 20:33
by rjay
Joined on Mon, Jul 28 2008, Posts 16

I've always used VEP in coupled mode so the metaframes are saved within my Cubase session but I'm thinking of setting up a template with all of my main libraries loaded into and then decoupling. So I get that everything in VEP will not be saved with the Cubase project, and for example I should use automation and pan/volume in Cubase rather than in VEP ... but what about those libraries where there are settings in the sample library GUI ? Such as choosing a specific patch. That is within VEP so how do I save those settings ? I don't "get" this part of how people work with VEP ...

Posted on Sun, Oct 14 2018 01:49
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1631

VE Pro is a host so all of it is saved in the state upon saving the Project or Server Project.
Save as, and then continue saving when you make a change.

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
Posted on Sun, Oct 14 2018 08:20
by rjay
Joined on Mon, Jul 28 2008, Posts 16

But the whole point of decoupling a large template in VEP is that you don't have to keep reloading the same libraries for every prject. If I'm saving it as you suggest, there is no benefit: it must be reloaded every time.

Posted on Sun, Oct 14 2018 12:23
by Bill
Joined on Fri, Sep 23 2005, Berkshires, MA, Posts 939

He means saving in VEP, not your DAW.

Finale 25, Sibelius 2018, Notion 6, Overture 5, Cubase 10.0.2
Win10 x64, 32GB RAM; Focusrite Scarlett 18i20
Kontakt, Bunch of VSL, VIP, VEP, EWQL Orch, Choir and Pianos
August Forster 190
Posted on Sun, Oct 14 2018 13:28
by rjay
Joined on Mon, Jul 28 2008, Posts 16

I realise he means saving in VEP but then when I next load another project I don't want to be using this amended template, so I'll have to reload it. Which brings me back to my original point: what is the benefit of using large templates in Decoupled mode if you still need to save & reload every time you change project. I don't see the benefit ....

Posted on Tue, Oct 16 2018 00:05
by beatpete
Joined on Thu, Oct 01 2009, Posts 68

I decouple all my big libraries and I use a seperate instance (not decoupled) for VSTis that I want to tweak. I also use a seperate instance (not decoupled) for audio reverb sends.

Comp1: Windows 10 64 bit, Asus X99-A USB 3.1, I7 5930K (running at 4500 MHz), 32 gb Corsair Vengeance DDR4 ram, Radeon HD5450 graphics, RME Digiface, Steinberg UR824 and MR816x (X2)
(connected to Digiface), Cubase 10.5 64bit
Comp 2: Windows 7 64bit, I5 3450,32 gb ram, VEPro 7
Posted on Wed, Oct 17 2018 07:10
by mbira
Joined on Thu, Nov 23 2017, Posts 37

Myself and the guy I work with don't use different templates for different projects.  I think that is the point of Decoupled templates.  You have your main big template that you always use and so you load that up at the beginning of the day-or week-or whatever, and then you may work on different projects but they all use the same VEP template.  

Posted on Thu, Oct 25 2018 18:35
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1631

Originally Posted by: rjay Go to Quoted Post

I realise he means saving in VEP but then when I next load another project I don't want to be using this amended template, so I'll have to reload it. Which brings me back to my original point: what is the benefit of using large templates in Decoupled mode if you still need to save & reload every time you change project. I don't see the benefit ....

The benefit of decoupling is 1) it's independent of the DAW. Saving VEP every time you save in the DAW is, with a project of any goodly size, less stable for one thing and a save can take significantly more time. And obviously the need to save the work in the DAW does not through itself mean a need to save the VEP project(s).
2) in this independence you may leave the same server project up and move to other projects in the DAW, and the DAW does not load anything for you. See above as to stability and ease.

You save the changes you make on the VEP end as you need to. If you LIKE the DAW to load VEP, which is definitely slower at any rate, do that.  :shrug:

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
Posted on Thu, Oct 25 2018 18:43
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1631

Originally Posted by: mbira Go to Quoted Post

Myself and the guy I work with don't use different templates for different projects.  I think that is the point of Decoupled templates.  You have your main big template that you always use and so you load that up at the beginning of the day-or week-or whatever, and then you may work on different projects but they all use the same VEP template.  


I do not have "a template" for all seasons, every project relates to a DAW project. I do save a lot of things for further use, and I save it set up in Cubase or Nuendo as a template there. But I may subtract from this, I may introduce other things, I'm certain to make changes which suit the project.

The advantage is the independence, and I see no upside to coupling since it saves no time unless these projects are mighty little. It may well be that I keep a server project up and have another version of the DAW project, or it's a starter 'template' which is my modus operandi when I design the sound for a new project per se; so the established project is up and I instantiate 'new project' in Cubendo.

MacBook Pro 15,1: 2.9 GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
VE Pro 7
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.