Vienna Symphonic Library Forum
Forum Statistics

180,822 users have contributed to 42,142 threads and 254,366 posts.

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

  • no instances avaibles in VE pro 5

    hello, I just bought VE Pro 5 but I don't manage to start it in Logic Pro because it tells me I have no instances availables in VE PRO 5 Server Windows... How to add instances? cordially

  • last edited
    last edited

    Hi Tiri,

    Did you follow the Quick Start guidelines in your VE PRO 5 manual (page 7)?

    You can also find out a lot by watching these VE PRO tutorial videos.

    In short: You need to start a VE PRO SERVER (32 and/or 64 bit), so that you can connect to it with the VE PRO SERVER INTERFACE plug-in which is inserted in your DAW.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • With the new update, after several crashes, no server was available to connect to, consistently. Can't be me, after I reverted it's working as it should.


  • Hi, 

    Would be great to get those crash reports, for our developers to check. 

    The more info you can add (when does this happen, how to reproduce, which OS....), the better. 

    Please send to

    Thanks, 

    Paul


    Paul Kopf Product Manager VSL
  • Sorry, that wasn't a good sentence. The crashes aren't going to belong to the new version. Generally they belong to the intersection of BFD2 64-bit in any VE Pro 5, IME. VEP crashed during a render and the log pointed there, for instance.

    But this nothing to connect to is new and I encountered it three times in a row, so I uninstalled and installed the penultimate build.


  • Hi Paul, Thank you for your quick answer ! Unfortunately, i read the quick start guidelines again and again and i started VE PRO SERVER 32 and 64 bit but I still have not instances availables... the instances availables windows in Logic pro is empty.... Help me please ! Best, Tiri

  • last edited
    last edited

    Hi,

    Our developers are looking into this problem as we speak.

    Shouldn´t happen with Logic, though.

    TIRI, could you please send some screenshots to for me to check?

    Thanks,

    Paul


    Paul Kopf Product Manager VSL
  • Hi, All right but which one ? Tiri

  • Hello Tiri, 

    Just some screenshots that show VE PRO Server open, and the Server Interface plug-in (on the same screen), with the eLCC software open, and maybe step by step  from inserting the Server Interface - basically so that I can see what you see... 

    Thanks, 

    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul,

    just wanna let you know that this problem's happening to me as well since I installed the latest update.

    I'm working with Logic 9.1.8 and VE-PRO 5.3.13141.

    - no server's showing up on the connection-window of VE-Server

    - after manually typing the localhost-URL (127.0.0.1) the software's running fine though!

    all the best,

    - Miro -


  • Hi there, the same is happening for me too.  I am using only one computer - no slave.

    All software is up to date. 

    I open VEP PRO Server 64-bit, load up a metaframe, and an instance of VEP opens with an audio input ready.

    Thanks,

    Jack

    Mac Pro 3.2 GHz Xeon 8-core

    18 GB RAM


  • last edited
    last edited

    Hi,

    Please update to VE PRO 5.3.13151, available in your User Area.

    This bug should be fixed now.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    Hi Paul,

    Still not working for me.  Its very strange, because a few days ago, when I first installed MIR, and thought I would start to migrate to using VEP5 as a server so that I can keep instruments loaded between Logic songs, it worked! I managed to get a single channel of audio from Logic to VEP5 successfully.  Then I wanted to be able to automate the faders in VEP5, so I looked up the instructions and inserted the VEP Pro Event Input plugin on an instrument track in Logic and then found that the instance of available VEP5s was blank.  Going back to the audio channel, this too was now showing "not assigned" and none available in the list.  After numerous retarts, and creating new Logic songs and new VEP5 instances, no luck.

    So now I have installed the newest version of VEP5 as you suggested, restarted, and now it is the same deal.

    The OS is 10.8.5, Logic X 10.0.6, Intel Xeon 8-core with 18 GB RAM.

    Thanks,

    Jack

    @Paul said:

    Hi, 

    Please update to VE PRO 5.3.13151, available in your User Area.

    This bug should be fixed now. 

    Best, 

    Paul


  • I am having the same issue with the latest version 13151. I am no longer able to connect to an instance on the same computer no instance available


  • Hi Jack and Charlie,

    Please send me some screenshots that show both the VE PRO Server in the background open and the connected Server Interface and then the Event/Audio Input plug-ins.

    Please include your OS versions and used software versions.

    Charlie, does it work if you type 127.0.0.1 in the SLAVE field?

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul,

    Have just sent you screen shots.

    I should also add that I tried it with both Logic 9 and Protools 11, and it was the same story.

    Thanks,

    Jack


  • Hi Paul ,

    I have also sent my screenshot to support@vsl.co.at 


  • I have a solution on this that worked for me.

    I upgraded to VE Pro Version 5.3.13151 - but I was launching Vienna Ensemble Pro Server (64 Bit) from the dock.

    Somehow, the dock icon seemed to be launching an older version of VE Pro Server, rendering the 64-bit Server and the Interface incompatible.

    (You can check this by typing 127.0.0.1 into the Interface's SLAVE field, as suggested by Paul and reading the warning that comes up).

    Solution - I went to the new 5.3.13151 version in my Apps folder, opened VE Pro Server from there and - hey presto!

    I dragged the icon from the updated folder to the dock and now the correct versions are all launched.

    Hope this helps - it works fine for me now.


  • It has taken a while, but what solved my issue (see above) was to disable Little Snitch, and Norton Firewall.  Little Snitch I found wasn't configurable to let the VEP server connect with Logic, and the Norton Firewall was picking up the connection attempts as "suspicious activity", therefore blocking them.  Strangely, though, even after registering all the attempts as "trustworthy" it still didn't work, so I have disabled the Norton Firewall and enabled the OSX firewall which doesn't seem to have a problem.


  • When I updated to 13151 on my PC the instances disappeared from Logic. Turned off firewall on PC, no help. Reverted to previous VEP version and now it works fine.