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.
IAA vs Audiobus performance
is there any difference in performance/cpu consumption when running a synth or effect either as iaa or audiobus?
Comments
The biggest difference is (probably) is how latency is handled. In Audiobus the latency setting is clearly displayed, so you are aware of it, and changing it is easy.
With IAA latency is determined by which app was opened first, presumably the host app, and has to be set in a settings page somewhere - but crucially that might not be respected if it is being overriden somewhere. Auria at least tells you the actual latency that is being used, if it doesn't match what is set.
Presumably there must be some cpu cost to running audiobus just because it's an extra app running.
good point! didn't think of that (obvious) cpu cost.
Does Audiobus just generally work better? I was always an IAA-hosted-in-Audioshare type but I've crept more towards AB lately and it seems less glitchy.
Perception is reality, right?
^I think so.
For example IAA doesn't always know how to close apps. An app can sometimes linger in the background even if you "force close" them.
I was under the impression that under the hood, Audiobus was now using IAA. They have just wrapped it in some intelligence to cover up the flaws and make it work better. So, I would say there has to be a CPU hit from using it. OTOH, it tends to work a whole hell of a lot better.
You can create chains in Audiobus you can't with IAA. A practical concern for me is that with so many IAA apps, the developers of many host apps haven't taken the time to create an ordered list you can use to select the apps you want to include. Being able to set the latency can often mean the difference between a viable audio chain and one with corrupted audio output.
Being able to have the main start/stop button in Audiobus is very convenient for recording or playing Link supported apps and many times I find AB Remote very useful as well.
I don't trust my perceptions.