a stable network for this purpose requires a static IP; I can't help you with Windows system however

You don't need to reserve threads for the DAW, btw.

Technically the most efficient is one instance.

I don't use all those return channels, which is a bear to CPU.
I could actually do with one. I use several instances because I would be approaching the max number of automation parameters, and in Cubase all of that in one instance is unwieldy, with say 4 I can hide 3 and focus on the one.

The reason I do more than one stereo returning is I tend to mixdown a master bus with reverb separately but at the same time. I don't have a need to return 16 or whatever stems, I mix in VE Pro with automation, rarely touching even the volume of the instrument channel.

Your user name/Library/Application Support/Vienna Ensemble Pro

You may have to unhide this directory.

I did a trial of it as well. I did it in order to get nested tuplets. Which is quite broken, easily *the* worst experience I've ever had with music or audio-related software, I never got one measure done. To be fair, it was in a polyphonic framework but inside a single part it could not be accomplished in that setup. It was kind of shocking, as I was able to do this in Finale years and years ago.

I didn't have a problem understanding anything, it's just bug-ridden for this. Caveat emptor.

As of build 921, no internal VS Pro -edit: Equalizer- factory preset will load and prior settings appear to be lost across the board. Had to uninstall and roll back. This is particulary bad as I had saved over and even in the prev. build these settings were now gone.

if it isn't, ensure Sys Preferences/Security/Automation has VE Pro controlling system events.

Cubase has a preference "Never reset chased controllers".

be sure both elicenser and VEP are set to control the computer. In Sys Preferences, Security and Privacy/Privacy, Accessibility, Allow These Apps...

Keyswitches can be 'chased', which you should google rather than rely my writing ;)
If you do not have the first KS before your first note in the sequence, it could still be seeing a later one and give you that indicated articulation, 'normally'. 

They are 'latched' but any new KS, accident or what-have-you conveys via the connection; you could try writing the KS note as a long sustain throughout and see if that obviates what you describe,

Well, in the meantime see if your DAW has a reset on stop preference you can select.
I agree with the use value of such btw.

. They are strictly from midi, so look to the midi tab in the Automation map.

Sehr cool how installation and activation is all one process now.

If you mean the send is from an instrument channel generated by you playing, the fact it involves an instrument would include that latency, vs. an audio track. IE., a project with only audio would tend to behave quite more snappy than a full-on midi arrangement. 

Just set Cubase preferences for automatic latency compensation and forget about it, VEP is perhaps the very best at that.

Originally Posted by: lahatte

I should have been more clear... I want to use my plugins, not VSL plugins, in VE Pro and see them show up as sends and/or inserts that I can choose in Cubase. So far I have not seen anything show up in my sends in Cubase.

Yeah, VE Pro is an instrument plugin, not an effect plugin as far as the DAW is concerned.
"So far I have not seen anything show up in my sends in Cubase." - you won't.

With the exception, the addition known as Audio Input, which is _the_ way you can send to it (as though an FX rack).

[connect to VE Pro and] add FX Track in Cubase and insert VE Pro Audio Input. Connect to it via its popup, which appears pretty much as VEP does in the VST Rack. Instantiate an Input channel/Input in VEP and make that correspond. It returns to Cubase as per that instance of VEP. You can send Audio or Instrument Channel out to it. Not as an insert directly on that channel but inserted on the FX Track and sent to. Now, this is an external device to Cubase so when you go to print the result you want Realtime Export (otherwise it prints nothing).

it varies a lot. latest project a couple hundred channels. a fair no. of FX. If it's more than a few instruments for me VEP is going to tell on Cubase. One thing is a decoupled server vs Cubase loading it with all it already has on its plate, the separation of processes.... I noticed it in a big way the first time, I had a modest Kontakt multi kind of maxing me out already (Cubase 5.5.3). I do it all on the one internal drive, it seems to me the old ways are not needed today.

weird

good to know

The new instance with freshly created automation shows at once using VST3 here

It really means you lack the drive space; the installation needs more space than is finally used.

Originally Posted by: lahatte

I can't find a manual for VE Pro 7. I need to know how to use plugins, like reverb, etc., in VE Pro 7. 

I want to be able to have the plugins to be seen by my DAW as send effects, hosted in the VE Pro server.

Is that possible?

Using FX in VE Pro isn't any different than normal paradigms, insert, create send buses etc.

VE Pro works as an FX rack via the Audio Input feature of the VST3 version, so yes insofar as that goes.

Originally Posted by: lahatte

I would like to hear from those that have used VE Pro on the same computer as the DAW. Did you find that performance improved by being able to move plugins and instruments out of the DAW and access them via VE Pro?

Yes, dramatically better performing. I've done it Local Host for 6 or 7 yrs. I have done with the more powerful of two machines as slave, and when I abandoned that I didn't see a real difference I could tell. It wasn't enough for a massive fully detailed symphonic project without a lot of rendering anyway. I think having slaves pays for itself at that point, but for me one (8-core 24GB) slave vs the same as Local Host wasn't the difference for me.

The only way VE Pro appears as an effect is VE Pro Audio Input; the send/return paradigm doesn't apply to regular VE Pro, it's an instrument only.