@Eric Bettens said:
If I use separate VEP in Logic Pro ( 1 sound / VEP) linked to 1 instance in VEP, I can use my Logic Mixer, routing, ...
But if I use multi instrument ( VEP multi or PRO AU3), when I make a volume automation on one track, it affect all the volume of the same multi instrument).
So just to elaborate a bit more on what Paul said.. In logicPro, when you use multi-timbral tracks...the "volume" automation on each track is basically trying to control the mixer fader in LogicPro of the VePro.AU3 instrument. There is only one mixer fader for the entire VePro.AU3 plugin. In fact if you put volume automation onto a couple of multi-timbral tracks...if you put, for example, volume ramps in opposite directions, you can watch LogicPro's mixer fader bounce all over the place as the volume automation from two tracks is merged to one mixer fader in LogicPro.
So basically don't use the "volume" automation in LogicPro in this situation.
You will also notice in the automation popup menu you can select parameters corresponding to the VePro.AU3 plugin. By default they are named as "Param1", "Param2", etc..
So then you have to go into VePro7's automation mapping feature and map those to exactly what you want to happen inside the VePro Instance. You can map them to many different things, including VePro's mixer faders, or to plugin parameters within each channel strip, or to midi controller's, etc. Whatever you want. And you can name them appropriately..and then they will show up later in LogicPro's pop up menu with the name you specified, so that you can pick the right one to use on each of your multi-timbral tracks to automate whatever thing you want to automate within VePro.
Just remember that when using Multi-timbral tracks in LogicPro, all the tracks are sharing one multi-timbral plugin (in this case its VePro.AU3). So each of those LPX tracks will show the shared list of parameters as you specify in that VePro instance automation mapping... its then up to you to make sure each track in LPX will choose the right parameter to automate that will be mapped to the correct thing inside the VePro instance...