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
Thanks.. seems the midi part of the modular setup is ‘almost complete’.. now it time to give audio some attention (Auv3)..
I’m looking forward to ‘snapshots’ of entire states...morphing etc.. like this.
Sure, the scenario i'm thinking of is LK in standalone mode. Let's say I'm using LK to sequence hardware. Controller in LK would be mapped to midi cc of the hardware, and the controls in LK would be mapped to a midi hardware controller.
This way it would be a handy way of mapping controls quickly without having to update Midi CCs on the midi controller itself. It's almost like having a midi translator built into LK itself, without a third party app like MidiFlow.
Thanks for explaining. I see. I will add this to our feature suggestion list (low priority).
No worries. Thanks, agreed, it's a nice to have.
@sinosoidal I have these annoying timing issues when I try to record from the Launchpad sequencer to LK. There is always some steps off beat. It doesn’t matter if I record quatized or unquantized. I tried in AUM and Drambo. Any help on how to get the midi from the LP to LK unchanged is greatly appreciated.
We have that bug in our todo list. We haven't been able to look at it yet. Sorry!
It‘s OK. You got lots of stuff that probably affects more people. I just managed to record into drambo and then back to LK, which worked. I‘ll try that for now.
Is there a way to filter midi learned messages. I use midi keys to trigger clips and my synth is receiving them.
LK is even recording them .. weird
What happens if you unarm the track?
Well, then there is no midi at all going thru. IMO these midi learn events should be filtered, first time I see an app behaving this way I could filter them but it's annoying that they get recorded in LK
So ... the app needs to remember all the notes that you've used for mapping and exclude them from pass-through and recording? I guess I never ran into that because I would always use a midi CC's or a separate midi channel for automation. I typically use channel 16 for automation. That's not always an option for controllers that can't change channels, I know.
Each track can be told to listen to a single midi channel rather than All. I don't know if that helps but is the method I use.
The app already knows if a midi message is a binding or not, so filtering that event isn't a big deal.
In Drambo if I assign a midi event to some function, it won't be recorded or sent any further.
Btw in LK, even a CC gets recorded and will go thru, the only way is to assign a different channel, set the track to a single specific channel, so every time I'll need a new binding I have to re-channelize it before it hits LK ? Not the greatest workflow.
I’m getting stuck notes when I hit the undo button. Anyone else?
Trigger quantize and record quantize don’t seem to be saving to project correctly. When reopening it shows as they were saved but functions in a buggy/glitchy manner requiring those two parameters to be reset. Anyone else?
Record quantize seems to capture some unquantized notes. I set record quantize to 1/4 in a one bar clip and played four quarter notes. The first note I play shows up on the grid simultaneously at the very end of bar 1 and on measure one. Happens every time. I am probably playing the note a hair early.
That last note in the picture below shows up on screen at the same t8me as the first note
@sinosoidal Thanks for all your hard work in bringing this great app. I'd like to add two small suggestions into the mix (unless there is already a way to do it?)
Old bug. Not solved yet. It's on our list. Sorry!
We will take a look.
I don't know if this had already bern requested... I would like to have some more functions to draw automation. A line tool for example. Yesterday I wanted to apply a growing probability to an 8 bar clip with many 16th notes - that was quite impossible without zooming in, but then it’s hard to keep the line straight over 8 bars.
It has been requested before. We will eventually get there.
Midi mapping on clips is a bit weird, if I have a single track with cc_1, cc_2, cc_3,.. then add a new Track, the mapping is rearranged horizontally, cc_2 will now trigger clip 1 on track 2, cc_3 will trigger clip 2 on track 1, ...
Any special reason for that ?
Does the mapping change when adding new tracks? Can you make us a short video on how to reproduce the problem?
Between the 2 pics I just added the new track
This is definitely a bug. We need to look at this. Thanks for reporting.
Yep.. I requested the 'Draw' mode for Prob/Vel, as CC does... Doubling down on that request.. could be really nice..
Thanks..
Thanks. Being able to run smooth from the get go is a big plus with workflow and getting started.
Really getting into this app, its fantastic, thanks so much!
@sinosoidal if it helps I have trigger quant and rec quant both set to none when state saved (for ambient jams). Both have to be pressed when opening the project (aum) to fuction properly.
I really like the app but it crashes really too often for my taste, using it with Drambo, just one instance of LK (using MIDI Bus app for routing), on an iPad Air 4 th gen.
Rebooting doesn't help and the crash is very random, also sometimes the GUI is all black although the plug seems still working. Removing LK and trying to reload doesn't work, only way is to restart Drambo.
Recovery state prevents from loosing all my work, but not always.
Any idea ?
Are other users having this experience? We have the lowest crash rate in 90 days.
Maybe there is something particular about your setup that is triggering those crashes.
Can you please make the simplest project that replicates the crashes very easily? Maybe that would help us finding the problem.
Thanks!
I get the odd crash here and there but nothing to write home about. I save very regularly in AUM anyway as presets are generally tiny.
I’m on iPad Pro (2019 I think) and iPhone 11 Pro