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
I’m not there yet, but I think I will still need those StreamByter scripts because I’m so used to use them daily since several years. Perhaps some things will be more easy now, especially effects management in my case. What Loopy Pro seems to certainly brings to us IMO is an all in one looping environment with groups, multiple sources/colors, midi support, effects/on screen controls, timeline/sequencer, advanced auto detection, and much much more. It’s very deep!! It will certainly partially change the way I approach some of my looping, because it opens to new possibilities which can/must be explored. Now, it’s needed to answer this question: what kind of music I want to make with it? That will define how I will use it. Or will it inspire me to create new stuff/differently? I’m sure I will not be the only one in that case, as less limitations leads to a more open world. It can be frightening but who don’t like to explore freedom?
Loopy Pro’s many follow actions simplify a lot of things that one might currently have needed to use StreamByter and Mozaic to do in Loopy HD. The actions let you set a lot of parameters, too.
From my perspective, I feel like the modular design of loopy pro also allows me to say yes to almost all requests, because pretty much everything has a fairly natural home in widgets and actions, without adding clutter. That’s a big win for me as someone who likes to say yes 😄
OK... let's play the "How Many Pages Will This Thread Be When Loopy Pro is in the App Store?".
Just like the months we waited for Drambo and the thread got longer and longer. Good times.
I'll take '69.
Please say “yes” to MIDI filtering and MIDI inputs for MIDI AUfx! 😉
@Janosax mentioned Streambyter above and that’s a great example of a modular piece that I’m not sure you want to build yourself as a widget?
That said, I love the concept and the execution of the widgets!
He’s already said yes to these 🙌
The audio unit effects are they only available in the Standalone?
Most likely yes since an AUv3 can not host another AUv3...
From the looks of it Loopy Pro is turning out to be a pretty awesome AUv3 host so the 'need' for AUM etc. will likely be reduced.
AUv3 can’t load AUv3. Loopy Pro has a number of built-in effects and it eventually be multi-out.
The crazy thing about Loopy Pro is that it can be configured to perform like a mini facsimile of Ableton Session View, should that be your goal. It's so much more than a looper, but when used as a classic looper the configuration options allows you so much flexibility.
My personal use case is more at the mini Ableton Session View side of things, so for me, @Michael being the Audiobus man from Delmonte, means everything from this point is all gravy from a functionality perspective.
Except ableton session view does midi and audio right? I’ve never used ableton so genuinely don’t know.
This is what I’m aiming for with my LK/Loopy mashup anyway, though dunno if there’s any plans for launchable midi clips in Loopy?
Edit:
This has just sparked a thought…
You can setup a donut to have a ‘play’ follow action and a ‘stop’ follow action. These can be midi notes or cc’s sent to an au. What if that au was atom 2, and it was set to launch and unlaunch on those notes? That would be a way to make a donut a midi clip launcher right?
420 (sry, it is the internet)
Blaze it
Yes, but not at initial release.
I'm guessing Atom 2 or another midi looper can be hosted in it and do basically the same thing until then though.
Just edited my post with this and you replied in the meantime 😊
Hadn’t thought of using atom 2 yet. Hmm. I’ll try another proof of concept.
I didn’t realise midi was planned for Loopy though! That’s absolutely huge!
Ok, just tried it and it won’t work yet because you can only target follow midi actions to audio sources, not midi sources. Hopefully will change when @Michael allows midi sources to control other midi sources
That's dope.
I'm curious about beta testers using M1 ipad pro's on iOS14.8 vs. iOS15.
I'm still on 14.8 because it is very solid but wondering if iOS15 offers better M1 CPU/RAM utilization?
At earlier stage when I asked M about this it was one of those rare ‘not likely to happen’ in the thread. Not sure if that changed since.
I think you can do it now by setting a clips Follow Play action to tap a widget whose Tap action is to send midi.
You would have to do a little midi routing shenanigans by sending the midi out of Loopy and having it loop back to a midi input LK is listening to. There are a few ways to accomplish the loop back.
Ah I see. Sounds like a ballache!
Probably easier to stick with using LK in Loopy for now until midi donuts exist
Yep, LK or other MIDI clip solution works much better IMHO. And the widgets can certainly help create the "glue" between LP and MIDI clips.
Loopy Pro itself would be the audio loop aspect of Ableton Session View. Ableton was audio-only for many years before midi clips were added and Session View was effectively an environment designed specifically for audio loop acrobatics. As to midi loops, I think it all depends on how far @Michael wants to go with Loopy Pro as a host environment. Follow actions are an Ableton invention too and these will prove to be super powerful just as they are in Ableton. I have no idea as to whether the original intention was to make Loopy Pro customisations so Ableton like, but I suspect much of the direction of travel comes from how well the Launchpad Pro Mk3's function as hardware interfaces for iOS apps like Atom 2 and Loopy Pro.
One big advantage to having Loopy pro do the midi, or at least loopy widgets launching midi clips in some way, is for clean launchpad integration.
I haven’t tried my loopy pro / LK hybrid with launchpad yet, but it’s not like the launchpad will be able to control both at once.
It would be cool if Atom 2 and Loopy Pro had some form of integration where midi and audio clips had exclusive slots on the matrix so both could be triggered via some form of MIDI thru handshake. You'd get 64 slots on the matrix but the mutual exclusivity of Audio vs MIDI would happen seamlessly as the clips are saved as Audio or MIDI. Completely blue sky thinking here, that probably hasn't got a chance of working in the real world, but I think it's an interesting idea nonetheless.
I just tried with Loopy in AUM rather than stand-alone. Can’t do it there either. You can add loopy as a midi source to an AUM audio track, but nothing shows up in the midi destinations within Loopy.
@gregsmith We're drifting heavily here from the core of what Loopy Pro is set up to be right now, but you never know, @Michael might store the ideas we're discussing aware for a later date. The general idea of a Launchpad Pro integrated looper that functions with both audio and MIDI loops is a sound one, and I'm sure a lot of folk would find it creatively rewarding should it ever be realised.
people like me
Thing is, it’s so nearly there. @Michael has already confirmed that midi sources will be able to control other midi sources at some point - doesn’t seem much of a stretch to allow midi actions to target midi sources too.
And if @wim is right, and midi loops are coming in the future anyway, then it’s already gonna happen. I thought this would definitely be too much of a departure from Loopy’s intended purpose.
I get a lot of accidental plugin selections while scrolling through the list. Could be my screen protector complicating things but if there is a way to reduce the occurrence it would be awesome.