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
Hello,
Is there a way in LK to keep a note playing when changing scene?
I try to add an empty clip in the next scene but even in this case the note is cut.
Is there any solution?
Thanks
No solution right now. That would be a great addition, though.
As a workaround you could repeat the same note at the beginning of the next scene, but depending on the sound this could be audible and not what you want
Thanks for your answer.
I’d like to hold a pad in the background trigging the note again cut the pad.
I will sample it and trig it in one shot so it’ll last even when changing scene.
I’m also missing a way to play from first scene when using host sync using AUM.
For now it play from current scene.
If anyone has a trick? For now I use a second instance of LK with a single scene a that trig the first scene of the other instance of LK.
Anyone has a more elegant way?
When we trigger another scene, we need to stop all notes from the previous clip because it is not active anymore.
Ideally we would need the bare minimum project that replicates the crash in order to fix this.
I have this problem too when pressing record in AUM. I can’t get it to trigger the first scene.
What I do is use the scene stop button in LK, then hit record, then hit the first scene to trigger it. Means I get a small pause at the start of the recording but not a huge issue.
As my project has a lot of external devices and almost no software synths it is questionable that you could reproduce the problem with it. Maybe the project of @gregsmith is more portable?
Maybe it is worth the shot.
As each track correspond to a specific midi channel. When there’s no clip in the tracks maybe you can avoid to send midi note off on this channel.
Just a suggestion, dunno if it feasible.
I don't have it, but I think I read somewhere in the forum that Atom 2 can do that
@sinosoidal @xglax there is an issue with pitch bend not being properly recorded. After a note recording with bending, when you release controller the data recorded should always stop with note off, or it will be audible as a note bending to zero pitch during this same note off LK playback. See Helium screenshot for proper pitch bend data recording, and see in LK how pitch bend starts to go to zero value before note off, this is with quantize off. See second screenshot. This looks like quantize/grid issue. CC recording should also have maximum resolution, Helium goes up to 1/128. This CC recording resolution setting should be independent from notes quantize/grid settings.
Also there is an issue with undo not working on pitch bend. PB data should always be attached with midi notes and undo/redo should affect both at same time. EDIT: Undo/redo don’t work on any CC recording!!!
In Helium pitch bend resolution is always 1/128 even if global CC is set to another value, and PB data is always attached to midi notes regarding undo/redo (because if not, it’s a mess when you record another take and forget to delete PB data after notes undo).
@xglax @sinosoidal Another issue which also makes LK unusable for now for me: all my AUM midi actions are lost on AUM session restore, except track 1. This is certainly because LK load default 1 track 1 scene before loading AUM state saving, here 4 tracks 4 scenes preset, so AUM cannot restore properly midi actions.
Before saving/closing AUM session
After restoring AUM session
Initial one/one default which must be the issue during AUV3 loading
Also, I have some bad crashes from time to time with AUV3 node in AUM.
This app is full of possibilities but still too much unstable for proper live use IMO. That’s not cool because we need it in iOS live music making 🙂
@sinosoidal sorry I had been so busy with my live set that I forgot to answer. So, @wim was right. It was the Midi loop. When I changed all LK track inputs to none the problem was gone.
Wait @Janosax …
Unless you’re talking about MPE, pitch bend is not related to note on or off in any way. It’s a completely separate midi message and acts on all playing sounds whether they’re being held down or not, as long as they’re sounding.
Perhaps, I’m not an expert in definition but what I can say is that PB don’t work as it’s supposed to be in LK. Try to record some bends with iFretless bass in LK and Helium to make a comparison and see by yourself.
But, you’re describing something that is completely not how Pitch Bend works unless I’m completely misunderstanding you.
Me or the screenshots? I’m not a dev. I report as a musician only. Hope this helps LK, I suppose screenshots are enough, I’m not here to fix.
There are unwanted PB data if you prefer, leading to unwanted audible PB movements.
Now I see. Helium screen shot shows the proper behavior. Pitch Bend is unaffected by note-off, as it should be. LK is returning pitch bend to zero on note off. You’re right, that is incorrect behavior.
A> @wim said:
Yes. It goes to PB zero but finger is still bending note on iFretless Bass. Not that easy to describe the issue
Sorry I take so much time to report so much bugs I can loose some patience at times 
iPadOS music making 4 life!! 🤘
Yep. Definitely a bug.
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?