sleepfacingwest
New Member
Hey all,
I hope this is the right place to post this. My issue isn't with Kontakt per se, but it's the only place that seemed to specialize in scripting. This is an issue getting automation data to go to the correct place using Logic Pro, VEP, articulation sets, and logic scripting.
Setup: Logic Pro X on mac master, Vienna Ensemble Pro 7 on PC Slave running all my instruments.
I've managed to simplify large templates in Logic pretty heavily by making use of articulation sets and Vienna Ensemble Pro. For example, I can set up all my violin I articulations in one frame in VEP, then use articulation sets to seamlessly switch between articulations from a single track in Logic. After doing some digging, I discovered that VEP uses CC99 to route signals to various ports. This means instead of being limited to 16 VEP articulations, I can conceivably have 2,032 per track (127*16). Before this, I had to have 4 frames in VEP setup to house my 64 articulations just for Violin I. Now I can stick them all in a single frame. Total game changer!
Logic has a weird tendency to send cc99=0 somewhat randomly, so the best way I could make sure articulations got to the right port/channel was to write a script to send a cc99 message before every single note was triggered. This made sure that no matter what weird stuff Logic was doing, the note data got sent to the right place. Works like a charm! The problem is when I try to use this same technique to send controller automation data. The same technique works in theory/on small scale, but in the context of a large template, sending something like modwheel automation bogs things down pretty heavily and I get clicky/glitchy playback. I'm guessing this is because it's sending so much CC99 data when a parameter is being changed continuously.
I just want to get the automation data to get routed to the same instrument that is currently playing. (I've heard this called articulation chasing). It's a tough thing to google since the logic+articulation set+VEP setup is so specific, but I'm hoping some people here have tried to tackle the same problem. Anyone have any links they can provide to educational resources?
For what it's worth, I've tried Ski Switcher, artzid, and the vienna ensemble pro environment window setup. None of them have the flexibility I'm looking for. This DIY approach is the closest I've gotten, but the automation issue is a pretty huge snag at the moment.
I hope this is the right place to post this. My issue isn't with Kontakt per se, but it's the only place that seemed to specialize in scripting. This is an issue getting automation data to go to the correct place using Logic Pro, VEP, articulation sets, and logic scripting.
Setup: Logic Pro X on mac master, Vienna Ensemble Pro 7 on PC Slave running all my instruments.
I've managed to simplify large templates in Logic pretty heavily by making use of articulation sets and Vienna Ensemble Pro. For example, I can set up all my violin I articulations in one frame in VEP, then use articulation sets to seamlessly switch between articulations from a single track in Logic. After doing some digging, I discovered that VEP uses CC99 to route signals to various ports. This means instead of being limited to 16 VEP articulations, I can conceivably have 2,032 per track (127*16). Before this, I had to have 4 frames in VEP setup to house my 64 articulations just for Violin I. Now I can stick them all in a single frame. Total game changer!
Logic has a weird tendency to send cc99=0 somewhat randomly, so the best way I could make sure articulations got to the right port/channel was to write a script to send a cc99 message before every single note was triggered. This made sure that no matter what weird stuff Logic was doing, the note data got sent to the right place. Works like a charm! The problem is when I try to use this same technique to send controller automation data. The same technique works in theory/on small scale, but in the context of a large template, sending something like modwheel automation bogs things down pretty heavily and I get clicky/glitchy playback. I'm guessing this is because it's sending so much CC99 data when a parameter is being changed continuously.
I just want to get the automation data to get routed to the same instrument that is currently playing. (I've heard this called articulation chasing). It's a tough thing to google since the logic+articulation set+VEP setup is so specific, but I'm hoping some people here have tried to tackle the same problem. Anyone have any links they can provide to educational resources?
For what it's worth, I've tried Ski Switcher, artzid, and the vienna ensemble pro environment window setup. None of them have the flexibility I'm looking for. This DIY approach is the closest I've gotten, but the automation issue is a pretty huge snag at the moment.
