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.
(SOLVED) Drambo is not receiving MIDI within Audiobus
Dear Audiobus Community,
I have a Drambo patch which is controlled by a MIDI controller I made within Loopy Pro. When I have Drambo opened in background, I can control the patch using Loopy Pro as the main app in foreground. When I have Drambo as audio input in Audiobus and Loopy Pro as MIDI input and Drambo as MIDI receiver in Audiobus, Drambo is not receiving any MIDI cc. I can't route Loopy pro as MIDI controller for Drambo when using Audiobus or AUM, but only as separate launched apps. What am I doing wrong? Thanks in advance!
Comments
Have you put a midi monitor AU between Loopy Pro and Drambo to confirm that it is making it to Audiobus?
Is Loopy Pro's background audio option on?
The Drambo app can't be loaded as an input in Audiobus...only the AUv3. Is there a reason you are using Audiobus rather than just Loopy and Drambo?
Can you post screenshots of how you have it set up? Including the midi setup in Drambo.
Drambo standalone doesn't publish a virtual MIDI input.
Thank you so much. I'm using Audiobus because my live set includes also other AUv3s and it's handy to monitor them all.
Here's the Audio page within Audiobus. 
Here's the MIDI page. (I loaded Midispy to monitor and Loopy pro is not sending any Midi CC.) 
Here's the MIDI controller I made in Loopy pro. 
When opened as standalone apps, Loopy pro in foreground sends MIDI cc to Drambo just as I midi mapped it. 
Here's Drambo settings when loaded into Audiobus. 
Here's Drambo settings when loaded standalone with Loopy pro as main app (you can see it showing as Midi input)
If you're using Drambo in Audiobus, you're using it as an AUv3. If you're expecting midi to go to the standalone app when set up this way, it's set up wrong. The AUv3 will receive the midi from the AU Midi Input 1 port. I've tested and this works.
If you want to get control to the standalone Drambo (which will not be monitored in Audiobus), then you should set the Audiobus midi output to Virtual Midi Bridge. Then in Drambo it will be received from "Audiobus 3" (not Loopy).
But, as I mentioned, the standalone will not play its audio through Audiobus. It can't be loaded there as a standalone app, only as an AUv3.
So, you have to choose between using the AUv3 version of Drambo, or the standalone. They're two completely separate instances of the app.
Configuration for standalone Drambo (will not play through Audiobus mixer):
Yes, I need it as an AUv3! I want to open just Audiobus and get the work done. I would like to play everything within Audiobus, no standalone. Do you think there's a way to route Loopy pro MIDI to Drambo working as a receiver? I can only make it work when standalone!
I put Loopy pro in the AU midi input 1 port as you can see. Why isn't Drambo receiving any MIDI cc?
Loopy Pro is kind of the successor to Audiobus – pretty much anything AB can do, Loopy Pro can do better (perhaps with the exception of legacy IAA). What is it about AB that you’re preferring at the moment, out of curiosity?
If you can do it in Loopy Pro, you’ll probably have an easier time – generally the more moving parts you add, the more scope for difficulty.
Are you using Loopy Pro Standalone or AUv3? If Loopy is in Audiobus then it's the AUv3 of Loopy that will be sending to Drambo. Loopy Pro Standalone can't be loaded in Audiobus.
Yes, it's AUv3 loaded into Audiobus MIDI input.
Is the midi output from the Loopy AUv3 controls set to "MIDI Out" (Not Drambo or Audiobus 3)?
Problem solved, my bad! I was sending CC to Drambo and not to MIDI out. Now everything is working good in Audiobus. Thanks y'all :]
....
In what way can Audiobus monitor things more usefully than Loopy Pro? I am genuinely curious, as I find Loopy Pro more convenient as a host (as well as more capable).
I dunno, when I was troubleshooting I was really reminded how delightful the Audiobus workflow is. I'm not switching back, but Audiobus is such a classic! ❤️
Oh that’s nice to hear!
In Audiobus I like the way you can quickly switch between AUv3 which are opened in almost full screen mode. Maybe there's something I'm not aware of, but I don't find it convenient the way AUM or Loopy open apps as little pop-up windows that I have to adjust in size in order to use them. Also in Loopy I have to open AUv3, tap full screen mode, close the app, open another AUv3 and repeat the same process. Audiobus is stuck in full screen and the switching is easier for me.
Loopy is for me the best MIDI controller I have ever used tho 🤍
Good to know! And thank you!