the direct USB connection between E1 and PC is solely used for editing presets.
all MIDI-traffic to and from the E1 is done via port 1 DIN MIDI into the MioXL MIDI router
that router is connected to the rest of the gear but also to the PC via RTP MIDI 1 and 2.
The Electra 1 (connected to MioXL DIN MIDI 2 here) routes its info not only to the synths and the second and third MioXL (via RTP Midi 9, and eventually 11), but also but to the PC on RTP Midi 2.
In other words: while the synths and the E1 are talking to each other, they also sent the same info to the synth for Midix-Ox to witness. But as this happens on a different port than the E1 programming port, I circumvent the lack of āmulti-clientā mode a PC has.
Yeah Mac users have had the multi client driver support for a while now, not just for midi but for audio with the aggregate something something (Iām on windows, obviously) that lets one combine soundcards into one mega-card as seen from the application using the driver. Luckily my soundcard has more I/o than Iāll ever needā¦ But also forces me to stick to windows
My Motu midi XT can only rename itās I/o on macās, another stupid windows USB limitation. Honestly a big inspiration for swapping it for a mioxl, along with all the usb-host capabilities.
Eager to see what CME comes up with their 19" interface under planning. I have a bunch of their u6 pro, and they are super flexible, good drivers and very low cost.
Via USB , you mean? Iām no longer USB to PC connections on the Mio but RTP-Midi: the Mioās interconnect as well when the PC is down (my PC not always turned on when making music).
But I do recall when I used USB it did show as multiple MIDI devices in my DAW too.
Thatās good news. The good thing: Iām using themxfor many years now and it has a certain stability so what the underlying capabilities are, I already forgot
I found that the listening function has a hard time to detect the right SysEX question and Response if they contain variables. Add the variables only at the end.
What I would propose: keep both questio sysex and reply header hardcoded (as in your example), check that the synth does respond, and now make sure via the listening function in the E1 editor, you see the reply coming in, ready to be parsed.
You then choose a patch for which you set up at least 3 parameters on 3 different values, known to you (for instance put VCO1 level on 3, VCO2 on 6 and Noise level on 9).
Then request that patch and in the webeditor check for yourself if you find those 3 values on the places you expect.
I managed to find changes with three parameters so far using the Sysex Librarianā¦ Will now try to see how to proceed with the receiving and sorting in the E One.
