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
And there is an issue with too small resolution for pitch bend and other CC. That must be 1/16 on screenshot. Difficult to have some musical precision.
@Janosax
Thanks for reporting those two issues! We'll try to see what is going on! We aren't spending much time on LK right now since we're working on VS for custom shading import and audio import too, but we'll try to dig those down as soon as possible.
We have some improvements planned for the automations
Regarding the crashes, do they happen when you make certain actions? Is there a specific behaviour that is more prone to LK crashes?
@Janosax thanks for reporting this issues. We will investigate.
Thanks. Unfortunately there are no evident factors involving those crashes. I had one a few minutes after loading same AUM session quickly after closing it, so perhaps AUV3 instance memory issue? Another one was when loading a LK preset inside AUM. I had other ones when recording consecutive midi clips on various LK tracks and scenes without interruption.
Regarding the crashes. We are always looking forward to make the app the more stable as possible. The most difficult part is to find a way of sistematically reproduce a crash but that's usually the number on step to squash it.
We don't have complex setups like you, users, have. That's why we need your help. You guys explore the limits of our apps by far. If you find a way of reproducing a crash, pass us the project and tell us how to reproduce. that will help a lot!
We see a considerable number of crashes related with midi but we can't reproduce them. Are you able to make a project that reproduces the problem? That would help us a lot. Thanks!
Just unlocked Matrix mode today. Loving it so far, especially with my LPPMK3. Is there a way to map the mixer volume and pan to AUM channels? I couldn’t figure it out. Can the piano roll get smaller than 1/32 notes? Also got the controller unlock. Any chance it will be more customizable in terms of what’s offered button/knob/fader wise?
Lastly, what are people using for audio clip launchers? Man, if I could host them in this guy with multiout into AUM… mmmmmmmmmm.
Only real downside is that the manual is not very good. Took a few reads to figure out some basic things.
Thanks!
Right now, if you are using the plug and play integration, you won't be able to use it in any other way unless you custom map it to AUM.
Is anyone else feeling this need?
Not at the moment. We have a lot work in several fronts and the resources are still the same.
This is always a big question here in the office. We could add audio to LK but would that make sense? Also, we could not offer it as a free upgrade as it will require some huge amount of work.
Would the community be available to pay for a in-app purchase to unlock audio? Or would it make sense to make a new app that is essentially a stripped out matrix module with midi sequencing and audo clip playback with multi-track output?
This are some of the questions that arise when we think about it...
Yeah, this is an old issue. We basically need technical writers. We don't have time to develop and update the manuals. Ideally a technical writer would need to be a pro in our apps, know about the ecosystem and be confortable to work with git. Anyone around?
Don't know what we can do about the pitch bend issue you're describing. We've just tested the behaviour of pitch bend recording in Ableton, Logic Pro and Reaper, and all of them record the pitch bend just like LK.
I understand what you're saying, but if we make pitch bend recording linked with note events, then, it won't be possible to record pitch bend information separately. Imagine you have a clip with some notes, and you just want to mess around with pitch bend.
Another case that won't be possible is to record pitch bend information when notes have long release times. If the pitch bend information is fully linked with the note off event, then you won't be able to affect the pitch of the release state.
Right now I'm not seeing any alternative to the issue you're describing.
Regarding the cc grid resolution and the undo problems we'll look at them asap
Yes, I'd wish for 1/64 and especially dotted and triplet versions of every current choice, like:
...
1/4 1/4. 1/4t
1/8 1/8. 1/8t
1/16 1/16. 1/16t
...
Maybe they could be arranged like this so the menu doesn't need to grow vertically?
If that would include loading compressed audio (m4a/ogg/opus) and good time stretching then yes!
But I agree that it sounds like quite some effort. And people will expect it to record and edit audio too. Neverending... 😉
BTW it's done quite nicely in Nanostudio 2:
Even the swing slider will move grid lines accordingly which helps a lot when editing notes snapping to a certain swing value, then change the swing and edit another group of notes.
I see some sense in it, but since you can simulate it with basically any multi-out auv3 sampler like koala or drambo, I'm not sure it's worth the effort.
Sorry but NO, that’s not the way pitch bend should be recorded
I made some suggestions, as I’m not an app maker I can’t diagnose perfectly but I can only report some issues when making music and I noticed there was some kind of weird pitch bend quantize to the grid, and pitch bend value goes to zero BEFORE the end of note and should absolutely not if this is not what is played.
Here is a video, same iFretless Bass recording/playback in LK, Helium and Cubasis. LK is wrong with that bend off at the end of note, pitch bend is performed until note off, correctly played in Helium and Cubasis.
If you can’t fix this really basic thing (in terms of midi app very essential feature), it’s a bit sad but I will not use LK anymore as I need proper PB recording for most of my bass lines
Big one, definitely!. I think people would definitely pay for audio capabilities.
I suggested the way I see it a while back… let me try again.
I would sort of de-couple audio clips from the main LK app. If possible, I’d do a whole new auv3 instance to handle clips, seamlessly integrated with LK.
When we discussed this, we didn’t have 4pockets Neon or the upcoming Loopy Pro, but it still (even more) applies. You’d have a LK Clip auv3 that you insert in a AUM channel. LK would see those instances and you’d treat them just like midi, you get the loop bar, progress, etc… You can manage these other apps (loopy, Neon, Multitrack) but the integration is not there… you can send midi commands but it’s cumbersome and get no updated display. With LK’s own clip auv3 you’d record and play clips from LK, LK would act sort of like a remote control, which is how it works anyway with synths and midi stuff hosted in AUM.
Even better, recording process with correct recording via LK midi thru to bass, and unwanted added bend off added to LK playback:
Seems like the note is ending earlier. Can you try to do the same without the snap turned on just to see what's the outcome?
Just tried, it’s still there.
Bummer!
The tricky part is that you played correctly and then during the playback it had not the same behaviour. We just need to find a way of reproducing the problem sistematically. We are investigating.
Please listen and look carefully, it’s not a note ending earlier, this is pitch bend going to zero before note end. Third video, sorry for bass distorsion:
Thanks for those videos, you're right. I was missing the issue here. We'll give it a look and see what can be done to solve that!
deleted - something is double posting my posts when I edit them.
Glad to read this, thanks 😊
Doublepost - deleted.
@sinosoidal said:
Oh yes please this a big drawback for me I often remove the snap and it’s not very convenient.
+1 for me, up to 1/128!!!
@sinosoidal I think I would wait until Loopy Pro comes out and see how well people succeed in creating a setup with Loopy, AUM and LK. I think that Loopy is very ambitious and if it delivers what Michael aims at it will be a quite comprehensive audio looping solution that will be hard to compete with. Probably it would be a good idea to find out what both of you could do that both apps integrate well and that there is no conflict with controllers like Launchpads.
But I also like @tahiche idea of a simple companion multi-out AU that doesn’t do much more than playing back the clips and integrates automatically with LK and wires everything up. That would saves us from all the wiring between samples hosted in the sampler and creating the corresponding clip in LK.
@sinosoidal
Is it possible for scene to play from the position set in the host song position?
Or at least keep the Lk song pointer in place when stopping the host( for now when I stop playing, the position indicator disappear )
Dunno if I’m missing something, but I only think this is worth doing if it’s all in matrix. A midi clip has a piano roll when you go into it, an audio clip has a waveform instead. The difficulty I guess is piping audio into it to record? But not an issue if it’s in an fx slot in aum for instance.
I would 100% pay for this, even with loopy pro around.
I’d have a look at how remixlive works (I think it’s free to try..,). Imagine audio clips like this alongside midi clips. Lovely.
The matrix would still display the available audio clips. But the advantage of having them “outside” is that you are free to do any routing, effects, etc.
How would you add auv3 effects to LK audio if it was contained in an auv3 LK instance?. You can’t.
In standalone you’d have to figure out multi outs, host effects, etc, etc.. that’s a massive, massive endeavor. So I’d stick to an iap that allowed for auv3 clips.
Again, it’s what you can already do with some clip launchers, loopers, Drambo… but in a way that just works. I’ve done some pretty big LK projects with audio. Drambo, Enso, L7, Multitrack… tried it all. You can get it to work but it’s just not worth the hassle.
As for “it’s all in the matrix”, the operation would be…
Is this approach technically possible?. I don’t know… the LK clip would have to “inform” the LK matrix of the audio length and so on to get a nice realistic display of the loops and audio. I know that Atom2 or Neon seem to be aware of other instances, so this kind of communication might be possible.
Here’s what it’d look like: