Vienna Symphonic Library Forum
Forum Statistics

190,303 users have contributed to 42,730 threads and 257,098 posts.

In the past 24 hours, we have 4 new thread(s), 25 new post(s) and 42 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Losing a connection between Pro Tools and Vienna Ensemble Pro Server

  • Losing a connection between Pro Tools and Vienna Ensemble Pro Server

    M
    M

    Hi,

    Can anyone help. I can't find any posts from anyone with the same problem. I've just started using Vienna Ensemble Pro across a network to a Server on another Mac.

    I'm using Protools and yesterday I tried to re-open a session and Vienna server refused to open on my second mac with all my Vienna patches and Virtual instruments and I couldn't connect. All my other sessions open and connect perfectly normally. Now the weird thing is I had a version A and B , 2 different Pro Tools sessions. Version A couldn't connect to the server (across my network to the second Mac) and Version B was fine. I deleted all the midi tracks in Version B and imported all the midi tracks and tempo, key sig etc into the session from A to try to recover it (the instruments and patches in Vienna were almost identical between both versions ). THis worked ok, but when I then closed and re-opened this session, bearing in mind it's basically Version B with the midi tracks imported from A, it still wouldn't load Vienna - back to the same problem ??

    Can anyone she any light on this ? - I'm using the latest version on Vienna Ensemble Pro and Pro Tools 8.1

    Thanks ! 
  • civilization 3C
    civilization 3C

    what tracks are in the project etc hasn't anything to do with your connection. You are keeping the PT session coupled with VE Pro; are you saving the VE Pro frames or metaframes separately? If you have, a way to troubleshoot is to see if you don't have a problem loading the things in VE Pro per se. I guess you are expecting them to connect automatically from PT's side; are you unable to connect to them manually? 
  • M
    M

    Thanks for the reply.

    Yes, I am expecting them to connect and load automatically and they won't but I can't connect manually either (I've tried all the usual re-starts, deleting and creating a new instance in the same session and they still don't connect) . You say the tracks in my session have nothing to with the problem and if I'd read my post I probably would have made the same assumption, but then how do you explain a session that will save and load the Vienna server perfectly but then won't as soon as I import session data i.e only midi tracks and tempo maps, from a 'corrupt' session ?

    Just to clarify I have a saved pro Tools session that won't load Vienna server on another mac across a network after re-opening it. If I import session data from that PT session into a session with an existing instance of Vienna that will save and load correctly this works ok until I try and close and then re-open the new session. Importing this session data somehow corrupts the working session and that too won't save and load Vienna or indeed see a connection at all. 
  • civilization 3C
    civilization 3C

    my thought is that something has corrupted the VE Pro frames; in fact when I was working with coupled projects, I found upon returning later to working on the projects I found corruption. That is of course strictly anecdotal and we only find a possible correlation... but I am happier decoupling projects and handling VE Pro separately from the sequencer projects for more than one reason, and I can throw that, to me inexplicable problem on top. It's true for me for more than one project which was hard to rebuild.

    The loading time is much faster decoupled, the save time in Cubase is much much less time which is more crucial and there is no confusion. I can't imagine a particular advantage to coupled sessions that isn't heavily outweighed by the problems avoided. To do this, one must completely load the VE Pro side before launching the DAW project or it will open new, empty instance in place of what you want. This way connects the two projects automatically, it just won't load it merely from opening the DAW project.

    That said, 'won't see a connection at all' I wonder about. I can say that if your IP addresses are dynamic, that might explain the lack of a connection, and I might draw a correlation with the problems I had with older projects, which were probably before I learned to fix the IP... that dawned on me as I typed this... Even if you stick with coupled instances I would say to save on the VE Pro side as metaframes, as VI frames, and as channel sets so if you have to rebuild stuff you have the components to do it at hand readily.
  • D
    D

    Are you using fixed IP?

    DG
  • M
    M

    no, I'm not. I am connecting the macs across quite a large network though (20-30 computers).

    And the fact that no matter what I do I can't see the server on the network seems odd. 

    I appreciate you suggestion of working de-coupled, however I often have to switch between 4 or 5 projects several times a day and it's much more convenient for me to only having to worry about loading one session. When it works , it's great and very fast. There is obviously some bug somewhere I'm determined to get to the bottom of. 

    I have some free time today so I'll experiment and try and find out exactly what it is in the corrupt session that's causing this problem. Thanks again for your input. 
  • M
    M

    * Sorry, I mean YES I am using a fixed IP 
  • M
    M

    ok, you're absolutely right. I'm now using Vienna 'decoupled' and it's a much smoother way of working. The advantages by far seem to outweigh the disadvantages. Would love to know why I was losing the connection initially but it doesn't really matter anymore.

    Thanks
  • T
    T

    I have a 12 core Mac Pro running on OSX 10.6.8 and I use Pro Tools 9.0.5 as my DAW I can't get Vienna Ensemble Pro to connect within te same computer (not even  on a network), following the quick start instructions. First time trying to use Ensemble after many years of VSL.