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 tested the beta. The trackpad support zoom in the clip window which is very cool.
On the other side scrolling doesn’t work with the mouse nor the trackpad.
That works in the track view but the midi pads playing surface is still 4x4
@Jeezs
There is a bug in the underlining framework we use regarding the scrolling in iOS. The bug was already fixed in the new framework version, but updating our apps to it will require a lot of work since major things have changed and major refactors will have to be done in order for the apps to properly run.
Sorry for this behaviour.
@janpieter
Will see how to increase the time of the popup. Thanks for the feedback
OK. Thanks for the info
@xglax how do we join the beta?
Send your email via pvt message
It still freezes but now it's just the LK playhead that stops(freeze), you can even move midi notes around which you could not do before this last update. I only noticed it because I got a note hanging on the instrument LK was connected to. Weird.
ARGH this piece of software is one of the best for music there is on iOS, and it must some day run stable ... : )))
Sounds like progress.
For Imaginando to finally pinpoint the culprit in this whole long ordeal - maybe(?). For me it still meant, as before, a restart and thus an unwanted break in the process.🤓
@janpieter
Is the timing sensitivity of the notes' popup better now?
I'll check tonight!
wait a second - playing around with the inferior atom2, i discovered a new "reload ui" button there! LK is not the only app with this problem, it seems. perhaps such a button can solve the issue for now?
Sorry if this was discussed before: When I use LK on my iPAD to control Ableton (via UBRIDGE) I cannot have clips from two different tracks overlap on the piano roll (i.e. by clicking SHIFT + both clips). Actually the overlap seems to last like a millisecond then it is gone. As soon as I close LK from iPad the problem is gone. The piano roll from both clips can overlap without any issues. I saw this same problem was commented by someone on reddit (it was this comment that made me try different solutions until I found that closing LK on my iPAD solved it): https://www.reddit.com/r/ableton/comments/p39xki/shift_key_not_working/
Has anyone encountered this or know of a solution other than having to close LK every time I want to overlap clips?
Thanks
I notice a strange bug when using Lk with AUM or loopy pro if I set the tempo to 90 BPM.
Lk sometimes double the notes! it often happen when after the first clip loop but sometimes randomly in the clip sequence.
If you set to any other Bpm the bug disappear.
It happen both with latest beta and the current version.
@sinosoidal and @xglax could you please add recording quantization individual setting at least per midi clip and even per track and per scene if possible. Sometimes I need tighter 1/8 quantization on drums kick and snare because I use only visual metronome with flashing light and no sound, then I need 1/16 on everything else, so individual settings already predefined in a live template make sense.
Anyone can confirm or am I the only one in case at 90bpm?
@xglax and @sinosoidal I can confirm @Jeezs issue with 90 bpm doubling notes, see video:
Hope it’ll be solve soon.
Yes me too I love 90 bpm!!!
I don’t experience this bug. I loaded LK in AUM on a MIDI track as an AU MIDI Processor, added one audio track with Hammerhead and created the same pattern as in the video above. It’s been running for a couple of minutes now with no double triggering. I changed the tempo from 90bpm to something else and back, but I couldn’t replicate the issue.
OTOH I do on rare occasions experience some skipped notes, but never got to figure out if it’s LK’s or the plugin’s fault.
I also have a very odd issue since several months, I think this one will be challenging!!
When I start a template session using LK with already pre routed AUV3 instruments and controllers and rec buttons enabled, everything works perfectly except if I use 32 buffers!!!!! There is in this case no sound playing via midi though (only) LK during 30 seconds to one full minute. After that midi is passed though LK no problem for both virtual and hardware controllers. No issues at all with 64 buffers and above, midi playing works immediately when session is loaded. Once I’ve loaded a session at 32 buffers and the midi pass though LK, if I quit AUM and load the session again, there will be no issue. This is only when loading the session first time of the day or after a few hours with no AUM running. I use that session everyday the issue happens everytime.
If anybody can test and confirm? Issue is with iPhone 14 Pro Max and iPad Pro M1 since months/32 buffers is doable in AUM.
One more bug I noticed:
I usually end up my tracks by setting the last scene’s follow action to stop and this is where LK sometimes retriggers the last scene if there are notes at the very beginning of clips. I figured out that this is happening only on clips that I extended.
For example if the longest clip in the last scene is 4 bars, so the scene is 4 bars long, but I have a few clips that are just 1 bar long and instead of setting those clips follow actions to stop I just extend them to 4 bars (and delete notes from bars 2, 3 and 4), the clips will retrigger the first notes after the scene stops.
Is this happening to anyone else?
Hi good people. Sorry for the lack of feedback. We have our heads under water at the moment.
As we have shared a couple times here already, we are working on something new. It is our most ambitious project so far and it has a lot of work to be done. This project envolves working on LK sequencing base and adding a LOT OF features on top of it. We are completely focused on this work right now. Therefore is very difficult for us to iterate over LK at the same time and our attention to the problems raised might take more time to be available.
We are looking for early testers to give it a spin on our new thing. We can't call this a beta yet. We will provide early access to long time fans of LK and participants of this thread, this is not a public beta and we will not provide access to just anyone.
If you are interested and if you consider yourself a long term user and supporter of LK and Imaginando products feel free to reach me out via private message.
Ok thanks for your answer. Please consider at least fixing 90 bpm issue. Also LK beta on TestFlight have only 21 days remaining, don’t forget to renew at the end!! Cheers.
Hi again, I know you guys @xglax and @sinosoidal are working on something else but another bug kills LK usability: some note off are missing, or are played on wrong notes:
My main live setup use LK for midi live looping, using also LPP for audio, all in AUM. This setup took me dozens of hours to create and optimize for live in reliable conditions. There is no alternative to LK here.
Please fix this when you will have time, tons of musicians here have invested such effort in LK.
THANKS to LK!!!!!!
Not a shameless plug, just to give you an idea of my motivation with your app 
@Jeezs Can you try to repro this:
It seems that at 90 bpm notes are doubled only if notes off are snap to the grid. No issues if you you record via midi controller, only if you enter manually notes in edition mode. Just select all notes and change notes duration with snap to the grid disabled. This should work
@xglax @sinosoidal
@xglax and @sinosoidal
About my notes off wrong/missing issues above it seems that I’ve found the culprit too: when recording iFretless bass as a controller routed via LK to another iFretless bass instance, when playing with bass note gliding some pitch bend data is recorded in LK. When quantization is enabled that pitch bend data is recorded/quantified a specific way, I asked for this fix one year or more ago. It works perfectly except that it seems that some notes off are missing/played on wrong notes on other LK midi tracks so any instrument can be impacted, in this case it was mostly audible on a piano but also on iFretless bass (which also had some odd pitch bend playback playing). This is very random. Anyway, deleting iFretless bass pitch bend data fixes ALL notes off issues on all tracks. Using iFretless bass in fretted mode with no pitch bend is the workaround. Writing pitch bend data in editor directly seems to give to issues, this is only with iFretless bass recordings and quantization on.
Hey all… since I kinda started getting warmed up to the idea of clip-based live performance due to my time with the Roland MC707, I thought maybe I’d give LK a shot, but reading this thread makes me hesitant to dive into a half-baked mega app…
What’s the consensus? Is LK stable enough to learn? The devs responses are not all that encouraging.