Massive X Loading problem when launched from Komplete Kontrol

Plaffe · 2025-01-28T20:36:41+00:00

There was an error rendering this rich post.

I am using Logic X on a M1 MacBook. When I launch Massive X from Komplete Kontrol I get a Loading problem. When launching Massive X (AU) directly in Logic, it works, but my Kontrol S61 mk3 goes to default midi template.

All installed plugins are working in Logic. No plugins are being listed as non working (I saw this in another post)

Massive loading problem.png

Find more posts tagged with

Komplete Kontrol SW

Massive X

Accepted answers

Plaffe

Update: I got it all working by launching the standalone Komplete Kontrol which then scanned all apps and updated the database. I guess during installation something went wrong and the database got corrupt.

All comments

Kymeia

Have you installed the VST3 version?

Plaffe

On mac Native access installs everything automatically and only the Audio Units versions are installed. Or is this assumption not correct?

I do not see any option in Native access to add VST3 versions.

something I did not mention: both application and content are on an external SSD which seems OK for the rest of the NI instruments

Plaffe

Today I reinstalled Massive X and Komplete Kontrol, but the issue is still the same. I also found a VST3 version in of Massive in the "library>Audio>Plug-ins>VST3" folder (information I got from the uninstall instructions )

I also noticed that 3 applications seem to exhibit the "same" problem: when launching Massive X, Kontakt 8 or Reaktor 6 the Komplete Kontrol keyboard goes to standard midi template, so no Komplete Kontrol user interface is available.

I bought a new S61 mk3 keyboard one week ago to replace the mk1 and it's a bit frustrating to notice that the Komplete Kontrol user interface is not available for some important apps that I bought myself into.

Plaffe

Kymeia

https://community.native-instruments.com/discussion/comment/207713#Comment_207713

I don’t think it’s that- it’s standard practice to scan all plugins in the standalone first

pranaearth

Yes, anytime you install an NI product that has a stand alone version, you always launch the stand alone version before using the plug in version of it. It took me years to remember to do this, lol

Plaffe

Aha, I did not know that it was standard practice to launch the standalone version first ….

Maybe hints in Native Access can help people like me to get this knowledge?

Anyway, that was the trick that did it. Reinstalling the software did not do it, launching the standalone version did solve the problem. My best guess would be a database issue but you may disagree ;-)

Quick links

Unanswered questions