Kontrol 3.x requires instruments to support VST2 to VST3 migration now?

Teilo · 2025-05-15T17:14:05+00:00

There was an error rendering this rich post.

I am trying to load the latest versions of Arturia Complete instruments in KK (3.5.0). Every single one of them refuses to load. KK reports an error that instruments must support VST2 to VST3 migration.

This is a clean install of Arturia Collection V 11 Pro. NKS and VST3s are installed. NKS previews for these instruments work in KK. KK is NOT running in Rosetta mode.

Why must an instrument support VST2 to VST3 migration if I am not even trying to use VST2 versions of those instruments, or migrate VST2-based projects? For that matter, why is this error coming up at all when I'm not using Rosetta?

Find more posts tagged with

Komplete Kontrol SW

Accepted answers

Teilo

A rescan fixed it. So bizarre.

The only odd thing I noticed this time around (setting up a new Mac) was that the initial plugin scan took an exceptionally long time, and was getting hung up specifically on the Arturia plugins. But the rescan was very fast. My U-he plugins scanned quickly on first launch, and they all worked immediately.

All comments

Kymeia

They are loading normally for me, I don't think anything has changed and they already fully support migration anyway so I think that message is in error. Try a full plugin rescan.

Vocalpoint

What computer type and OS are you running. Assuming Mac?

What Arturia instruments are you trying to load?

And finally - what DAW?

Teilo

A rescan fixed it. So bizarre.

Teilo

https://community.native-instruments.com/discussion/comment/226477#Comment_226477

Yes, Mac. This was standalone. All Arturia instruments had the same problem. Resolved on rescan.

Vocalpoint

https://community.native-instruments.com/discussion/comment/226478#Comment_226478

Yeah - the scanner looks like it should be rock solid on the first pass - but not always.

Glad you got it sorted.

Kymeia

https://community.native-instruments.com/discussion/comment/226478#Comment_226478

It’s just how some plugins implement migration - u-he plugins also do this, they require a full plugin scan to set them to the right version (native or Intel). I guess somehow that got reset but a plugin scan fixes it (as long as done in native mode not rosetta which switches it the other way)

Quick links

Unanswered questions