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
From what I can see it's a good alternative but no better than some other options. I was going to get this because I do love different LFO tools...but then realised I could build much more varied LFOs in SunVox (now it has midi out) which has more unlimited possibilties
It’s at a low enough cost that it won’t be a calamity if you don’t use it, but the low enough cost wasn’t enough to tempt me seeing as I already have plenty of LFO options (Arthur Kerns, Brambos, Sunvox etc). I tend to think twice these days when it comes to iOS MIDI utilities as the compound effect of using too many can end up adding too high a processing load for the reward.
The great thing about Max for Live MIDI utilities in Ableton is that after you pay the initial hit of loading the first M4L device, secondary devices come almost for free so you tend to chuck them in all over the shop, in the knowledge that the penalty won't be too high (within reason, if you're adding a complex device, the hit will be proportional to its capabilities).
I like art’s as well. Basically it has 16 LFOs, instead of 4. It was only $2.99 Intro price so I grabbed it. It does do really extreme speeds of modulation fast and slow.
I'm always a fan of slow lfos, if it can go even slower than midiLFOs, i might be tempted.
How does 130442 beats sound? Slow enough for you?...😉
I think I'm having a major User Error issue, but it's possible it's a bug in the app so maybe someone will see this and can guide me. Pardon my clunky terminology, I am a CC noob and am using this app to help learn it:
I had an instance of mLFO going earlier today, with two LFOs - one controlling an instance of TAL's volume (LFO 1 of 16), another controlling OSC2 detune on OBXd. Once I engaged the second LFO controlling OBXd, the routing of LFOs between the apps got all sorts of tangled. TAL would listen to LFO 1 & 2, or none at all. LFO 2 started detuning TAL somehow, and everything got a little chaotic for a second so I ejected mLFO, and restarted the AUM session. ANYWAY...
Like I said, I'm a CC noob... Are CC channels the same as MIDI channels, or is it at least recommended to keep them similar? For example, in this AUM project, the TAL with the LFO pointed at its volume was the 7th channel I created so its default CC for volume was Ch 7, CC 5 (or what-have-you), so I pointed the LFO at channel 7, CC 5 and hooked it up to TAL via MIDI routing. If this instance of TAL is receiving MIDI on channel 1, should I just change that AUM channel?
I know I could figure all of this out with a few minutes of noodling but I'm away from my iPad and this all happened this morning before I left the house while I was having my coffee.
Yikes at that wall of text. Thanks!
P.S. @Poppadocrock I had some crackling the other day in AUM with an instance of mLFO, but none of my experiments with this app have been "keepers" yet so I can't pull that project up to confirm.
The thing that always brings me back to Arthur Kerns LFO is that it has a negligible CPU overhead. It’s also more than slow enough for my needs. I also like the UX and visual feedback.
AUM "channels" - lets call them "mixer lanes" to avoid confusion have no relation to MIDI channels. You can have mixer lane 7 listen to any combination of midi channels (you choose these in the midi setup panel). It defaults to listening to all channels. So if you want to be sure that TAL only listens on a particular channel, make it the only one highlighted in the channel dialog. So, yes, setting AUM to listen only to channel 7 will help to avoid accidentally getting LFO input from other channels.
What I don't know in your case is if TAL is listening for CC 5 for volume directly in the app, or through AUM's AU Parameter control. What I suggest is to use AU parameter control. If you do this then you don't need to route mLFO to TAL at all. Instead you route it to MIDI Control.
That should be it.
Sorry, I know that probably sounds confusing. It's difficult when there are multiple uses of the word "channel", multiple ways of routing, and multiple ways to control things.
You'll get it. Be patient, and before you know it, in 5-10 years it'll all start to make sense. 😉
Turns out, what I really need to do is go back and watch some AUM tutorials for a (deep) refresher. I thought the routing matrix and MIDI control were interchangeable (or worked in tandem) so I must have been mixing signals a bunch of times, going in circles.
This explains a lot about some recent sessions where I've had to disconnect EVERYTHING and go back through with a notepad. Sheesh.
@wim thank you so much for this write up! That was extremely informative AND eye opening. With how... ornery the internet has become, and with how shitty google results are these days, I'm very happy to have such a welcoming board where I actually feel comfortable posting questions like this and being able to figure this out before it compounded, or made me give up on developing my mad midi skillz.
Thanks for the info.
Great, @timelining - I’m glad it made sense. It didn’t feel like it was going to as I wrote.
Possible bug report: I’m enjoying the super slow rates you can get with these LFOs, and the fast way you can assign ccs- BUT - I often use LFOs to automate fader movements in AUM, and shifting the Phase option on two different ones does not let the second fader move at a different point in time to the first - it seems everything defaults to the phase of the first LFO. Annoying… Art Kerns’ offering has no problem with this. I’ve emailed the dev, and I’ll report back.
I’m a big fan of midilfo. And I use a lot of LFOs to control parameters in a single synth. What I like about mLFO is the 16 in one window— one LFO window, one synth window. I also like that you can midi trigger the LFOs. But here’s a request: a way to trigger the individual LFOs from the overview window. You can currently solo each LFO with a long press, or trigger each with note input, but that will only toggle (not what I’m after but interesting). Each LFO can be activated with midi cc (parameter exposed in AUM). So….
Is there an app where I can build an interface, much like Lemur but AUV3, to send cc messages from a single window? LK CC comes close but that’s limited to 8 strips—I’d love to have 16 (or more!) per window.
Hope this makes sense, and thank you.
miRack, Audulus, and Sunvox are the closest you’ll get. miRack would be my pick of the three as you’re not having to build things at component level (as long as you’ve had a bit of experience with modular’s, you’ll be fine), and much as I love Sunvox, the Tracker mindset can take a while to adjust too.
Ok, thanks, @jonmoore. Looking for an AUV3 solution, so maybe when loopy pro midi happens, we’ll have the AUV3 “lLemur” some of us have been waiting for.
Those are all AUv3.
Well said. This is the spot my friend. For the most part, We all try to keep it that way too.
maybe i misunderstand, but loopypro au already can send midi from it's various widgets...
He’s talking about creating bespoke cyclic modulators, envelopes, rise/fall modulators etc, etc.
so i got this totally wrong. sorry
Did you just respond to developer via the AppStore or find a better way to contact. I wanted to mention my crackle issue. Thanks.
@Poppadocrock : hi yes, and got a prompt friendly response where he had made a video failing to replicate my issue. axilleas_sourlas is findable at axart.net.
Recently updated. Can now set the rate with a single tap (well, ok, two taps) using a button matrix. Useful!
It happened to me a couple times. But hasn’t happened since I posted about it. Not sure if an update fixed it or my cpu was running high or what, but it’s been awhile since it happened so maybe it was user error, or a device issue.
Thanks for looking into it though. Are you still having the issue.
Great Stuff!
Hi there! (first post here on Audiobus btw
)
I'm using mLFO in Loopy Pro and I'm unable to save the user defined LFOs, so I basically need to redraw the curve every time I close the host (Loopy). The other settings are saved though, so I was wondering if the issue is with mLFO or Loopy Pro.
Welcome @unlink! 😎
That has to be an mLFO problem. Sometimes developers don't properly implement saving of some parameters. When that happens there's nothing that the host can do about it.
If you have another host that you can test it in, that will confirm whether this is right or not. Or maybe someone reading this can test in AUM or another host. I don't own the app myself or I would test.
Hi wim! You are right, Drambo does the same. I'll email the developer then.