Glenn Venghaus wrote:Alhough can not be sure , it does sound like a configuration problem. As i have, beside the full home cooked controller functions based on this protocol, also tried a few ipad apps that simulate mackie hui and they all work fine over network midi.
Thanks, this is not a 'real' HUI, is a Mackie MCU (& extender) running in HUI emulation mode; HUI is an ancient surface that Mackie once made for Digidesign). Also are v1 MCUs (MIDI, not USB) and so this hooks in via a 8 port ESI M8U-XL interface. All studio MIDI /USB ports are seen and used by ProTools, Nuendo etc, i.e. Windows aware of all, are named consistently, and can pump data around, sync etc as per various MIDI monitors and application configurators confirm.
Akai Avance 61 (2 MIDI ports)
Mackie MCU - ESI 8x interface, port 3
Mackie MCU extender - ESI 8x interface, port 4
Ableton Push, G-System, Avid 11R
In other words: anything MIDI in the studio can talk to anything else, either hardware or software.
Update then:
The port nomenclature in the list identified by Resolve is a bit garbled. It starts counting from other devices and so (say) 'MIDI port 3' I/O is not named & routed sensibly (Resolve sees this as port 5). In this case, the first two MIDI ports Resolve happens to find are from an Akai Advance 61 & so it continues to count down the other 8x ESI rack mount ports, then on to Ableton Push etc. In the case of the MCUs they connected via ESI ports 3 & 4, Resolve identifies these as '5' & '6'. That's on the way in. On the way out is further confused by another Microsoft MIDI rabbit of some sort ...
Anyways, patch in the right ports in Resolve & the MCU-HUI faders do work. Nothing on the transport panel as yet: play, stop, rewind, scrub, zoom etc are dead.