Bug using Beatstep Pro?

Hi I’m on VCV 2.0.1 on Ubuntu Studio 20.04, both up to date. I’ve been using VCV with a Microlab keyboard through the MIDI > CV module and all works as expected. However this evening I thought I’d try using my Beatstep Pro (BSP) as a a controller. I set up a simple patch with MIDI > CV and as soon as I start the BSP running i.e. sending MIDI, VCV crashes within a few seconds. This happens repeatedly, and on any MIDI channel. The same patch on VCV 1.1.6 works OK, so it seems to be something that has changed in the new version.

The log file looks OK when the patch is loading. The relevant part for the crash appears to be

[45.041 info src/patch.cpp:192 saveAutosave] Saving autosave /home/tim/.Rack2/autosave/patch.json [45.041 info src/settings.cpp:437 save] Saving settings /home/tim/.Rack2/settings.json [48.393 fatal adapters/standalone.cpp:60 fatalSignalHandler] Fatal signal 6 SIGABORTED. Stack trace: 13: ./Rack() [0x403ccf] 12: /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f308ae80210] 11: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb) [0x7f308ae8018b] 10: /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b) [0x7f308ae5f859] 9: /lib/x86_64-linux-gnu/libc.so.6(+0x903ee) [0x7f308aeca3ee] 8: /lib/x86_64-linux-gnu/libc.so.6(+0x9847c) [0x7f308aed247c] 7: /lib/x86_64-linux-gnu/libc.so.6(+0x9a0ed) [0x7f308aed40ed] 6: ./libRack.so(_ZN4rack4midi10InputQueue6tryPopEPNS0_7MessageEl+0xd5) [0x7f308b4a9d35] 5: ./libRack.so(_ZN4rack4core7MIDI_CV7processERKNS_6engine6Module11ProcessArgsE+0x82) [0x7f308b4dea22] 4: ./libRack.so(_ZN4rack6engine6Module9doProcessERKNS1_11ProcessArgsE+0xa15) [0x7f308b56a345] 3: ./libRack.so(_ZN4rack6engine12EngineWorker3runEv+0x199) [0x7f308b563fe9] 2: ./libRack.so(+0x81b730) [0x7f308b9ba730] 1: /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7f308ae20609] 0: /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f308af5c293]

Has anyone else found the same? Any ideas about how to fix it? Thanks

Edit - I’m using Jack to make the MIDI connections.

Hm… There have been a few instabilities reported on the forum involving Jack, but it sounds as though you were using that for the Microlab too?

There are also reports of crashes when a lot is going over MIDI (see here; apparently Support is already on it); can you monitor (with whatever the Ubuntu equivalent of midiox is–drumstick?) to see if a whole bunch of stuff is getting sent out by the BSP on connection?

Thanks gc3. Yes I am using Jack for all MIDI connections.

Further research:

Using a MIDI monitor, BSP is only sending note on / note off as you would expect.

The same happens when using the drum sequencer part of the BSP to MIDI > Gate in VCV - a few seconds then crash.

However using the BSP as a CC controller to MIDI > CC in VCV doesn’t crash, and that’s more data transfer, I would think.

To take the BSP out of the equation I created a repeated arpeggiated pattern in my DAW, Bitwig, and sent that to VCV the old way (not as a VST), with VCV as an external instrument to Bitwig and receiving to MIDI > CV in VCV. This doesn’t crash but is very flaky, speeds up and slows down and skips notes.

I’ll write all this up and send it in as a bug.