Vienna Symphonic Library Forum
Forum Statistics

181,941 users have contributed to 42,195 threads and 254,636 posts.

In the past 24 hours, we have 5 new thread(s), 13 new post(s) and 51 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Local VEPro instantly disconnects after connecting.

  • Local VEPro instantly disconnects after connecting.

    J
    J

    I don't know if this is a Cubase issue or a VE Pro issue.

    I'm Using VE Pro 4, though the same problem exists in VE Pro 5 with a trial license.

    In Cubase 8.0.10, I have a large 230 track orchestral template, using 2 instances of VE Pro - one local and one on a remote PC.  (Both are running Windows 7)  When I started the project, everything was fine.  But after rebooting and reloading, the local instance of VE Pro in the server window shows as connected to the local machine, however no midi data transmits.  Also, if I look inside Cubase at the VST Rack for the local instance of VE Pro is shows DISCONNECTED, and I don't see my populated VE Pro instance because outside of cubase it thinks it's connected.

    If I force a disconnect in the VE Pro Server, inside Cubase I can see it in my list and reconnect to it.  It shows connected in the Cubase hosted plugin, but again no midi is transferred, and if I bring the plugin back up a 2nd time, it shows DISCONNECTED -- back to the original problem state.  (Connected according to server pane, disconnected according to plugin inside Cubase).

    As for the the remote hosted instance of VE Pro, it has no issues at all.

    Additionally, if I load my Cubase project with empty VE Pro Servers - the remotely hosted instance loads the template, but the local one brings up an empty VE Pro instance (with the same connected/disconnected problem as above when I have the template pre-loaded).   Also, each VE Pro instance hosts about 8 Kontakt 5 instances.

    Any ideas on this odd behavior?
  • F
    F

    Also having this exact same issue. From some testing I'm wondering if it has to do with the "size" of the VE Pro Instance I'm trying to connect to. For example, I can connect and disconnect without trouble to a VE Pro Instance with a few instances of Kontakt running inside it, but if I try the full 9-Kontakt instance I'd like to be running, this glitch appears.

    To reiterate: The local instance appears in the connection list. Selecting it and clicking "connect" causes it to fall off this list. In the VE Pro Server pane, this instance will register as connected. But the plugin within Cubase will still read as "Disconnected."

    Cubase 8.0.1
    VE Pro 5.4
    Mac OS 10.10.3
  • M
    M

    I have had this exact same issue. If I disconnect a VEPro instance while the session is active and then try to reconnect, the slave instance registers as connected, but no MIDI data is transferred. In Cubase, the plugin no longer sees the slave computer in the list of available instances, but it does not register as being connected to any instance.

    This happens in Digital Performer as well as Cubase.
  • M
    M

    I have the same problem within Pro Tools!

    and in addition all VSL VEP VST3 PlugIns are not working within Cubase. Some help would be really great :/
  • PaulP
    VSL Team
    PaulP

    Hi, 

    We cannot seem to reproduce this here. Can you please send some sequencer projects to support@vsl.co.at, with a short reference to this thread?

    Please include which versions of all involved software (sequencer, VE PRO 5, Kontakt, additional plug-ins) you are using. 

    Thanks, 
    Paul

    Paul Kopf Product Manager VSL
  • D
    D

    I was having a similar issue with my slave machine (Mac mini) suddenly losing its connection and having to force-disconnect in the server instance on the Mac mini in order for it to appear in the host plug-in window as an option to reconnect to. Additionally, it was causing the MOTU Audio System (MAS) to shut off. I was using the MAS version of the VEP plugin.

    Once I woke up the Mac mini, did a force-disconnect, and relaunched MAS, everything seemed to behave normally again.

    Did a test and set my Mac mini to never go to sleep and I did not encounter the problem. Hopefully that helps some of you...was driving me crazy!
  • A
    A

    Was this ever resolved? I am having the same issue and it is extremely inconvinient. I have wasted over a week with constant troubleshooting and it essentially renders my files uselsess when I try to onnect them. Hoping for a solution!
  • C
    C

    hello,

        I have been using VE Pro5 on OSX with Pro Tools and Cubase (Host), connected to a Slave Windows PC, everything worked fine.

    Now I switched to a Windows 10 host PC running Cubase 8.5 / 9. I keep getting the disconnect problem continually, only when I try to connect to a local instance. I'd like to give more info, but I'm still changing so much all the time, since I'm still setting up...

    Did anyone find out what happens? I would expect a local connection to be the least trouble...

    thanks
  • PaulP
    VSL Team
    PaulP

    Hi cmatt, 

    It's usually sleep settings, AV programs with extreme settings, firewalls or third party programs like "Little Snitch" that interfere with network connections. 

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • C
    C

    thanks Paul,

     it seems that if I open a Server Project, all is fine, but if I start a new instance from scratch the disconnecting happens.

    I'll keep checking...

    C