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
Anyone expecting freezing issues with Enso? The only time my iPad Pro 3rd gen locks up—no touch response then AUM crash—is when I’ve got Enso in the effects slot.
I do for sure if I use more than 2 instances. Only time AUM ever crashed for me in all these years. With one or 2 instances - less crashes but still sometimes. Usually just Enso crashes though. But 3-4 Enso and total lockup freeze crash.
Yes had issues in AUM hope it’s not Abandonware already may be due to RAM / buffer issues maybe it’s unfixable issue.
I used Enso in a recent remix and had 4 instances feeding off each other but this was with a second gen iPad Pro and apeMatrix as the host. The performance was silky smooth but I'm not sure I'd push things any further.
I suspect it won't be abandonware as it took quite a long time to come to market (I remember seeing it at one of the trade shows at least a year before release).
Until iOS devices come with more Ram, Enso is going to perform better on the desktop but I like it on iOS as it somehow feels less like a plugin.
At first, I thought you were hoping AUM wasn’t Abandonware.
If you abandon the idea of using Enso like Loopy, and just use it as a Tape Looper, it works pretty well. Put it on a buss so you can selectively inject different tracks into the loop, or adjust the mix of what is being fed into it. You can get a lot of variety out of just one instance.
No freezing issues for me, but it crashes quite a lot. Love what it can do though. Once you midi control it all it becomes lots of fun.
Follow-up: Enso is consistently freezing my iPad Pro then crashing AUM (3 instances), making it worthless fo live use.
Is there a fix in the works?
I love this app but can’t use it!
Plus 1 on that great app but crippled comon @Chris_Randall please fix this.
I sent an email to Audio Damage last night about Enso crashing/freezing. Perhaps anybody else having issues contact them as well.
Contact AudioDamage directly. They probably won't respond but they will see the message and know more about the number of people that care and are affected.
I contacted them day one about the app and desktop issues never heard back.
Yeah I contacted them a while ago, but hope more people email them too.
It is worthwhile writing to devs even if they don't write back. So, thanks for contacting them.
Not sure what's going on with Audio Damage these days. Chris used to be Mr Social Media, with lots of direct contact with customers and potential customers. One can only presume that he's got a lot on or he's been burnt once too many times by the ugly side of social media so now he only uses social channels as a broadcast medium.
My biggest bugbear is that the desktop apps no longer have published release notes. At least these are forced on AD with the iOS App Store. With the desktop apps after release, you've no idea about things, especially whether bugs that you hear about through social channels have been fixed.
Not so long ago the release notes of both the desktop and iOS releases were published on KVR, so you always knew where to look for update and release info, but now there's nothing.
Just successfully recorded 5 looping instances of Enso in AUM, but now i can’t play them, nor load them after a reboot. Enso crashes after loading 3 instances in either AUM or Audiobus 😞 Started a twitter thread with Chris if anyone wants to draw more attention to the issue:
I also emailed support fwiw.
Ok, so here's the workaround to get over the crashing. I just record a loop into Enso, then save the Buffer to my AudioShare Folder. Then I load that file into AUM via File Player and play it. I then record another loop into that same instance of Enso and save the Buffer to AudioShare. I repeat this as many times as I need to based on the number of loops I want to generate for the given composition I'm working on. Not great...but at least being able to use the great Looping/Capturing aspect is nice...until they fix the CRASHERS
@echoopera your Enso instances will perform better if you turn Long Memory OFF
Yep...did that...and still crashes with over 3 instances.
😳 not sure what else to try then...
I'm just recording my loops in Enso (single instance) then Saving the recording to the Buffer, and loading it back into AUM File Player, and recording my next loop in that single instance of Enso (after clearing the previous loop).
It's a little slow from a workflow standpoint, but it's working now. Sometimes slowing down is ok ya know
If BlocsWave had the time stretching feature of AUM or Enso, I'd probably just use it...but as of now, I like recording into Enso from in AUM...crashes aside.
A few days ago, I started up AUM and loaded ENSO to a channel, instant crash - nothing else running besides AUM/ENSO.
I restarted and tried again, got ENSO to load - recorded a 4 bar loop, but messed it up, so I deleted the loop, and then as soon as I hit the record button in ENSO, total freeze of AUM. (nothing running but AUM, Enso, and 1 synth)
I could understand the crashing if I was recording long loops, or had other apps running at same time - but I often get total freeze-ups or crashing with Enso set to only 1-4 bars and little else running (and the Long memory on/off doesn't seem to matter in this kind of situation)
It is pretty unstable with more than two instances even if the loops are long. I've contacted AD about it.
I think @WaveMachineLabs has contacted them in response to bugs I reported with Enso/Auria Pro issues. There a second instance reliably causes issues. I like Enso a lot but have used it less than I would because of the crashes.
In my opinion, they also need to make clicking less likely to happen my adding a micrafade at the the loop point.
Also using it far less than I would like due to the crashing
but the click at loop point is also a major issue, especially if one is experimenting with reversing loops etc live. Really makes it unusable for what it actually was designed for!!
Agree. I put in a request for 1. A slew control when you go from fwd to rev to simulate some inertia in the drive system... seems obvious.
Also ax’d for a record level. For instance, I want full input volume, full loop an dry, but I want the new recording to be barely perceptible so I can “smear” a thin layer on the loop each pass. Kind of like feedback level, but for new signal.
I’m having no problems here on my 2nd gen iPad Pro.
4x Enso instances
I often use 4 or more on my 2nd gen pro. Sometimes there are no problems, other times crashes and freezes. So it’s unpredictable.
After spending a bit of time with this, I think I finally realise that it's an app that really only works properly on an iPad Pro. If you have anything else, forget it... I think Audiodamage need to own this now and advertise it accordingly.
What kind of iPad are you using?