Maschine 3.0 Crashes Silicon Mac

tkurfurst

Maschine 3.0 appears to crash my Mac almost instantly after loading as it prepares the GUI. Allowing full disk access appears to delay the crash and the software will start and appear to work, then crash the system almost irretrievably. After launching Recovery Mode everything is back but I dare not run Maschine 3.0.

Has anyone else experienced this issue. Is NI aware of any compatibility issues that might affect my system? Any guidance would be appreciated. FYI running Mac Studio (M2 Max) with Sonoma 14.6.1

tetsuneko

Max family CPU issues again, eh? No probs on my M1 mac running Sequioa

I'm only bringing up max cpu family, because IIRC, there were some other issues related to them earlier this year..

Kymeia

I’m on M1 Max and not had a single crash with Maschine 3

tkurfurst

Additional detail as the issues remains after a full uninstall and reinstall with no other applications running and peripherals disconnected AND after a full diagnostics was run on my hardware, drives and systems software to full out other issues …

Issue Description:

Upon running the Maschine 3 software, my system encounters a kernel panic. The crash report indicates an error related to the AppleT6020PlatformErrorHandler, specifically involving the AMCC0 DCS GROUP 0 CHANNEL 0 M3_AIC_IRQ_EN_FLD error. Attempts to halt multiple CPUs (1, 4, 5, 6, and 7) failed with error code -5, suggesting that halting is not supported for this configuration.

System Details:

• System: Mac Studio (M2 Max)
• OS Version: 23G93 (Sonoma 14.6.1)
• Kernel Version: Darwin Kernel Version 23.6.0
• Secure Boot: Enabled
• iBoot Version: iBoot-10151.140.19

D-One

Yeah Max/Ultra versions do seem more problematic with NI.

No issues here on M2 Pro or M1.

Ali G.

Same problem here
Mac Studio M2 Max
Is there going to be a fix for the problem?

Kymeia

https://community.native-instruments.com/discussion/comment/191719#Comment_191719

I guess, once the problem has been identified, I think NI will need more information first and to test it themselves. It seems possibly to be just Max series Macs but not M1 Max as I have had zero crashes.

tetsuneko

Both users reporting crashes have M2 Max CPU. Coincidence?

Kymeia

https://community.native-instruments.com/discussion/comment/191735#Comment_191735

Possibly not but that just shows that there is a correlation which helps in narrowing down potential conditions under which the bug occurs, but not the underlying problem. That would need further investigation.

tom80

https://community.native-instruments.com/discussion/comment/191735#Comment_191735

Could be just the M2. No issues here on my M1 Max.

Kymeia

Thing is the architecture is meant to be the same for all Mx chipsets, just as it is meant to be for all x86 chipsets. I wonder what could be different between the regular and Max versions (and not the M1 Max?)

D-One

https://community.native-instruments.com/discussion/comment/191752#Comment_191752

Good question, this is not the first time, NI's SW often has issues with the Max CPU's.

Kymeia

https://community.native-instruments.com/discussion/comment/191802#Comment_191802

But not the M1 Max - I have never had problems with it and can't recall seeing reports whereas I have also seen several for M2Max and above. Maybe this is about load balancing between the Efficiency and Performance cores? Hard to think what else is different - more GPUs is unlikely to be the issue.

D-One

https://community.native-instruments.com/discussion/comment/191803#Comment_191803

I can't be 100% sure but I vaguely remember seeing a small number of reports initially when M1 Max/Ultra was still new, then it stopped. Yes, I guess it's probably some developer allocation mambo-jumbo, I often see devs talking about how complicated that stuff is for realtime audio on DAW's or DAW'ish SW.

It could just also be that Max and Ultra chips are much more rare in Audio thus the least tested, since mostly they offer more GPU power and not a lot of CPU advantages.

tkurfurst

By way of update I have been working with NI support teams to resolve this issue. After extensive analysis of system crash reports and NI diagnostics, it was proposed that I reduce my screen refresh rate (I am using a Gigabyte M32U at 3008x1692 144Hz) from 144Hz to 60Hz.

This resolved the instantaneous crashing, but in full screen mode the UI/UX was still very laggy (5-10 sec response times), so there is still an issues of some kind, but at least the Maschine 3.0 software is usable (as long as screen is set to 60Hz, and full screen mode avoided). So that is a temporary win. Hopefully NI will resolve this since I have not had these issues with any other software.

NI was quite responsive to this issue, and I do appreciate that, and hope for a deeper and more complete resolution of the issue in future updates.

D-One

https://community.native-instruments.com/discussion/comment/192040#Comment_192040

OH, wow. A few days ago i reported that Maschine 3 does not run at 60 FPS (on a 60Hz display), it more about 40, which makes it look a bit staggered and clearly shows screen-tearing on the playhead for example, it's def not due to lack of graphics power on my systems end; maybe these issues are related.