VI frames clearing on Host computer Metaframe

[Chris T]

I've been encountering one very annoying problem which I can't seem to remedy:

I have Metaframes on both my Host computer (New Mac Pro) and also on 3 Slave Macs. I run DP8 on my Host. This happens MOSTLY on my Host computer:

When I load a "template metaframe" - i.e. a standard metaframe I've built which contains a collection of VI frames, when I then load my "General Template" in DP, often, some of my VI Frames in the Host metaframe are CLEARED OF ALL SOUNDS. VEPro seems to be getting a message from DP and clearing itself... (I usually have my VI plugin tracks Disabled in DP until I need to use them, to save juice).

I know it has something to do with Decoupling (i.e. so it doesn't 'talk' to DP as far as loading sounds go). However I can't seem to SAVE my Metaframes with "Decouple" selected, thus when I load a metaframe, the Decouple seems to be always deselected.

Can you tell me a good, fool-proof solution to avoiding my VI Frames being cleared by DP ? (e.g. a "Best practice") ?

thanks!

[DG]

Firstly check is that you don't have "Load Incoming Data" set in your VEP Preferences. If this is not the issue try:

1. Make sure your template is backed up...!
2. Load your template without loading a Metaframe first. What happens?
3. If everything looks fine, check "decouple" and then save your DP project.
4. Now load your DP project again. Do you get the same problem?

DG

[Chris T]

THanks DG

Re. "Load Incoming Data" do you mean:

VEP Preferences... / General  - Incoming project data behavior - "Ask" 

?...

I don't see an exact selection for "Load Incoming Data"...

-------

[Chris T]

I did this:

"Load your template without loading a Metaframe first. What happens?"

I have my General Template open in DP.

I load an empty metaframe (i.e. the VEP Server) on Host.

WHen I "Enable" the VI plugins for my Synth tracks (8 of them), they load Instances in my Server with teh corresponding name to the VI Plugin in DP. However all instances are blank (i.e. NO VI's loaded, ONLY Master Bus)...EXCEPT 1 random Instance. In this one, one of my Omnisphere instances was blank, the other DID have sounds.

Not sure why almost all my VI frames are coming up as blank.

Is it true that the most fool-proof way for me is to

1. ALWAYS Decouple.

2. ALWAYS Save a new Metaframe with each corresponding DP file (especially if I make changes to that Metaframe).

Also, why won't my "Decouple" setting SAVE when I save the Metaframe?

Should I always load Metaframe first, select all Decouples, then load DAW ?

Does it matter if I save DAW with VI Plugin tracks DISABLED. Will is be ok when I subsequently ENABLE and connect to my (Decouple) metaframe?...

Sorry for all the questions!!

[Paul]

Hi Chris T, 

This is now quite confusing to me ....

Here are some guide-lines: 

1) The most fool-proof way is to NOT decouple. 

=> This way, all VE PRO data is always saved with your song. 

=> You can also WORK in decoupled mode, but when you save your song, COUPLE ALL instances, so that you´re safe. 

2) It´s a good idea to save your Metaframe file separately in any case (also to have your templates available for other projects). 

3) The DECOUPLE state is saved with your SONG, it´s a status of your VE PRO Server Interface plug-ins.

4) The best way to find out how all of this works is to check with simple (!) songs. 

 

I´m afraid I can´t really follow your questions... maybe someone else can chime in here?

 

Best,
Paul

[DG]

@Chris T said:

THanks DG

Re. "Load Incoming Data" do you mean:

VEP Preferences... / General  - Incoming project data behavior - "Ask" 

?...

I don't see an exact selection for "Load Incoming Data"...

-------

Ok, I'm still on VEP 5, but this is what I see:

DG