I agree that the epicentre of this trouble is Kontakt.

Not to be counter productive but in all honesty I remember that these long save times were prevelant when using Kontakt as a plug inside PTools years ago. I also remember people on the DUC complaining about it.

BUT despite the long save times they did not result in a crash. That is new.

Jeremy can you explain something to me?

I agree that the way to work if we are using large instruments in Kontakt is to de couple (surely other users are using big orchestral templates in Kontakt......no?).

For this to work then we need to save our Metaframes and Instrument files on our slaves. No problems there.

BUT how do you then get ProTools to connect to your saved metaframe?

For the life of me I can't do this.

Here is what I do…

I open VEPro by double clicking on the saved Metaframe that I want to open (mframe32). This opens the server and all the instrument channels.

I then open the VEP plug on the host from withing PTools and all that is listed when I hit connect is "new". The instance that I have sitting on my slave is not there to choose from in the list.

How do I connect to it?

I have to save the channel set and bring it into the "new" instance and when I do I can be sure that some of the chanell I/O have been messed up (but I'm not concerned about that).

I'm fine with de coupling and working that way .......because I have a hugh investment in Kontakt instruments, but I need to be able to connect my saved files with PTools.

Am I missing a simple process here or is this a part of the PPC "works but not supported" funkyness?

@philco said:

BUT how do you then get ProTools to connect to your saved metaframe?

It's definitely not intuitive, nor obvious, but I stumbled upon this today while working it out...

1. Let's say your PT session is happy, and you are connected to various instances of server(s). Good. Now save PT.

MAKE SURE uncouple is selected. For me, I also have "preserve instance" UNCHECKED on each server instance.

2. Close protools session. Your server instances should close.

3. Now open the protools session. it will load EMPTY (default) server instances.

4. Now open the metaframe or projects at the server. Dialog: "Do you want to save changes to the project" - NO (this is a stupid interface design element - by default instances should be empty, without placeholders... but that is besides the point) -- and now your metaframe or projects should simply load.

Yes? Works for me, but I am only using one instance per server.

Don't forget to save your projects on each server. Just like the old days.

Please report back.

PS --  Phil, are you also saving viframes (projects) ?

I have no difficulty connecting to a single instance per host plugin.

Thanks for the reply Jeremy. I save both files. (although I still don't understand why....I just do it)

I tried your method and it does not work for me.

I decoupled in PT and saved.

I closed the session in PT.

My session in VEPro closed.

I reopened the session in PT.

As you said (and as I've seen a million times) VEPro opens a "new" project with 2 channels.

I open my metaframe in VEPro. It asks if I want to save. No I don't. My project opens.

I have to now connect in the Plug in PT. Nothing is there in the plug. It is not displaying my just opened metaframe. Only "new". If I connect to "new" I get the same two channels.

Nothing is written in the "preserved session"   box or the "salve host name" box (should there be?)

I cannot connect to this instance. The PT plug will not see it and NEVER has since the day I started using VEPro.

I thought this was normal behavior.

Something is wrong.

We have the same PPC don't we Jeremy. A dual 2.7?

Also note that when I open my saved metaframe it is automaticaly preserved.

I cannot un preseve it because it will close.......because there is no active connection.

And I cannot connect it.

@philco said:

I cannot connect to this instance. The PT plug will not see it and NEVER has since the day I started using VEPro.

I thought this was normal behavior.

Something is wrong.

We have the same PPC don't we Jeremy. A dual 2.7?

Yes. 2.7

Do you have your machines set to static IPs?

Try this. 

On the server, make a new instance, name it.

OPn the host, make a BRAND NEW protools session. Don't import session data. make a new stereo AUX (not instrument). instantiate a VEpro. Can you connect to the named server (not "new") ?

if you can't do this, you will not be successful with the uncouple workflow. Time for a new thread on this issue. 

My Ethernet Port = Ethernet 1 has a self-assigned IP address and will not be able to connect to the Internet.

So I think that is a static IP address.

I did your test and it worked.

The plug in PT saw the test metaframe and connected to it. Not only that but I was able to open a saved viframe and connect to that.

So I get it.

If I start VEPro Server by opening a saved mframe32 then I CANNOT connect to it from PRoTools.

If I just open a blank server and then connect via the PT plug to "new" I can then open my saved viframe32 within that new instance and leave PT connected.

That viframe opens INSIDE the "new" instance in the Server.

Ok I get it.

Did doing your test actually "reset" something in PTools I wonder?

More likely I have just been stumbling along and disconnecting when I shouldn't or opening the Server by opening the metaframe and wondering why it wouldn't connect.

So you have to open the server, then make a new instance, connect to PT, open your viframe inside that new instance and leave PT connected.

Can I just say with all respect to those involved how freaking confusing that is?

Oh PT just crashed again..............here we go

Thanks for your help Jeremy, I can now work decoupled.

@philco said:

My Ethernet Port = Ethernet 1 has a self-assigned IP address and will not be able to connect to the Internet.

So I think that is a static IP address.

Hmm... self assigned does not smell right. Are you using a router and/or switch? 

You should manually assign an IP to each machine on the network, with the same subnet.

Such as this:

And your slave should have a unique number, such as 192.168.0.19

IF you are using a ROUTER, it is suggested to use a switch BEFORE the router - and DO NOT use the router's built-in switch, since most routers on the market have piss-poor LAN throughput. If you don't believe me, check this out:

http://www.smallnetbuilder.com/component/option,com_chart/Itemid,189/

And visit Tomshardware.com and other hardware sites, and you'll see that consumer grade routers are a terrible SWITCH solution.

So get a gigabit switch. Put all of your boxes on it, then connect the switch to your router. Make sure you constrain the DHCP range of the router to outside the range of your static IPs. That's really all there is to it.

Thanks Jeremy, my router is an Apple Airport Extreme and I have all the house's computers plugged into that.

If you don't I mind I will do a diagram and ask you to check the system configuration as to the necessity of a gigabit switch. I better learn some more about that switch.

My slave is also on the internet..

I'll get back to you.

By the way the computers are hard wired to the AExtreme.