Komplete Kontrol 3.3.3 Crashing Ableton Live 12.1.1 Projects on Launch

BMan · 2024-12-01T00:25:22+00:00

There was an error rendering this rich post.

Recently ran into an issue where having an instance of Komplete Kontrol 3.3.3 on any Ableton Live 12.1.1 track causes the project to crash at load (screenshot at end of post). I've seen some other older posts about KK crashing, but they're either (a) closed (example) or (b) aren't the same behavior I'm seeing.

I can load KK VST3 onto tracks in a new Live project, and they work just fine. It's only after I save/close then go to re-open the problem that the issue presents.

This doesn't happen with other Native Instruments plugins, including Kontakt 8 and Maschine 3). I've verified that I'm using the VST3 version of KK. It also doesn't happen with any other plugins by other manufacturers (e.g., Arturia, Modartt, Universal Audio, UJam, UVI plugins). The issue also doesn't seem to present itself in Maschine 3 (standalone) or in Logic Pro, although I haven't spent enough time to really test those applications as I primarily work in Live.

Other things I've tried:

Followed all of the troubleshooting guides on this page: https://support.native-instruments.com/hc/en-us/articles/5217260793617-Komplete-Kontrol-Crashes
Reinstalled Komplete Kontrol 3.3.3 according to this guide: https://support.native-instruments.com/hc/en-us/articles/210291865-How-to-Uninstall-Native-Instruments-Software-from-a-Mac-Computer
Reset Ableton Live 12 according to this guide: https://help.ableton.com/hc/en-us/articles/209070609-How-to-reset-Live#h_01GFR78BDSN9K99MFKY350SBHF
Uninstalled Ableton Live 12 according to this guide: https://help.ableton.com/hc/en-us/articles/115001172024-Uninstalling-Live-macOS. Then reinstalled Live 12.

None of this had any impact. The only way I can load projects in Live 12.1.1 that have Komplete Kontrol VSTs in them is to hold option while opening (to disable third-party plugins), remove the KK plugins, save, then re-open and try to add the plugins without KK.

My system information:

macOS Sonoma 14.7 (running on Apple Silicon Max M2)
Ableton Live 12.1.1
Komplete Kontrol 3.3.3
Kontrol S49 (latest version) MIDI controller
Ableton Push 2 controller

I've also submitted a support request with NI (#4437956) as well as a support ticket with Ableton. Looking for any ideas/help here.

Find more posts tagged with

Komplete Kontrol SW

Ableton

VST3

Error Message

Accepted answers

Jeremy_NI

https://community.native-instruments.com/discussion/comment/195163#Comment_195163

Please include all of this information in your support request, it will fast things up.

All comments

Jeremy_NI

Do you know what instruments you are using in Komplete Kontrol inside Ableton? Do you use Battery 4? There is a known bug that crashes the DAW when using Battery inside Komplete Kontrol. I'm wondering if this could be related.

In this thread you can find some older version of Komplete Kontrol, can you give these a try?

https://community.native-instruments.com/discussion/34866/komplete-kontrol-3-3-2-crashes-daw-on-close-if-hosting-battery-kbdsw-7913

BMan

https://community.native-instruments.com/discussion/comment/194998#Comment_194998

Thanks @Jeremy_NI for the quick reply!

I'm not using Battery 4 (actually I don't believe I've ever used it).

I'm using a range of instruments (some NI, some not). Some NI instruments include: Sequis (v1.0.3), Session Bassist - Prime Bass (v1.0.2), Session Percussionist (v1.0.0), Symphony Series String Ensemble (v1.4.2), and Alicias Electric Keys (v1.0.0). Outside of NI, I also have tried: BM-HYPE2 (UJam), Augmented Grand Piano (Arturia), Pianoteq 8 (Modartt).

I can give the KK 3.3.1 or 3.3.0 a try. If I read the linked post correctly, I can't go lower than 3.3.0 because I have a Kontrol MK3 S49 keyboard that's on the latest firmware (v1.8.7).

To downgrade, I'm assuming I have to remove/uninstall my current version of Komplete Kontrol per the directions here. Is there anything else I need to do?

Kymeia

Can you make it crash with KK in the project without any plugin loaded? That would help eliminate them

Kymeia

Just tried to replicate with Augmented Grand Piano and Pianoteq 8 (all I have of those) but can't so far. Do you have Live set to load the last project on open? Try disabling that and just loading manually

BMan

https://community.native-instruments.com/discussion/comment/195072#Comment_195072

Thanks @Kymeia for this suggestion! I hadn't tried that (not sure why it didn't occur to me), but was a great idea.

Before trying this, I already had downgraded to KK v3.3.0. This didn't appear to solve the problem, so I uninstalled v3.3.0 and tried v3.3.1. Same result. I then removed v3.3.1 and just bumped to the latest version that I had originally (v3.3.3).

Without any plugins loaded (just KK loaded), I had no issues. I made a project with 10 tracks all loaded with KK, then stopped there.

This got me wondering then if it was specific plugins. So I started systematically adding plugins (including the ones mentioned above that you didn't have problems with).

I didn't have issues with any of them, and then I tried some other older projects that had errors. They loaded fine, which was different.

The only way I was able to recreate the original issue was by loading a UJam plugins (BM Cozy) via KK. When reopening the project, I then had the original error. When I removed that instance of KK, I could then open the project again.

So I suppose it could have been something with projects that had (or had at one point) a UJam plugin loaded via KK? It could have been something was messed up with my installation of KK v3.3.3 (that didn't get fixed when I reinstalled)? Not really sure.

For now, I'll avoid using UJam plugins in KK and see if the issue happens to come back.

Thank you all for your help!

Matthew_NI

Since KK is itself a plug-in host, it was likely one of the hosted plug-ins causing KK causing Ableton to crash. If you're able to confirm which plug-ins for sure, or send over a crash report, that'd be a great help.

BMan

https://community.native-instruments.com/discussion/comment/195161#Comment_195161

Hey @Matthew_NI, yes, happy to. ~~I did attach a crash report as part of the issue I filed (#4437956). Are you able to access that?~~

I didn't upload it as part of that issue actually. Is there a good place to upload, or just send you a DM?

Matthew_NI

Attaching it to a ticket, if you have one open already, would be the best way. Thanks!

Kymeia

https://community.native-instruments.com/discussion/comment/195152#Comment_195152

Ok that sounds a possible culprit, I have heard some reports of problems with their plugins. A crash report would also help confirm

Jeremy_NI

https://community.native-instruments.com/discussion/comment/195163#Comment_195163

Please include all of this information in your support request, it will fast things up.

BMan

https://community.native-instruments.com/discussion/comment/195207#Comment_195207

Updated the ticket (#4437956) with the crash report as well as the cross-post link to this thread. Thanks!

daeus

wow I must have gone from a v2 to this v3.3.4 and no project will open (Ableton 10), I hadnt ran Komplete to re-scan plugins, so I did that;

Its re-scanning everything , plugins and presets (For hours)!

This has shut my entire studio down, why do they do this, I think my new strategy will be to keep on the same version until I get a new machine, that machine gets archived, so I can open any project in the future on that machine

Jeremy_NI

https://community.native-instruments.com/discussion/comment/215819#Comment_215819

The issue of OP here was due to a third party plug-in, Ujam. Your issue is probably a different one, maybe you should create your own thread with more details, like your operating system, etc…

Matthew_NI

Please also note that the latest version of KK is 3.4, not 3.3

daeus

https://community.native-instruments.com/discussion/comment/215903#Comment_215903

From what I can see its because v3 deletes all VST2 plugins, without any warning for the user before updating

Quick links

Unanswered questions