Komplete Krashtroll on Cubase 13 / Sequoia / M1 Pro

Hi,

I'm using Komplete Kontrol in C13 on an M1 Pro Mac running Sequoia, and frequently get crashes when I close KK windows.

I've tried reinstalling KK (following steps on the NI website w/ com.plists and json) to no avail. Aside from never opening/closing such windows, has anyone figured out a fix for this?

Thanks for any insight/suggestions you can provide.

Find more posts tagged with

Cubase

Mac

Komplete Kontrol

Comments

benmuetsch

Hi everyone,

just jumping in to report that the same happens here on Ableton Live 12.1.1 / macOS Sequoia 15.1 on Intel Mac Pro 2019.

astavi

https://community.native-instruments.com/discussion/comment/190206#Comment_190206

Oh wow, that's a bummer. Was sure it was a Cubase or Apple Silicon glitch. Ableton was always rock solid for me back on the day.

Any chance you're using a headless MacBook Pro? I am, and I'm wondering if it isn't trying to draw to a screen that isn't there or something.

benmuetsch

I tried again and it seems like it's only happening with Battery 4 and also doesn't happen everytime.
I like using Battery inside Komplete Kontrol where it's possible to pre-audition the kits.

Regarding your other question: I don't know what you mean there exactly, I am using a Mac Pro 2019 workstation tower with external screens connected.

astavi

I bought an MBP with broken screen, removed it, and use it with an external monitor. Starting thinking that was why this is happening, but guess not.

Wonder if it's related to something happening plist/json files given that it happens to me with multiple plugins, but only with Battery for you.

JesterMgee

Pretty sure this is because the latest macOS is not yet officially supported. One of the joys of macOS is that every update is an exciting time finding out that it breaks compatibility with almost everything you own and you have to wait (and hope) that developers can patch things up and have enough duct tape left to make it all work again.

This is why it's suggested/common knowledge to try and refrain from updating macOS for a production system for as long as possible, remaining essentially 1 whole update behind the latest. Will have to wait until the next release is announced to be Sequoia compatible.

astavi

https://community.native-instruments.com/discussion/comment/190831#Comment_190831

This makes sense and sounds like a good rule to follow in general, but it was actually crashing on me before Sequoia. My genius brain thought "ok, newer better", but that was obviously a giant nope.

Quick links

Unanswered questions