Hi all,
I'm having a bit of a rough time using VEPro on 2 x slave machines and a sequencer running Cubase.
My setup:
Intel Quad Q6600 4GB XP Pro 32bit sequencer running Cubase 5.0.0 - my template has 3 VEP vst3 plugins open in 'decouple' mode so I can keep my slave samplers running and loaded at all times with the same content. The Cubase template was obviously saved when I had all the correct connections. The gigabit network I have is only for the samplers:
Slave 1 - Intel Core Duo £4500 @2.2ghz Win7 64bit 8GB. This machine Has the 64bit VEP server with one active instance of VEP loaded.
Slave 2 - Intel Zeon 8-core Win7 64bit 24GB. This machine, as above only I have 2 x active instances, saved together in a meteaframe, loaded into the VEP 64bit server.
I also have 4 x Gigastudio PC's that use my network for Midi Over Lan.
The problem is that although my template in Cubase has the Decoupled VEP vst plugs, sometimes when I load my template one or the other of the slave machines will load a 'New' blank instance and I'll be connected to that instance... just as if I'd selected New from the plugin. I'll then be connected to the New instance and won't be able to select my usual named instance, although I can see that it's present on the sampler (not in the VST plugin). On the odd occasion I'll see te named one and the 'new' option and I'll just disconnect/reconnect, but then sometimes I won't be able to connect to anything at all - the VST plugin connections window is blank.
All seems to be totally unpredicable - I'll shut down a track I've written from the template just fine, and reload the template to get spurious connection issues...!
What badly need is to be able to open my cubase template and reliably be connected... am thinking of using Bidule/ADAT just so I know what's going on but it'd be a shame as when VEP is working for me it's great...
Any help would be most appreciated.
Thanks,
Tony
-
VE Pro - unpredictable 'New' instances on slave machines when decoupled.
-
I can confirm that I (and another composer running VEP) have also experienced issues like this running VEP AU instances in Logic Pro 9.1.1 under OSX10.4.6 running the latest VEP on a slave Mac Pro over gigabit.
I wasn't able to track down the exact cause and the behaviour was sporadic, in fact the other composer who I've been helping with VEP has just called me with this issue and a 1 hour deadline. What a pain!
I just thought I'd chime in and say that Tonus is not alone with this type of behaviour.
-
Thanks Gents for your input... Karel, I've tried today to reproduce the problem from a totally blank Cubase template (opening 3 x new instances of VEP vst3 in the template) and then saving/reloading the project... couldn't reproduce the problem. In fact annoyingly I had a day of trouble free writing - no reconnection problems. Still is 'nice' to know that I'm not alone with this issue - and interesting that a mac/mac slave can also be problematic in this way. As for the latest VEP versions... I installed version 5436 twice now to try and get a result but have had the weird issue of the new vst plugin not showing up amongst my VST instruments in Cubase, although I can see it's present in my VST Plugins folder... (any light shed on this little puppy would be useful!). Worth noting though that I'm still on Cubase v5.0.0 until I'm between projects... I'll try the very latest 6150 version and see if that clears things up - yt020490... the problem here is just as sporadic as you describe... I'd be pushed to imagine that it was a network based issue as there's not really that much going on LAN-wise. Many thanks - will think on, Tony BTW - where have my paragraphs gone? Looks like one big sentance when I post!!!
-
@Tonus said:
[...] BTW - where have my paragraphs gone? Looks like one big sentance when I post!!!Open your "Profile" on the top (it's in the forum's main navigation bar), select the "Community"-tab and switch the content editor to "Enhanced".
HTH,
/Dietz - Vienna Symphonic Library -
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.
-
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
-
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?
-
@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
-
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?
-
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?
