huh… so far i’m only sending midi to my dwarf (1.13.2.3174) from an m-vave chocolate - it has not yet failed. does it still fail for you if you eliminate the hub?
m-vave Chocolate, novation ReMOTE 25SL, and Behringer BCR200, all through a Kopplen HUB-USB02SGR (4-port) hub into the Dwarf. i also had an expression pedal coming into the MIDI DIN input of the 25SL from a DIY MIDI controller - can’t use the expression pedal input on the 25SL because it’s currently on the fritz. i assigned various controls (including switches, knobs, faders, expression pedal, and keyboard) from each controller to do various distinct things in my pedalboard. i rebooted the Dwarf 10 times; everything worked flawlessly every time.
virtual midi loopback enabled, and ports in separated mode as you did.
one possibly interesting note: the Chocolate and BCR2000 were recognized and functional immediately after the Dwarf was rebooted, but i always had to unplug and reconnect the 25SL after Dwarf reboot before it was properly recognized and functional.
sorry i didn’t test output from the Dwarf to anything else.
Oh thanks for the tests !!!
I can’t reproduce the problem, it seams that it’s happening if I boot (or reboot) when the Dwarf is quite hot (75°C in the webUI)…
I didn’t try to downgrade too, I’ll take time to do it next week.
okay… I’ve reproduced the problem, in fact 2 problems :
my main pedalboard uses 83% of the CPU, it seams that when the Dwarf heats a bit, it doesn’t respond to midi messages. When it happens, if I switch to a 256 buffer, restart the, everything goes to normal.
when too many mini messages are send at the same time, the Dwarf take only 2 or 3 messages. I’ve put a delay time between each messages in the Morningstar configuration, and everything is okay when I set a 4ms delay.
