I am having issues with automation when using Smart controls to VEP 7 Automation. I had set up automation in VEP 6 that worked very well but has run into stumbling blocks with VEP 7. I have lemur controls that link with Smart Controls and the Smart Controls link with VEP 7 automation of 8 to 15 mics (mostly with Spitfire plugins). With Kontakt 6, I can change the actual mic volumes from lemur thru Logic Smart Controls, however the Logic Smart Controls with their feedback do not respond with visual change of the mic decimal until 1 min or so later. For some reason the Range Min and Range Max freeze on to the actual decimal at the original connection. When I alter the volume, the Kontakt Instance in VEP 7 responds to the change but as I said the feedback does not. Then after a min or so the Smart Control resets to the new value. With the Range Min and Range Max locked to the new percentage value (not decimal display). That is something new for VEP 7, In VEP 6 the Smart Control display is a O to 1 Range Min and Range Max and the control displays the value in decimal. In VEP 7, the Smart Control display is not decimal but actually Percentage. Also in VEP 7, I cannot access Kontakt 5 automation settings, when I try to use Kontakt 5 rather than Kontakt 6. Since the automation in VEP 6 worked without issues, This appears to be a bug in VEP 7.
-
VEP 7 Automation Feedback failing, Logic Pro X, Kontakt 5 and 6
-
It's not just Kontakt, there are problems of agreement of values between BFD3 & VSL Synchron and Cubase that aren't trivial. EG: 0dB in Synchron mixers are 0.2 in Cubase. All the values are fairly coarse.
I had some back-and-forth with M. Saletag of VSL but he was saying there are limits to what can even be done.
In VEP 6 I had very fine control and the correspondence was good, I could type in finer values which stuck; now this is impossible for about anything and in certain cases the result in the Status Line jumps to 100%. Long story short, the way VEP 7 reports the exact automation parameter name sacrifices a number of correct behaviors, primary of which for me is determining precise values manually/typing. Kontakt, 5 or 6, is the worst of these. I don't know enough about programming to fully understand his statements.
-
EG: 0dB in Synchron mixers are 0.2 in Cubase. All the values are fairly coarse.
and here, inconsistent, appearing to depend on where the fader or control was when I instantiated automation.
-
While I haven't seen his explanation, I would hope that they would offer preferences that would allow functionality to be altered so that users could adjust the desired protocols based on their need. After having spent so much programming time to get the automation working between Logic, Kontakt and VEP 6 and now to have it broken and extremely crippled is a great disappointment. I do like the added features of VEP 7 but I spent a great deal of time programming the automation to enable the necessary workflow I needed and now to have it so crippled with no attempt at a solution makes me reconsider my approach to continue with VEPro if there is no solution..
-
No, he didn't offer any such thing, it is what it is. That said, I got him to take a close look at particularly BFD3 and the compromise there for me is just coarser values; in that the mixer parameters are represented by percentages now vs abstract representations, I can work around it. 100 values now from -infin to whatever its max is (-infin to 0dB is 0-80%). Kontakt is still kind of broken as I cannot manually do anything, the Status Line value vs a fixed arbitrary value in the Inspector, so it's too much a crapshoot.
Contact support, attn Saletag if you want to hear his explanations.