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.
Loopy Pro Questions
This discussion has been closed.
Comments
Control Profile Switch from widget button or midi binding is not working yet?
No need to apologize. Being abrupt isn't a problem. Everyone would like to help you get this figured out and have only been trying to gather details that would help answer the right questions. At this point we have no idea where to start. We don't know what you've tried and where the failure is.
How about starting by answering this: When you get to the Define action screen and press your foot switch, is the press registered? If so, what does it say? Knowing now that you have a momentary controller, you should see the right CC recognized, and you should be sure that the trigger is set to "On". For long-press, it should be set to "Hold".
If you get that far and it still isn't working then it would be good to know more specifically what isn't working.
ok, I'm sure it's been covered, but the threads are immense and I couldn't find an answer when searching...
Are multi-out auv3's useable? I can load them in LP, but can't find a way to route them. Creating a new instance loads an entirely new instance.
Loopy Pro doesn’t yet support multiout AUv3
Loopy Pro is visible to Xequence as a midi destination. In Loopy , add Virtual MIDI as a MIDI source on the mixer page. Then set the AU as a destination of virtual midi.
Xequence publishes a a virtual midi out port. You would need to direct xequence to use that port for an instrument’s output, but I don’t think it gives you that option.
For future reference, virtual midi in/out in an app generally means the port that has that app’s name when in other apps.
For example , in Audiobus, the port it calls virtual midi in/out are the ports other apps see as Audiobus.
Just to try to clarify a little further, if an app publishes a Virtual MIDI port, everybody else sees the port with the app's name, e.g. "Loopy Pro", but the publisher sees it by some internal name, like "Virtual MIDI". So, when you were sending to "Loopy Pro" and Loopy was listening to "Xequence Source", the two apps were on different ports, so no data could flow.
AUM is the only one I've seen with a rational solution to this. Internally, it calls its virtual port "AUM Destination", while the public name is "AUM". It'd be nice if some other devs would make the internal name look like the public name, instead of using meaningless techie phrases like "Virtual MIDI Bridge".
Is Loopy Pro universal. Just put it on my phone but balked at the purchase page in case it charged me again.
It is
Well, would you believe, now I can't find where the buy link is. Possible just opening the store activated my purchase as I bought it on the ipad?
This Video answers all of my questions. Thanks anyway.
https://youtube.com/watch?v=7Gfz-PqIZwg
Excellent. I added that video to the Wiki page.
Hi all. I just tried to use Korg Gadget as a sequencer with Loopy Pro. The steps are:
On my iPhone 12pro iOS 15.2 this works very well. On my iPad 6 iPadOS 15.2 it does not work. Any ideas?
Hm. MIDI from Gadget seems to come in fine via the virtual MIDI port though on my iPad. On my phone its different. Very strange. Maybe it is an iPadOS ossue?
Does a midi monitor in LP show any midi coming in from Gadget?
If the target is AUM rather than LP does that work?
What is a midi monitor in LP? LP on my iPad lets me choose between „virtual MIDI in“ and „Gadget“ as an input. When I choose Gadget nothing happens. When I choose virtual MIDI in I get the MIDI from Gadget and can use it to drive any AU synth. When I test it now the behavior is identical on my phone. Hm. Maybe I made a mistake this morning. In AUM I need to route from AUM destination to an AU. The Gadget port dies not work there neither.
If you point Gadget to Loopy, in Loopy choose Virtual MIDI In not Gadget.
@Doc_T : re midi monitor. i meant using a MIDI Monitor AU
https://wiki.audiob.us/doku.php?id=loopy_pro_troubleshooting&s[]=monitor
I think you may be confused by the confusing Virtual MIDI port naming, described in my previous post here. The name of the same port is different inside and outside an app, so if Gadget sends to Loopy, and Loopy listens to Gadget, they're on different virtual ports, and there is no connection. It's an area where "it just works" just doesn't.
Yea. This is what I wrote.
@Doc_T - Is background audio turned on in both Gadget and Loopy Pro?
In LP yes, in Gadget not necessarily, since I only use the sequencer of Gadget but not the audio. I did not find a way yet to route Gadget audio into LP.
You have to have background audio enabled in Gadget for it to continue running when you switch to LP. It will immediately suspend and no longer send midi.
That said, I don't know if you've got Gadget or LP in the foreground when it's not working for you. If Gadget is in the foreground then what I said doesn't apply.
You can’t route audio into Loopy from another app at the moment. IAA is on the roadmap.