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 for your feedback!
I’ve been away from LK for a while and everything looks great but it seems like a whole new app now and I’ll have to learn and relearn what all the icons represent. Referring to the previous post about on screen help and a manual, maybe something like a quick start guide would be an easy place to start? This would be easier than a full blown manual. Even a screen shot of the main matrix view with icons labelled would be very helpful. Off to poke around in LK and try to figure out what’s going on. Edit: the icons on the piano roll could also be labelled in the screen shot too.
Yes! What an epic update! Love how you changed automations in this release. Displaying them large and over the pianoroll timeline. So cool. And CURVES editing!
Wish more devs would implement automations like you did in this release. Epic.
Thanks!
updating... Thanks..
Such a good update! Curved automation lanes that can be named and copied to other clips. Overall cleaned up UI looks nice. Still with some mysterious icons that one has forgotten the purpose of since last time around ;-)
which icons?
The two icons to the left of Automation, what do they do? I suspect one is for displaying a ghost clip (?), but I have forgotten how to set it.
Next to the left is crop, which can be a bit confusing. Is it an EDIT action sitting in-between icons for adjusting display? Maybe that's ok ... but would it be better if the zoom didn't change after cropping? I wonder if this crop edit would be better placed under the new wrench tab for editing.
Next to the left of that is the "zoom to fit", which is easy enough to re-remember upon trying it. Perhaps it could act as a toggle, bringing you back to full length view if you tap it when already zoomed in to fit. If you understand my poor wording.
At the bottom, I forgot what the tape icon is. The others are easy to figure out just by trying them (if you are in matrix view. If you try most of them out while being in piano roll view, you're out of luck). Seeing the online manual now, tape is for overdub recording. Makes sense. Must remember.
Btw, when tapping Help in the plugin nothing happened.
If you want to cut down on the number of UI icons, things like the headphone might as well be hidden in the settings menu (if its sole purpose is to say whether the vertical keyboard outputs midi when tapping).
The qwerty keyboard was not appearing to change LK track name or save session as.
Updated iPad to 15.3 and it now works
@sinosoidal What's your opinion on live jamming with clips and quantisation?
When global launch quantisation is 1/2 or one bar, launching the next triggered clip at 1.1 certainly makes sense.
But with shorter LQ amounts or launch quantisation=off, wouldn't it make more sense if there was a clip setting that allows us to
A: Launch the next clip at the beginning like now (good for one-shot phrases)
B: Launch the next clip at the current playhead inside the clip. If the new launched clip is shorter than the previous one then just wrap the bars around (developers would say "mod 4") so the beat always stays in sync with the other tracks.
I'm definitely not the best person to discuss live performance usage at the time being!
Maybe this is a good question for this community in general.
Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now
Can you please tell me what kind of crash is this?
What about the context in which it happened?
Can you send us the AUM or Loopy Pro session?
This bug is like a needle in a haystack, but the needle must be somewhere...
The AUM host node itself is not crashed.
AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.
LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.
AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.
Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.
That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.
Too bad as LK is best AUV3 for live midi looping on iPad.
Today while working on some bug fixes based on crash data we have been able to perform signifcant performance optimizations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.
A new build has already been submited for beta review. There is hope!
The new beta is now available. Please let me know if you find in this new build anything better stability wise.
Thanks, so there is hope!!! One of my current live setup use several apps as you can see on my screenshot and LK has such good capabilities to record multiple instruments, so really I don’t want to try something else it’s perfect. I will let you know
You guys rock. Level of support and improvement on this application has just been amazing.
Thanks for your kind words!
Just wondering if you had any chance of using LK lately?
Not yet this weekend sorry, but I will use it everyday this week, I will let you know today in the evening how stable it was
Hi @sinosoidal, I've been using LK on my iPad Pro in Live mode to control Live 11 on my M1 MacBook Pro. Generally, I far prefer LK to TouchablePro for reliability, note editing and clip control, but when it comes to device control I'm having some problems...
1. Main is issue is that moving any parameter results in very jittery movement. See video
2. In the user guide it shows how you can see and control devices in the drum rack chain, but in Live 11 it seems you get 16 macros and no way to access the chains
3. Renaming a rack in Live shows up instantly in LK but renaming a macro control (or adding parameters to 3rd party plugins using configure) shows up eventually but not sure how to make it happen. The only reliable way is to toggle the script on/off
https://photos.app.goo.gl/QzxBmxHrh4oTgo4W8
I've double checked my midi settings in Live and have the latest ubridge running.
This shouldn't be happening. We will see if we can replicate. Thanks for sending the video.
You need to enable 'Include chain' option under 'Song Model' setting. It will be much slower to load because there will be a lot of information, specially if you have a large session.
Maybe there isn't a specific property listener to report such changes and they will only be reported on the next full report for that device.x
@sinosoidal Thanks for the update! Just confirming that include chain did show device chain. I did see that option in settings but Song Model didn't make any sense to me. Maybe it should be Device Control: Show device chains (slower loading) or something similar.
Also, in Live 11 racks can have 16 macros. If you load an empty rack it will show 16 macros but if you place something in the device chain the top level rack reverts to showing only 8 with no way to access the second 8. Devices in the chain don't seem to show extra macros when added either.
Touchable seems to have the same renaming issue for me, so maybe you are right about the specific property listener
I’ve used LK latest 1.12.1 beta all this week, total 6 hours, and not a single crash!!!! It’s promising I really hope you definitely fixed it, it was super stable during all those sessions with this complex session on screenshot above. Thanks!!!👌🙏🙂
That is really good news. Yesterday we have uploaded a new build 1.12.2 that is already available for testing.
In this version we are still aiming bug fixes, crashes and a couple of fixes that could lead to crashes or deadlocks.
We are also introducing two little feature requests:
This two new options available under matrix settings.
The problem should be fixed in the latest beta 1.12.2. Can you please confirm?
Thanks for the suggestion. It makes sense!
Hi and thanks @xglax and @sinosoidal for "arm track on select' setting" , really very useful and awaited
Works like a charm !
Lov"
I am thinking of a very nice next step tell me what u think :
how about with "arm track on select' setting" , double taping the track records the selected clip ?
like when u double tap a clip to create one , but this time for launching a selected recording clip ?
;-)
Would be a game changer for looping live on the fly
and personaly my last request before being able to replace my ableton-mac with my LK-ipad on stage 
hey, thanks for quick fix!!
Happy to test but not on the beta
Wow.. Congrats… Great update..