< Back to IRCAM Forum

Max crashes when loading a midi file

Hello

I cannot seem to load a midi file into a mubu container. The 16 channel midi file is generated using this python library GitHub - spotify/basic-pitch: A lightweight yet powerful audio-to-MIDI converter with pitch bend detection and it loads fine in a [seq] object.

Here’s the midi file in question:
basic_pitch_output.midi (28.7 KB)

And below is the stack trace from the crash.

Does mubu support reading a midi file with multiple channels? Any guidance would be appreciated.

Process:               Max [11412]
Path:                  /Applications/Max.app/Contents/MacOS/Max
Identifier:            com.cycling74.Max
Version:               8.3.1 [f487da5cc84] (8.3.1)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Max [11412]
User ID:               501

Date/Time:             2022-06-15 16:16:09.101 -0700
OS Version:            macOS 11.1 (20C69)
Report Version:        12
Bridge OS Version:     5.1 (18P3030)
Anonymous UUID:        2DCDED3E-B6E7-38EF-8AB2-137015185AC7


Time Awake Since Boot: 5700 seconds

System Integrity Protection: enabled

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

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000054
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [11412]

VM Regions Near 0x54:
--> 
    __TEXT                      105098000-105ed4000    [ 14.2M] r-x/r-x SM=COW  /Applications/Max.app/Contents/MacOS/Max

Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   mubu                          	0x00000001298e62ec read_channel_message + 428
1   mubu                          	0x00000001298bb119 midifile_read_track + 953
2   mubu                          	0x00000001298bab26 midifile_read + 2374
3   mubu                          	0x00000001298e593d mubuContainer_importMIDI + 1229
4   mubu                          	0x00000001298d6239 readFile + 3097
5   mubu                          	0x00000001298d255f mubucont_readBuffer + 511
6   com.cycling74.Max             	0x0000000105473200 defer_medium + 64
7   mubu                          	0x00000001298b170a readMethod + 202
8   com.cycling74.Max             	0x0000000105430c09 typedmess_fun + 377
9   com.cycling74.Max             	0x000000010541c112 outlet_anything + 1426
10  com.cycling74.Max             	0x0000000105430c09 typedmess_fun + 377
11  com.cycling74.Max             	0x00000001053faaaa aeval + 2314
12  com.cycling74.Max             	0x00000001053fa14e atombuf_eval + 142
13  com.cycling74.message         	0x000000010f782a17 jmessage_atombuf_eval + 567
14  com.cycling74.Max             	0x0000000105430c09 typedmess_fun + 377
15  com.cycling74.Max             	0x000000010541c112 outlet_anything + 1426
16  com.cycling74.dropfile        	0x000000010f770625 dropfile_out + 165
17  com.cycling74.dropfile        	0x000000010f7708e2 dropfile_drag + 658
18  com.cycling74.dropfile        	0x000000010f770332 dropfile_drag_drag + 82
19  com.cycling74.Max             	0x00000001053f46e0 object_method_imp + 352
20  com.cycling74.Max             	0x000000010511a6dc jdrag_process_dropitem_cb(_dragitem*, _dp_iter*) + 172
21  com.cycling74.Max             	0x000000010511a2b4 jdrag_process_drop + 836
22  com.cycling74.Max             	0x0000000105348151 jbox_dragdrop + 97
23  com.cycling74.Max             	0x00000001053f46e0 object_method_imp + 352
24  com.cycling74.Max             	0x0000000105119277 DragRecipient::filesDropped(juce::StringArray const&, int, int) + 231
25  com.cycling74.Max             	0x00000001057f32c2 juce::MessageManager::AsyncCallInvoker<juce::ComponentPeer::handleDragDrop(juce::ComponentPeer::DragInfo const&)::$_90>::messageCallback() + 98
26  com.cycling74.Max             	0x00000001056cc299 juce::MessageQueue::runLoopSourceCallback(void*) + 57

Thanks!
James

Hi James,
thanks for the bug report!
The crash is fixed now and a new release will be out in the next few days.
Best
Riccardo