I would, for one or two things. What BFD3 exposes to VE Pro is a single automap; which I edited to get objective names so that I don't have their hardwired eg., 'high tom 2' where in fact I put a cymbal there, so after a point it's all ''BFD3 ch(05) gain" etc and every preset may be different. I'm not going to edit their [xml] map over and over again, it's tedious.

Short of the user-determined name, I think you could lose "Vienna" in the string 'Vienna Synchron Player"; cf., "Kontakt" is just "Kontakt", not "Native Instruments Kontakt"

I use pencil fairly frequently for CC; I also use line and parabola. At this point I prefer to edit in Note Expression even if I'm not otherwise exploiting it, because it's more flexible than the lanes.

There are certain instruments which are made to exploit particular controllers (there is a trumpet for Kontakt recently developed) where it would be much easier to have the physical controller, though.

I would have to constantly refer to the automation map for the number of the parameter and try to make the parameter in Kontakt match or resemble it in order to rely on memory instead, if I could (itself unwieldy) because what Cubase had was really down to that in the end. Now that problem is gone. 

Originally Posted by: Daniel Stenning

[...] important that there's some way in VEP to have custom shorter names - aliases for use in the DAW in order to clearly see which parameter one is automating in the DAW

EG: Giant/Kontakt/Reso vol/The Giant. I can make the first and last as short as 'G'.

this is how it is in the automation map and in Cubase.

link to screenshot, new window:

string name, actual

Contact Martin Saletag. Ask him about custom string names.

Which version of VEP 7?

Really, "Vienna Ensemble Pro" shouldn't be in there.
Current project here has around 370 parameters (fr. Kontakt, VI Pro, Synchron Player, BFD3, LABS, Hybrid Reverb, Replika XT, ) and none has that in the string. I don't fully recall the first build of VEP 7, because it had such issues I couldn't use it, but it seems like it that was the first thing I noticed, that the old strings were just gone in favor of the actual exposed name.

I would contact support about this, that's not right. Attn M. Saletag.  Also this is who you want regarding what the string can or cannot be.

I don't have Una Corda, but Kontakt is Kontakt. I just saved an .nki as 'Bow' from '73 Stage Bowed' and while it took closing and reopening the Cubase project, it informs what the string is now. "4/73Bow/Kontakt5/Gliss Time/Bow".
I can determine '73Bow' (channel name) and 'Bow'  here.

The exception is midi, where the string starts with "VE Pro plugin/midi in_"

Yeah, it's all 7 here. The initial build basically would only be force-quit (albeit I never hung around to see it quit much_later) but the first update addressed that for me.

So the problem would seem to have more than one parent.

First of all, what you depict is just odd for VEP 7.

how it appears here

The beginning of the string "Vienna Ensemble Pro" is a thing of the past.
Here, the Kontakt instrument Thrill is represented in Cubase by "3", the number of the channel; THRILL, the name I gave to the channel; the automation name in Kontakt's Host Auto; & the name of the .nki. This I believe is the minimum communication from VEP to Host as coded. The person to verify this, btw, is Martin Saletag.

Whzt you CAN do in Kontakt is save the .nki as a very short name, and the name of the exposed parameter tends to be brief, eg., "Tine Level", and give the VEP channel a very short name.
So this exposed to Kontakt might be "73/Kontakt/Tine Level - 73".  Or compare my screenshot; to make it shorter I could change my channel name and/or the .nki name, the rest of it is de rigeur.

But again, VEP 7 at this point is revealing to Cubase what it has from the exposed parameters, and my understanding is it cannot be more minimized than this. Yours looks like VEP 6 days, though, I don't understand that unless it's down to an earlier Cubase.

Yeah, it's been the last two versions I've used on Mojave. Can you not go past 8.5 on that hardware?

hopefully so

cheers

I had this for a bit, it wasn't anything about focus. I reinstalled the OS (mojave) and it quit. Which may be coincidence.

I want to be clear, my hangs on render can't be related to loading or quitting issues, which both are very responsive here.

You have to have the slave version match the version you're connecting with anyway.

6 works on mojave

edit: now redundant

Whether it's additional (prob not redundant, not if I save the matrix) work or not, I don't necessarily agree with the default layout (I like non-vibrato as more primary) so I would tend to need to roll my own anyway.

It's not anything to model yours after. :D

I have certain basic notions of it, like one for shorts, one for performance legato and marcato, one for repetitiions.

But I might just build them ad hoc according to what I need. Not that they'd be incoherent but I'll end up with a 'shorts and dynamics' in two rows with CC1 to get the second row in matrix 2 while 1 is Performance legato +_ marcato. The thing is with me, I don't like to have a preset with a lot of stuff disabled (w. 10-12 cells, you know), I don't do 'whole' type of templates at any level, each piece is rather different, not generic.

aaaaand now it works right.
I uninstalled it and re-installed. 

1) VE Pro does not host AAX.

2) "If I load a VST version of Kontakt for exmple the AAX plugin in Pro Tools receives audio from the VST plugin"
VE Pro however does connect as an AAX plugin in Pro Tools.

This is how it works. No, there will be no difference in audio quality unless something is broken.

Yes, it's the same here. I have to adjust it anew every time.
This was supposed to have been fixed. It was true of VEP 6 for me though, at least in later iterations.

It may have begun with me with a new computer with a different screen size.

Yes, this is a feature of VEP the plugin; it has the host use it as an external device as well.
Something has to act as host anyway you cut it.

But, the problem is on your end, the instrument itself is quite reputable.

Pretty much impossible to diagnose directly from the info provided.

It could be as simple as your CC11 expression is way down and there's not enough energy to whereever its output is. It could be you are using the system's sound and it's garbage (you didn't say whether or  not all computer is like that; if it isn't, it narrows it down to this extent).

Chances are *not* high that it's the converters of a legit audio interface through itself.

The business end of the first video, as per drum maps functionality is that it uses the paradigm of Input for the Keyswitch naming and the Output to the instrument; "I/O". Drum maps traditionally can re-map the input - with no alteration - to whatever note name by specifying that in the 'O'. This is probably why drum maps are employed for this, at least as a beginning.

You have a picture of the drum map going to VE Pro Port 5 channel 5 and a picture of Kontakt assigned to channel 2. 

Port in VE Pro is meaningful when you have more than one specified in Preferences. If you do not use the VST 3 VE Pro or one of the workarounds for Logic or other hosts, you have one port, Port 1. It looks like the Kontakt Cello is Port 1 Channel 2 (there appears no Port designation); so if you intend the KS from the Drum Map thingy to communicate to that instance that's your target.

Ok, that is interesting. My drum maps from BFD3 import to Cubase in a way to show exactly what the note numbers trigger, I suppose I could make one do that, never thought to.


"how DM work to actualy change the articulations without placing a midi keyswitch note on the same track as the midi music." 

Just so long as it's on the right channel.  I don't get why having it on the same track is a big problem, I guess. I definitely want it on the MIDI track instead of having to refer to someting else. 
I meant same channel, it can be on a different *track* on that same channel.

I don't know what the question was except 'VE Pro templates' for third party instruments. I wouldn't know. The Kontakt Factory Library VSL Demos follow the usual as I described, in that limited scope of the thing.