Heh, your fantasy goes beyond the truth. There are quite a lot Logic users (not AG users) who contacted me to ask why their Logic templates (which contain some custom Environments) crash after the LPX 10.4.4 releases.You are misrepresenting the situation in order to try to sell your software.
The Mutli Timbral Channel Strips you create and map to different VEP Ports are Environment objects!ok, but AU3 VEP is not using custom environment templates.
Yes, the upcoming "AG VEP Multi Instance" will offer 8192 MIDI Channels per VEP Instance with AU3 8 Ports which is much more than 127 tracks. I could add much more but I guess 8192 tracks is quite enough.Ivan perhaps your system provides more then 127 tracks per vep instance and that could be a valid selling point but it is misinformation to say that AU3 is broken.
So your source tracks should not be set to ALL, they should be set to Port 1, channel 1 and port 2, channel 1, respectively.. something like that.
when you create the VEP AU3 track to get started, its easier if you click the multi-timbral checkbox and select two parts in this case. That will make sure the actual tracks do NOT have the midi channel set to ALL. But you'll need to adjust the ports and channels as you desire.
Then you put an articulation set on each of those source tracks...and while hte articulation set only allows you to specify a channel each each articulation ID, it will funnel all its activity through whichever port you have that track assigned to.