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.
Poll : Do apps still need to support IAA?
If an app works as an AUv3, does it still need to support IAA?
What do you think?
- Is IAA support still necessary in an AU instrument or effect?108 votes
- Yes, definitely needs to support IAA28.70%
- No, definitely not necessary to support IAA71.30%
Comments
Nave needs it! 😆 or Nave need Auv3 support
I voted "no" for "instrument or effect", as that was the question.
However I do appreciate that hosts still support it, if nothing else for the one app I use regularly (Drumperfect Pro) that isn't fully AU 1, but still has unique-for-iOS-functionality (the only drum app with multi-velocity samples that also handles multiple time-signatures/tempos in the same tune 2).
Yes, I know about the DPP "player" but it isn't the same thing ↩︎
NS2 is the closest, but has other issues such as no audio etc ↩︎
Voted No, but every app needs some kind of connectivity and ability to be hosted. For example I do not like that Audanika cannot be hosted inside of AUM or Audiobus, which requires using the home button or multi-tasking to access the app. I prefer instead to access the app via AUM or Audiobus (or whatever host, which is likely turning out to be Loopy Pro next).
Yes mainly for Lumbeat and other drum apps
I'm not sure you read the question fully.
Or maybe it has since been edited, because I don't remember reading it that way at first?
Put that way, the question doesn't apply to apps like Lumbeats apps that don't work as AUv3.
Also, put that way, I can't imagine any scenario where it would be needed for an AUv3 app (not a host) to also support IAA. It would be good to hear why from anyone who feels that it's important in that case.
With the exception of being fullscreen I can’t think of any other benefits to IAA over AUV3.
Ps…. So we hinting at Patterning being AUV3 (yes please!) or is this a new app?
Frankly... IAA (Blocs/Lumbeat, etc) just doesn't work right in iOs 15. State saving is critical to song creation... It's sad when you've come up with the perfect beat in Funky Drummer ... Shut down the project and it is gone when you decide to go back at it.
BTW... Suggester's loop button does not 'state save' anymore.
@RajahP : iOS 15 didn't break IAA state-saving. IAA has never had it. What problems domyou have with BlocsWave or LUMBeat apps specific to iOS 15?
I imagine Ben is asking because he is thinking of writing an AUv3 and wondering if people still want IAA versions. For those that don't know he is the developer of one of Hall of Fame candidate Patterning and several other great apps.
I voted “no” - if an app works as AUv3 why would you want to load it as IAA?
As someone mentioned above, I really appreciate hosts still supporting IAA as I still use iProphet, ODYSSEi and have recently had to dig out DM1 to recreate some old tracks. God I wish these would all be updated to AUv3 (along with iMS-20)
+1 and FunkBox
Oh shit. Are we going to see Patterning as an AUV3 soon? 🙏
hosts SHOULD support IAA as long as it could be. Instruments and fx - not necessary
I put it this way, if app has standalone version then yes, it needs to support IAA and other good stuff. Otherwise it useless in that format. Some devs include stripped down standalone version just to prevent one star AppStore reviews from ignorant people. I get that but don’t like.
And I’m totally fine just with AUv3 app.
Current AUM update came very close to full screen AUv3 experience when you maximize window without left/right/bottom borders.
+1, this would be enough and allow us to pipe-in audio from those apps.
(I have just a few of those left that I use somewhat regularly. Nave, BeBot, Chordion, PolyChord & iOS Sound Canvas).
Sure I wish the all the Korg apps were AUv3 and when needed I can live with piping them thru Gadget and exporting audio in case IAA would be totally gone...
@benkamen Chordion remains as one of my main 'fun & easy to play' apps. It's so cheesy it's crazy!
(I do hope at least the hosts retain IAA support so I can keep on enjoying it for long, long time to come...).
I put no, if the AU version is identical to the standalone then there is no need for an IAA plugin.
Stand-alone audio apps are designed to be used with audio interfaces with external devices like a computer or hardware, so if a standalone exists it doesn’t mean it should support IAA, I prefer if the standalone apps support multiport interfaces etc.
I think IAA is still nice to have but no longer needed if the AU version has full implementation.
One word: Samplr
Still irreplaceable!
Yep.. IAA never had State Saving (AFAK).. iOS 15 just made it much harder to load…
Didn’t know Ben, Mr. Patterning initiated this.. I think I would use Patterning more if it was Auv3.. as a matter of fact, I don’t use it.. and it is supposed to be a top drum app..
Can we just scrap IAA… please..
I read it fully but didn’t understand completely…
Actually the most common reason AUv3 apps also works standalone is simply for demo purpose and to get it through app review.
And even better fullscreen mode will come!
@j_liljedahl Oh, I wasn’t aware that it helps with Apple app reviewing process, make sense then.
If Apple would review things according to their own documented standards, there wouldn’t be a problem. It’s hardly a help nor it makes sense to jump extra hoops simply because Apple is lazy to do their part. One size can’t fit all...
This whole IAA vs AUv3 thing... they aren't really different technologies. Not the way I see / understand it.
IAA is just a way of getting an Audio Unit in one app (one of the various kAudioUnitType things) to present itself to other apps. Again, IMHO, the main problem with IAA is that nobody really told developers how to support IAA properly except for that one blog article by @j_liljedahl
And yeah, if your AU container app doesn't do "something" Apple will reject it
I don't mind AUv3. It's just that some apps in their AUv3 formats are not the same as their standalone. Example would be Electribe Wave, World Piano by TAQS.IM. You’re unable to use the drum or step sequencer in the AUv3 version of the apps.
This is a good point. What I love about DM1 is the workflow, if an AUv3 version of it removed the sequencer I’d not use the app at all
If AUM gets an opinion to remove iaa from the node selection menus, so that I don’t press it by mistake, then I don’t have any problem with it.
The requirements aren't clear. An app that doesn't have any functionality outside the included extension isn't allowed. What I do with my container app is on the border of meeting the requirements. I've been able to argue it meets the reqs. successfully on appeal, but I wouldn't do a commercial release this way if I were a large company. The best thing Apple could do would be to get out of the way entirely. The iPad ecosystem could really grow then.
It’s with the host side of things that I find IAA to be a most important consideration, but only AUM pushes this capability past the basics with it's 8 individual IAA output ports. I really with ApeMatrix offered the same number of ports and Drambo would be ace if the standalone output 8 individual ports (that way e.g. Drambo hosted AUv3 chains could be used in Cubasis and Studiomux).
It goes without saying how flexible 8 individual IAA ports would be as an output from the Loopy Pro standalone.
Even iOS drum machines could benifit from 8 individual IAA output ports. By offering this feature drum machines standalones could become AUv3 hosts that stream to the likes of Cubasis and Studiomux.
You end up having to manually adjust for plugin delay compensation but that's not a major headache.
It's a pity that Apple see IAA strictly as a deprecated technology as it currently still has it's own benefits over AUv3's.
Having said all that, if AUv3s could host other AUv3s in the same way that desktop plugins can host other plugins (as in Native Instruments Maschine and suchlike); at that point IAA could be put out to pasture.