Ok, for the first point, everything is clear. And Pan and Send A to E woks as expected. But there is a problem with the flip function. I checked it with midi monitor and everything seems to be fine. In "flip" mode the encoder one sends: CC 0 and 32 (100% = 0/127 and 32/127) If I compare it to the fader of the Alphatrack CC 0 and 32 (100% = 0/127 and 32/96) I see just the difference in the 100% value of CC32 ! But anyway, I can't control the protools fader with the encoders of the push in "Flip" mode !
Thanks for the info. The value difference you pointed out there should, at worst, result in incorrect volume values being set. So something else is going on here. FWIW, the flip function works as it should in Reaper, which is what I used to develop MCU To HUI. I'll get First installed ASAP and see if I can track down the problem.
HI Stray, after more or less a year, I think it's time to ask again, if you had the time to "push" this one a bit? I can imagine, that the group of users, who like to use push2 with protools 12 is a small group, but you can make these people extremely happy, if you can find a solution to use push2 in hui mode, or eucon maybe ?
Sorry to resurrect such an old thread and be somewhat off-topic on top of it... but I'm looking for a HUI to MCU mapping translation for Logic, and was wondering if the solution you were working on for Pro Tools could somehow be used for Logic as well (e.g. does this run standalone via a virtual MIDI loop and translates between the incoming MIDI before it is sent to Pro Tools, or is it some sort of plug-in or script that Pro Tools would access directly, and that wouldn't work for Logic?)
Of course Logic supports MCU natively, but on the controller I'm using it becomes apparent that Logic's MCU implementation has extremely buggy metering (works fine in other DAWs with this controller). In HUI mode, the meters respond just fine. You wouldn't notice on a real MCU since the meters on the LCD are pretty useless to begin with, but my controller has a 24 LED chain for metering per channel, and the problems become blatantly obvious.
Somehow Logic won't allow me to re-map the controls myself, if I try to use the HUI protocol because of the meters, but change the buttons etc. to the same values that the MCU uses (and use MIDI learn to assign whatever the HUI would send for that button). Parameters that are changed (even if correctly) just stop working.
In short, if this app would allow me to use the HUI protocol in Logic, but keep the functionality of the buttons on the hardware controller the way it is mapped for the MCU protocol, this would be perfect.
If you're curious, the controller I'm using is a Mackie d8b digital console, with piece of hardware called a "Probox" connected to it, and the other end goes via USB to the computer. This makes it appear as a MCU with two extenders to Logic (in fact, I have two d8b's/proboxes, emulating 6 Mackie Control units and providing 50 motor faders). Everything works great, other than the meters.
I wouldn't exactly be able to alpha-test this for Pro Tools, but maybe this could expand the functionality of this HUI->MCU translator to other DAWs as well (??)
Welcome to the forum. On the first question, yes, the translation is done in a standalone application (called MT Player) so it could be used with any application that supports the HUI protocol. For example, it was actually developed using Reaper and not PT. However, it wouldn't help with what you're trying to do here.
For your purposes, you don't need translation, you need to use alternate MIDI routing and filtering from Logic to the controllers via some application that could handle such a task (Bome's Midi Translator Pro for example). The routing from the controllers to Logic would remain the same as that has nothing to do with metering.
The routing chain from Logic would look like this: Logic MCU out ---> router in (let all data pass except meter data) ---> controller in Logic HUI out ---> router in (block all data except meter data) ---> controller in
Logic would send MCU/HUI data to virtual ports (such as IAC), which you'd connect to the router app and that would send the filtered data to the controllers.