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
Ok great thanks for the info @Samu, that is very helpful. I’ll have to consider whether the frequency range customization will work for my purpose, otherwise I might just use multiple channels with the Multiband app in combination with single band compressors/expanders (since I’d be switching UI screens using different instances anyway). Maybe I will try the demos first on macOS, and test that way, thanks for that suggestion as well, great idea.
Just a note here (got a response from Toneboosters):
“MBC indeed only supports one side chain. There aren't that many hosts that can handle multiple side chain inputs, and hence implementing that feature can cause issues in various hosts.”
so… sounds like…. it IS possible with certain hosts (like AUM, I’m assuming), but there’s some kind of overall standardization not yet in place, which might mess up other hosts if they did try and implement it
Host supporting multiple-outs from AUv3 Effects are also pretty rare.
The per band side-chain input filtering in FF-MB from one input is sufficient for 99% of the use-cases for the remaining 1% iI feel it's better to mix into sub-groups and treat them individually.
As for AUM the bigger priority (compared to multiple side-chain inputs etc.) would be to get multi-threading in place so we could actually push the faster devices to their limits and not be limited by the single-threaded audio-engine, it feels off to know that the CPU is capable of running more stuff and the software puts a stop to it...
Thanks for the info @Samu.
Good to hear the side-chain input filtering works for you in nearly all cases.
So sounds like AUM is ahead of the game in some respects (multi effect ins/outs), and behind the game in others (multi-threading)? Is that correct?
AUM has slightly more flexible audio & midi-routing but what good does that do when it lacks proper automation, sequencing, recording, editing etc.?!
As far as I see it AUM is a 'Live Noodling Station' and that's about it, some love it but personally I've left it behind as it doesn't do what I need it to do, ie. record midi, automation, audio and provide a way to edit the recorded stuff.
...and I ABSOLUTELY HATE the whole 'Lego Franken DAW' concept...
TB or Fab Filter , aside from price ?
I would say TB since you get two compressors/expanders per band and personally the UI is a bit easier on my eyes.
Just about the only disadvantage for TB is that you can only use the side-chain input for one band at a time while FF allows you to use the same side-chain input for all bands with per band filter of the side-chain input signal.
If you have access to a desktop both are free to try and I suggest doing that before deciding.
Definitely the fewer the main apps the better, but haven't been able to replace AUM's functionality for my specific purpose (as an advanced guitar looper tool incl live performance and all production aspects). It seems to be getting closer though as LoopyPro covers a lot of ground. But AUM's routing options and monitoring tools (for figuring out specific latency issues, etc, in the context of live performance) keep it in my rig. Serves a different purpose from regular music production for sure.
Getting back to the EQ plug topic... I guess it makes sense that app developers don't want to necessarily develop features of their app only for specific hosts as it would take too much extra work for little return.
Yepp, that is it. It took a long while before we even got hosts that could do basic side-chain routing.
Initially when the FF plug-ins dropped no host was able to do side-chain routing prior to getting an update
Hosts that support multi-out AUv3 Effects are rare and so are the AU3 Effects that provide multiple outputs.
So until more plug-ins utilize or require these features I doubt we'll see any major updates to hosts with these features added.
The 'mantra' of iOS/iPadOS music making has always been 'work-arounds' for various tasks and in the case of multiple side-chain inputs it's equally easy to just create busses and use multiple instances of the plug-ins.
some of the unique benefits for each that stand out to me:
TB MBC:
FabFilter Pro-MB: