Plugins Incompatible with M4 CPUs

[Sekops]

Any specific plugin that triggers it? I can likely test for you?

Could you test Reaktor VST3? Blocks, Form, Molekular, … I also had a crash when loading Freak (from the Crush pack, I think).

I’m still testing, but I haven’t had a kernel panic or any other major problems since I’ve stopped using NI plugins.

Well, Reaktor 6 VST3 worked fine in live 12.1.5 on Sequioa 15.2 on my Apple M4 Max, tried Forms, Block Base, Molekular, all good.

But, attempting to load Freak VST3 resulted in an instant forced reboot, no warning, just MacBook restarted. Ouch.

After reboot tried again and both VST3 and AU worked fine. /Shrug

Tried all in Bitwig 5.2.7 and no problems.

[Sekops]

Perhaps unrelated but updates to Massive 1.7 and Massive X 1.4.5 just dropped In Native Access today, both citing Sequioa support, although they were both working fine for me, but perhaps other updates are on their way soon?

[aMUSEd]

I’m getting kernel panics when using Native Instruments plugins in Live 12 on an M4 Pro Macook. I don’t know if it’s Sequoia or new CPU related. I’ve contacted support only recently and haven’t heard back yet, but I sure do miss Reaktor.

Unlikely to be Sequoia as I have been running it a while now with no significant issues, and I know others the same. There have been reports of similar issues with M4, which is weird on the face of it as it should in principle be the same architecture as the other M's, but possibly something has changed developers need to adjust for?

[aMUSEd]

Perhaps unrelated but updates to Massive 1.7 and Massive X 1.4.5 just dropped In Native Access today, both citing Sequioa support, although they were both working fine for me, but perhaps other updates are on their way soon?

Actually there was graphics bug that this update fixed with Massive X when loaded in Komplete Kontrol in AU hosts - however that one went back to Sonoma

Interestingly the same bug also affects all NI FX that have the HDPI interfaces (Crush pack etc) except for Guitar Rig 7. It hasn't been fixed yet for them but I guess that is in the works now they have fixed it for Massive X.

[nanostream]

Any specific plugin that triggers it? I can likely test for you?

Could you test Reaktor VST3? Blocks, Form, Molekular, … I also had a crash when loading Freak (from the Crush pack, I think).

I’m still testing, but I haven’t had a kernel panic or any other major problems since I’ve stopped using NI plugins.

Well, Reaktor 6 VST3 worked fine in live 12.1.5 on Sequioa 15.2 on my Apple M4 Max, tried Forms, Block Base, Molekular, all good.

But, attempting to load Freak VST3 resulted in an instant forced reboot, no warning, just MacBook restarted. Ouch.

After reboot tried again and both VST3 and AU worked fine. /Shrug

Tried all in Bitwig 5.2.7 and no problems.

Thank you, that’s interesting. Maybe it isn’t Reaktor related at all, maybe it’s just the Crush/Mod pack. I’m going to try again today and leave Reaktor open for a while, it’s possible it takes some time to trigger that bug.

Yeah, I know macOS 15 isn’t officially supported yet. But I hope letting them know and sending crash logs helps.

[nanostream]

I’m getting kernel panics when using Native Instruments plugins in Live 12 on an M4 Pro Macook. I don’t know if it’s Sequoia or new CPU related. I’ve contacted support only recently and haven’t heard back yet, but I sure do miss Reaktor.

Unlikely to be Sequoia as I have been running it a while now with no significant issues, and I know others the same. There have been reports of similar issues with M4, which is weird on the face of it as it should in principle be the same architecture as the other M's, but possibly something has changed developers need to adjust for?

Looks like it, yeah. I’ve found a number of reports of OS crashes, most of them were gaming related, maybe it’s a graphics thing? Also, all these crashes seemed to be happening on M4 Pro or Max devices, which is weird as well.

By the looks of it Apple resolved some, if not all of these gaming related issues with 15.1 (iirc). Let’s see if NI and other developers can solve this on their own or if it’s Apple‘s problem.

[uOpt]

I imagine you'll get a straight bat from NI: https://support.native-instruments.com/ ... -Statement

But that doesn't mention M4 one way or another.

No, but as soon as they determine you're on an unsupported platform (Sequoia), usually that's the end of the conversation.

In the case of NI support that might be a good thing. Same result, less time

[nanostream]

Well, Reaktor 6 VST3 worked fine in live 12.1.5 on Sequioa 15.2 on my Apple M4 Max, tried Forms, Block Base, Molekular, all good.

Thank you, that’s interesting. Maybe it isn’t Reaktor related at all, maybe it’s just the Crush/Mod pack. I’m going to try again today and leave Reaktor open for a while, it’s possible it takes some time to trigger that bug.

After playing around with Reaktor (Blocks) the whole day, I just got a kernel panic/sudden reboot again. Interestingly, it didn’t happen when I was interacting with Reaktor, but when I tried to load a Live fx rack containing a handful of Arturia fx on a different track.

[dermage]

Any specific plugin that triggers it? I can likely test for you?

Could you test Reaktor VST3? Blocks, Form, Molekular, … I also had a crash when loading Freak (from the Crush pack, I think).

I’m still testing, but I haven’t had a kernel panic or any other major problems since I’ve stopped using NI plugins.

Well, Reaktor 6 VST3 worked fine in live 12.1.5 on Sequioa 15.2 on my Apple M4 Max, tried Forms, Block Base, Molekular, all good.

But, attempting to load Freak VST3 resulted in an instant forced reboot, no warning, just MacBook restarted. Ouch.

After reboot tried again and both VST3 and AU worked fine. /Shrug

Tried all in Bitwig 5.2.7 and no problems.

Reminds me a bit if windows 98 times, this happened when a process wrote on the wrong memory region. But maybe NI use some kind of service app like NTk deamon which handles licensing now, which has system level access and may do something fishy when activating the license for the first time.

[Sekops]

If it’s happening with both Arturia and NI, perhaps it’s more a problem with Live than the plugins? Might be worth sending Ableton your crash reports…

[Sekops]

Of course if you were using a DAW with plugin sandboxing you might not have these problems /s cough Bitwig cough.

[nanostream]

If it’s happening with both Arturia and NI, perhaps it’s more a problem with Live than the plugins? Might be worth sending Ableton your crash reports…

I’ve sent plenty of crash reports to Ableton, but haven’t contacted support yet. These Arturia plugins have been very stable, I’ve been using them all the time without a problem. Only when I introduce NI software the machine starts crashing.

For now, I’m going to assume it’s an NI — or Apple — issue. Userland apps shouldn’t be able to crash the whole system anyway, sandboxed or not.

[sin night]

Ouch! I ordered a Mac Mini M4, I have plenty of iLok software and some Sonnox plugins are among my go-to…

It looks like I will have a few months of “testing” before being able to use my new computer for music production.

What a great xmas news!

[sin night]

I just tried the Inflator but it works correctly on my M4 Mac Mini; I didn’t activate Rosetta so I’m confident it’s running natively (I’ll check again tomorrow, now it’s late night here).
I did a clean install, I didn’t migrate anything from any previous machine.

[Sekops]

Intriguing, I get a corrupted message on an M1 Max, have tried uninstall / re-install, but no dice, plenty of other options these days, so not overly concerned and so far haven't had any issues with other vendors.