Apologies for not explaining well – it was an off-hand comment in another thread, not actually a support request.
I’ve already got a USB midi router – Bome Box in my case, but it’d be the same with e.g. the iConnectivity hardware. That box has a dozen or so DIN and USB midi devices on it, and I want to be able to change which devices are routed through the MidiHub on the fly (easy, with the Bome and a tablet), using the MidiHub USB inputs and outputs, and possibly also use the MidiHub to add DIN ports to the Bome. I’d like to be able to reconfigure the MidiHub without needing to unplug stuff, and test configurations with USB attached devices while I’ve still got the editor set up. I’m not interested in replacing my functional and already latency optimized midi router with a raspberry pi that I have to manually turn into a midi router. If I wanted to go anything like that route, I’d just rewrite the MidiHub pipelines I care about in Lua and run those on my Electra One (which I may in fact do).
If the editor ran over sysex, I could have the Bome set up a network midi connection to a laptop, which would be running at USB speed and be at least as performant as the USB serial link they use, and would also add the possibility of expanding beyond the eight internal presets. Blokas’s stated reason for not enabling the editor via Sysex is performance, and I guess if you were running it over DIN, it would be a bit slow – but still better than nothing. Given that USB midi routers exist, though, it’s a pretty silly stance.
Really, I just wish we could ditch USB and DIN entirely and move everything to ethernet, but that’s a different rant.