Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
AURIA Pro and MCU/HUI utilization and mapping : help needed !!!
Hi, I'm completely lost with MCU/HUI mapping in order to control Auria Pro. I recently bought a BeatStep Pro, without knowing it was compatible with MCU/HUI protocol. Before, I was using a NanoKontrol 2, super easy to use (nothing to configure, just switching it to Protools mode), all the main transport controls and 8 faders. So I was positively surprised to discover that the BSP was compatible with MCU/HUI protocol, and better, controls could be mapped with the dedicated desktop application. For those who own an Arturia device, the MIDI Control Center is very efficient and easy to use. I made lots of maps for my MiniLab, so I know the basics of MIDI CC and to map a midi controller. But with this MCU/HUI protocol, I don't understand a single thing. Even with BSP MCU/HUI chart, I feel like reading a papyrus. So far, I wasn't able to move a single fader or pot, and even the transport controls behave not as expected.
I really don't want to give up, the NanoKontrol 2 has been a significant plus to my workflow, so I imagine the BeatStep Pro with an appropriate mapping, combine to all its CCs will be a great boost.
So, if some of you are in my situation, knows how to configure MCU/HUI controls, especially on a BeatStep Pro, or if I could just benefit from someone's experience with this particular midi protocol, I would really appreciate it !
Thank you...
If you don't know the BeatStep Pro but are used to work with MCU/HUI , here's BSP MCU/HUI chart :

Comments
the Mackie protocol is sysex based, so you may check if some sysex filter is active in your midi routing
and of course the midi interface has to support sysex - an Alesis ioDock 1 does not (as an example)
if both topics are checked and it still doesn't react, the main suspect would be the Beatstep
the MCU/HUI protocol is quite delicate - it's not so rare that it's not properly implemented
cheers, Tom
Thanks Tom for your answer. I confirm that the BeatStep Pro support sysex. In the Midi Control Center, Arturia desktop application which allows you to configure and map all their midi controller-, there's a midi console, very helpful feature, which describe in detail every move you make on the controller : so you know which cc number or midi note goes where and on which midi channel or midi port. And I saw this sysex term written on many occasion, so the BSP handles it.
But what I really can't understand is the MCU/HUI chart of the BSP ! Since I never deal with this protocol before, I don't know what the words means and to what they refer to. I realize that the file attachment didn't work on my post, this was the MCU/HUI chart. I'm gonna post it here and if you are familiar with its terms, maybe you will be able to give me some clue !
My understanding is Auria Pro does not respond to midi cc messages - only Mackie messages. (FYI, sysex is short for system exclusive; midi messages specific to certain devices). I don't have the beat step, but if it can be put into a default MCU mode it should work with Auria. From what I've read you may need to try both of the mackie protocols options in Auria, and make sure receive remote is checked (both in the AP midi settings).
You may also want to post over at the Auria forum - Rim is quite responsive and may have specific info for your set up.
Best of luck!
@cyril777 the table is just the mapping of 8 switches (vpot1-8) to Midi CCs and the mapping of the faders to pitch on 8 different channels, probably useful only in own programming
it doesn't help much in context of a control surface
cheers, Tom
Thank you both for your help. The BeatStep can be set to MCU or HUI with its desktop application, so I will switch it to MCU and continue to try from there !
About the table, I had the feeling it wouldn't help me... even if I didn't understand it !
Auria is very fussy about how it's controlled. It's well documented on the Auria forum. There is an update coming which will make it more compatible but I could not vouch for it for sure working. I have been trying for some time now to get my behringer Xtouch mini to work with MCU. I can control the faders from Auria but not the other way???
Maybe Rim the author of Auria will one day get this fixed for those of us who want to use external mixers in this way.
Korg nanokontrol 2 works well, presonus faderport also works.
Db
I bought the NanoControl 2 just for Auria because of its MCU/HUI compatibility and it works like a charm. And it's very useful with AUM too. And no need to use a desktop application to switch the NanoControl from a MCU config to a classic CC config, you just need to press 2 button when you plug it... couldn't be more simple.
I would come back to my nanokontrol 2 without an hesitation but I changed my configuration and I don't use a USB hub anymore, so I would have to by something like the iConnectivity MIO and it kind bothers me... having a brand new BSP...