Native Instruments have just released Komplete Kontrol 2.8 and Maschine 2.16 which now includes VST3 support as well as Native macOS M1 support. While this is a long awaited and overdue addition there are some things that users will need to be aware of especially in regards to 3rd party libraries such as the ones created by FreelanceSoundlabs. 

VST3 brings some improvements in performance for DAWs and is now the only way developers can move forward since VST2 is now officially unsupported by Steinberg. In the overall scheme of things there aren't all that many improvements on the surface that users will really benefit from so it is not a "requirement" to move over to VST3.... unless you are a macOS user. 

While Windows users will have very few issues running VST2 plugins for some time macOS users that are running Apple Silicon processors will find that VST2 plugins are no longer available within Komplete/Maschine and therefore cannot be used unless you are launching Komplete Kontrol/Maschine/DAWs in Rosetta compatibility mode. Developers of VST plugins are working to update their VST plugins for M1 compatibility but this will typically only be AU and VST3 versions leaving VST2 (and all your old projects you have not yet completed) out to die.

Firstly, don't panic, just have some patience. If you are running on mac M1 then you will still need to run in Rosetta Mode (including your DAW) because although KK now is M1 native, not all plugins are updated yet and most NKS libraries are also not working with VST3 plugin versions. You will be very busy checking every developers site to see if they have VST3 versions of your plugins that are M1 compatible.

Secondly, please try not to message me direct saying this or that isn't working now or asking "When will you be updating these libraries". I am aware things aren't working for mac users now but this will take a heap of time and it may be a year or more before your plugin libraries are updated since priority is on fixing and maintaining current libraries and developing new ones. 

VST2 Libraries with VST3 Plugins?

98% of NKS libraries I have tested will NOT simply work with VST3. While some libraries (such as UVI) have very talented developers that know how to code in the required "Migration" requirements to have things work automatically with VST3, almost ALL plugins do not have such talented developers and simply dont work. In some cases I have noted a plugin "may" load but the control parameters are completely different ID numbers so either there is no control or parameters are seeminlgly random.

Basically to make these older libraries work with VST3 a new version of the library will need to be created/updated. This has to be done on a plugin-by-plugin basis and will take some considerable time. Again, Windows users have no problems for the moment but M1 users will have a long wait ahead.

I have a list which is updated that details the status of each plugin library and if it is currently supported by VST2/3 or Both along with what is currently planned for updates.

Check This List Here

• For macOS users, continue running in Rosetta mode for now if you value things to work. If you do not want to do this, you will just have to deal with the loss of your libraries for the moment. 

• Libraries need to be upgraded and tested which I am deep into work doing right now. For most libraries a new controller map is required and VST3 based libraries will not be backwards compatible with VST2.

• Some plugins have no VST3 or M1 compatible versions so that is up to users to research, not me. If you want to use a Mac system and also M1 be prepared for some plugins to be lost to you without any hope to ever have them back. I will still update libraries if a VST3 version of a plugin exists even if it is not Apple Silicon compatible as it may be one day.

• Because there is an overwhelming amount of time needed and people are impatient some updates will have a small cost. I will try and release some updates for free but bottom line is I receive very few donations beyond the actual library costs so I have to impose some maintenance costs and I am certain most can afford $5 here and there to assist with development and maintenance especially since most libraries are maintained for years for free. Users can help to speed this up by Donating to assist in covering some extra time and helping to lift any upgrade costs. 

• Lastly, PATIENCE on your part is needed. There is never any guarantee things will always work, all findings and updates will be posted both here, on my Facebook page and monthly updates will be emailed out around the start of the month.

What's The Fix / When Update?

Just as there is a lot to read, there is also a lot to work through and I can only devote so much time to this problem. 

For the moment, macOS users will have to look using all apps in Rosetta mode until updates are available or just wait patiently. 

I am not able to offer any solid timeframes on when I will have a library updated (or even if) since I need to test every single library. Currently as of writing this blog I am testing some new tools I have developed which should save some time and help me work through this much quicker than re-processing plugins from scratch. 

Just know this is being worked on, some libraries have already received updates and it will depend very much on the support of users as to how fast this rolls out!

How can I keep up with development news? 

Best way is to jump on the NI forum and switch on notifications for this thread here: 
https://community.native-instruments.com/discussion/305/nks-freelance-soundlabs-3rd-party-nks-libraries-for-komplete-kontrol-maschine#latest

Or follow my facebook page here:

https://facebook.com/freelancesoundlabs

If you are a registered user and you receive my monthly newsletter I will also send out status updates at the beginning of each month so if somethiong is not covered in these channels, assume I have no further answers for you.  

FAQ

I have just updated to Komplete on my Mac M1 and now nothing is loading

Run KK (and your DAW) in Rosetta Mode for now and use VST2 versions of plugins.

I don't wanna run in Rosetta mode now KK is M1 native

That is fine, just don't expect many things to run just yet since all NKS files created call the VST2 plugin and have to be migrated. 

But I paid for this library and now it isn't working

Yeah that's the risk you take when updating to a system that people are still trying to add support for. We cannot offer refunds but add support and updates where it is possible. 

How long will it be before my favorite NKS library gets updated

Could be a week, could be a year, could be never. Depends on what is involved (if it is even possible) to migrate the library to VST3, how much work it will take, how many people own the library to begin with and how much I could personally be bothered to do the work. It can take many hours and that is time I cannot work on new libraries or even make a living so please consider this before complaining if there is a small charge for updates.

Is there anything I can do to help speed up the process?

Sure, If you feel inclined to assist you can send a Donation since I still need to work other jobs to cover my bills and expenses so can only devote hours I receive income for. Purchasing NKS libraries and donating will help me devote more hours to updates.