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
Ohh, now I understand the workflow. Yeah, thats a bug. We'll fix that in the next build. Until there, if you want a workaround, you just need to unarm the tracks or disable recording (instead of firing the scene), that the clips will record until the next trigger position, stop the recording, and automatically loop.
Hello,
I 've try the new multi bus option and it works perfectly for me as well as all other part of the plugin.
Thanks very much
Hi Jeezs , I cant see the multi bus option , sure it is right in front of me but where ? thanks
Instead of having a single LK midi output, now there are three additional ones, LK 1, LK 2, LK 3. You should see them in AUM midi route table, and you should see them as midi ouputs on LK tracks
I try record program change from my keyboard, but instead of recording the program change, LK load the project according the program change received.
Is there any solution to avoid this behavior?
Thanks
That was a flash feature implementation. Right now it is not possible to disable it. Our bad. Sorry!
We need to add an additional layer of control. My idea is to have a settings panel just for MATRIX.
Thanks for the answer.
No problem I’ll wait for the feature to be finished.
LK has a new beta build (255) that matches the clips colours with the launchpad colours. Could you give it a try @gregsmith ?
Just a quick note. The colours wont match in your already made sessions. In those, you must manually change the clip color (in the clip properties panel) or the track color (in the track properties panel). The available color options will match the launchpad ones.
This new build also fixes the problem reported by @paikan777 . Could you please see if the issue with the scene triggering has been fixed?
Thank you guys for your constant feedback and support
How many of you here have the AKAI APC 40 controller? Mk1 or Mk2?
I made a test LK project with 64 clips using all 64 colors in the same order as in the color picker.
Here is a screenshot from LK:
And here is a picture of my Launchpad X:
In reality the colors look closer than in the picture, I'd say they are a pretty good match. Some red and light blue ones are harder to distinguish on the Launchpad than on the iPad and the top 4 grey ones have a pinkish hue on the Launchpad, but grey is not really a color so I guess that's how the Launchpad shows it. Also, keep in mind that LK is stopped, so all clip colors are subdued in the LK screenshot.
Thanks for this update, it's much easier to use the Launchpad with LK now!
Awesome! Thanks for this incredibly detailed feedback!
Hi
very nice 
This works .
Well thank you first of all
It is difficult for me to work on the beta since even if i reinstall etc , doesnt want to restore the matrix i bought ( on the beta only ) ...
As for " record clip on scene launch" , it works fine when i relaunch the scene
But : if i only record one clip .
Now if i go next step on the workflow = then record another instrument , very simply
Lets say
only one scene
track 2 = piano
track 3 = violin
I arm track 2 / launch the scene , it records a piano clip . I can relaunch it and all is fine now bravo
But :
If I do that= record a piano loop then , " on the fly" I :
1/relaunch scene
2/ quickly "arm track 3 violin
3/ then quickly launch violin clip to record it , its like it mutes last notes of piano clip though there are well recorded .
As if , the action of arming another track sent a "mute" order , i dont know
I think I will make a little video later if u need me to
without waiting for it to play a full cycle with nothing happening 
To explain my general workflow on ableton , well it is logical for a live musician :
I arm a track=instrument , when i launch a scene it records it
At the very end of the loop i just recorded , i quickly arm another track instrument to record it on the fly , so that i already have the first loop in background
Sorry this was not very clear :
tell me if not 
Meaning ,
1/arm track 1 , 2/ launch record scene it records a clip
at the end of my recording just before the end I
3/ relaunch the scene
4/ arm track 2
For now in LK + 5/ I push the clip so it records
The best would be that : when relaunching the scene , with another track armed , it should work again = record on scene launch , with the new track
I am sorry i hope i am clear enough !
@paikan777
to be honest I don't know if I'm fully understanding your workflow =p. Are you trying to record another clip when the previous one has already looped? If you trigger a clip/scene after the trigger timing, the clips will wait for the next trigger time to start recording/playing. For your workflow to function you must either changes the trigger quantity to "None" (which might not be a good solution when recording clips without pre defined length) or you must trigger the recording a little bit earlier so the clip is ready to record when the trigger timing comes.
If this is not the case a video would help a lot understanding your workflow
"or you must trigger the recording a little bit earlier so the clip is ready to record when the trigger timing comes."
Yes that is absolutly what I do
and it works , clip on track 3 records well , but "mutes" the last note(s) of the clip recorded just before on track 2 lets say
@xglax In fact this is a method i have long been using with clyphx pro on ableton , works like a charm , trying to do smth close to that
did it with iphone 6s , gonna try with ipad 8 ...who knows . i ll tell you
Are you saying that only the last notes are muted, and not the whole clip?
absolutly
gonna film it ...
Thanks, will help a lot to see what is going on!
Okay I got it
the pb is not linked to scene launching at all .
So I made a simpler video .
Impossible to see on the video , tough to film and play but : 3rd note , i still had my finger on the midi keyboard while arming other track with same hand ( . And that "mutes" the third note . But ! i did the same with releasing the finger before arming other track and no problem . Meaning I would say , it is a problem of note on note off message
Oh and I dont know about you , but I always play the first note " a little late" , or is most of the time not recorded
I've managed to replicate the issue. Will try to see what is going on.
I'll also have a look on that second issue you're reporting!
Thank you ! I am very happy to contribute a little
Hi all , quick tip for beta testers with testflight , i did not understand why i could not restore my purchase . Didnt read " purchase is not factured for beta event if you click on "buy" in beta app . Then I had a problem , coud not after entering my apple code go down the page to "enter" , so just learned on a keyboard on ios juste press "shift+return" , is like pressing enter .
Have a good evening from France !
I have one one the way (mk2). Personally I don't know too many people using it on iOS, but they're pretty popular with ableton people. Not launchpad popular, but popular none the less. More popular than the apc keys.
I figured I'd be scripting my life away in Mozaic getting the apc40 to work remotely well, but if you're thinking of including this, i'm down. I need actual knobs.
Also, I havent tried the new beta yet, but thank you for fixing the colors for the launchpads. Its pretty much kept me from using LK outside of composition directly on the ipad, and unusable for performance.
Purchases are working in the latest beta 😊
Still don’t work here!!