GP4 Crashes on MIDI Learn on Helix Native

Gig Performer on Mac OS X
1

Hi all,

Forgive me if I’m doing something wrong here. I’m using MacOs Ventura v13.6.5, Mac Mini M1. I have the Helix Native plugin (AU) I have an Expression Pedal assigned to volume positioned just before the delay and reverb so that if I heel down the volume the trails continue to be heard and fade out. On my floor helix this works great but when I try to add the exp volume pedal via the learn function GP4 always crashes out and I have to reload it again. The same happens on my Macbook M1 with any audio device I connect, GP4 always crashes. I am using GP 4.8.2.

If GP4 cannot insert MIDI messages half way through my FX chain then I’m not sure how this can be done. I may be missing a trick or something important here so I appreciate any advice.

Thanks.

2

Please post crash report. While GP4 is legacy now (we’re at GP5) it shouldn’t crash while learning.

3

Translated Report (Full Report Below)

Process: GigPerformer4 [13333]
Path: /Applications/GigPerformer4.app/Contents/MacOS/GigPerformer4
Identifier: com.deskew.gigperformer4
Version: 4.8.2 (4.8.2)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-02-18 13:51:23.1040 +0100
OS Version: macOS 13.6.5 (22G621)
Report Version: 12
Anonymous UUID: 2CB42AEC-0DCB-DB3F-6A08-56D5DA87B618

Sleep/Wake UUID: 73AEF978-18ED-4D74-ABE9-D954F6DEFBF1

Time Awake Since Boot: 48000 seconds
Time Since Wake: 8064 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: GigPerformer4 [13333]

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x183df4704 __pthread_kill + 8
1 libsystem_pthread.dylib 0x183e2bc28 pthread_kill + 288
2 libsystem_c.dylib 0x183d39ae8 abort + 180
3 libsystem_c.dylib 0x183d38e44 assert_rtn + 272
4 HelixCocoaView 0x11528458c 0x114a14000 + 8848780
5 HelixCocoaView 0x114e83f40 0x114a14000 + 4652864
6 HelixCocoaView 0x114f721e4 0x114a14000 + 5628388
7 HelixCocoaView 0x114f998dc 0x114a14000 + 5789916
8 HelixCocoaView 0x114f9887c 0x114a14000 + 5785724
9 HelixCocoaView 0x114f976b0 0x114a14000 + 5781168
10 HelixCocoaView 0x114d74320 0x114a14000 + 3539744
11 HelixCocoaView 0x114afbf88 0x114a14000 + 950152
12 HelixCocoaView 0x114f9a398 0x114a14000 + 5792664
13 HelixCocoaView 0x114f99d10 0x114a14000 + 5790992
14 HelixCocoaView 0x11503c444 0x114a14000 + 6456388
15 HelixCocoaView 0x114e844a4 0x114a14000 + 4654244
16 HelixCocoaView 0x114b160cc 0x114a14000 + 1056972
17 QuartzCore 0x18b4159ec CABackingStoreUpdate + 480
18 QuartzCore 0x18b470480 invocation function for block in CA::Layer::display() + 64
19 QuartzCore 0x18b414958 -[CALayer _display] + 1632
20 QuartzCore 0x18b413ae8 CA::Layer::display_if_needed(CA::Transaction*) + 760
21 QuartzCore 0x18b5874d4 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 456
22 QuartzCore 0x18b3f62c0 CA::Transaction::commit() + 648
23 AppKit 0x187259108 __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 272
24 AppKit 0x187935a34 ___NSRunLoopObserverCreateWithHandler_block_invoke + 64
25 CoreFoundation 0x183f09960 CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 36
26 CoreFoundation 0x183f0984c __CFRunLoopDoObservers + 532
27 CoreFoundation 0x183f08e84 __CFRunLoopRun + 776
28 CoreFoundation 0x183f08428 CFRunLoopRunSpecific + 612
29 HIToolbox 0x18d75edf0 RunCurrentEventLoopInMode + 292
30 HIToolbox 0x18d75ec2c ReceiveNextEventCommon + 648
31 HIToolbox 0x18d75e984 _BlockUntilNextEventMatchingListInModeWithFilter + 76
32 AppKit 0x187130134 _DPSNextEvent + 636
33 AppKit 0x18712f2d0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716
34 AppKit 0x187123734 -[NSApplication run] + 464
35 GigPerformer4 0x100cb4578 0x1006d0000 + 6178168
36 dyld 0x183ad3f28 start + 2236

4

OK as suspected, the crash is being caused by HelixCocoaView, not by Gig Performer. See bold items below. You should report this to the Helix developer.

Also, try using the VST or VST3 version rather then the AU version

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

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x183df4704 __pthread_kill + 8
1 libsystem_pthread.dylib 0x183e2bc28 pthread_kill + 288
2 libsystem_c.dylib 0x183d39ae8 abort + 180
3 libsystem_c.dylib 0x183d38e44 assert_rtn + 272
4 HelixCocoaView 0x11528458c 0x114a14000 + 8848780
5 HelixCocoaView 0x114e83f40 0x114a14000 + 4652864
6 HelixCocoaView 0x114f721e4 0x114a14000 + 5628388
7 HelixCocoaView 0x114f998dc 0x114a14000 + 5789916
8 HelixCocoaView 0x114f9887c 0x114a14000 + 5785724
9 HelixCocoaView 0x114f976b0 0x114a14000 + 5781168
10 HelixCocoaView 0x114d74320 0x114a14000 + 3539744
11 HelixCocoaView 0x114afbf88 0x114a14000 + 950152
12 HelixCocoaView 0x114f9a398 0x114a14000 + 5792664
13 HelixCocoaView 0x114f99d10 0x114a14000 + 5790992
[/quote]

5

Thanks for looking into this. One would assume to use the AU instead of VST version, I’ll try this when I return back and get back if there’s still a problem. Many thanks.

6

Why? If that was true, then why would companies release VST versions for the Mac?

Remember that Apple’s products are the only ones that only use AU. Other DAWs and live performance hosts that run on Mac are perfectly fine with VST/VST3

More importantly, because the VST versions run on lots of hosts (and on Windows as well), they tend to get tested far more deeply whereas the AU versions typically only get tested with Apple products

1 Like
7

Yes, I never thought of it like that, thanks for the suggestion. I have just tried the VST3 and it does not cause GP to crash. From now on I’m using the VST3 version.

Much appreciated :+1

1 Like
8

I would encourage you to move all your plugins to the VST or VST3 format. Also, be very careful with AUs that are still Intel only as that will cause Apple to automatically load Rosetta and there are absolutely no guarantees that interaction between a Rosetta translated plugin and a host will work flawlessly.

9

You should still report the issue to the Helix developer, letting them know that VST version works fine.

10

Yes, reported to Line 6, not sure if anyone will take action.