SJ_Digriz wrote: jancivil wrote: SJ_Digriz wrote: Sampleconstruct wrote:
SJ_Digriz wrote: But, it would be nice if the CC assignment for macros was saved with the patch as an option.
You can hard-wire CCs in the modulation assignment, that way they will be saved with the patch (in opposition to assigning CCs to Macros via right click).
It's not life/death.
And, since I work primarily in Cubase and VEP, doing automation mapping to my controller has not been a huge issue, other than the macro configurations being slightly annoying.
So it exposes all automatable parameters to VE Pro?
Like ED said, you use the host mapper function of VEP.
actually "first need to decide which parameters will be exposed to the host" was his statement. Which afaic didn't answer the question. So_I_asked.
In VE Pro, you open the map and the list of [exposed] parameters (in things I worked with so far, that means all of them) appears in the assignment slot for 'Parameter x (or MIDI channel x/channel x). So it appears they are all exposed to VE Pro. I do not have to decide which ones are exposed to it. I don't know what Cubase does for instance, except it gives a list of 'Parameter 1 through... 256' maybe.