Understanding Decouple

[Firepan]

Hi -

For example, I launch my VEP 64bit server, load the metaframe, launch Nuendo, create a new session utilizing my laboriously created template, lay down a couple of Omisphere or LASS tracks with a sound different than the one loaded in the VI at the launch of the metaframe. If I save Nuendo, start a new project and utilize diofferent sounds, save that project and go back tot he previous project, will VEP rember the sounds I had chosen previously? Is that what Couple vs Decouple does? Or, should I be saving the soundsets in VEP as projects?

Thx for the help.

[civilization 3]

It means that Nuendo is not charged with remembering what is loaded in VE Pro. This is a great advantage; it generally means faster loading, particularly if there is substantial loading, it means you can preserve the VEP metaframes in order to close your Nuendo project and load a new one. It is more stable with a larger project as well.

It means saving VEP metaframes separately than the Nuendo project of course. If you don't have metaframes to connect to, Nuendo will instantiate empty instances on the VEP side from its connection. Also, in VEP 5, where you have saved a coupled frame at all, any reconnecting to that means Nuendo will reload what it remembers in place of what's loaded. Even when you have decoupled later and saved.

[Firepan]

Ah, so I should use Decouple. Makes total sense.

My current metaframe loads everything in VEP to align with my template in Nuendo. If I make a change to a sound in Kontakt or say a multi in Omnisphere, should I then just save that as a project in VEP thus letting my primary metaframe load as it does for the template but switch things out for each new session (project) I may work on?

I only use the primary tempalte as a starting point and swap sounds out as I write something new. Is this a good way to be using VEP with Nuendo?

For Example, If I am working on a TV show or something where I need consistency in my sound palette, this may not as much of an issue; however, I am building a cue library currently, and I find myself using instruments and sounds that may not be included or part of my primary template. Is it best to leave the VEP template alone, and load VIs into Nuendo to accomoadte deviations in the template for this kind of work?

I totally appreciate the help.

[civilization 3]

@Firepan said:

I only use the primary template as a starting point and swap sounds out as I write something new. Is this a good way to be using VEP with Nuendo?

That's how I approach it. I make Cubase templates that are connected to how I approach VEP:

I have a consistent way, I know more or less what I'll put in the metaframe, and I name the instances "1,2,3" corresponding to slot number 1 etc.; with more descriptive names if I have enough deviation from my norms. "2" is always BFD2, "3" is ww/brass but I could add percussion to "2" or synths to "3", like that.

I have so many templates, vi frames and metaframes. I seem to always make new ones from where I start. Where most of it isn't changed, reloading the earlier or 'basic' frames is going to be very quick, decoupled. Also I save channel presets and channel sets when I change the compression/EQ etc. So, you know, 'Trbns [project name]'.

for instance, I have two projects I was refinishing last night. One is kind of a sweetening of the other, using audio from the first. They use a very similar first slot that started to be the same 'template'. If I had slow loading I would have to consolidate the differences and approach this a lot more intelligently than I ended up doing. As it is, loading back and forth involves just a very few seconds loading time.

for me it's best not to couple the two. I don't instantiate very much of anything in Cubase anymore so the thing about a template on that side is how it's connected to VEP.