I am not sure what that means, but it seems like there is some fatal errors, but not 100% sure what to make of it.
Is it because I might be overloading the Gate>Midi module?
When I disconnect the inputs for that midi module the patch loads fine, but then I don’t get the LED feedback I’d like. I am updating all 16 outputs at once, to get 2 radio buttons of 8 each.
Any tips for understanding the log.txt is appreciated!
Looks similar to a crash I found caused by a bug in Rack’s RTMIDI wrapper. I reported the bug and provided a fix, but VCV hasn’t released the fix (and I don’t know if they plan to). I posted the description of the issue and the fix a while back, but I can’t find the post.
I’ve send a report to VCV support, with description and link to this thread, hopefully they will look into it, since you also reported some issues with the RT midi wrapper.
The LED feedback is kind of important, when trying to build a more hands on setup with midi controllers and you can’t really do that, without sending lots of data. Pure Data does this pretty well.
Huh I’ve occasionally ran into this recently too working on a MidiThing V2 bridge (essentially sending channels of CV using tons of pitch bend messages). @pachde / @Jaffasplaffa - keen to hear if you hear anything from VCV support.
So I’ve been in contact with support, they are asking for log and so on, which I will provide.
Meanwhile, I think I got a little bit closer to understanding the issue. It’s not actually the patches itself that’s the issue. It’s when I load patches with a complicated midi setup, right after each other. So if I have one patch with a complicated midi setup and I load another patch with a complicated midi setup, I get that error and Rack crashes.
If I have a patch with complicated midi setup and then first load an empty patch and THEN loads another patch with complicated midi setup, it works fine.
At least that’s what I experience, when I load an empty patch in between the patches that have complicated midi setups, it works.
I’m pretty sure @pachde has an understanding of why and a fix linked above. Or if you mean how to trigger it, then just sending lots of midi and waiting a long time (it’s rare).
If it happens to actually be the same issue, yes. If you have a consistent repro case, and you can build Rack, you can verify if my fix works or not. Fix is given in the linked thread.
I wasn’t able to provide a consistent repro case, because my plugin requires hardware that VCV likely don’t possess.
If you can provide a consistent repro to VCV support, it’s more likely VCV will fix it.