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.
Comments
I’m on the same boat. At first I tried to implement the “usual” midi workflow, using LK and whatever synth, trying to trigger LK scenes, output mapping, etc… But I got bored and opted for just bouncing whatever midi to an audio loop. So liberating!!. Try out stuff, record it to a donut, move on…
I keep the original midi info in an idle LK instance in case I want to redo something, but that’s about it. I’m not organized enough to recall every setting, synth, preset in case I want to change something further on, so I’ll just do it again. But the benefits of just “moving on” and settling on stuff are very rewarding.
So my workflow with midi is: LK as a midi source. Set destination/s auv3 instruments, record some phrases, try out stuff. Commit to audio and mute LK. Repeat and rinse. If you wish you’d done something different you can come back to LK and try to recreate the sound, will probably not happen but you’ll find something else that you like and you use that instead.
Yep, I wish you could choose the new color. Instead you get a random color that you have to change after the fact, plus you need to change the name or after you change the green to gray you still get the “green” text label.
Is anyone having trouble with Koala? The problem I’m having is that often I’ll load a sample onto a pad and the app (Koala) will then crash and LP will say reload. This does not happen 100% of the time.
Here is an example:
@Michael for your information.
Far from random. They appear to be added in order of colors in the spectrum. Aka the colors of the rainbow. I like it this way, FWIW. Much better than having to choose a color every single time you add a channel. Or donut, etc.
This is great advice. I got in on the beta fairly early and have slowly figured things out as I go (and as it has evolved quickly). But in the last few days it has really clicked and things are humming along right now> @echoopera said:
I’ve found this too! Flow is so much better with this app
Can I insert a PC and CC message send on the timeline mode? It’s for switching patterns in Pure Acid and Drum Computer
If I'm not totally mistaken we'll have to wait for the midi-clips to get implemented first...
Is there a way to add latency/timing compensation to MIDI messages that I send via a button? A scenario where this would be handy:
I'm hosting LK and Mozaic (and a synth app) in Loopy Pro and I've made a setup where I route MIDI loops out of LK through Mozaic in order to transpose them. I'm controlling the transpose value via customized buttons that send the required CC values. When I set the trigger quantization of those buttons to 1 bar, the transpose should happen on the 1 following the button press.
Nominally this works, but in practice the transposition often happens a tad too late for the first note of the MIDI loop to be affected. So pushing the CC message some miliiseconds early, slightly before the 1, would be of great help.
Currently, to have it triggered by the timeline, I think you would need to a loop or oneshot with a send midi follow action
@espiegel123 sounds good!
How do I do it?

Do you guys know a vid describing how to make a loop/oneshot with a “send midi” ”Follow action”? or shall we all make our instructions viddies soon?
Cheers
This is basically my workflow too. When I think about it, I rarely change notes after a certain early point in creating a song, so I’d be happy with just audio, but the thing holding me back is that you can’t automate the audio source afterwards. Quite often I want to open up an envelope on a synth over a number of bars, but if it’s already committed to audio you wouldn’t be able to do this.
The LK workaround is perfectly workable, but a way to do it natively in Loopy would be lovely.
Does anyone use ableton in this case? Does it record midi and audio together?
Does any one know how to map midi from a midi generator, e.g. Polybeat, to trigger a button? I've set up a trigger action, works fine from controller incoming midi, but I can't find away to send midi from the midi channel to anything other than another midi channel or audio track.
To add a follow action for a clip:
tap Follow Actions towards the bottom of the panel
Is this external midi or from a midi AU loaded in loopy?
When you record midi, audio isn’t recorded by default but it could be. You’d simply need to insert an audio channel, route the midi channel’s audio to the audio channel then record. You can also render a midi track to audio by freezing then flattening
Just guessing, but is there maybe a MIDI Learn destination, as there is in Audiobus.
Same story. In LP I made two almost ready to go tracks this Saturday. Without any complex planning, editing and etc, just pure fun. Esterday was back to basics and I spend almost one hour poking around with midi clips in atom and another half tryin different synths for this clip. Despite all challenges end result in LP sounded more pleasant and interesting. So I'm more in more in this approach - just make something cool and move on.
Currently (but changing soon), the MIDI Control system listens to external devices an the Virtual Midi In.
So, to send midi from inside Loopy to MIDI Control right now, you need to use a solution that gets MIDI to the Loopy Virtual MIDI port.
With the MIDITools MIDI Route AUv3 loaded in Loopy or miRack you can do it with no additional apps running. (For miRack you have a midi in module connected to a midi out module and choose Loopy as the destination.
The other way to do it is to use Audiobus or MidiFire or AUM or the like (Freeewi might work) to loop back the virtual midi out to the virtual midi in (by watch out for feedback loops).
It's from an AU loaded into a MIDI channel in loopy.
@espiegel123 appreciating your knowledge sharing in this thread! 👍
me too, really helpful. I realised that with your advice to use MIDI route it is straightforward to have the MIDI from the AU routed back into loopy. Thanks!
++ with extra plus
Has anyone here tried to use Beatstep Pro to control LP? I seem to recall @krassmann you're a BSP guru and perhaps there are some more of you or there... Thanks in advance! 🙏
Thanks. So similar to what we’ve got with Atom2 / LK already in Loopy.
Yes. In Ableton, audio and midi are different kinds of tracks.
Yep @espiegel123 you’ve been an absolute legend throughout the whole beta as well. Thank you.
The wonderful thing about Loopy Pro is you can get back to those sounds. You can leave all the apps and FX in the project, but idle them, and they really do free up all their resources. This has always been a big problem for me until now as I have woefully under powered devices. My dilemma has always been the difficulty of getting back to where I was to record new parts because if having to remove all the apps to save CPU. Now I don’t need to. I can go on for hours adding as many apps and FX as I need, knowing whenever I want I can pick up where I left off if I get new ideas.
BTW - this was great. 👍🏼
If that dismays you then maybe you could describe how you'd like it to work. I'm sure @Michael will read it with an open mind.