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
@sigma79 - it's nothing that buying a few more iPads for your setup won't cure.
lol. I know.
Anyway.
Thought Id be useful and post sampler ipad.
Dealing with audio/samplers has been way more hassle than midi.
All samplers have issues or you need all samplers combined.
It were Koala no multiout to fx.
A mio randomly triggering loopy.
Now Drambo scanner sampler just crashes project on trim.
Not sure I need this routing but it would then just be sending to Koala.
Vid wont be available for a while.
.
@sigma79 @mistercharlie @drconfusion @espiegel123 @wim thanks for all the info and dialogue it’s given more than I expected
(I put loopy in dRambo mostly but How do you host AU in loopy pro)? I heard people doing that
No worries.
Info provided isnt great tbh.
Are you talking about hosting AU in loopy pro standalone? There is a plus sign in the mixer view to add AU, hardware inputs, midi sources, etc. if you haven’t already watched any tutorials, there are some good videos out there.
If you are talking about the loopy AU, AUv3 can’t host other AUv3.
It's easy to host AU's in Loopy Pro. Go to the mixer, hit the plus sign, and then Add Audio Unit Input for audio apps or Add MIDI for AUv3 Midi FX apps.
Or did you mean something else, such as how to host AU's in Drambo when it's loaded in Loopy, or how to host AU's in Loopy when it's loaded in Drambo? Neither can be done. AU plugins can't host other AU plugins.
Damn! Yer still quicker on the draw then I is pardner. But by jiggers I swear imma gonna whip ya some day gol durn it.
Yes: I meant standalone . Thanks guys . I’m going to experiment more with Loopy. It’s so powerful and all encompassing, it really is a Loopy DAW with all these features.
And wim, that’s crazy how your posts were momentd apart but almost exactly the same reply from two different people (you guys are really awesome on this ABF!) thanks, especially @wim who has really put up with a lot for helping me out , kind of you man
Edit
Can’t believe i didn’t see what the plus sign was doing…maybe because i had it within a DAW….can’t believe i missed that….. wow! This thing is a mini DAW like Drambo…
The question might be “Loopy hosting Drambo” or “Drambo hosting loopy”. You can do either, really. I think it comes down to if your song is more “audio” based or midi based.
For example:
A) Audio tracks are the building blocks: You have bass, 2 guitars, vocals… then you have Drambo do some drums and trigger synths and some sound fix or whatever. I’d go with Loopy hosting Drambo. You can “tie” Drambo scenes to Loopy donuts, scenes or widgets by sending a midi message from Loopy to Drambo.
B ) mostly midi: host loopy in Drambo. Before Loopy 1.1 you didnt have multi out which meant you’d need one Loopy for guitar, another for bass, etc… now you can have just Loopy auv3 instance and deal with the different colors/outputs as you see fit…
If in doubt, my personal opinion is that controlling Drambo from Loopy is easier than the opposite. Drambo has a more “fixed” structure with tracks and scenes, where in Loopy you have a more flexible layout. Also if triggering a loopy loop from Drambo’s timeline you’d need to make them the same length… (although you could get around this by using a “once” trigger).
Note: I hadn’t thought of using a processor block to host Loopy and thus saving the loopy preset. Super helpful advice!
BTW I don’t love either solution 🤦🏻😂. I have some weird TOC thing where I dislike opening Loopy or Drambo in an auv3 window. Feels strangely unnatural, as if the interaction isn’t as immediate or transparent. Crazy.
Thank you for the detailed reply. Your right. I just thought the same thing. Depending on what kind of track it is, you might want one or the other
Can I ask you , what do you use instead? It sounds like you use a daw, and when you use something like Hammerhead or Beat Scholar , how do you set the MIDI triggers in loopy pro?
Do you move to the timeline at that point? And if not how do you handle changing patterns (by trigger notes)?
I’ll more often use Loopy to get stuff going, and might even just use the Loopy sequencer to export the whole finished track. If I want a “proper mix” I’ll export donuts and mix in a daw (Zenbeats or now Logic).
As for Drambo or drum machines in Loopy… honestly my recommendation is to just bounce the midi instrument to a Loopy audio donut, do that for as many parts as needed. Then you have the auv3 “idle” and you can always add more parts. It does feel a bit “temporary” as in “I’ll do the proper rhythm later” but I often just stick to that initial loop.
It just makes sense in that every thing you hear has a graphical representation (donut) in front of you, everything is in one “space” and that is somehow reassuring, more under control. Also less having to think about sending this midi cc on this action, midi learn this there… you stick to loopy donuts and life is easier 🍩
Maybe when midi clips make it to Loopy it’ll be different, but for now I’d say bounce everything to audio. Not because the results will be better, but the experience is.