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.
Loopy Pro: FIRST LOOK
This discussion has been closed.
Comments
Yes, you see i blew you a kiss there at the end?
How lovely! ❤️ ❤️ 🦄 🦄
@gregsmith yes this is exactly the technique that I meant. I’ve seen this video some time ago but unfortunately I didn’t bookmark it. Now I did. Thanks. I successfully adopted this technique with my Arturia BeatStep Pro that drives an iPad drum app. It‘s really working well.
@espiegel123 Thanks for sharing. So theoretically it would be possible. I just think it might be a bit tricky to control this setup in a live situation. Do you think one of Loopy‘s UI widgets could control the recording of Atom 2?
I think it would be so cool if Loopy would already embed everything that is needed for the Jeff Mills technique so we wouldn’t have to struggle with wiring up Atom 2. But AFAIK Michael plans to add Midi features later on. So this would be on my wishlist.
Loopy’s widgets can send midi and do anything you can (and more) as your fingers. Also there are follow actions
No, not in the way you're thinking. What you would want to do now if you want just one unified project is to put Loopy on a bus, then use bus sends on the apps you want to capture. You'll need to capture them one at a time.
Or, you can host all the apps in the standalone. One huge advantage to doing that is the amazing "idle" function for apps. When you bypass an app in other apps, it doesn't free the resources for that app and doesn't really help your CPU use. If you're outta gas you have to delete the plugins and make sure you have a way to put things back the way they were if you need to make adds or changes. In Loopy when you turn a plugin off it's as if you removed the app entirely from the session. But, when you bring it back, all the state is restored for that app.
I still work on an iPad Air 2. I can add as many synths, FX and amp sims as I please, capture the ideas, idle them, and move on practically forever, while keeping well below 30% cpu all the time, all the while knowing that if I want to add new ideas with those idled apps, I can instantly re-enable them.
The other night I even added Visual Synthesizer on the master. When active it was pulling 50-80%. When idle, CPU was below 15%. This meant I could keep VS in the project while I built the music and only needed to burden the CPU when I wanted to work on the video.
It's amazingly good.
So true, brings fresh life to old machines! And Loopy Pro streams audio from disk, as well. Remarkably efficient!
I seem to recall Loopy multi-outputs are on the roadmap. I think that’s needed for the AUM - Loopy auv3 combo complete. That is, if you prefer AUM over Loopy standalone. I’d say the deciding factor here is what’s your primary source, midi or audio. The mixer in Loopy has evolved tremendously but AUM is amazing and obviously more mature.
Without multi-output Loopy in AUM is pretty limited, basically a really good looper, but no sound tweaking after, all the fx would baked in. Unless you use multiple instances of loopy, one for each instrument… wow, it gets confusing!. Anyway, I’m really glad that there’s a lot more focus and efforts on audio in iOS. Audio was way behind midi and Loopy is stirring and shaking things up.
You'd need multi-inputs as well to do what @gusgranite wants.
Yeh, multi-outputs are needed for that. Should be on the way some time after release.
I think this is what you mean? Seems easily doable. (though I think Atom is not yet fully stable transmitting the notes as you hear, or might be user error…)
[Xequence keyboard recording in Atom that quantizes the bunch then unmuting Poison)
Anyone know how to extract samples from Apps like Launchpad to use with this?
You can use the record function in Launchpad. (the recordings are quantized to the beat)
I think there’s no ‘direct export’ in Launchpad?
I think I could do with this to make jamming productive, I have a less-than-functional habit of playing then just walking away…
At this point in time if I’m going to spend-to-support imho it’s the host developers that need it.
There’s a strange bug with atom2 in loopy at the moment so I can’t confirm the Jeff Mills hypothesis.
I know Michael has all sorts of midi plans coming. I have no problem with using atom for the time being.
Here’s a couple of ways I’m going to test:
Route the audio source (eg koala) to a donut with retro record on. Route midi controller into atom, into the audio source. Tap out a beat, recording midi into atom2. When it finishes playing the quantised loop, hit the donut to grab it as a retro record. Stop atom / mute the audio source.
Setup as in 1 but with threshold recording rather than retro on the donut. Turn off midi thru in atom (this should effectively mute but still save the notes to the roll, right???). Tap out the beat in time. (Might need to turn midi thru back on at this point?). Let it play the quantised loop - the donut will automatically grab this with threshold recording.
There is a strange looping behavior of Atom 2 in Cubasis when Cubasis is also looping. Both loops don’t get along. AFAIK both devs blame each other. Is this a similar issue?
Sounds like a plan (or two). Please let uns know how it works out for you.
Don’t think so, no. This is something to do with not all the midi notes sounding.
Will do! 👍
Sorry, missed this! That’s basically it, yeah. I think that’s the same atom2 loopy bug I’m getting. It doesn’t seem to happen with every synth
Ok, here’s a video test 1 on iPhone. I used Drambo’s sequencer for the quantized midi to get round the atom2 bug.
So the first loop you hear is me playing sloppy, second is Drambo playing it back quantized, third is the donut + Drambo as I didn’t mute it quickly enough 😂, but then I switch to an empty pattern so you can hear just the donut.
Presumably it’s easy enough to mute and unmute Drambo Jeff Mills stylee, but it was already fiddly enough on iPhone!
LK doesn’t seem to have Atom’s troubles.. But I don’t know how to let LK quantize immediately after recording (I can only do it by selecting the notes and then quantizing, which works fine)
edit: t was right in front of me just not used to LK, but fun this method..
Oh that’s good. Last time I tried LK in loopy it had similar issues to atom2, just not as bad, so I assumed it was the same bug.
Loopy and Xequence also seem to get along on a first try-out (Ableton start/stop, playing an AU in Loopy via Xequence MIDI, MIDI learn). And you can have ‘‘em both on the same screen.
Has anyone tried using any of the Lumbeat apps like Soft Drummer together with Loopy Pro?
I am hoping it will work as well as the Lumbeat integration that Quantiloop supports.
@gregsmith and @janpieter thanks for your testing. Good to know that this basically works. It’s probably the question if this is a feasible workflow or if it is maybe too fiddly. BTW, how to make LK auto quantize after record?
The initial Loopy Pro release does not support audio from IAA apps.
@BladeRunner
I have recorded reggae drummer into loopy pro via AUM, didn’t have any problems
Didn’t try anything technical, but recorded lots of loops at different lengths etc
Was all i needed
I should have phrased that better standalone Loopy Pro doesn't do IAA (yet) but as an AU in Audiobus or AUM, you can send anything at it that the host can see.
Is it going to get released this week?
Awesome news.