Vienna Symphonic Library Forum
Forum Statistics

183,054 users have contributed to 42,273 threads and 254,975 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VE Pro - unpredictable 'New' instances on slave machines when decoupled.
  • C
    C

    I had that issue, sporadically but not real frequently with that build. the next build I didn't. IIRC an engineer here thought it was a network thing and suggested the next build in beta, which was right in my case. I haven't seen it in some time.

    I noticed cubase 5.0.0, which isn't a great idea.. I'd go to 5.0.1 right away.

  • K
    K
    last edited
    last edited

    @Tonus said:

    Sorry - meant to add... I'm currently running VEP v4686 on all machines... Thanks T

    That's a very old version. It's very unlikely that you'll experience any of this in the latest version 4.0.6150.
  • T
    T
    Thanks Dietz and Karel... really good to know that an update might fix this - BUT I'm trying to move to the latest build but am coming across another problem whereby when I install (6150 build or the 5436) Cubase doesn't see the Vienna Ensemble vst3 in my instrument plugin list (although I can see the .dll in my VSTPlugins folder), even after rescanning... odd because when I roll back to 4686 it sees it fine... Any thoughts? T
  • K
    K

    That sounds strange. The VST3 plugin is installed in "C:\Program Files\Common Files\VST3\Vienna Ensemble Pro x64.vst3" and "C:\Program Files (x86)\Common Files\VST3\Vienna Ensemble Pro.vst3" on a Windows Vista/7 x64 system. Could you verify those files exist on your system? Also, did you try doing a plugin rescan in Cubase?
  • T
    T
    Thanks Karel - I was actually using a 32bit Cubase 5.0.0 but just updated to v5.1.1 and now cubase will see the VEP Plugin. I'll give it a shot working with my two VEP machines for a while with v6150 and report back if I run into the same issue. Many thanks. T
  • I
    I

    I'm rebuilding my template from FX Teleport to VE PRO. I just tried the decoupling for the first time and got this problem straight away with the latest build. I'm using Cubase 64 in Vista 64 and VE PRO x64 server on the DAW and two slaves (x64 and x32).
  • D
    D
    last edited
    last edited

    @info_9427 said:

    I'm rebuilding my template from FX Teleport to VE PRO. I just tried the decoupling for the first time and got this problem straight away with the latest build. I'm using Cubase 64 in Vista 64 and VE PRO x64 server on the DAW and two slaves (x64 and x32).

     

     Firstly, make sure that decoupling is actually what you want. I would suggest getting your systems up and running without decoupling, and then see whether or not you nedd it.. It will take a while to get all your project files in the right state to do this, but the only reason decouple was introduced into the software was to make save times faster. It may not even be necessary in your case.

    DG
  • I
    I

    The save time for my template in Cubase is over a minute so I think that qualifies. [:P] I aim to make a standard template that my two 8 gig slaves load automatically when they boot up. Isn't decoupling mandatory for that? Can't I just recouple them when necessary to make a backup of the whole thing at once so that I don't have to wonder which template version belongs to which piece in case I have to reopen something finished or use two different templates in two different projects?
  • M
    M

     I have a very similar problem and some others too. I never know whether Pro Tools will connect with the decoupled instance or if it will start a new one. This is true for all 3 slaves but one most commonly. Also sometimes ProTools shuts down on startup for no known reason. I do a lot of shutting down everything and restarting or rebooting until everything wants to cooperate. It takes up a great deal of time sometimes.

    I'm running Pro Tools 8.03 on a Mac Pro, Snow Leopard. My VEP is 5436. I'll get the newer one if it will help. But will it?

  • K
    K

    It might, but I can't garantee it. I haven't been able to reproduce this behavior with 6150 at least, but neither with previous versions.
  • T
    T
    I guess I could try and couple my template back up... my reason for using decouple was to have the slave machines just sit there stable and fully loaded, and to just access them in the simplest way... will give it a go though... T