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.
Lumbeat MIDI In Control workaround
For anyone interested in using MIDI in to control Lumbeat apps, I've figured out a workaround for my own setup, which is a 2021 iPad Pro M1. In my case, I could not get the note based MIDI in controls to work using either virtual MIDI via AUM and Surface Builder, or via an external MIDI keyboard. The CC and PC commands work fine. I verified the MIDI data being sent to the app via a MIDI monitor app in AUM.
I had to use notes that were one octave above what's listed in the app - for example G3 triggers play instead of G2. I've reproduced the behavior on Soft Drummer, Funk Drummer and also Hip-Hop Drummer (which I love - the flex feature is great).
I emailed the dev and submitted a bug report a few days ago, but have not heard back yet, so wanted to put this out there to see if others are observing the same. If you look at the attached screenshot I've mapped out most of the changes that are working for me. I was not able to test out all of them yet, but I suspect they are the same. I saw an old post from 2021 in this forum about this issue, so it seems that at least some people are using the MIDI in feature.
Comments
Btw, octave numbering is not part of the midi spec. since the beginning there have been two common numbering systems because Roland’s and Yamaha’s — some apps and hardware use a third .
When using numbering, you need to know which numbering convention is being used and adjust accordingly.
@espiegel123 - An excellent point. I was going off of what other apps were using and MIDI reference tables from the internet, so this is a good tip for others in the same situation. I imagine the reference/help info in the app should list the MIDI note number as well as the note name, to avoid any confusion.
There are plenty of apps on iOS that disagree about what octave middle C is. Middle C is note 60 by definition. Audiobus calls that note C3. AUM and Loopy Pro call it C4. Neither is wrong.
I think AUM’s popularity has led to C4 becoming frequently adopted, but it isn’t more correct than calling it C3.
For anyone that lands here looking for clues to use LUMBeats apps: it’s worth mentioning that the “Live Pads” can be controlled via MIDI and change between various Bank, Rhythm, Soundset settings.
As the OP mentions: using a MIDI Montioring app is very helpful when troubleshooting MIDI control configurations.
I hope someone posts an AUM project to patchstorage.com/AUM that shows a working configuration involving Live Pads and a MIDI controller that works within AUM like Mozaic, MIDI Messenger or the new Surface Builder.