Jump to content

Recommended Posts

Just out of interest, are you guys using a real HUI. or is it another controller that uses the HUI protocol?

The reason I ask, is I was looking at implementing it in more detail.

I think I can do most of what the MCU supports without any issue, but it may be missing functions specific to the HUI controller that weren't migrated over to the MCU.

It's still early days though, and I'm unsure how much free time I'll have to work on it.

Share this post


Link to post
Share on other sites
On 6/3/2019 at 6:07 AM, msmcleod said:

Just out of interest, are you guys using a real HUI. or is it another controller that uses the HUI protocol?

The reason I ask, is I was looking at implementing it in more detail.

I think I can do most of what the MCU supports without any issue, but it may be missing functions specific to the HUI controller that weren't migrated over to the MCU.

It's still early days though, and I'm unsure how much free time I'll have to work on it.

Mike,

I don't have a controller so implementing HUI will not directly affect me at this time.  Traditionally, Sonar\Cakewalk has embraced controller protocol support.   HUI appears to be a comprehensive controller protocol that is enjoying new popularity among manufacturers.

Share this post


Link to post
Share on other sites
On 6/5/2019 at 2:15 AM, fogle622 said:

 HUI appears to be a comprehensive controller protocol that is enjoying new popularity among manufacturers.

Any reference for such statement?

Modern controllers usually do not support old protocols at all on hardware side (Ableton oriented, NI, Nektar), try to mimic completely (Behringer) or partially (Presonus, Icon, NI Machine) MCU. Some specify "HUI" in addition, just as "ProTools compatibility". Unlike "MCU" clones I have not observed "HUI" clones (note that original device has different from MCU physical layout).

Mackie and HUI protocols have fixed number of channel, no support for TFT displays, touch sensitive knobs nor colored LEDs. EUCON pretend to be more universal, but it is hard to support on both sides. In practice all that make no sense since controllers are connected with USB/Ethernet and so can follow whatever protocol they want (== what is cheaper to implement for defined set of hardware elements). The rest can be done in a proprietary (or open) driver (including conversion to old protocols, usually with limitations). F.e. Behringer while using Ethernet and sending MIDI messages throw it has not bothered to implement any "common" MIDI over ethernet solution. Why pay money for licenses, develop special firmware and get all sort of complains "your XXX implementation does not work with YYY?".

"Proprietary" is the trend in modern controllers. So "we do what we want, you are with us or we do not care about you" style.  The openness vary. Some give protocols for free (Ableton), some do not open anything (Nektar), other can allow you to communicated with the device throw proprietary driver if you ask kindly (NI).

 

Share this post


Link to post
Share on other sites

I have to agree with @azslow3 here.

There's nothing particularly comprehensive about the HUI protocol. It's incredibly chatty compared to MCU, and if you look at the history, HUI is basically a legacy protocol.

Mackie originally developed the HUI for ProTools. They then developed the Logic Control, which was later updated to become the MCU. The Mackie MCU & MCU Pro have backwards compatibility for HUI & Logic Control simply to provide an update path for those users.

HUI is a format for ProTools. Any manufacturer that supports it is only doing so for ProTools users.

If you do have a HUI only controller, then an implementation is not far off. I've got most MCU equivalent buttons, faders & metering,  and jog wheel working.

V-pot controls need more work, as does the the v-pot ring display & other displays, i.e. 4 char channel scratch display (and I thought 7 chars on the MCU was bad!!), and the time display.

If you're really impatient and can't wait, PM me and I'll let you have a  preview copy.

Share this post


Link to post
Share on other sites

BTW I have checked HUI with AZ Controller. I could only test with HUI emulation of Novation Nocturn (no display, only part of strip controls). I had to make AZ Controller more tolerant to mixed use of CC messages, but I had no problems otherwise.

Logic Control Protocol is officially (and openly) documented (in early Emagic Control documentation), but HUI is still "proprietary". Some manufacturers have failed to find Logic Protocol (f.e. initially Icon), I guess HUI implementation in some "compatible" devices is even worse.

  • Like 1

Share this post


Link to post
Share on other sites
On 6/5/2019 at 2:15 AM, fogle622 said:

Mike,

  Traditionally, Sonar\Cakewalk has embraced controller protocol support. 

jim, i have to respectfully disagree here - cakewalk (the company) stopped adding (new) controller support years ago, to the point where frustrated users convinced them to release the sdk so people like azslow3 could develop their own controller plugin...

/fwiw

Share this post


Link to post
Share on other sites
Posted (edited)

@pwalpwal,

I agree with you that the developers have not added support for an additional controller protocol in some time.  But we shouldn't overlook or dismiss the body of work performed in the past. 

A lot of time development will broadly focus on different areas.  The focus may shift as first audio is the primary focus, then the main focus may move to midi, then gui and so on.  Just because there has not been any recent Sonar controller protocol developments does not mean that future controller protocol development is not desired or planned.  We've already seen a Cakewalk poll asking forum members to vote and help set development priorities.

Edited by fogle622

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×