Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Options
Go to last post
Posted on Tue, Jul 06 2010 16:23
by Tonus
Joined on Sun, Sep 27 2009, Posts 17
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
Posted on Tue, Jul 06 2010 19:09
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173

That sounds strange. Is there any way you can provide a step by step description to reproduce the behavior? We haven't noticed any of this during our testing. Thanks.

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Wed, Jul 07 2010 10:04
by yt020490_13791
Joined on Wed, Apr 20 2005, Posts 40

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.

Posted on Wed, Jul 07 2010 11:05
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173

Does it still happen with the just released update 4.0.6150?

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Wed, Jul 07 2010 20:56
by Tonus
Joined on Sun, Sep 27 2009, Posts 17
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!!!
Posted on Wed, Jul 07 2010 21:01
by Tonus
Joined on Sun, Sep 27 2009, Posts 17
Sorry - meant to add... I'm currently running VEP v4686 on all machines... Thanks T
Posted on Wed, Jul 07 2010 22:08
by Dietz
Joined on Tue, Aug 06 2002, Vienna / Europe, Posts 7763
Tonus wrote:
[...] 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
Posted on Sun, Jul 11 2010 06:23
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1838

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.

MacBook Pro 16,1: 2.3 GHz 8-core i9
64GB 2667MHz DDR4
Mac OS 11.6.1
VE Pro 7.1056, Cubase Pro 11.0.0
Posted on Sun, Jul 11 2010 11:14
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173
Tonus wrote:
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.

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Sun, Jul 11 2010 11:52
by Tonus
Joined on Sun, Sep 27 2009, Posts 17
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
Posted on Sun, Jul 11 2010 13:32
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173

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?

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Mon, Jul 12 2010 20:32
by Tonus
Joined on Sun, Sep 27 2009, Posts 17
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
Posted on Thu, Jul 15 2010 18:01
by info_9427
Joined on Thu, Nov 04 2004, Posts 57

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).

Posted on Fri, Jul 16 2010 07:01
by DG
Joined on Wed, May 12 2004, Posts 8608
info_9427 wrote:

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

Nuendo 6.03, 4.3
2 x Intel Xeon x5675 3.07GHz Hex Core
48GB RAM
Windows 7 (x64)Pro
RME Multiface II
Intensity
ATI HD5400 series graphics card
Posted on Fri, Jul 16 2010 13:34
by info_9427
Joined on Thu, Nov 04 2004, Posts 57

The save time for my template in Cubase is over a minute so I think that qualifies. Stick out tongue 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?

Posted on Sun, Jul 18 2010 14:45
by mahag
Joined on Thu, Dec 02 2004, Posts 69

 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?

Posted on Sun, Jul 18 2010 16:26
by Karel
Joined on Mon, Jan 19 2009, Belgium, Posts 2173

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.

Karel Bassez
Software Engineer
Vienna Symphonic Library
Posted on Thu, Jul 22 2010 18:53
by Tonus
Joined on Sun, Sep 27 2009, Posts 17
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

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.