Vienna Symphonic Library Forum
Forum Statistics

200,448 users have contributed to 43,198 threads and 259,084 posts.

In the past 24 hours, we have 1 new thread(s), 8 new post(s) and 79 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. Please explain this Kontakt 4 and build 6853 behavior.
  • J
    J

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

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

    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?
  • P
    P

    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.
  • J
    J
    last edited
    last edited

    @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. 
  • P
    P

    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.
  • J
    J
    last edited
    last edited

    @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.
  • P
    P

    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.
  • P
    P

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