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.

having your generated audio on another drive is actually traditional.

the difference in running a sizable project in Cubase vs VE Pro can be enormous.

I was running like 7 Synchron Players in the latest project. but it took all 4 buffers on the VEP side.

Even as VSL informs us this can't happen, I had such issues with the initial build of 7 I had to rollback for a couple, three days. And I had saved a VEP 7 version of the current project; which did load and work except for where I had instantiated included Vienna Suite Pro internal instances to replace the old which of course did not. Since the official line is no, I wouldn't count on it but it did here.

No, he didn't offer any such thing, it is what it is. That said, I got him to take a close look at particularly BFD3 and the compromise there for me is just coarser values; in that the mixer parameters are represented by percentages now vs abstract representations, I can work around it. 100 values now from -infin to whatever its max is (-infin to 0dB is 0-80%). Kontakt is still kind of broken as I cannot manually do anything, the Status Line value vs a fixed arbitrary value in the Inspector, so it's too much a crapshoot.

Contact support, attn Saletag if you want to hear his explanations.

Originally Posted by: civilization 3

EG: 0dB in Synchron mixers are 0.2 in Cubase. All the values are fairly coarse.

and here, inconsistent, appearing to depend on where the fader or control was when I instantiated automation.

It's not just Kontakt, there are problems of agreement of values between BFD3 & VSL Synchron and Cubase that aren't trivial. EG: 0dB in Synchron mixers are 0.2 in Cubase. All the values are fairly coarse.

I had some back-and-forth with M. Saletag of VSL but he was saying there are limits to what can even be done.

In VEP 6 I had very fine control and the correspondence was good, I could type in finer values which stuck; now this is impossible for about anything and in certain cases the result in the Status Line jumps to 100%. Long story short, the way VEP 7 reports the exact automation parameter name sacrifices a number of correct behaviors, primary of which for me is determining precise values manually/typing. Kontakt, 5 or 6, is the worst of these. I don't know enough about programming to fully understand his statements.

IE: VE Pro will not be seen as an effect; VE Pro Audio Input will.

I don't use DP but here's the look fr. Cubase (link to picture opens in new window/tab:

instantiating AI

(add FX track (I named it 'AI for send'); connect to extant instance.)

Then: 

insert input

there it is

Here, it's assigned (default) to the master bus, which is my reverb target in that project. Now you can do whatever, in the normal mix paradigm.

For the return to DAW, it's down to the output assignment in that instance of VEP.

External Device means a real-time render or it doesn't print. (unless DP is that different)

Can't get DP to see the metafiles on the other computer, and when I create a new one, the effect sends do not see the file as a possible input

If I'm following you, it seems you're expecting 'Vienna Ensemble Pro' in the DP mixer to appear as a send target.    

VE Pro is not quite following that normal FX paradigm, simple send. The DAW will not see VE Pro itself as a send target, it's an instrument. (Also note that it's essentially an external device for this.)

What you do is instantiate Audio Input (seems like I was doing this in VEP 5, I don't 100% remember) as the effect and connect that to an established instance of VE Pro, to input channels there (not channel input, input input).
That's VSL's workaround for it not being an actual Effect, the Audio Input version.

Originally Posted by: Bela75002

Could it be a Real Time Audio Performance Problem like in this video  : https://youtu.be/GUsLLEkswzE ?

I should add I have many hard drives through a hub, but my Cubase sessions are on an external drive directly linked at the back of the iMac, just like the SSD drive with the VSL samples.

In case it would be of interest, I also have linked two more screens through the thunderbolt ports at the back of the computer.

2) many hard drives through a hub - many? For what purpose? I wouldn't run samples through a drive connected via a hub and expect great performance. Once upon a time it was considered de rigeur to use a drive other than the system drive for recording, for handling audio in the pool, on top of streaming samples. SSD obviates all of that.

"many" drives + "hub" (eg., USB 2) are things you want to look at. It's not that you don't have enough power to run the impulses in Synchron and need to cut it way down.

So, yes, what he says in the video is true, it's some device locking the process up.

Well, that's good, because string sections built from 'individuals' is unworkable in samples anyway.

You can optimize all of VSL in VE Pro (only what's used is called upon once learned) to conserve RAM.