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
Just pay attention to the light blue line under the loop bar, that’s your selection. Works pretty good
Thanks... Will give it a shot...
I believe there were people here that have asked for something like clip actions, a dedicated section where someone could chain multiple midi events that will be sent when the clip plays/triggers.
If someone has in fact ask for this, could you please elaborate a little bit about this? Like what kind of messages (only cc, or also notes) and if each message is supposed to have an independent channel. Or, if I'm misunderstanding this, what you really want with actions is the ability to, for instance, mute/trigger/solo other clips/tracks with one single clip when it plays or is triggered. If this is the case which actions do you think a clip should be able to call?
Thanks
HI @sinosoidal,
Finally I experience big trouble with the program change: even with no midi in connection Lk change it’s patch when I change my programs on my external hardware, I even try to to des activated Lk in AUM ( using a left swipe on lk icon), but even disactivated it respond to in on Ming program change so I lost my song each time I change the sound on my externals synths.
The only solution is to disconnect my hardware or remove LK from the channel strip and reload it, or save the song and reload it .This is not very convenient.
Can you do something to make it better?
Thanks
To me, this would be a nice option to add custom MIDI controller support - you'd set a specific message to be sent (ideally on a specific output - either select MIDI output on standalone or AU MIDI output on AU).
Two types of actions: trigger clip (ready to play but not yet playing) and play - when the clip actually starts playing.
Option to select note / CC / PC would be helpful (in the worst case, one can always transform it via e.g. Mozaic script) + of course a number, note velocity would be great bonus.
One extra: option to select if the MIDI message should be also sent on project/AU load: To initialize all the LEDs with the controller, not only on the playback.
Of course, this would be useful also for e.g. triggering PC on scene change to change presets on your hardware (or even software) or so.
Or, if I'm misunderstanding this, what you really want with actions is the ability to, for instance, mute/trigger/solo other clips/tracks with one single clip when it plays or is triggered. If this is the case which actions do you think a clip should be able to call?
Hi
To me the most obvious multiple midi events to be sent would be for example with one midi note , why not in a clip :
arm track + trigger selected clip
Why ? to loop live : lets say
track 2 = piano
track 3 = violin
on the fly "with record clip with scene launch " option On",
First : I arm track 2 and launch the scene = i record piano
just before the end on my piano loop recording i want to record the violin on the fly , I only then have to push Only one button , which i will have midi mapped to the clip that says : "arm violin , trigger selected clip" , and this launches the violin clip recording
Or, if I'm misunderstanding this, what you really want with actions is the ability to, for instance, mute/trigger/solo other clips/tracks with one single clip when it plays or is triggered. If this is the case which actions do you think a clip should be able to call?
Hi
sorry i write it better :
To me the most obvious multiple midi events to be sent would be for example with one clip that has 2 midi notes , one for arm , one for trigger selected clip
arm track + trigger selected clip
Why ? to loop live : lets say
track 2 = piano
track 3 = violin
on the fly "with record clip with scene launch " option On",
First : I arm track 2 and launch the scene = i record piano
just before the end on my piano loop recording i want to record the violin on the fly , I only then have to push Only one button , which i will have midi mapped to the clip that says : "arm violin , trigger selected clip" , and this launches the violin clip recording
I’ve asked for multiple midi events in the past… i mentioned it talking about the controller module but then expanded to the matrix/clips.
Let’s take a song with drums on channel 1, bass in 2, synths on 3 and 4 and a guitar on 5. Say you want a part of a song where you mute everything but the bass and drum…
This “muting” scenario is obviously just an example, you could get a clip to solo a track plus activate a phaser fx send, plus increase the size on the reverb bus, increase the feedback delay, or whatever… Yes, you can do it with scenes, but it takes more time, more space, and... Are these scenarios really “song scenes”?. Furthermore, scene clips have midi, maybe you just want to mute/unmute whatever is playing, detached from midi notes. With clip actions you’d separate notes from events like muting, fx sends, Cc changes…
To take it a step further, if you could send to any channel from a clip (select channel per event) you could have automation clips to for example fade in or out multiple instruments. I believe it would really speed things up, unclutter projects and provide a lot more flexibility and improvisation tools.
Sorry for the long post!. I do hope it made sense.
far better general idea if I may :
A new option in settings that would be :
clicking on a blanck clip on a track that is not armed , records the clip
= no need no more to click on arm + click on the blank clip
Or
Why not simply add an option in settings = " arm track of selected clip" ?
nstead of nothing happening when clicking on a blanck clip ?
so with this option On , clicking twice would record the clip ,
( I know double clicking on a blanck clip creates an empty clip , this wouldnt change since the option should be chosen )
What do you think about that ?
Lov'
Yes, we will add an extra layer of control to the next release. There will be a song settings panel in which you will be able to enable/disable this feature and decide which device/channel should be allow to perform this action.
Thanks a lot!!
@sinosoidal Just reporting a bug / issue for me with LK. Not sure whats going on, but LK is crashing on save in AUM frequently. The worst thing about this is that every time it happens all the midi learn assignments are lost with the invalidated instance in all LK projects.
I cant quite pin-point when and why it happens but often it seems to be on first save after opening the AUM session version where I save the (restored state) version with the original file name (ie without restored state at the end)
Happy to provide some projects, AUM session or logs if that helps?
@paikan777
Can you please see if in the latest beta the two issues you've reported (the note not playing when disabling arm, and the notes not being recorded if you play them before the clip starts playing) are resolved?
Thanks
Same for me.
A workaround is to stop playback before saving.
At least it works for me.
Hi-gh ! just been on it !
Works and is a game changer for live looping , Essential !
Bravo !
notes not being recorded if you play them before the clip starts playing) /// Check ! works like a charm !!!
(the note not playing when disabling arm Check ! works like a charm !!!
I have played several ways , same scene , with scene changing etc
Will keep on playing of course and let u know
BEAUTIFUL !
Merci
Are you able to create the minimal AUM project set that reproduces the problem and the minimal steps, or a video showing how to reproduce it? That would be the fastest way for us to tackle the problem. Sorry for the hassle!
New beta (build 257) tries to resolve the following reported issues:
@gregsmith / @branis -> clip length with wrong number on clip properties (i think this was only happening with clips created with record)
@Jeezs -> program change now has device and channel filtering (located in the song settings panel)
Composer now retains its visual state when switching modules.
Great.
No more program change trouble for me!!
Hi ! New beta lost nearly ... all the settings
Check the new settings icon at the top-right of the matrix window
Oh beautiful ! I checked on iphone not ipad ( I usually test on both ) so i did not see the wheel !
Thank you
@sinosoidal Made a quick video.
I open AUM session, open LK GUI, press save, crash. I then repeat but it doesnt crash. Let me know if there is anything else I can do to help diagnose.
https://photos.app.goo.gl/8EjXt8VZVH5UzPAo8
I love your app but I do find the files feature a little bit clunky.

Each time I save an LK project in a AUM session I have to remove the appended (restored state) message from the filename.
Sometimes I end up with files that either have or look like they have the same filename. (maybe I left a space when I removed the restored state part)
I have to load a project to delete it. There’s no swipe from right to delete.
LK updated to version 1.11.3:
Thanks for making the video. We will try to reproduce the crash.
When you save a AUM session, LK is treated like a plugin and the state gets recorded in the AUM session. When the session is loaded, LK receives a state from AUM. Since that patch was in memory, we put it back into memory with the same name and with the suffix Restore State.
We do the same for all other apps, we just don't use the "Restore State" suffix. We use the * convention.
I agree with your complains because this has been source of confusin many times. I'm still unsure what would be the best way to improve this workflow.
Indeed. Besides swap to delete what other ways could we add to improve this workflow? Just trying to gather some consensus here.
@sinosoidal Thoughts on releasing on M1 Macs?
@sinosoidal Been having a think about it and comparing with other apps. I guess it will always be a little confusing with saved state vs saved patch.
In Drambo, you are just forced to Save As… the first time you save after session is opened. The filename is just the regular filename. So, you can save over the top if you want to but harder to accidentally save a session state on top of a saved patch. It has the advantage of not having to mess about removing the “(restored state)” appendage. In Drambo you do have to choose the location again though. Not sure if this is best practice but seems to work ok.
I think having to use the keyboard to remove that “(restored state)” text makes it seem more effort than it needs to be. If you have the * and force SaveAs you then have the Overwrite warning. If you Ok that warning then it should just save without further intervention. Thats my 2cents worth.
The preset line height is good for seeng lots of presets but maybe a bit fiddly for swiping to delete etc.
LK is useless without a touch screen. Composer will not work with the mouse.
Why do you believe LK is a usefull tool in a Mac?
Can you use DRAMBO as an AUv3? Or you use it always as a host?
Wonderful LK has levelled Up a lot !!!
Brillant evolution
Thank you
Thank you for your feedback!