After upgrading to Komplete Kontrol 2.8, my Omnivision and Iris 2 VST3s no longer work. Omnivision won't load, and Iris 2 causes an immediate crash.
Is there any way to go back to 2.7?
The Komplete Kontrol 2.8.0 and Maschine 2.16 updates bring the long awaited M1 native compatibility. Not all plug-ins are compatible yet. Please check this article: KOMPLETE KONTROL / MASCHINE Error: "*Product* could not be loaded, as it may not support Apple Silicon or VST2 to VST3 migration."
It can also happen that when loading old projects, Maschine will crash.
Until all plug-ins are M1 compatible or can be migrated to a compatible version, the solution is to run Komplete Kontrol and Maschine in Rosetta mode.
Yeah Omnisphere should be fine as I have tested that on a few machines and have reports from macM1 users it is all good.
Iris I have not updated or tested and is still listed on the VST2 only list for my libraries. Until I get a chance to test/update assume it is VST2 only at the moment. In saying that tho, if you are selecting the plugin direct from the plugin list to load and it is crashing KK, that is a plugin/KK/OS issue and if you are on mac, that pretty sems pretty usual at the moment.
Mac I assume……..
run things in Rosetta mode for now
Did you read @JesterMgee 's post above?
It’s Iris 2 that’s broken - outdated plugin no longer being maintained - you really can’t expect Komplete Kontrol to keep working with it indefinitely and Iris is never going to be in a native version - blame iZotope for dropping it not NI
I’m referring to the OP
Ah I see what was happening. If you were running Logic in native and KK before 2.8 was not native Logic would have been automatically wrapping it in its built in Intel bridge (which seems rather finicky tbh about what it bridges and what it doesn’t - compared to say the one in Bitwig which is more stable in my experience). Now KK is native too it won’t be doing that and although I guess KK would be faster in that scenario it won’t load all the old non native and VST2 plugins and may also not benefit from any sandboxing built into the bridging process.
That makes the most sense to me, from what ive experienced.
Omnisphere does load, it just doesn't migrate
I actually wrote to Spectrasonics support and they told me it was being looked into and they thought it was a good idea but couldn't say how long
2.8 COMPLETELY broke my plugins. Load up my projects and get "Library is empty" message. Rescan takes forever as it scans all my plugins, but then they arent there, same message. Tried this in VST and Standalone modes, Nothin. Uninstalled, cleaned registry, reinstalled, nothin. No way to revert to older version, so until they fix whatever broke it, i guess i just don't get to use Komplete Kontrol.
Same here, after upgrading to Komplete Kontrol 2.8, Spectrasonics RMX is not loading. Can't use the sessions I am working on. I also need to go back to 2.7x but how??
Same Problem here. All was fine in M1 mode and Komplete Kontrol 2.7.2
Now in KK 2.8 I get the error "Plug-In Preset could not be loaded, as it may not yet support Apple Silicon or VST2 to VST3 migration"
Perhaps the Recent update to Logic 10.7.5 has something to do with it. Though launching the older Logic 10.7.4 shows it now has the same problem.
Continuing to test, but yeah, for now Komplete Kontrol needs to be used in Logic Rosetta. Its broken in Logic M1
EDIT: I was able to copy both the Komplete Kontrol 2.7.2 Application and Audio Unit component from an older system of mine. I have replaced 2.8 and everything is working again.
EDIT 2: for me, the issues is not only with 3rd party VST’s. Absynth 5 and other things as well.
? Wrong post? I don‘t have Iris 2 installed on my system?!
Yes, and thanks, but I use Logic since April NOT in Rosetta and I am VERY happy this way. I am NOT using a lot of third-party, and I just want to have it back (and stable) before I updated Komplete Kontrol to 2.8. I hope you understand. Again, everything was fine until I updated to this version. And my question is, how I can downgrade to Version 2.7.x . That's all I want to be happy again. 😀
No idea about that, but downgrading will cause the program to run in Rosetta mode as far as I understand since it is not M1 compatible in 2.7 so you really aren't fixing anything there. KK is now "Native" with macOS ARM and so it will automatically disable things that are not compatible. To force it back to how it was in 2.7, that's compatibility mode.
If you really feel you have to go back to 2.7, can't help you there but to simply say backups before updating are probably a good idea.
