This is the VST we keep talking about

We have been babbling about installing Kontakt for the past week or two and here is where we are at this point. There are a TON of VST’s on the market. Some are free, some are not. As with most things, you get what you pay for. For us, and what we are looking to do, this appears to be our best option. There are hundreds, if not thousands, of sound libraries that support the Kontakt player. You can review a small example here. Not enough? There are LOT’s more – Just Google it.

As of this post, we are so close – yet, so far away! This might be as simple as a single mouse click that we missed along the way, or not. For now, a complete failure on the OAX side yet, it has worked exactly as expected everywhere else. 🙁

If you have not been following along, review our recent posts showing that we have a basic setup working in our test setup (BUT – with no Wersi software in the mix). Everything in that setup works as expected. In addition, we also have Kontakt installed as a VST within Sonar and Logic Pro X and yep, it works exactly as expected.

Tomorrow is a new day and we LOVE a challenge. We will be taking another run at this at the crack of dawn. It might be as simple as walking away for a few hours and in the morning we will have a “DUH” moment or ??? What have done so far?

  1. Installed “Native Applications”. This allows you to download whatever NI (Native Instruments) you own and update them as updates are released.
  2. Once that completed used the above to install the Kontakt5 Player.
  3. Next, install the Kontakt Factory Section (this is the free sample library).
    • It’s includes enough basic sounds to show you how things work and what is possible.
    • From here you would purchase / add other samples.

We are at the P/C level on the Sonic and the “Native Applications” app is up and running and we have two out of three modules that we are interested in installed. The 3rd one was installing when we took the screenshot and at this point has completed:



We can “load” the VST from OAX and launch it – What you see is Kontakt up and running within OAX BUT connected to nothing.


At this point we can hit some keys on the upper keyboard and Kontakt does respond (meaning we can see MIDI data coming in). That’s a good thing — BUT — as soon as we attempt to connect Kontakt to the outputs OAX crashes and well, this says it all.




9 thoughts on “This is the VST we keep talking about

  • 08/07/2017 at 09:30

    HI Curt

    There are 3 Kontakt 5 dll files in the Native Instruments plugin folder, all with a different number of outputs, have you tried all of them. (My guess is the 8 outs would probably be best chance until the update comes out)

    In addition, was there an option to choose the VST Host when installing at the Windows level, as if so, you will need to make sure you choose the VST3 option. (I can’t remember as I installed Kontakt some time ago)


  • 08/06/2017 at 12:44

    Nope – 64 bit (although for kicks I tried 32 after 64 failed). Been messing with a little more today and it is about time for an Ale or two!

    Not really sure how to check the outputs as you suggest? If you run as stand-alone there are both MIDI and Audio menus under “options”. When you bring it up, in what I’ll call “VST mode”, neither of those options are there. That is true when running in OAX or in our DAW.

    At this point the difference would be in the DAW I understand how to route things (and of course, nothing crashes). In OAX – I thought I did but as mentioned above I’m not getting much of a chance. OAX crashes instantly when you connect the output on Kontakt to either of the line outputs.

    • 08/06/2017 at 14:12

      Hi Curt

      Download and Effect Plugin such as the convolution reverb I mentioned, and then connect Kontakt to the reverb and the reverb to the line outs to see if this works.
      If you still have problems, then it may be worth performing a backup and reinstalling OAX to see if this solves the problem, otherwise it may be an email to Wersi.

      Hope this helps


      • 08/07/2017 at 07:01

        Good idea Bill. Sadly, exact same results with one minor difference. This time the crash occurs when I connect the output on Kontakt to the input side of the reverb. I did have the output of the reverb already connected to the inputs of line1 / 2 on OAX.

        Going to do three things next:
        1. Try above without being connected to the “lines” on OAX.
        2. Remove / Re-install Kontakt at the Windows level.
        3. Drop a note to the Wersi team.

        On a side note I saw a post on a different site about the possibility of an OAX update coming soon. No clue when or what it may offer but it should be interesting of that improved the issue I’m having.

        Time will tell!

        • 08/07/2017 at 07:43

          Based on the excellent news in the post below from Carlo – I’ll take at look at the output section using our test lab and anxiously await OAX 1.50.

          • 08/07/2017 at 12:55

            hi Curt,

            You can temporarily fix the problem by manually editing the OAX-UserDatabase.

            If interested, email me for details.

            Best Regards,


  • 08/06/2017 at 07:06

    Hi Curt,

    I had exactly the same issue with UVIWorkstation.
    I contacted the OAX-support, and this was the answer from them :

    “Der Fehler bei der UVI-Workstation lag an den möglichen Ausgängen. UVI hätte da max. 17 und nicht wie üblich 16.”

    OAX can only handle VST’s with a maximum of 16 Output-channels.
    You have to change the number of Output-channels in your VST.

    This is wath i have found in the Kontakt 5 User Manual :

    “15.4 Outputs in Host Mode
    When using KONTAKT in stand-alone mode, the assignment of physical outputs within the
    Channel Configuration dialog is straightforward: the drop-down menu will contain all outputs
    (up to 32) which are provided by the audio interface that you’ve selected in the Audio tab of
    the Options dialog. When using KONTAKT as a plug-in in audio hosts, things get a little more
    complicated, as each host handles plug-ins with multiple outputs differently.
    The maximum number of (mono) audio channels that you can assign in host mode is limited to
    32 for the VST version of KONTAKT, and 16 for the AU and RTAS versions. The VST plug-in is
    special in that it comes in 3 different flavors with 8, 16 or 32 outputs. In AU and RTAS environments,
    the host will determine the actual number of outputs. Refer to the documentation of
    your host program to learn how this is being handled in your case.
    Note that KONTAKT has to advertise its number of outputs during instantiation, which means
    that it can’t successfully change its output configuration on the fly during operation. In consequence,
    when you try to change anything in the Outputs section, a window will pop up asking
    you to save and reload your song in order to let the host accommodate to the changes. Before
    you do this, go to the Presets/Batch Configuration menu and select the appropriate option from
    the Save current output section state as default for sub-menu.”

    The hole Issue will be solved in the new OAX-release 1.50 that will be publiched in the next days…

    Hope this helps,
    and Best Regards,

    • 08/07/2017 at 07:21

      Carlo – Excellent information! I was just about ready to drop Uli and team a note. Guess at this point I just need to hurry up and wait on OAX 1.50!

      Many thanks for the insight!

  • 08/05/2017 at 18:53

    Hi Curt

    You aren’t trying to use the 32 bit version are you, as this can cause problems?
    In addition make sure nothing is already assigned to the audio outs in Kontakt, as this could also cause a problem.
    If you still have problems, get some Real Ale down you, and all your problems will go away, (smile) at least until it wears off.



Leave a Reply

Your email address will not be published. Required fields are marked *