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
Same here, freezing when editing notes after a minute or two, and during playback.
This will be hard one to fix for @xglax since it has been around for so long now ....
@janosax no other AU crashing at the same time, all is and have been stable for years. LK is the only unrealiable app in my quiver, sadly. since i rely on LK for composing/performing, i am running it in crashed state live which feels really, really awkward ....
Running it in crashed state? Do you that it is crashed or that the u.I. isn’t drawing? These are two different issues.
UI is unresponsive/frozen, sorry .... is hardly ever crashes on me (plugin crash, reload necessary).
1.12.6 beta just came out, no freezes or crashes tonight (yet)
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?
Did anyone find a solution to this? I also have the same issue of LK becoming unresponsive in a pretty basic project with a single instance of LK sequencing 2 tracks, along with a few other tracks (drums from eg pulse and one track being sequenced by Aphelian) on my iPad Air m1. I’ll see if I can reproduce it but it is happening very frequently and does not appear to take much to happen, e.g. in one case I made some minor changes to one of the scenes and closed the window, then tweaked an effect on one of the tracks being sequenced by LK, and the window was unresponsive immediately after that. Everything else is working fine, and lk itself does not crash but becomes unresponsive and greyed out like reported above. Also if I remove the lk instance and try to reload then it just says “still waiting..” and the project stops responding but doesn’t actually crash.
I’ll see how it goes with tweaking a track not being sequenced by LK, not making changes to any of the scenes, adding to the project without lk and then fiddling with it etc and see if I can reproduce some steps.
It’s kinda disappointing though to see that this issue has apparently been around for a while but still does not appear to be solved. I can’t really think of anywhere else that lk would be really useful other than within AUM. I’ve been sticking to daws and using AUM only for jamming and working alongside the daw, and was hoping to do a bit of both with AUM i.e. also lay some sort of structure within an AUM project. Haven’t used lk in a while but it would be perfect for this if it actually worked. So hopefully I can solve this problem or maybe will give Xequence 2 a shot.
I had the same issues with LK in AUM - after a few minutes the UI locks up and everything you did is toast. Really disappointing after so many positive comments on the app. For me it was a waste of money - no point in losing your work every few minutes.
Hopefully Imaginando gives LK some love after their new app is out. I won’t be buying any more of their apps till they fix this issue.
Just on a wild-ass guess, what are your buffer settings in AUM? Even though midi apps don't produce audio, they still work within the sample-rate and buffers of the host.
My buffer size is 256. Should I try increasing it?
Nah, that's probably not it. Some apps have trouble with very large (2048) or very small (32) buffer sizes.
The only other thing I can think of is to check carefully that you don't have a midi loop going on.
Hey, if that can be of any help, it happens to me sometimes too. Is your LK instance responding (eg midi thru or playing) but the window is all black? In my case it is always running, and resizing the plugin window makes the UI show up again. My 2 cents.
-see edit 3-
EDIT: Should've mentioned this before, most of the time when it becomes unresponsive it's usually alongside note hanging and afaict the gui becomes unresponsive BEFORE the note hanging occurs.
EDIT 2: noticed that the devs confirmed on the main lk thread that they will look into this more closely once BAM is released, so here's hoping for a resolution soon.
EDIT 3: none of what I wrote before is relevant because eventually as a project develops lk just starts locking up or becoming unresponsive all the time and is unusable in its current state. It's by far my most unstable auv3 app and I really hope they fix it soon.
Didn't occur to me before that I could just use Drambo for a clip-style workflow. Limited to 16 tracks per instance when hosted as an au within aum but that's more than I'll need in practice most of the time anyway. So I guess my solution for now is to just use that instead of lk, and the silver lining in all this is that as a result I'll finally dig deeper into Drambo too.
No, I'm not on the beta list. Was testing in MiRack today, LK hangs every 10-15 minutes and one time I completely lost a patch in LK.
Is there a new beta? I was on the beta but the last version is long expired.
I’m having lot of problems too, it hangs when LK is hosted in AUM but also with LK in standalone firing AUv3 instruments that are hosted in AUM. Had lot of investigation and seem that the instruments and effects already loaded in AUM have an effect in the % of possibilities for LK to hang…. Been preparing and Playing “in C” by Terry Riley along a string quintet and is was a pain for live… it’s a piece with just 4 tracks, 53 patterns and about 45-55 minutes long…. LK standalone send MIDI to AUM. I’m manually firing the clips using a Launchpad. LK hangs almost once from three times we play. Managed to lower the % by unloading imaginando owns K7D echo from AUM and substituting it by dubstation2. Mérsene seem to hang LK quick too. Don’t know how those plugins hosted in AUM can have the effect in LK standalone… but they seem to have an effect! @sinosoidal , @j_liljedahl any clue?? Thanks!
I understand they need to focus on one thing at a time, but they're talking about deferring for months or a year, not weeks, effectively abandonware - I've given up waiting on stability and moved on to other tools.
LK seems like a dream come true but some of the instability combined with learning a new workflow had me sideline it for now. I blamed my 2017 iPad for the performance issues at first, I have been meaning to try it out again sometime though. Some of the workflow system design is really intuitive, especially for someone who primarily uses AUM (but probably should be using a real DAW instead lol)
Well there was one positive about LK being broken. It made me learn Drambo inside out and now I don’t need LK anymore. It’s a shame as it’s a great piece of software, if it didn’t have these freeze issues that have been around for months. I understand that resources are limited but we have essentially paid for a lemon. That is not cool. It’s like a car manufacturer saying well we know this model blows up every other time you start it, but we’re working on a new SUV and once that’s done we’ll fix the model that blows up.
This is coming from a very big fan of imaginando and all of their apps. They are a great team and very responsive all the time. But they dropped the ball on LK. Perhaps a lesson learned for imaginando.
Sorry if I’m asking a stupid question. What is the difference between BAM and LK.? Isn’t BAM a replacement for Lk? Many software protects need to be rebooted due to accumulation of design flaws and legacy code, applying what the developers learned in the process.
LK is a stand-alone and AU midi sequencer and controller. BAM is a groovebox, similar to Grooverider 16. The sequencer inside BAM is based on LK.
Thanks for your comment. But since you are replacing it with the groovebox functionality of Drambo, can’t the same goals be achieved with BAM, which is compared frequently with Drambo in that area?
BAM as a clip / scene launcher with follow actions is definitely the fastest way to get a song going in AUM/ ApeMatrix.
Thank you very much. The reason for my questions is I’m evaluating the best app to emulate in iOS the Berlin school techniques that SynthtSeeker explains in his YouTube channel, using Ableton Live. I'm guessing BAM or Sand may fill the ticket, also Drambo
Yes it can. BAM is just not completely baked in yet. Right now in my opinion as a groovebox mimicking hardware GR-16 wins the category. As you know Drambo is much more than a groovebox. When BAM is ready it will be definitely a contender in the beginning and can become a leader in the groovebox category.
I used LK with AUM not Drambo. Drambo’s sequencer is great. I used to use LK in AUM as my main sequencer, especially for live performance. With LK and bunch of sound and effects AUs, I’m basically creating my own DAW. But I can’t rely on it for a live set anymore. Drambo fills in all the holes and much more.
I have videos on my YouTube channel (@rezolve-music) showing what I used to do with AUM, LK and a couple of midi controllers live. I miss LK 😞
I want LK for other things besides just using the sequencer in BAM. And it’s lightweight on the resources so using BAM to sequence things outside of it doesn’t make sense, at least to me. LK was made for that.
I’ve been trying LK with apeMatrix instead of AUM, I put the same instruments in ApeMatrix that was in my AUM session that crashed constantly, and left it running for the whole day. That’s almost 12 hours continuous playing and is working fine! No crash… I’ll try tomorrow again replicating the entire AUM session including effects and also connecting the Launchpad… maybe is the LK-AUM combo what is failing?? Anyone with the hang/crashes in other DAWs or just in AUM?
Did they actually say that long? I know the last time it was brought up @sinosoidal said it would’ve be right away but never said it would be a year. Just that it would be after BAM is released.
Any further word on this problem? I tried working with LK again tonight, and am still losing the UI. Very frustrating, and after more than half a year I’m beginning to lose faith in Imaginando. I question the ethics of a company that devotes resources to developing new apps while still selling apps that just don’t function as they should.
They have explained in a number of posts that due to their limited resources, they have been focused on completing BAM. To create BAM, they have created an updated framework that will allow them to update LK. BAM has just been released which I think means they will soon start updating LK with the new framework.