Hm, I’ve always thought that H4MIDI WC has all the features of H2MIDI Pro and then some. Could be wrong. What in your view makes H2MIDI Pro more versatile than H4MIDI WC?
Also, all the ports that each of the connected devices exposes - those are defined by the device itself, righ? You don’t configure them manually? But then you can select, to which E1 “PORT” those ports are routed to?
Re. BLE MIDI - yeah, it could be tricky sometimes, I found out that using it for anything timing-critical could be less than ideal, but for simpler control tasks that are less time-critical, works fine.
CME seemed to me the most reliable ecosystem in BLE MIDI.
MIOXl… OMG, it’s a whole rack unit! )))
Typo. Its the H12MIDI Pro. 12 >> 4 > 2
And yes, the number of ports a device has is defined by the device (manufacturer). Some devices only have 1 port. The H12MIDI Pro has 8, the MC6 controller has 4.
1 Like
Ah, that’s a totally different story))) I was really excited when it came out, but I still have less MIDI-controllable devices than this thing has ports))))
My crystal ball says that will change
. I have some devices solely because E1 presets made them usable.
1 Like
Another quick question: I still can’t figure out whether the Detailed View is callable via LUA? The one that you get when you hold your finger on a fader, for example, when it fills in the entire screen? This is a super attractive UI mode for me, I’d love to use it much more actively and in a controlled manner.
I tried to map it to an external MIDI command, but it never worked.
1 Like
Not sure that is currently doable. But others (@Martin) will know.
1 Like