Architect.MIDI crashing in Logic Pro when saving preset

[d3zd3z]

I was just trying to test a few things before purchasing, and went to save a simple preset. When I do so:
"An Audio Unit plug-in reported a problem which might cause the system to become unsable. Please quit and restart LogicPro".

This is on an Apple Silicon Mac.

I'm not sure where the preset is getting save to tell if it crashed before or after actually writing the file.

[d3zd3z]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

The fault seems likely to be a null pointer exception from the plugin:

Code: Select all (#)

Process:               AUHostingServiceXPC_arrow [39778]
Path:                  /System/Library/Frameworks/AudioToolbox.framework/XPCServices/AUHostingServiceXPC_arrow.xpc/Contents/MacOS/AUHostingServiceXPC_arrow
Identifier:            com.apple.audio.AUHostingService.arm64e
Version:               1.0 (1)
Build Info:            CoreAudioServices_AUHostingServiceXPC_arrow-1456345000000000~8
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
Responsible:           Logic Pro [39764]
User ID:               501

Date/Time:             2025-01-20 17:48:04.7893 -0700
OS Version:            macOS 15.2 (24C101)
Report Version:        12
Anonymous UUID:        6382C293-F4A7-4D5C-1557-19F9D30591D6


Time Awake Since Boot: 630000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000090
Exception Codes:       0x0000000000000001, 0x0000000000000090

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [39778]

[colin@loomer]

Ok; let me see if I can work out what is going on here. Which version of logic is this?

[d3zd3z]

Logic Pro 11.1.2, on an M3 pro MacBook Pro.

[colin@loomer]

Thanks for the info. I'm just building the latest 0.10 with some upstream fixes, and I'll PM you the build. If this still has the issue, I'll look into a build with additional logging.

[colin@loomer]

... actually, I have managed to reproduce this issue. I'll PM you shortly.

[Soman]

Thanks for the info. I'm just building the latest 0.10 with some upstream fixes, and I'll PM you the build. If this still has the issue, I'll look into a build with additional logging.

Could you PM me this build, too, please? I have mentioned this bug four or five years ago and I‘m glad it has been fixed now.

[twofold]

Could someone please share this build?

outtrig (at) gmail.com

Looks like waiting for any further updates is futile.