Vienna Symphonic Library Forum
Forum Statistics

194,143 users have contributed to 42,912 threads and 257,925 posts.

In the past 24 hours, we have 1 new thread(s), 13 new post(s) and 80 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. VST3 Program Change Limitation

  • VST3 Program Change Limitation

    K
    K

    It's a real bummer that the VST3 plugin does not passthrough Program Change data. That would have been nice. Not quite ready to kick the Giga Machines to the curb. I hope that will be implemented at some point.
  • S
    S
    Does the AU Version transfer program change data (to lets say kontakt instances with many Programs in a Bank) ? I assumed it would!! That would be the only workaround I can actually see for the 16 Midi-Channels per Instance and 8 VE-Pro-Instances (128 Midi-Channel) Limit for AU. (For Au its obviously less of a luxus feature than for vst3 at least generally)
  • D
    D

     The VST2 version works with program changes though, so try that out.

    DG
  • S
    S
    And the AU Verison =/ ? . . .
  • D
    D
    last edited
    last edited

    @scorefrog said:

    And the AU Verison =/ ? . . .
     

    Don't know. Try it.

    DG
  • S
    S
    oh yeah thanks! I can't unfortunateley try the demo version because of having no elicenser key ... (Am still struggling with buyning cubase and leave my so much loved Logic Template with all the cool Space Designer Reverb Settings and EXSes)
  • D
    D
    last edited
    last edited

    @scorefrog said:

    oh yeah thanks! I can't unfortunateley try the demo version because of having no elicenser key ... (Am still struggling with buyning cubase and leave my so much loved Logic Template with all the cool Space Designer Reverb Settings and EXSes)
     

    If you are definitely buying Cubase, then you can use that dongle. if not, then you have to stump up for the dongle separately.

    The Cubase reverb is every bit as good (and some say better) as Space Designer, and there are other compensations, like being able to use multi-timbral instruments, VST3, stereo panning and advanced MIDI features. the downside is that you will have to build anything but the MIDI side of your template from scratch. However, any VSL stuff can be stored in the vi-frame format, so that should save time.

    It would also be a good idea to transfer the EXS stuff to Kontakt, because then you can use it with any sequencer and on any platform.

    DG
  • S
    S
    What a luck Steinberg kept on supporting OSX (after that break years ago)) Many Thanks DG! You convinced me! (=
  • D
    D
    last edited
    last edited

    @scorefrog said:

    What a luck Steinberg kept on supporting OSX (after that break years ago)) Many Thanks DG! You convinced me! (=
     

    I also have heard (but not checked) that after all those years without, there is now a Cubase demo. I'll check that up for you.

    DG
  • S
    S
    Oh great, but I used to be a Cubase User for many years anyway until I changed to Logic (1997 or so) when Cubase was no option for a Mac and ... wow the years passed by quickly and its time to go back to the roots (-; Thx
  • B
    B

    Hi Martin.  Loving VEP thus far.  It's a relief to move on from FXT.

    I'm wondering if you have made any progress implementing program changes for the VST3 version of VEP, or is this simply a limitation of the VST3 spec and a change that we're unlikely to see in the next update?

    Thanks - Brett
  • K
    K

    Same here. Hope that will be implemented...
  • M
    M

    The next update will not include this, we have to make some research to see if it is even possible. The VST3 standard has simply removed the common MIDI program changes, in favor of a new patch selection system.
  • K
    K

    how about a CC# to PC conversion within VEPro to work around that?