VST3 - Maschine supporting existing NI VST3, but none from other vendors?

CT Blaze
CT Blaze Member Posts: 7 Sine
edited April 27 in Maschine

I don't understand this any longer... I paused for 2,5 years, only to find a TOTAL mess with VST2 and VST3 support. Firstly, screw STEINBERG for causing this, but also everyone else for blindly following Steinberg on their "Standards". Proprietary technology is always dangerous, and fires back eventually...

Having said that, WHY on earth does Maschine support NI's own VST3 plugins, but seemingly none of the others?

I have VST3 plugins of vendors like Roland, Plugin Alliance, Overloud, Audiothing and Togu Audio Line (TAL) sitting in C:\Program Files\Common Files\VST3 , they are not being recognized while scanning ! WHY?

Is Native Instruments actually aware that any new developer cannot provide VST2 any longer, thanks to Steinberg? Is there a problem with VTS3 itself, is it not a standards they can rely on?

Please, enlighten me, and I know there were several threads in the old forum about this, from 2020 on, I can't believe this is still not resolved?

Please convince me not to switch to something else, more modern, with more flexible code base, right now. Why would I spend any money with NI products right now, in this situation? I've been a user and fan since 2014, and now SUPER DISAPPOINTED, as you might have guessed already...

Comments

  • Kymeia
    Kymeia Member Posts: 42 Tri
    edited February 20

    Of course NI are aware, that's why they are adding VST3 support but it isn't as easy as you may think. Maschine and Komplete Kontrol are both at the moment very dependent on VST2 due to the NKS standard, that is changing and the goal is for them both to support VST3 from third party developers too, but they started with their own plugins because it makes sense to implement and test it first with the plugins you know best, before opening up the potential can of worms that is third party VST3 support. It looks from several NI statements that they plan to open up to third party developers gradually rather than all at once, starting with those who are already NKS partners. This makes sense, if they just add it without going through this process it will likely be a crash fest and just as importantly from NI's perspective, the transformation of NKS from VST2 to VST3 isn't something that can be rushed all in one go. Start with trusted partners who are willing to work collaboratively on the transition process rather than making it a free for all.

  • ozon
    ozon SwitzerlandMember Posts: 347 Saw
    edited February 20

    Actually, Steinberg didn’t make a mess and gave developers plenty time to migrate their products to VST3.

    From the Steinberg news here:

    https://www.steinberg.net/en/newsandevents/news/newsdetail/article/vst-2-coming-to-an-end-4727.html

    (which unfortunately isn’t available anymore)

    Late 2013 we announced that the Software Development Kit (SDK) for VST 2 would no longer be maintained and would only be available as subset of the VST 3 SDK. Five years down the line and this transitional phase is now also coming to an end.​

    And in 2018, Steinberg stopped issuing VST2 developer licenses.

    @CT Blaze wrote:

    Proprietary technology is always dangerous, and fires back eventually...

    …which seems to be the case with NKS.

  • skrutiny
    skrutiny Member Posts: 22 Sine

    There is a neat workaround to get 3rd party vst3's working in mashine. Its a vst2 shell that cleverly wraps any vst3's. Ironic that native instruments cant do this natively =] https://www.xlutop.com/buzz/zip/vst3shell.zip

  • skrutiny
    skrutiny Member Posts: 22 Sine

    oh and btw, if you updated to the latest version of mashine, this will not work. lolz

Back To Top