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
I may be really, really dumb, but I cannot figure out the chorder module to save my life. I understand that a layout appears to be a collection of presets. But configuring a preset eludes me. First of all, why does the major preset start on C#? I can't find a way to change the root note of the preset. When editing a preset, I can select a scale, but it always starts with C. Is there no way to choose the root? Interestingly, when I create a major scale, starting on C, the preset decides to start on F when loaded. Finally, it seems like you can only edit a preset if you remember the name and save it as the same name again. Is that correct?
I don't get it either. Also, why cant you at least order the chords chromatically... I think it orders the chords in intervals of 5ths starting at C# and it then leaves out all the chords you didn't select. I don't know who finds that intuitive... In the chord keyboard integrated into their DRC synth you can at least choose the interval.
The chorder module has some UI flaws indeed. A lack of root note selection is not of them. We need to get some spare time to improve it. MATRIX module is taking a lot of our time lately.
Can anyone else reproduce the AirPod pro issue I’m having, where LK plays too fast in AUM? I know most don’t use Bluetooth for making music but maybe someone can help? I’m stumped.
Sorry, I just can't reproduce this.
Sorry if this has been already commented (this is a long thread..) but I’d just would like to know if there’s a way to change the behavior of the Shift function as I find it not only counterintuitive and convoluted but also against all IOS UI/UX standards.
The only purpose of holding the Shift functions is to enable new buttons with three dots which further enable new menus above them, overriding the column selections in the last row of clips.
My point is:
The Shift buttons and their behavior are redundant, counterintuitive, very uncomfortable to use and take precious space on the screen
Proposal:
-Why not just add the three dot menus in all columns exactly the same way as the other combo menus for MIDI channels, IO, etc? They would use very little space and would be ready to tap without the need of a “Shift” function.
-If the two Shift buttons are removed then that space could be used to acomodate the other missing navigation functions that are only available after the tap and hold of the Shift button, avoiding redundant taps and speeding up the navigation workflow.
Again, sorry if this has already been addressed. The app is really awesome, clearly the only and best clips sequencer on IOS, but I find the Shift functions very annoying and I know for sure that many other users think exactly the same.
Hopefully this can be improved in a future update.
Long pressing clips opens a menu with extra functions, maybe the same could be applied to tracks and scenes.
The shift has several alternate functions:
The are probably more features I can't remember right now.
In summary, shift isn't only used for activating the context menu for the tracks.
That's redundant and wastes space in phone view.
Shift/alt operations are very common in many software/harware solutions in order to accommodate functions without spending space with extra buttons.
We do hear users opinions and make improvements when we feel a common sense among the community.
@branis the problem with this solution is that it conflicts with the track selection operation that occurs when we press the track label. Not relevant in midi mode (for now) but it will definitely mess with Live mode.
@Rodolfo thanks for your feedback. We are always listening to the community and trying to improve the experience based on it. Merry xmas!
I 100% get it, software development priorities are always difficult. I was explaining to a co-worker yesterday why we have had to ignore some really nice ux updates to a major feature for almost 3 years
@Rodolfo - The shift function is less problematic now that I learned you can double-tap to keep it open. I still don't like it much, but it's workable for me now.
Let me know if you should find a way to make it work for you. Does not seem to be a very common problem.
Yes, I know about the double tap, but honestly it's the only IOS app I know to use something like this, and as I already mentioned I consider it totally counterintuitive and cumbersome. I also know I'm not alone... ;-)
Thank you very much for your comments!
I just expressed my honest and transparent feedback on something that I consider could be drastically enhanced if the Shift function is eliminated. I know a lot of gear that uses the same approach, but no IOS app with this "hardware" concept, as far as I know.
I also understand that it's not easy to modify a very complex (and awesome) app like LK, but I would kindly ask you to think out of the box just for a moment. You already know the reasons for keeping the Shift function, but maybe you discover that there are better options, who knows... I believe it's worth trying...
Merrr xmass!!!
GR16 also use shift button. Shift is ok, imho
Same for me. Didn't take long to get used to.
How weird.
I made a very simple video below which shows the problem. At the start of the video, LK plays in time with no AirPods. Then I pause, connect AirPods and hit play again. Notice LK then goes faster than the metronome? Then I disconnect AirPods and it plays in time again.
Does this help? Can anyone else reproduce? It literally does this every time for me with AirPod pros on iPhone 11 Pro.
That drift seems like an issue related to a change in the sample rate from 48K to 44.1K when AirPods are connected...
That’s what I thought tbh. This wasn’t happening with LK, but suddenly started happening after an update just before the most recent.
Does it happen if you connect your AirPods before launching AUM with LK?
Just tested this...
If I connect AirPods start an AUM session with LK already playing the clip it plays in time.
If I do the same but launch the LK clip after loading AUM, it’s out of time 🤷♂️
It wouldn't be the first AU to not be able to adapt to changing host sample rate.
It’s just odd that this wasn’t happening 2 LK updates ago (unless I missed it somehow) which means a change to the code since then has presumably caused it.
AUM was updated too ...
Or, maybe you just didn't switch over to the AirPods mid-session before? Anyway, hopefully Imaginando can reproduce it now that the steps are more clear.
A problem with tempo at 48kHz was introduced when the timing issues were solved. That problem was quickly fixed though and LK’s timing is now accurate at 48kHz. The bug you found looks to be what Wim said - LK doesn’t adapt to a change in the sample rate if it’s already running.
Yes very true. Fingers crossed this helps.
@sinosoidal if I can help any further just gimme a shout.
@sinosoidal : I just recorded a MIDI part and there is a note at the very beginning that plays the first time the loop plays but than doesn't sound on any of the repeats. This is with the latest beta. If I move the note a 32nd note later it sounds on the repeats but if it is right 1.1.0 or a little later it only sounds the first time.
I just want to remind you, these guys are portuguese (from Braga, I think?)
So if anything is not working, it’s your fault (the “pecinha”)
I have to say I agree with @Rodolfo here about the Shift thing. Sometimes we feel guilty as if any criticism is going to offend our respected dev, I feel like that often. Constructive criticism on an app that you use and love shows implication and involvement. It also shows you hate the Shift function! 😂
I did mention a while back various aspects of the UI that I find confusing. Thing they stop being confusing after some use, so those are hard to manage. You have to travel in time to see and trust your “I’m lost” moment.
I remember a few:
“M” for monitoring?. Thought it’d be “Mute”
Assigning cc’s on the midi control page is hidden below, extremely unintuitive.
Opening up the midi sequence with the little bar, seems obvious now... but I remember it wasn’t.
Double transport bar... this one still confuses me.
Overall these are all little details that only matter on the first hours of use, but those are crucial to newcomers. Specially ones with little patience. A few touches would go a long way IMO. I remember abandoning Modstep cos I kept getting lost, to me that was an amazing app ruined by weird design options.
BTW. I’d rather you leave the UI as it is, just change “Shift” to “Alt” and add audio clips instead! 😂
Feel you. My drummer was Portuguese. Can you imagine the drama?. 🙃
M stands for mixer actually because it hides Mute and Solo functions that are usually connected to the Mixer concept.
Agree! A better solution will take too much valuable time for now. Sorry!
Where is the duplicated transport bar? The one inside the composer is regarding the clip only.
Tell me a complex piece of software that you are able to master in a day and get to know all its features. This days people are impatient about anything. They want to do everything in a snap because there is so much happening.
LK is quite complex software with a lot of features and it is very hard to learn all this features just by looking at the screen. This happens with any other complex application.
I experienced the same thing with Modstep. Full of options but it looked like a maze.
It is impossible to please everyone.
We are still working on features that have been asked here in the last couple of months. We prefer to implement this features than spending a lot of time changing small details that only people that haven't spend enough time with the app will complain.
That doens't mean we are not hearing or getting offended with criticism. We usually have two options: we can ignore it or defend our point of view!