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.
M AUDIO to AUM via Digitone - Button cc not being sent
Hi all,
Anybody have experience mapping buttons on this controller to control the transport in AUM?
I’ve gone through the manual to program the button to output midi messages but so far I can’t get it working. My midi monitor app shows the keyboard sending messages but nothing from the buttons, even after I change their midi channel and midi cc number.
I’d really like AUM to be my brain to the setup, but I don’t want to have to press play on the iPad screen.
I’m sure there’s a simple step I’m missing, bearing in mind this is the controller who’s default setting was to disable midi out!
Thanks!
Edit: title change - through some great advice here, I’ve worked out this is an issue in the Digitone. Read further down for more info.
Comments
@jameslondon74 You're right, it looks pretty simple. The only gotchas I can see are: are you using the preset where you edited the CCs, and is the Button Mode button set to MIDI (red)?
Does your keyboard have more than one virtual MIDI port? Some MIDI devices show up on the iPad as 2 devices -- one that sends notes and one that sends transport and other messages.
You may want to contact M-Audio support.
I think the transport on the code is a mackie kind of thing and can't be changed. I use the mappable buttons below the faders on my code 25 to start/stop/record.
Are you pointing to the midi control on right of aum matrix.
Well, thanks for all your helps... I may have just uncovered another issue that’s causing problems.
My problematic setup:
MAudio (midi out) to Digitone (Midi In)
Digitone (usb) to iPad (usb)
This setup has no response from the buttons, nor is there any other options in AUM. The only midi input in AUM that works for the keyboard is to select ‘digitone’ in the list.
However! when I connect the M AUDIO directly into AUM via usb, several different M AUDIO options suddenly appear in the AUM list, and when I select M AUDO MIDI, all buttons work perfectly.
So... why dont the button functions (and I assume others) work via Digitone? Ive looked at all the digitone midi settings, consulted the manual, tried several different settings and I can’t seem to figure it out.
According to the manual, all the buttons can be set to MIDI mode. It looks like each button has to be manually set.
@jameslondon74 : are you certain that you have set the buttons to the right mode onnthe Code 61? check with a midi monitor in your iPad to see if any buttons, knobs and faders are sending data.
Which MIDI Monitor are you using?
I’ve definitely programmed the button correctly, because it works fine when I connect the M-AUDIO directly to the iPad.
It’s only when I go via the digitone that it doesn’t work.
Instead of mixing 5-pin MIDI and USB MIDI, you probably want to use a USB hub, and connect all your devices by USB.
The problem with 5-pin MIDI is the way the connections work. MIDI IN on the Digitone means messages will end at the Digitone. The Digitone USB interface probably sends messages initiated by the Digitone, and receives messages to control it, only. The Digitone is likely not a MIDI to USB converter/interface.
I was assuming that you you had your Code 61 connected to the ipad. If I understand what you last implied, your question doesn't really relate to AUM. The issue is how to configure your devices so that the MIDI from your code 61 makes it to your ipad. You might want to re-title the thread.
If the Digitone is sitting between your Code 61 and the iPad, you will need to dig into the Digitone manual. Also, you might need to play with the code 61 configuration to make sure it is sending MIDI ccs out the Midi Out port...I think I read that the default setting is Off for that, but I could be wrong.
Yes it’s definitely not an AUM issue.
I was hoping I could use midi thru but not sure. I’ve posted this on the Digitone forum. Let’s see.
Thanks all.
Have you enabled MIDI out in your Code 61 to ensure that the CCs are making it to the Digitone?
Can you change the title of this thread to remove the AUM reference? A more accurate title might also attract the attention of someone that knows the best solution.
@jameslondon74 - this post may help you. Note the "Midi Thru" reference to page 60 of the manual. Apparently the Digitone has midi thru provided the signal is received via DIN connection to it. At least that's what it seemed like to me was being said: https://www.elektronauts.com/t/send-clock-over-midi-out-and-midi-thru/61898/8
However, if you can connect your Code 61 and Digitone to a hub that might be better. Unless ... you need to control the Digitone from the Code 61. That wouldn't work from a hub.
Done.
Yes I’ve enabled Midi out. The keyboard works fine. It’s just anything ‘non keyboard’.
Yeah it seems like I’ll need a hub to do this properly. I did read the manual this time
It’s just puzzling to me that ‘MIDI data’ doesn’t seem to include all cc messages. I’ve tried all combos of the midi settings to no avail. So hub seems to be the way forward.
As I said, conventional MIDI hookups are basically "one hop", except for MIDI THRU, which just passes all the input on. The problem with doing what you want is that it would have to merge data streams, and handle collisions. That would require buffering, and a computer dedicated to handling MIDI. You can get USB MIDI interfaces which do all that, but since your gear all handles USB, a hub is the simplest solution. Apps like AUM will then see your devices as different MIDI inputs and outputs, so you can do any routing you need.
Cool. I understand. Out of interest, seeing as you seem to know a lot, would you recommend anything or have anything as an example. I’m a bit of a novice, sorry.
Think we’re talking about these transport ones:
I’ll keep an eye on the thread as I’d love to use em. Probably possible to do something with Mozaic for specialist cases if nothing else.
I think the mackie protocol that the code controllers use for transport might be bi-directional? Not sure really. Never got those transport controls to do much that I found practically useful — I’d have loved to set them to CCs or program changes or something too.
Pretty sure you can't map CC to the transport controls. They are dedicated to Mackie or HUI.
Sure. Only suggestions though; what works for me. First, I assume that you already have a USB adapter for your device, so all you need is a plain USB hub. The landscape can be more complicated if you have a USB-C (not Lightning) iPad, and want some kind of multifunctional dock.
So, if your gear draws relatively low power, or uses separate power supplies, you can probably use a generic passive (unpowered) USB hub. I got my 4-port years ago at Best Buy, and it worked fine until I needed more power. If your USB adapter also has a power connection, like the Apple USB-3 Camera Adapter, connecting a charger to it can supply a little more power for the gear. This handled two MIDI keyboards and a separately powered DAC. When I added another MIDI controller, it kicked me over the edge.
Alternatively, if you need to power your gear from the USB, you may want a powered hub. These have their own power brick, capable of supplying significant juice. I have the Atolla 7-port powered USB-3 hub, which works great. It even includes a 12-watt charging port for the iPad, so one power brick does it all. If you don't need 7 ports, there's a slightly cheaper 4-port model.
My safe startup method is to get everything plugged and powered without the iPad. Then I make the Lightning connection to the iPad last. That way, the gear is ready when iPadOS tries to connect to it, so there's no confusion.
With this setup, apps like AUM will see your various MIDI devices, and you can route their MIDI in the usual way. This gives you another level of separation over the normal MIDI channels.
Amazing, thanks uncle Dave. really helpful.