This might not be the most pressing thing, but having to use hex values, and not having a ‘learn’ function makes dLive really annoying to work with when it comes to midi. I’m having a hard time understanding just ‘why’ it has to be this way. You don’t need to change any of the underlying functionality. Just change the user facing part of it. I can’t really think of any other product that forces you to have a hex lookup table to make it work. A learn function would of course also be welcome. Even if nothing else was changed, then at least you could address scenes with custom midi commands in an easier way.
(dLive should of course also support RTP/Core midi, but thats a topic for another time)
It would be very nice if A&H updated their “third party” control protocols. Not just Midi, also for other “industry standards” like OSC. It seems like the next logical update if A&H wants the DLive system to remain competitive in today’s environment where interconnectivity is becoming more and more important.
It should be OSC, like everyone reasonable - unfortunately the folks working on DLive have consistently taken a “why on earth would you want that? We have MIDI!” Attitude.
being able to trigger the console using plain text commands in OSC from Qlab is a very common setup for many consoles, we need it on DLive as well.