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.
AudioBus vs IAA
Hi guys,
i just wanna know what you think and what/how you use.
Where are the BIG difference?
I read somewhere IAA is way better (Latencys);
IAA: you have ONE "sandbox" were you can integrate apps, no latency summarys then...
AB: a "sandbox" were you can route other "sandboxes", but if you have 3 FX inserts you will get 3 x the latency of it....
is this correct?
I have not much experience with IAA cause, how can i say this:
i`m not getting the "warm" "home" feeling in Cubasis(IAA).
And i like the community around AB,
yes i mean you too man ;-)
but i will play live so latency is very important!
did i have to wear big socks and try cubasis again?
:-)
greetz
obi
(hope there is no other thread.....)
Comments
IAA is a technology. Audiobus is a technology, an app that standardises interaction between other apps, a way to discover compatible apps, and this community on top.
We're also currently working on incorporating IAA into Audiobus.
IAA can be a powerful thing if implemented correctly and if all apps in question play nicely together. But there are still limits to what developers can cram into the interface of an existing app. Adding user interface for routing between apps in every app in a different way can be confusing to users and also tricky for developers of apps that act as hosts. Then there's some limitations of what can be done with IAA's 'connection panel' - namely that it can only be used for transport control and it can only switch back and forth between host apps and nodes, not between nodes itself.
Finally there's a question of which workflow is preferred by some users.
Some users don't like the plugin->host layout that everybody is used to from the desktop and which IAA is designed after. The most used workflow in Audiobus does not even have an app in the output slot. In my opinion this points to users actually using mobile music apps differently than desktop plugins.
Audiobus allows a more direct interaction, a more casual way of making music that fits very nicely to a mobile platform.
Currently IAA cannot control, save or restore any state or parameters of the client applications it loads. This is pretty unfortunate for a plugin-like architecture that focuses on the use of a "host" app, and prevents a truly useful saved session in a DAW-like host. AB2 only recently added the state saving and preset loading feature that makes it possible on the AB side, so it stands to reason that Apple may eventually follow suit (it had better!).
IAA does integrate sample-accurate midi event delivery directly into the client apps, which is a nice improvement, as well as its built-in sample accurate sync, tempo and transport support. Those things, along with the reduced latency are IAA's biggest advantages, in my opinion.
So, it really all depends on your preferred workflow, because right now AB and IAA are both better at different things.
@obiwahnkentobi there is less of a "community" feeling in general with respect to Cubasis, but i think, from my short time on this forum, that there are lots of people that use Cubasis, so you feel free to ask questions.
As for IAA and Audiobus, it's best to exploit the advantages of both. What I've found is that experimenting and trying things to see what works are a must. That takes time, and sometimes it might feel like "wasted" time if you don't come up with anything that you like, but it's good for learning how the tools operate together. I spent some time last night experimenting with IAA in Cubasis, including freezing tracks, and recording through Audiobus into Cubasis, and found that some apps are better with Audiobus, and some are better with IAA. Unfortunately, I think it will be like that for users for a long time on iOS, but given the dedication of the Audiobus team to its app, and how excellent it is, that might not be such a bad thing.
@Sebastian if you put IAA inside Audiobus don't forget to to make an Audiobus Node out to IAA...
First off, to the extent it matters to the "debate", many are of the strong opinion that there would be no Inter-App Audio if AudioBus hadn't come along in the first place. The fact that so many developers seem to prioritize AudioBus compatibility over IAA, even though the latter is first-party functionality created by Apple. (Reminds me of when everyone was using PayPal, so Google and Amazon thought about making their own "PayPal", but everyone was accustomed to using and trusting PayPal).
That being said, if I think that IAA is superior to AudioBus in some way, I'm certainly not going to withhold that opinion just because these are AudioBus forums and the developers post among us. In fact, if you're a great developer (which I believe the AB guys absolutely are), then you WANT that feedback and motivation. AudioBus continues to carry the advantages of enthusiasm and community responsiveness, as we've seen with the popular new features in 2.0.
Inter-App Audio SHOULD have the potential to do things that a 3rd party developer cannot because Apple can weave it into their operating system. They can connect one app to another without an actual 3rd app running in the background, which is a benefit for CPU usage (or should be, if properly implemented).
But, at the end of the day, I do honestly prefer AudioBus to IAA, and it isn't even close. IAA is a "back and forth" switcher, as Sebastian said. While I may use that once in awhile for a simple overdub project, I can't even imagine putting together a whole project without AudioBus loaded in the background. The technology that connects the apps was the big revelation, but the outstanding mini-controls that give you the core functions of another app without leaving the app you're currently in...not only is that a great invention for music apps - it's really something that Apple should have woven into the fabric of their operating system.
@Sinapsya said:
+1
yes please,let me use an AB node as a cubasis insert or instrument
For what it's worth, my experience of IAA v. Audiobus has mostly been with Auria and I have had buggy issue with both. I think the flexibility with AB is a tremendous advantage to those us using iOS as a recording platform and probably even more so to those using it for performance. As to latency, I have not noticed a discernable difference between the two methods, though with Cubasis there have definately been some issues in both methods. I think this is primarily within Cubasis and not AB or the apps I was using. Bottom line for me is both ways work and are useful, but as a hub for contolling multiple apps AB is an amazing innovation and tool that no iOS musicain can afford to do without.
Ooh! Regarding @Sinapsya's recommendation: +1 from me too!!!! Thesys does that--it's an IAA Host that can be Hosted by Cubasis. This would be a VERY, VERY cool feature!!! especially with the Audiobus presets!!!
+1
Smile
So i have give cubasis a second chance, hihi.
And of course
+1
Seeing as AUFX in Cubase IAA has been cutting out samples for the last 10 mins after reboots n all (+ a bit of brand loyalty & rooting for the underdog
- Audiobus is getting my vote 
Inevitable developmental hiccups & inadvertent glitches aside, its all good.
At the end of the day we are utilising previously unimagined sonic weaponry !
@Paul16 said:
Not that "blame" is all that important so long as problems are identified and get fixed, but when something goes wrong with AudioBus connectivity, the usual culprits are the hardware (not enough memory/RAM), or the input/output apps themselves not programmed to work properly with AudioBus. For example, MT DAW has an issue right now (discussed in other thread) where tracks are stopping for no reason. But that recording functionality works with other DAW's, so that tells me the problem is with MT DAW and their implementation of AB 2.0. Same could probably be said for IAA issues, though IAA seems to be even more glitch-prone.
@Sebastian said:
I would love to see more of that data shared. I reckon it has value to your business (and some of it to your potential competitors) so I dunno if sharing it is in the cards but that sort of stuff is fascinating. Maybe there's trivial stuff in there that wouldn't hurt to share? Top 10 most popular combos? Which app is most often paired with, say, Glitchbreaks? Would actually make a very cool "discoverability" web app. Mimic the AB UI, user selects an app in any slot and sees the other slots fill up with the most commonly associated apps. Click to buy! I'll build it for a cut.
I happen to like IAA very much. I won't say "more than audiobus" because that's really up to what you're trying to achieve, but for me, IAA represents zero latency. I also record primarily in Auria and I can tell a difference when playing my guitar re latency in IAA v audiobus. I think recording on iOS in general can be buggy, and I wouldn't say I've noticed more issues in one platform or the other (after some smart developers figured out how to appropriately harness IAA sans any documentation really from apple). I'm quite pleased to hear that audiobus is going to eventually incorporate IAA. I'm a little surprised that neither loopy nor soundprism has incorporated it yet, but not really. I get that Seb and Mike have probably been tied up with "other stuff". And kudos on that "other stuff". It's hot.
@boone51 +1 for IAA in Loopy and SoundPrism
I mostly use IAA these days, it's quicker and easier and I can keep everything at 24bit. AB is great for messing around with routings and what not when I'm messing around, but when I'm in Auria and working on a track seriously, IAA is what I reach for usually.
I prefer IAA because of the workflow in Cubasis, but it's not yet there.
IMO that's pointing the way to the ideal iOS way of working - having IAA apps/plugins open in a DAW like each of the instruments in Gadget work, modulation, saving presets across apps, etc. I think a lot of the enthusiasm for Gadget was because of the way it allowed one to focus on creating instead of doing app management.
The only question is if Apple wants to do that.
@raz said:
Agree 100%. Hopefully Apple's answer is yes. I think it would be foolish for the answer to be no.