Vienna Symphonic Library Forum
Forum Statistics

182,299 users have contributed to 42,217 threads and 254,750 posts.

In the past 24 hours, we have 3 new thread(s), 16 new post(s) and 43 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Kontakt inside VEPRo - patch changes?

  • Kontakt inside VEPRo - patch changes?

    B
    B

    Has anybody here had experience using Kontakt (v. 5) inside VEPro? I have a project where I had some VSL instruments in VEPro and some others running in Kontakt. Running Kontakt in Digital Performer outside of VEPro is OK, but when I tried running it as a plugin within VE Pro, using the same sequence and the same multis in Kontakt, the instrument banks in Kontakt no longer reacted to patch changes. It,s as though VEPro is filtering them out. 

    Ideas?

    Thanks in advance,

    Alan
  • B
    B

    Are you using VST3.  VST3 does not respond to patch change.  VST2 does.  Why Steinberg deleted this feature from VST3 is beyond me.
  • D
    D
    last edited
    last edited

    @Babe said:

    Are you using VST3.  VST3 does not respond to patch change.  VST2 does.  Why Steinberg deleted this feature from VST3 is beyond me.

    VST3 uses Program Lists, not Program Changes. It's just unfortunate that Native Instruments (and VSL for that matter) have been unable to code a VST3 version of their sample player. If they did, this would be a non issue.

    DG
  • B
    B

    Thank you both for your replies. :-)

    What I don't understand is why the patch changes work ok when I run Kontakt directly in Digital Performer, but not when I run it inside VEPro (running inside DP). I am talking about the same sequence and the same exact same multi in Kontakt.

    Is there a way to solve this inside VEPro, or is it not possible to use Konkakt instrument banks at all that way?

    Thanks again.  :-)
  • D
    D

    When you run it through VEP it is going through a VST3 connector. If you want to use Program changes, use the VST2 connector instead.

    DG
  • B
    B

    Thanks! :-)

    Can you tell me where in VEPro I can specify that?
  • D
    D

    It's not in VEP, it's in DP, and as I don't use that program, I can't help you. Sorry.

    DG
  • B
    B
    last edited
    last edited

    Thanks for your reply, but I don't understand. The whole point here is that Kontakt works just fine alone in DP; it's only when I run it as a plugin inside VEP that the patch changes don't work.

    ???

     

    @DG said:

    It's not in VEP, it's in DP, and as I don't use that program, I can't help you. Sorry.

    DG
  • D
    D

    OK, I'll try to explain it more clearly. Assuming that it is a VST2/VST3 thing.

    Kontakt is VST2, so when it loads in DP, Program Changes are passed on from DP to Kontakt.

    When you load Kontakt in VEP, if you load the VST2 version of the VEP connector, DP passes the Program Changes to VEP which passes them to Kontakt.

    If you load the VST3 version of the VEP connector, DP passes Program Changes to VEP, which ignores them, because they don't exist in VST3, so they don't get passed on to Kontakt.

    Hopefully that is more clear now.

    DG
  • B
    B
    Thank you. :-)