Question - do you see better CPU performance from VEpro 6 to VEpro 7?
This must be only a Mac related and also the graphics related on the Mac,There is definitely some performance difference with VEP7 compared to VEP6 on the mac. VEP7 is improved substantially, but only if you are on Mojave (or possibly High Sierra). When I first upgraded to VEP7 I was on Sierra and performance was worse then VEP6. I complained about it on the internet and ended up working closely with Martin at VSL to figure it out. We both ran tests on our systems and he even made some improvements to VEP7 that made it even faster, but in the end, we decided that I needed to upgrade to Mojave and when I did VEP7 out performed VEP6. The difference was particularly noted when the GUI was open (as opposed to being minimized), so the difference was not related to DSP, it was more related to OSX and graphics, etc.. It seems that VEP7 makes use of Metal and stuff that you need to be on Mojave to take advantage of, and if you aren't its a little slower. This is primarily related to a third party GUI development library that VEP is using, which has added performance improvements that take advantage of OSX Mojave, unfortunately at the expense of being a little more sluggish on older OSX. Its not a big difference, but a little bit yes.
I should add also that my system is using HiDPI on the monitor (ie, Retina display) which may have also contributed to the results in some way.
using cubase 10 VEpro 7 and PC and no automation issues in Kontakt 5. i would if i was you rig up a quick new test project and try it in that , it may be a time wasting but at least you can rule out an existing project issue you may hove glitched out because of your project from VEpro 6 into 7 just a guessanyone else had, and/or , resolved automation issues with VEP 7, Kontakt 6 and Logic Pro X?
I am thankful to report that the update today on VEP 7 has solved some of my big issues. Now I get a proper Smart Control "feedback" with Percentage in Logic Pro X when connecting to Kontakt and also Logic X Track automation of VEP 7 mapped parameters works again. There is still an issue with not being able to alter the Range Min and Range Max on the Smart Controls but it seems I can still alter the actual value of the control beyond the limits of the Range Min and Range Max values. I can live with this faulty functionality but the one remaining big issue that is very important to my workflow is that VEP Parameters in a VEP instance can only be mapped to one item or control in the VEP 7 instance. As I mentioned earlier, I was able to map one parameter to multiple controls in multiple instrument channels in VEP 6.Thanks for the reply. I have built a temp test with just one track. I think the problem is the combination with Logic Pro x smart controls and the interplay with kontakt. Here is a picture of the Smart Control in a new Logic Pro Project. I have Lemur mapped to the Smart Control also. Again this worked in VEP 6. View attachment 22495
I Just update in VEP 7 (cubase 10 windows 64 64gb ram), VEP 7 is sluggish when I connect the instances. Furthermore is slower when loading the instances at the beginning (disable all tracks) . Well I will downgrade to VEP 6, was much faster. Thanks . I thought that they have fixed already but no..For those of you who've taken the plunge, how are you finding VEP 7 a few months since the initial release? how is the performance and stability (especially compared to VEP 6 ?) Are you comfortable using VEP 7 on major projects ?
Ive been holding off on upgrading until things settle and most of the kinks have been worked out. Should I take the plunge?
I'm currently on a Mac running Logic Pro with a PC slave and VEP 6 running Win. 7