Vienna Symphonic Library Forum
Forum Statistics

199,382 users have contributed to 43,163 threads and 258,951 posts.

In the past 24 hours, we have 2 new thread(s), 10 new post(s) and 67 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Are they VST2 or VST3's

  • Are they VST2 or VST3's

    G
    G
    I am using VEP5 to host my NI Komplete9 VSTi's, and have recently had a glitch I need to resolve regarding MIDI Program Change. Within VEP5, I have a large Kontakt5 Multi of instrument banks, and they receive and respond just fine to the MIDI program change commands I send them. Within the same instance of VEP5, I also have occurrences of Massive, FM8, Absynth, etc., but while they receive the program changes (the selected preset in the browser moves appropriately) they unfortunately do NOT respond to MIDI program change. The sounds aren't changing along with the MIDI program change.This is a big problem for me. I know VST3 plugins have an entirely different way of working, but VST2 plugins respond to program changes as I expect them to. Unfortunately, in my instance of VEP5, there is no differentiation between VST2 and VST3 plugins. From Cubase on the main system, I have chosen the VST2 version of VEP5, so that "should" mean it is the VST2 plugins. I recently had to downgrade my version of Cubase, because there are known issues with this, but even de-installing (with AppTrap) and re-installing Cubase didn't fix it. I'm at a loss, need some assistance, and look forward to getting this resolved. Thanks, Glennzone
  • civilization 3C
    civilization 3C

    VE Pro does not support VST3 plugins anyway. No, the NI plugins are not VST3.
  • G
    G
    I appreciate your response, which certainly answers the question in the subject line. Thank you. So moving on from there, the problem still remains how to get program change commands working not only on Kontakt, but also on the other Komplete9 VSTi's. It was working fine for about a year. I'm using Cubase Elements 7 as the host, and I just backrev'ed to v7.0.6. I used AppTrap to perform the full de-install, re-installed v7.0.6, and the problem is still there. It's quite annoying. If anyone has any insights into how to resolve this I would appreciate those responses even more. Thanks, Glennzone