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 think this app tries it's best to always keep things in sync and "musical", but for "non sync" people who like to decide on their own, i think it's a big mess.
global clip settings, clip settings, playback settings, recording settings...
i have to spend too much time checking settings
for example when i record something into a loop that already has something recorded, the app changes existing pitch, speed settings and somehow tries to "sync" with... something?
back to settings...
a bit sad, but i think i give up on this...
Just checked. Battery went from 73% to 10% in 4 hours time. It used Loopy pro for 90% of the time. All i did was recording/playback of max 6 loops. On 1 colour i used Rymgarde and Alteza, and on another one Blackhole. Thats all.
I wonder if the UI is eating resources.
Just started the trial and it's pretty exciting the things it can do, been waiting for something like this for ever!
Template sharing: Do we have a central location for that or where would it be? Someone asked about sharing templates earlier on but I haven't found if there was an answer posted?
I can't figure out where imported audio is saved, if I want to reuse a loop in another project. Only takes me to options like cloud drive/files. But I've noticed when importing same clip from there into another project it appends 2/3/4 to the end so therefore it must be recognizing that one is already imported/stored.
I just want to say that the amount of fun I’ve been having with Loopy Pro over the last couple days has taken to the next level once I realized that we can take two fingers and twist a donut! ✌️🍩
It doesn’t work. It continues to loop.
Hmm strange...3/4 hour ago i had to go to the supermarket. Battery was at 12%. When i came back, a half hour later, it was 15%. I hard reset the iPad, and now it shows 20%.
My observation:
If the donut is set to play when the transport is started, it will loop.
If you disengage the loop before starting the transport, then trigger the loop manually, Play Once should behave as expected.
I don’t know what I was doing wrong but it’s working now. Thanks.
https://discord.io/loopypro
There is a channel is called #🐞bugs too.
Michael is onboard. At the moment the community is small but sure growing next days.
@Michael maybe even better if a threshold battery % could be set, and only show status when battery is below this - would alleviate anxious glancing at the icon
Issues with multiple instances of Turnado have been reported a lot throughout the beta process - I assume it’s quite difficult to track down and solve.
Have you tried Gauss?
My first track using Loopy Pro…I feel 20 years younger with this app
So it’s just me in need of a repitch algorithm preserving the transients in a “turntable” way? I can understand when working one project one bpm, but loopy pro could go far beyond that and become a live performance tool in a non looper way
>
Shit. I was out of commission for a couple days music-wise and now the thread has gotten out of hand. Catching up feels hopeless.
I will say that after a fun and novel initial foray, I’m more interested in going back to the MIDI tape recorder app than Loopy. Reliably making AU instrument connections and getting them to record how I want is still confusing. It’s kinda like NanoStudio 2 in the sense that the one-man designer’s vision has a few little “tics” that are off-kilter. Not bad tics, just design decisions that I personally don’t find intuitive compared to other stuff I’ve used. Gonna wait for the first update to see if there’s any routing streamlines and if that AU midi problem gets fixed, and a text manual. Then I’ll be back!
The launch key does not map to LoopyPro. I’m just using it to play instrument in LoopyPro via MIDI. The Launchpad is the device which auto maps to LoopyPro.
Make a screen recording that shows your settings and what is happening, please. It is hard to tell from what you have said is related to settings or a bug or what.
Loopy doesn’t have a built-in mapping for Launchkeys just Launchpads and one of the APC models.
For other things, you need to manually set them up. You won’t get matching lights on custom-mapped devices
The audio is saved inside the project bundle. You can export the audio clips but can’t see them with Files.
This sounds like the project’s bpm changed or was reset after some loops were recorded. Currently, changing the project tempo triggers time-stretching. It shouldn’t affect pitch. There are only a few settings you need to set to make the loops independent of each other and the clock. Once you’ve set up a project with those settings. You can create document with the settings you like and use it as a starting point.
I’ve done projects where the loops are not co-ordinated.
I am sure we could help you figure out the settings,
@wim @espiegel123
Hm, I just don't get it working. I think the workaround should be as easy as in Melda Production MSuperLooper:
once you stay let's say in looper channel 3 (green), input monitor to loop 1-2 and loop 4-8 should be silent. There must be a more easier way to make it working instead of creating dozens of new channels.
Just want 8 loops. And you just have a button for "go to Loop 3". Once you hit this button you automatically monitor your input signal in Loop channel 3. Then you can record your input signal dry without the effect the loop channel 3. After done this you hit the button "go to Loop 4". Once you hit this button you automatically monitor your input signal in Loop channel 4 (but no longer monitoring your input signal on loop channel 3!)
Important is to have different effect unit instances per looper channel.
This thing is incredibly deep and flexible, and yet pretty intuitive..
Is there a way to set Loop decays? and another one,
is it possible to set default clips colors?
Maybe I need to clarify:
The goal is just having 8 loops. Recording all loops dry without effects. You hit for instance "LOOP 3" which makes happen monitoring your input signal through LOOP 3 channel. And you can record loops in LOOP 3 channel. Meanwhile you stay with your input channel in LOOP 3 your input won't monitored in any other LOOP 1-2 and LOOP 4-8 channels. Each looper channel has different effect unit instances, means: not the same delay and reverb for all loops. Why to stay with your input channel in a selected loop? Because I want to use the same effect parameter settings of input channel AND to be recording / recorded loops of the chosen loop channel.
Not yet. Coming soon, according to Michael.
Currently, if you want to monitor through a color channel, you have to manually select the color channel to monitor through. Hopefully, actions will be added allow more automation of such things.
One does not need the same instances or effects on the channels if you don't want. I was under the impression from something you said that that is what you wanted.
Currently, you will have to do it by hand...which involves tapping the input source and telling it to monitor through a particular color.
Exactly! I asked this for a feature request.
I get matching lights on my little MPD218, including flashing lights when counting-in to record.
All I did was manually map the pads to a 4x4 grid of loops.
It just occurred to me that you can add multiple instances of your input source. Each can be directed at one color and set to monitor through that color. you would mute all but the instance going to the color you want. You could set up widgets, or follow actions, or midi bindings to unmute the desired input and mute the rest. I'd set up a widget, one per input instance and then follow actions, gestures or midi bindings to target the widgets.
It will take a few minutes to set up but once you have you can reuse that to start from.
Demo of proof of concept. The widgets make one mic instance active at a time. They can them be easily midi learned or triggered by gestures, follow actions, etc
With 10 hrs of light use claimed that’s not entirely surprising. Using an app like loopy with cpu heavy reverbs will tax the device and would probably be considered as heavy use.
You could try disabling the glow in main settings.
I’m sure Michael will soon spend more time tuning up the audio engine. He managed to pull off some miracles with AB3.