In standalone, when a Sysex from my master keyboard is sent to the mod-devel / arpeggiator v.1: 1.1-3 plugin the Mod Duo X freezes, it becomes unresponsive. If I am connected locally with the browser, I am disconnected, but I can reload the page.
How to reproduce
Load the Arpeggiator plugin, connect it to the Hardware ALL MIDI In
Connect the MIDI master keyboard through the USB port
Send a Sysex
Expected/suggested solution
This problem bothers me because I cannot configure my master keyboard otherwise, these are 4 non-configurable keys that I cannot do without (Shift, change of pad, octave- and octave +).
Hello. Very good idea, it works perfectly! Thank you so much.
I just noticed one thing, I didn’t know that when you connect a keyboard in USB there is no need to connect the MIDI patch, that is to say that as in my screenshot below, I can play with all this pedalboard as is. The “Hardware All MIDI IN” can only be used with a connection to a MIDI device? Thank you.
That is the “aggregated” midi mode, where all midi ins go through the same single cable, same applies to midi out.
You can click on the “MIDI” button in the bottom if you like to change to “separated” mode, which allows to connect different MIDI inputs to different things.
The default being “aggregated” just makes more sense, and it is easier to get things to work.
Any time the Arpeggiator plugin is turned on in a pedalboard, after some time (even if no MIDI notes are being played at all) all sound output will stop and it will lose Mod Web GUI connection. Input lights keep lighting up, output lights do not. Tuner no longer works. The rest of the UI on the Dwarf itself functions normally. If I click the reload button in Mod Web GUI, everything miraculously starts working again. Unfortunately, if the Wed GUI is not connected (oh like when I was on stage playing a festival show), the only way to resolve the issue is to restart the Dwarf. Loading a different pedalboard etc does not restore audio. Pedalboard layout doesn’t matter as I created a new pedalboard with just Arpeggiator and no connections and it will still “crash.” I also uninstalled and reinstalled the plugin.
How to reproduce
Turn on Arpeggiator
Wait (I tried timing how long and the times varied from 2:28-4:40)
So the workaround from the other report (MIDI filtering sysex) will save me! What’s odd (and I’ve run into this before) is that MIDI was still getting sent to the arpeggiator plugin even though it appeared that there were no MIDI cables connected to it. The author of the previous report was experiencing the same thing (I am also using USB) and it definitely happens sporadically.
I guess we can merge this with the other report since this bug has not been squashed yet?
Unfortunately, about a fix (and not a workaround) I’m not sure if there were any advances since this report.
Would the workaround “save you” for now?
Does it also happen when you are not using the “aggregated” MIDI mode, as @falkTX mentioned?
Filtering sysex before the arpeggiator totally works as a workaround!
I’ve never paid close attention when I’ve seen this bug happen. But only most recently it was in fact when in separated mode. I think it’s really just a UI glitch, there IS a connection there, but no cable is being displayed.
