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
It all depends on the granularity of the values. I have a feeling that the MIDI CC restriction of 128 values might be a little too coarse even with a max plus/minus of 1. On the desktop plugin you're able to achieve the same goal but using the full floating point resolution of host automation - that's obviously far more subtle, but the desktop plugin is ten times the price, so you'd hope there were bonuses! Another reason I'm happy I purchased the desktop version is that RAM isn't something you have to consider (especially if the workstation is stacked full of the stuff). I'm thinking that some of the errant behaviour people have been experiencing with the iOS version is down to device RAM.
I've been recording with full bar multiple loops and keeping the audio content away from the first and last 16th (or thereabouts), just to give a bit of freedom ref timing modulations. Helps stop clicks with subtle time variations. And as long as you keep to the same approach with the overdubs you should be safe. The other obvious thing, is to add reverb/delay and suchlike outside of the feedback loop. Helps glue things together without breaking the empty areas at the beginning and end of the recorded loops.
I've not had any problems but I've stuck to full measures on the quantise.
Another idea for wow and flutter is just to drop DAW Cassette into the signal chain after Enso, then dial up the quality settings for everything except motor quality.
This is exactly what I meant when I said earlier in the thread that Enso is unique and an instrument in its own right. By getting multiple versions going you have to think differently about how each "voice" fits and "fades" into the overall chorus. I find it to be challenging my old habits with fripperlike stuff.
It works perfectly! Thanks for the head slapping moment.
And come to think of it, Tap Delay has great tape emulation settings, there's even a Cassette preset (you'll want to lower the OTT hiss, but it will add wow and flutter no problem).
The quantize options are called Mode Quantize which implies they apply to the mode buttons. It would be cool to have a quantize option for the sector play buttons, too. It might be worth sending a note to that effect to Audio Damage.
My main wish is an option for a micro fade in/out at transitions to eliminate clicks.
And be sure to play with the Dub in Place setting. Turning it off lets you set up a tape-like degradation with hiss gradually building up.
That's exactly what we've been talking about with regards to 'Frippertronics'.
I'm personally not interested in using Enso with Dub in Place enabled, as there's any number of loopers that can do that.
It's surprised me that AD didn't go the Ableton route and have a default crossfade at the start/end of all audio chunks (a setting that the user can choose to disable). In Ableton it's hard to make an edit click, even with imprecise cuts that aren't 'through zero'. Auto crossfades can be troublesome if the user isn't aware of them but I would agree they're a great default option for a looper.
Set up Enso to midi map cc for the + and - values, then set up @brambos perforator to send those + and - cc values. So instead of sending LFO you’re sending increments. Just make sure you have same number of + values as - values or it eventually runs away. That way you can use Enso’s native increment values (ie the .01, octave, etc) to control how much each step modulates the value.
This is a pretty inspirational app. I’ve stopped trying to sequence stuff in cos I’m shite at it, but just playing basic licks into it with a beat on another channel is beautiful. Using it in its most basic way is fantastic. Itl be great for for improving playing chops and timing. I love it.
I posted this in the Creations thread, but I'm not averse to a bit of spamming, and thought it might be of interest to anyone using Enso. This began as an iMS20 jam through Enso, and that's going all the way though in the background with just a bit of Reason/Komplete stuff on top. I wasn't sure how this would fit into my workflow, but I can see now that it's great for jamming with, and could trigger all sorts of ideas for finished tracks:
Beautiful. Great job! Love the percussion/drums in later half.
Now that sounds interesting. Nice thinking good sir.
Ignore the ear bleed of this lol but can anyone tell me why the 2nd instance of enso records a 4 bars but only plays back one... Skip to the end to see what I'm talking about.
Enable the long memory option. Enso does this when the recorded loop exceeds the buffer memory allocation.
Haha wow really pushing the audio there!!! It's outside the circle 😄 sounds good tho
Oh dang, I was hoping to have like several ensos going with at least 3-5 minutes of loop , even with long memory it seems it'll be limited to about 60 seconds if you're using more than one instance!!
Anyway, thanks for tha answer, that'll have to do!
If you’re just wanting to loop stuff and don’t need all the mangling, Loopy is your friend.
Props for this screenshot from the manual:
I think the thing that's likely to catch people out with multiple instances of Enso in tandem with other instruments and FX is that iOS has a maximum RAM allocation of 360Mb for all combined AUv3's in use. It's not just the record buffers in the Enso instances that need to considered. Much as Enso has the long buffer option, one's ambitions with the feature will be clipped by the operating system limitation.
As great as iOS audio is, it's still crippled by operating system handcuffs that come down to Apples inability to couple Pro RAM capabilities with the Pro processor. Serious desktop audio workstation average 64Gb to 128Gb RAM these days. As awesome as the A12X processor is, it's not going to enable serious Pro work without equally awesome RAM capabilities.
It's a primary reason to consider purchasing the desktop version of Enso to go alongside the iOS version.
Absolutely, I love loopy, it's deff getting the dust off it since enso came out haha... Was really wanting enso to be the au solution for making the workflow better but regardless enso is a beast for what it can do, so I'm not mad hehe it's amazing still, and I can just keep over dubbing on one instance anyway..
Really going to need Apple to step it up with their pro audio!!! Ugh!!!! They deff should consider this in order to advance iOS to the next level
Really fucking good.
I’m getting a lot of issues with the record head just stopping...
Record then to overdub, mess with play/red speeds enough and the rec head just stops. Doesn’t record again until you press 1:1
It happening all the time for me... 😞
As I don’t really ‘jam’ I’m trying to work out how this fits into composing in a daw. I suppose having it on a send track allows you to record to it then control it via automation
Using a send track or subgroup track in combination with automation is a great way to expand your composition especially if dub in it's many guises is something you like to explore. But equally looper tools aren't for everybody and Enso is just one iteration of looper in a long tradition like-minded tools.
Here’s a video showing how Enso can be used to reduce CPU utilization in quick jams. There are many, many other ways to accomplish the same thing, but I find this kind of handy...
Thank you sir!