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
Because MacOS is a major red ocean for plugins: the total overkill of competition on the platform would make it less worth it to take the trouble to go there.
And besides, I've had enough work testing my plugin on all iOS hosts (only five so far). I really don't feel like dealing with all the intricacies of every MacOS host as well (not to mention having to buy them all).
Sorry, I should have pointed out that I kind of already knew that. I just tried to make a point regarding how 'effortless' the process is.
Just because something is technically feasible and you (brambos) are skilled enough to do it doesn't make it inevitable, which is the core of the problem for iOS musicians who are wondering why not more AU X are being released (faster).
Thanks, I've added that and 'envelope' from same dev to my list of apps to get after Cubasis 2.0 arrives
The problem is that you would have to monetise individual modules inside of an app via In-App Purchases. A few apps work like this but they're not massively successful, except for Gadget and Auria Pro. And one could argue that there's not much room left for a third competitor.
Well, since Audio Units are the de-facto plugin standard on MacOS, and AUv3 is (on that platform) simply the next iteration of the standard, I guess it sort of is inevitable that the uptake will eventually be 100% on MacOS.
For AUv2 plugins on MacOS there is a convenient bridging mechanism so it is trivial for developers to convert their existing plugins to the new standard and gradually implement it natively.
I'm not sure why -as a user- you'd care whether a plugin conforms to AUv2 or AUv3 as long as your host is compatible with both? So that likely explains why a search for AUv3 doesn't turn up many results.
But on iOS it's a different story because AUv3 is the first version. There are no legacy v2 plugins to be ported over and I'm not sure if you can easily port AUv2 plugins from MacOS to AUv3 on iOS, but it's probably a bit more work.
Please note: I'm not an Audio Unit evangelist. It's just the standard I chose to do something useful with the Ruismaker engine I already had sitting around from my stalled hardware project. I'll have a good look at AB3 once the standard is out to see if it fits my needs better, but for this particular project AU just happened to be the best fit.
>
Which I think makes it clear that AU Extensions are intended to be an additional interface, leaving room for the same instruments to run standalone and offer other interfaces as well.
Similarly there are great standalone iOS graphics programs (like Pixelmator) that also support extensions to allow a certain subset of its features to be used directly inside of the Photos app. We don't search for "Photo extensions". We search for great photo apps and a part of the distinguishing feature is that they "also" plugin to Photos
So I'll continue to shop for great iOS instruments and part of that greatness is allowing me to plugin.
And lest we get carried away with the Apple bashing... at least someone had the foresight to build low latency into the OS... without that there would be nothing to argue about further up the stack
One can almost imagine Audiobus becoming a clandestine subterfuge underground App Store based on IAPs.
And just like that I spent $10.00
I'd like to see every host offer affiliate links to cool AU in their store sections.
Hey @LFS how about that?
Well, if apps must be self sufficient, not requiring other apps, that counts out pretty much every effects app. If all effects, and others, such as sequencers, etc, were quickly recategorised as IAPs, that Audiobus could “manage” and “sell” through a “shop” then they’d not be “real” “apps” but mere IAPs.
Take for example AUFX:Push it's an effect that runs standalone, it's just more useful as IAA and would be even more so as AUv3
Worth it! Insta-bought upon seeing the link in this thread, really liked the reverb. Nothing breaks up a good discussion like a new product to buy
Except Apple.
Good examples are isem and remaster and a few other : they work as IAA and as AU , so nobody lose .Only AU is a suicide imho ...
Really?? Wow, that is indeed a huge WTF.
I wonder how one would make use of a standalone FX such as an EQ or compressor.
Who knows maybe VSTs may even venture to iOS someday soon.
Apple is centered on the mass market. I'm guessing enough people didn't bother to read or understand app descriptions that Apple decided to deal with the problem by making every app create sounds. The lowest common denominator management strategy is in full effect, expect more disjointed experiences and detective work.
Supporting niche music creation is weak and low priority. The App Store promotes IAP apps targeted for people which fall squarely on the side of app players rather than creative production tools. With little insight into the needs and desires of musicians, Apple's bonehead App Store and iOS music development decisions are frustrating.
Their pro app talk is just marketing fluff until they provide the tools and access developers need to create more sophisticated apps and developers are confident that their efforts are worthwhile.
Has iOS music plateaued? Will adequate stability and compatability for basic functions arrive? Self contained Korg Gadget type environments may be it. Multi-app work flows are enticing, but test people's patience on basic infrastructure work flow setups.
Multi app multi developer work flows can be a headache as Apple lacks leadership in trying to get developers and users on the same page. The Audiobus team has made great strides as well as other developers but my impression is that this is in spite of rather than because of Apple's core audio development team.
I have no idea where at Apple I'd direct my concerns and desires nor have much hope any action would come of it.
I think Cubasis' embrace of AU is their message...and Cubasis may end up being the reference standard for AU on iOS.
Cubasis (and other marketing savvy hosts) become the meta platform and discovery engine for compatible synths and effects.
What if AUX does generate new sales? Surely, it's not only for the benefit of current app owners but also possibly future-proofing the product.
Much like there are people - like myself - who won't buy an app until the devs add AB, IAA sync or Link compatibity, might there not likewise be potential buyers who view AUX in the same way?
I've got my audio setup pretty much locked down and in general am not buying new apps - but I carefully consider whether or not to buy each new AU released, as there is room to add or replace an AU on an FX bus here and there. More often than not I will buy them, even if just to test out and see if it's any boost over what I'm using currently.
In my case yes, no AUv3, no interest
...I would jump at a standalone Melodyne for iOS though
As a small aside, I noticed Apple updated the AudioUnitV3Example in the developer library today. My guess is that it's mostly a result of checking all their sample code still works on iOS 10, however it does include some factory preset handling stuff which might be useful
Thanks for the heads-up. I think they also fixed a snafu with retain cycles when unloading Audio Units.
It would for me, I am not interested in apps that don't work seemlessly in AUM. And I have a bunch of apps I like and am not inclined to buy anymore unless they are AUX TBH. I would even get rid of some if a similar AUX synth or effect were out there.
I would even repay for some apps like nave or effectrix if they came out with AUX versions!
For me it's Ableton LINK that is an absolute must. At the moment won't buy any apps that don't have it. AU is not (yet) of any importance to me on IOS. Since quite a long time now, I know that more complex stuff is too much of a hassle on a touchscreen.
There are rumblings about Nave AU
I strongly believe AU will generate new app sales. I'd rather load up the AU of a synth rather than the sloppy IAA route, and I'm sure a lot of people can agree. For developers, it's definitely a future proof investment to insure more sales. At some point, IAA app sales will drop in favor of AU. So it becomes a matter of sink or swim.
As of recently, I'm holding off on buying apps unless they're AU compatible. But some apps that were updated with Link are hard to pass up when they go on sale. So I end up grabbing what I may have waited on for an AU update in the first place and hope it gets updated in the future.
It would be cool if standalone apps added AU as an IAA so devs can get paid for the work. But I don't know enough about programming to know whether it's feasible, let alone possible.
I've bought a few AUx apps mostly because of the unique capability they add, but no way I discard or turn my nose up at good apps that aren't doing it. Considering it hasn't really caught on, I'm glad developers are still putting out good stuff despite whatever pressure they're getting to do something they don't want to do. And I think some don't want to. It might not fit with their design or be in their best economic interests. Even if it does catch on---and I like the idea---AUx still won't be make-or-break for me.