I have a problem with VEPro 7.2.1516, where disabling channels will only disable VST2 plugins, but VST3 plugins will stay active.
Anyone else encountering the same thing or is it on my end?
178,940 users have contributed to 42,069 threads and 253,948 posts.
In the past 24 hours, we have 3 new thread(s), 20 new post(s) and 60 new user(s).
Yes that's right!!!
I have the same experience. And this is a Major Prio. For example, when you create a Kontakt VST2 instrument, you will see the memory increase in the Windows task manager. As soon as you turn off the instrument, you will see the memory decrease in the Windows task manager. If you do the same procedure for a Kontakt VST3 instrument, the memory in the windows task manager will remain unchanged. This is very annoying for the efficient use of memory. I myself use midi controller automation to turn instruments on and off and this is also a great feature in Vienna Ensemble Pro 7. I hope that VSL solves this problem soon. Hope to hear from you Paul? Because I will continue to support your excellent products!
Thank you for the quick response.
Do you have a rough timescale as to when the next release will be? I am using Blue Cat Audio Patchwork as a workaround as I use a large disabled template to host my sample libraries. But would love to have VEP Pro working "properly".
Thanks for sending the links to the beta, I managed to spend a couple of hours with 7.2.1526. All works effortlessly. I have attached a clip showing the disable/enable functionality on a Kontakt 7 plugin with 4 associated mixer channels.
I am using a cc message button on composer tools pro to trigger the enable/disable function on VE Pro via the midi controllers on the automation panel. VEP is running on 2 (master and slave) PC's.
More than happy.....😃