Rack crashes when quitting with Akai MPK Mini


I’m new here, and to modular in general (be gentle!). I’ve been happily playing with VCV Rack standalone on my Macbook for the last few weeks, downloaded a few free modules - everything’s been fine.

In the last couple of days, I’ve plugged my Akai MPK Mini in for the first time. That first session, everything worked smoothly - I managed to do some MIDI mapping. But when quitting that session, and ever since then Rack is crashing all the time. It freezes when I choose I different audio out option, attempt to delete the Audio-8 module, or when I try to quit the app. I had installed MPC Beats when I got the MPK - on the first day both Beats and Rack were open at the same time, which I’ve read contributes to the crashing. But on a computer restart and opening only Rack, I get the same thing.

I don’t think it would be certain modules like vertibration’s issue, as everything was working fine before. I’ve even done a clean uninstall and reinstall just in case - and rebooted without the MPK plugged in.

This is what I’ve got:

  • mid-2012 Macbook Pro running 10.14.6
  • latest version of VCV Rack 1.1.6
  • Akai MPK Mini mk3

Excerpt from Log File after freezing when trying to delete Audio-8 module (routing to standard Mac output 1-2, no Midi device connected):

[94.023 info src/window.cpp:72] Loaded SVG /Users/bronto/Documents/Rack/plugins-v1/Valley/res/PlateauPanelLight.svg
[102.514 info src/audio.cpp:302] Stopping RtAudio stream 2
[156.760 fatal src/main.cpp:45] Fatal signal 15. Stack trace:
18: 1   Rack                                0x000000010f4d23cd _ZL18fatalSignalHandleri + 45
17: 2   libsystem_platform.dylib            0x00007fff7fb43b5d _sigtramp + 29
16: 3   CarbonCore                          0x00007fff54c2a411 TSLockMutex + 300
15: 4   Rack                                0x000000010f7cc525 _ZN9RtApiCore10stopStreamEv + 133
14: 5   Rack                                0x000000010f4af7c5 _ZN4rack5audio4Port11closeStreamEv + 117
13: 6   Rack                                0x000000010f4b0078 _ZN4rack5audio4Port11setDeviceIdEii + 24
12: 7   Rack                                0x000000010f50e524 _ZN4rack4core18AudioInterfacePortILi8ELi8EED2Ev + 36
11: 8   Rack                                0x000000010f50d4a5 _ZN4rack4core14AudioInterfaceILi8ELi8EED0Ev + 69
10: 9   Rack                                0x000000010f4fcea8 _ZN4rack3app12ModuleWidgetD2Ev + 40
9: 10  Rack                                0x000000010f50f01e _ZN4rack4core21AudioInterface8WidgetD0Ev + 14
8: 11  Rack                                0x000000010f530619 _ZN4rack2ui8MenuItem10onDragDropERKNS_5event8DragDropE + 73
7: 12  Rack                                0x000000010f4cc9c1 _ZN4rack5event5State12handleButtonENS_4math3VecEiii + 417
6: 13  AppKit                              0x00007fff510bd01a -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 1899
5: 14  AppKit                              0x00007fff510bc667 -[NSWindow(NSEventRouting) sendEvent:] + 478
4: 15  AppKit                              0x00007fff50f5be4b -[NSApplication(NSEvent) sendEvent:] + 331
3: 16  Rack                                0x000000010f5aaaad _glfwPlatformPollEvents + 109
2: 17  Rack                                0x000000010f4e9e0b _ZN4rack6Window3runEv + 139
1: 18  Rack                                0x000000010f4d1efa main + 1434
0: 19  Rack                                0x000000010f46b034 start + 52

I’m convinced it’s something to do with MIDI. Any help is appreciated, thanks for taking the time to read.

By any chance, do you have multiple Audio-* modules in your patch? The behavior you are describing sounds like it, and this scenario is not supported in Rack v1.

1 Like

Hi Ben,

Yes - I did have more than one Audio-* module in there, I noticed the audio would only come out of the original module set up with the default patch, and not any additionals. Ironically, trying to delete the extra ones was what was crashing me. What a simple fix - I’m all sorted now, thanks so much for your help!

  1. Please don’t hijack other people’s threads with a different question/issue.
  2. See Bugs and Features for properly reporting bugs and requesting features.
  3. Don’t paste log output as text. Either attach the file or format it as code with ``` surrounding it on each line.

I have moved and edited your post, but remember these for future posts.