Paul I have the latest drivers on both the main Daw (MOTU) and the slave machine (things have been running perfect on Vienna inst in Vstack for over a year).  One thing I just noticed is that when I open a new instance of VE - it shows on the lower left corner the latency of 1024.  That card on the that machine is set to 256 but the VE shows 1024??  Give any hints.

Installed the new VE on a second machine and get the same latency (1024) with that PC's card set also to 256???

I'll try a third (out of four of the slaves).

Rob 

Rob,

I've installed VE on one of my slave machines and it's working fine so far. My soundcard on the slave is a Wavecenter PCI sending back lightpipe to the main DAW (using MOTU 2408 mk 3, running under Sonar) -- buffer size on the Wavecenter card is 128 samples. I left the VSL Latency Configurer to 0 and set the latency to 'default' in the VE preferences. Anyway, everything seems to be working fine so far. If you want to know more tech particulars, just ask.

Mahlon

p.s. Vienna folks, thanks SOOOO much for the new interface, It's awesome and I'm already hooked on it. So easy to use!![:D]

Thanks - I'll try to set the slave to 128 and the preferences to default.   Thanks.

Rob 

 Very strange behavior.  What are you guys seeing as far as latency (lower left hand corner of the VE?)  On the slaves - seems like no matter what I do that stays at 1024 on the slaves and 512 on the Main Daw (running with C4.1)

I'll keep fiddling but I really need to get back on this project (have to go back to Vstack until this job is done I think.)  Interface looks very cool - really want to get this going.

Rob

(one of my slaves has 52/96 RME, one has pci Wave center and two have gina 24's - all seem to behave the same.  Delayed latency of at least 1024) 

That is wierd. I'm showing 128 samples in the left lower corner. All of my slaves have wavecenter pci's so I can't try it with a different card. In Sonar, I have the MOTU drivers set to 256 samples. I'm running Windows XP (SP2) on all machines. I'm sure you'll get it solved, and I hope you do, because it is really a convenient bit of software! The only glitch so far has been when I tried to open another instance of VE -- complete crash and automatic reboot.... haven't tried to do it again. I'll approach that gingerly after I've messed about with VE for a while....

Mahlon

 Thanks Mahlon for the reply.  Yea nothing I do seems to get this sorted out.  I am pretty close to waiting on this new software for a couple weeks until I can get done with current project and get this sorted out.   One of my clave PCs acts very strangely running VE in stand alone (CPU runs at 100% - lower right hand corner - with no instruments loaded.)  VE looks great my maybe not ready for prime time on my systems.  I'll keep tinkering as long as I can.

Rob 

 OK - the 'RME' slave is still haing problems.

When I go to 'preferences' and assigned the known ADAT out - an error message comes up the says ..."Device already allocated"

Any ideas?

Rob 

 AH success!!!!!!  I discovered that the ADAT output (that I used for Vstack) just gave me fits and then selected the ASIO 95/52 general out --- and VERY important --- let both settings in preferences to DEF!!!!!!!!

That combination and this is working.   One down - three PC Slaves to go!!!!!!

---This is some nice software VSL!!!!!!

Rob 

Congrat's!

Mahlon

Hey Rob (and others), I finally have a bit of time to try to move over to VE…  I’m having the exact same latency issue on my slave machine as you describe here.  (MOTU buffer set to 128… VE showing 2560).  Was there any resolution?  Maybe some setting I’m missing?  Vstack on the same machine (at the same time) is lightning fast.

Thanks!

Scott

Hello Scott,

this was a bug that was fixed with the latest version of the Vienna Ensemble. Please make sure that you are using the latest update of the VE.

Best,

Paul

Thanks for the quick reply Paul.  I have the latest version of VE (2.0.2781) running in standalone.  The latency on the lower left of the screen (2560) doesn’t match my MOTU buffer setting (128) – not sure if this is a problem or not, there was just some similar discussion earlier in this thread.  My problem is that the response of VE is very sluggish (unusable), even with the smallest MOTU buffer setting.  Vstack on this same machine is super quick.  I was hoping I was missing some sort of latency setting within VE.

Thanks again.

XP pro, P4 3.2

Hi Scott,

which Service Pack are you using with XP? Are you using VSTack and VE at the same time? What happens when you insert VE into your VSTack, as a VST instrument?

Let me know about your findings!

Best,

Paul 

Confirmed - latest build has fixed the issue (running VE within C4) 

Hi Scott,

the Vienna Ensemble should not cause any troubles used as a standalone instrument - that is the basic intention of this software.

Did you try to change the latency of your soundcard BEFORE launching just the Vienna Ensemble?

Best,

Paul 

Just tried it now – no change.  Looks like I won’t be leaving VSTack just yet…  I don’t know what the problem could be. Thanks for your help.

Scott