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
Is there a drum map for Ableton drum clips, when using with Live?
Here is an idea: create preset midi files that are of various lengths - 1 bar, 2 bars... that trigger one full length note in EG Pulse range and import that into an LK clip like you would load an audio file.
E.G. You have a drum loop of 2 bars in EG Pulse, at the pad that responds to C1, import a C1-2-bars.mid file into the corresponding LK clip.
You’ll need to spend some time to prepare the midi files, but it would be a one time job.
Is MIDI Export working for you?
That sounds clever, but as I have 6 scenes per track ranging from 1 to 8 bars, and notes only repeating every 2 tracks, that would give me way too many midi clips to make the setup any faster. But thanks for the suggestion.
No it’s not.
Now that I tried my idea from above, it’s not really working as I imagined it would because the midi file is always imported to a new track. Extra steps would be necessary to cut/paste the clip to the correct cell and to delete unneeded tracks. Though, since midi export is not working at the moment, I exported midi files from Troublemaker and Gadget for the test. Things could be different with midi files exported from LK.
With the refactor of the context menus, we broke midi export on iOS. It should be fixed on 1.10.1. Sorry for the inconvenience.
Haven’t tried triggering EG Pulse but I use LK to trigger Drambo patterns for drums which should be similar. As long as you’re triggering a pattern, and not individual hits, you only need to send the midi note message once and the length of the clip doesn’t matter. In the case of Drambo re triggering a pattern just stays on the pattern, it doesn’t reset the playhead so you can keep looping no matter the length. That means Drambo pattern and LK patterns can be different lengths.
The safest approach would be to send a pattern note message at the beginning of a clip and turn off looping for the clip, that way the pattern changes and stays there until you trigger another clip. I don’t see why you have a problem with clip lengths. That’s a problem if you’re using LK to, for example, trigger a phrase in a sampler, in that case you use gate or latch mode like you comment. But that shouldn’t matter for drum patterns where you’re not playing the individual hits.
Thanks...
Great update..
Great developers...
Really brings value to iOS music...
Did the update break the MIDI export? It’s not working for me now on my iPad.
Also...
when recording into clip using AUM, LK will reset to measure 1 and start overdubbing if I try to save during record, for example, during a long recording so I won’t lose what you’ve recorded so far.
can’t always select and type text in app, especially when renaming clips.
I really hope these bugs are fixed soon because otherwise I love working w LK.
(Please tell me if this should be in a different area or post...)
Yes! Last update broke export. We will fix it on next version.
Do you mean, save a project while recording? Can you make a small video reproducing the problem? That would help us a lot.
AUv3 or standalone? Any particular place?
We are always trying to improve LK so they should all be fixed when possible.
@sinosoidal,
I’ll try reproducing on video and post it soon, if no one else beats me to it.
It’s been happening often and should be easy and quick to reproduce.
Great that the MIDI export patch is coming soon. Thanks for your reply: very much appreciated!
I was able to video the typing related issue. I'm not able to upload the video (seems I'd need to host it and share the link?). If that's the case, I'm not able to do that.
I can email it to you/LK support instead. Please let me know, thanks.
Will try to capture the recording issue too...
EDIT: Just captured the recording issue also... I forgot to mention above, I think the typing issue only happens as an AU, not stand alone, but I'm not 100% sure.
Please post if you'd like to receive the videos by email, and feel free to repost the videos when you get them.
Not sure if you’re talking about audio or midi clips? 🤔 my problem is with audio loops. Anyway I‘ll try to follow your approach tonight (hopefully) and see if Drambo does something differently.
Oh, I didn’t get it before. So you’re using EG Pulse to launch audio loops. Ok, I do that with Drambo too. I’ve tried just about everything and there’s no good solution. If you find a way to make the loop trigger independently of LK length, then you can’t stop it on demand. I’ve really struggled with this and I’m alway complaining about the lack of audio clips solution in iOS. I think you’re stuck in having to control the lengths of the clips in LK. If nevando help you with doing so in Drambo let me know. Good luck.
I've seen the video. The fact that the keyboard is not popped while the cursor is in the text input is a problem and we are investigating.
Regarding saving during recording: if we are going to save the project we need to ensure that no modifications are happening during that process, therefore the song is stopped. Maybe we should prevent the user from saving while it's recording.
Why do you need to save while recording during long recordings anyway? Is LK crashing?
Is there a way to do 'draw mode' for Velocity and Probability? Seems to work just fine with CCs.
Double-tap 'select all' would be nice too..
Thanks..
@sinosoidal - Congratulations on the Imaginando website (not sure if you've updated it recently) but it looks great!
https://www.imaginando.pt/
The design has been around for more than 2 years now but it has been evolving. Thank you for your feedback!
i've been tryin for hours now to send midi notes from LK Midi Pads to ableton live on my PC.
While I can launch clips on the matrix and write notes on the fly there using devices and composers on,
it seems the midi controllers MIDI pads and CHORDER do not send messages to Ableton.
I am in Midi Mode, armed a track but no midi messages is sent on my PC
Am I the only one with this problem?
Okay re: the typing issue.
For saving while recording, yes, I was making song length clips from one LK instance to another one (200+ measures at times). This crashed out both instances on LK in AUM several times, even though there wasn't too much running in AUM overall.
In all cases, all recorded material was lost. That's why I started trying to save during these longer recordings manually. But, as mentioned above, this causes the clip to restart the loop start point upon save during the recording.
Thank you for checking it out!
@sinosoidal The more I think about it the more obvious it becomes...
LK could really use and additional on-screen note-input method...
...and what better way of 'flattery' than to mimic the functionality of Launchpad Pro Mk3 and its 'keys & chords' modes?
In practice this could easily replace, pads, chorder and maybe even the keyboard modules with one unified UI making the app easier to maintain
(But I guess it could upset a certain company).
The only app with proper isomorphic grid for playing is Musix Pro but it's not been updated in ages and I don't even know if it still works properly on the iPhone & iPad (I will not take the risk off purchasing a potentially non-working app).
https://shiverware.com/musixpro/
Cheers!
@Samu i tried researching about isomorphic keys. Saw a couple of videos and the theory makes a lot of sense.
You’re saying there’s no isomorphic keyboards on iOS?. What about all the apps with scales and pad keys, like BM3, koala...?.. Aren’t those isomorphic?. I don’t know music theory, for me it’s always been about numbers/spatial relationships like between frets on the guitar, also I suck at piano, so I’m quite interested in this. Any good ref material?.
Sorry for the off-topic!.
Velocity Keyboard can be set up isomorphic. GeoShred is isomorphic.
In this case it would honestly make more sense to have it built-in into LK since LK can also be used as a controller for Live and other apps.
KB-1 has nice scales mode and that'll have to do for now...
...Kai's probably too busy to consider adding additional modes to it at the moment.
But since the 'Chorder' needs attention maybe @sinosoidal will also consider alternate input methods and it's here the Launchpad style grid input would definitely fit like a glove.
GeoShred by all means but the UI hurts my eyes in a bad way...
...unfortunately the other app also suffers from sickening visuals.
Oh well, I might end up getting a Launchpad X at some point but I don't carry to controllers with me everywhere I go...
Cheers!
I own KB-1. Is that isomorphic?. Can you point me to some documentation or tutorial where I can check how the scales, chords, etc, work in isomorphic?.
I think if you look up a web page explaining isomorphic layouts, you will see how to do it. Isomorphic just means any layout where the same shape has the same intervallic meaning no matter where you make it.
If you tune a guitar so that all the strings are the same interval apart, it is isomorphic, for example.
It shoudl be fixed on 1.10.1 beta (build 206). Please confirm.
Do you have a midi device set up on UBRIDGE? Have you followed the setup guide?
https://www.imaginando.pt/products/lk/help/setup
Exporting is fixed, works great now. Importing midi still creates a new track and imports midi to the first scene, I’m not sure if that’s a bug or how it is designed to work in case of multichannel midi files.
Right now it is a design decision until we find a better option. We could eventually determine if there is more than one track and only create new tracks in that scenario. i think I will try to gather more feedback before doing further changes.