Plugins Incompatible with M4 CPUs

[Sekops]

Here's an odd one. Just upgraded to an M4 Max on Sequoia, and all is generally well, however Oxford Inflator has announced a problem with M4 CPUs:

https://support.sonnox.com/support/solu ... le-m4-cpus

They make it clear that this is not a Sequoia compatibility issue.

Any others that anyone's aware of?

Curious what the root cause is...

[uOpt]

Gotta love the amount of detail about the problem they give there...

[Sekops]

To be fair, they might not know yet. Sometimes the plugin loads after first install, then crashes, but will reload then never work again...

[jupiter8]

How is that even possible?

[uOpt]

How is that even possible?

Smells like DRM...

[Sekops]

If the instruction set in the CPU changes, then it's entirely possible if the code depends on that, there were some new additions: https://www.silabs.com/documents/public ... ecture.pdf.

TIL the M4 includes enhanced DSP processing, very useful for audio. Wonder if software would need to be re-written / compiled specifically for the M4 to make use of that?

Inflator is iLok, which is activated fine and on first install the plugin loads, just never again.

[uOpt]

If the instruction set in the CPU changes, then it's entirely possible if the code depends on that, there were some new additions: https://www.silabs.com/documents/public ... ecture.pdf.

TIL the M4 includes enhanced DSP processing, very useful for audio. Wonder if software would need to be re-written / compiled specifically for the M4 to make use of that?

Inflator is iLok, which is activated fine and on first install the plugin loads, just never again.

Sure, software would have to be at least recompiled to make use of new instructions.

But the addition of new instructions does nothing to the ability to run old code that doesn't use them. It's not that the "old version" of such instructions is getting removed.

[Sekops]

And even then the compiler might need to be updated to be able to make use of new instructions.

But you’re right, unless some instructions have been removed then I can’t fathom what it might be. Hopefully they can fix it and will disclose.

[Sekops]

At this time there is a compatibility issue affecting all Sonnox plugins on Apple’s new M4 chips.

What’s happening?

Sonnox plugins are currently crashing all major hosts when run on M4 chips. The fix requires an update from iLok, and we’re waiting for them to release the patch which we will then need to implement into every Sonnox product.

How long will I need to wait for these updates?

Based on the information we have right now, we estimate to have released updates for the entire Sonnox range by the end of February 2025. However, please be aware that this is subject to change, depending on when we receive the fix from iLok.

I use your plugins on every project! Is there a temporary solution?

Yes, You can run your DAW with Rosetta 2. We appreciate this is not ideal, but this will allow you to run your Sonnox plugins on your M4 while we work on this fix.

To enable your DAW to run via Rosetta -

Close all DAWs
Open the Finder on your Mac.
Navigate to the Applications folder and locate your DAW
Right-click (or Control-click) on the app icon.
Select Get Info from the menu.
In the Info window, tick the checkbox that says Open using Rosetta.
Relaunch your DAW

What about macOS 15 Sequoia itself? I have an M1/M2/M3 CPU.

This is not related to macOS 15 Sequoia itself. Sonnox plugins have been thoroughly tested on the new OS and run on M1, M2, and M3 machines with no related problems.

We’re sorry for the inconvenience and appreciate your patience while we sort this out. Our team is working hard to get things back to normal as soon as possible.

Thanks for sticking with us!

- Sonnox Support

[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.

[Sekops]

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

[Sekops]

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

[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.

[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.

[Sekops]

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.