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
It’s always like this. Humans are reluctant to changes😂we are slaves of our habits.
That was more of a practical question.
The answer seems that audiobus would be the only possibility.
I'm not clear on the IAA stuff.
Does the deprecation of IAA ONLY effect an app's ability to interconnect with other apps/hosts?
So, let's say IAA is fully deprecated as of tomorrow. Will IAA apps that run in stand-alone mode, and even record their own output... still even launch and run? Or, will that simply mean they can no longer be interconnected with other apps, but they'll still work fine in standalone mode?
Deprecated only means that Apple has labeled that technology as one that won't receive new features and that developers should use a more modern technology.
Deprecated APIs sometimes end up being supported and maintained for many many years. Sometimes the calls are pulled and not supported at all after a few years.
IAA is supported in iOS 13 and seems unlikely to be removed in iOS 14....too many major app developers are IAA-based for it to be pulled any time soon.
When IAA is truly removed, IAA apps will probably crash when accessing IAA features.
I'm thinking more specifically about apps that I don't necessarily need to interconnect with anything. Take Soundscaper, or Blocs Wave for example. Both of these apps are perfectly useful in standalone... can record their own audio and export it out for use elsewhere.
When IAA is fully deprecated... and you aren't trying to interact with any other apps other than to export recorded audio out... then should they still run fine even though IAA has been completely deprecated?
I'm also thinking about all of those packs I bought for Blocs Wave and LaunchPad. Both IAA apps. When IAA is deprecated, if those apps won't run anymore... I'll no longer have the use of those apps, but I'll ALSO lose the dozens of sound packs I bought that are proprietary to those particular apps.
...
It's not really possible to say what's going to happen with any given app. It depends on the way the developer architected the application. It is possible to say that an IAA app may well work after IAA is actually removed.
A big hint for when IAA will actually be fully gone is when you don't see it in GarageBand anymore.
@skiphunt : a lot depends on how the apps were written, which particular calls were used and more.
There were OS calls deprecated circa 2004 that were there through Mohave.
So, theoretically if a given app could still be completely viable/useful in standalone mode without need for interconnectivity and some of the calls to IAA features weren’t imperative to the app’s core use... then a developer could possibly just remove/edit the IAA calls and still have an app that could continue to live after deprecation without necessarily having to rewrite as AUv3?
Yes
@NeonSilicon @espiegel123 thanks for the clarification!
I’ve seen so many gems of apps disappear over the years, apps that were truly making iOs devices shine, and therefor doing a favor to Apple.
Apple should definitely come up with some sort of program to get these
out of oblivion for good.
If windows can run on a mac, I can’t believe why an app from a previous os version could not run in some kind of emulator that would fill the gaps.
I miss B-step sequencer, Grantophone, SynthX to name a few.
To me, iOs is a depracation in itself unfortunately.
No Auv3 so far have come close to what has been done as IAA.
Samplr, Elastic drum, Seekbeats, Borderlands, Sunvox, Caustic, Arpegionome, Thumbjam, TriqTrak, Loopy HD, Animoog, humbletunes fx, etc.
All momuments that diserve more than a mere: »update to Auv3 or disapear ».
The iOs music ecosytem and apple in general owe a lot to those related developers and customers.
Show some respect Apple for ... sake’s.
Kind of blew a gasket...
Yeah no problem. I think the confusion and worry is coming about because of a misunderstanding about the concept of deprecation in the software world. The main thing to realize is that the announcement of the deprecation is aimed at software developers and not end users of software. This is something that happens all the time from OS vendors and software library developers.
There are similar things in the hardware electronics world. When looking through product sheets, you'll run into products marked "Not for New Designs" or "End of Life." The supply chain for these parts will be around for some time, but if you are a manufacturer, you better start making changes now. This is the same kind of warning for software devs and really, it's usually a whole lot easier for the changes to be made in software than a similar thing in the hardware world. Plenty of great classic synths died when the IC's used to make them stopped being made.
Personally, I see the move to AUv3 as nothing but positive. Many new use cases can actually be enabled for these standalone music apps by them adding AUv3 support.
In the latest GarageBand update the option to select IAA instruments is still there. Once that option is no longer in GB is when people should worry.
For me I’ts totally counterproductive to remove iAA, Ok AU3 is nice but no point to remove IAA, I wonder where is their mind?
IAA allows the best of both/all worlds by connecting host to host and now with these limitations, we are stuck in one app. Sure we can export and import, but this is opposite of improving the workflow, so do they really want to make things better ? Not sure.
New problems that you'd never thought of before.
See:
https://line6.com/support/topic/52577-what-footswitch-is-best-for-use-with-pod-hd-pro-x/
A footswitch has one great advantage over Bluetooth headphones though:
It doesn't kill live playing due to audio latency.
@BCKeys Yes, and I think that the number of reported audio-related problems on the Pro models that don't exist on the cheaper models speak for themselves 😊
Pro is not always better, check out cheap products on ebay, the word "Pro" has rather become a low-quality warning nowadays 😁
Cool. I’ve stopped using IAA such a long time ago this has no effect on me what so ever.
I often use more instrument apps in IAA mode these days, piped into AUM ie electric vintage or accordion, ribbons, recently Skiid... not sure how this use case is addressed by auv3 , unless there’s a full screen mode that I’m missing?
Hopefully there’ll be a decent warning before I upgrade at some point...
Bringing projects from AUM jams into Cubasis will not work anymore. That’s the only point I am affected by it
Me before I got an ipad: I hate apple.
Me after I got an iPad: apple still sucks but these music apps are fucking awesome.
Me after a year of having an ipad: I fucking HATE apple.
its ok. and nothing we can do about it. just start migrate your set to AUv3 now, less hassle when this will be done
No one knows yet when, but its coming. And its shiny and good.
btw beta 14.b2 here.. some apps unavailable now for me (dev needs to update msg)
this is just a headsup, start saving render and replace with AUs
Yeah... because headphone jacks are incredibly useful.
smh....
smgdmfh....
What is in their mind? Reducing the OS maintenance load. Avoiding having to fix the rats nest of problems they've never addressed with IAA. Streamlining the OS. In short ... not much from user's perspective, but makes sense from their perspective. You have to keep in mind that revenue from music apps doesn't even register on Apple's radar compared to other revenue streams. Follow the money.
@Michael has indicated that as long as host apps continue to implement Audiobus compatibility, that they will still be able to work together using Audiobus.
Audiobus existed before IAA existed and @Michael has said that he can revert to the old way of doing things if/when IAA stops working.
That's some comfort anyway...
More than useful—necessary, if you care at all about latency.
It's also helpful to keep in mind that Apple plays the long game ... and they only reveal parts of that game plan when it's to their advantage to do so. I wouldn't be surprised if they have some plan tucked away to enable AU hosts to host other AU hosts eventually.
AU apps on iOS already run as separate processes from the host, communicating back and forth with Inter Process Communication. It's very possible that communication API could be extended to other apps. It's just a matter of whether Apple is willing to go there given their apparent lack of priority toward music apps on iOS.
You know, I never understood why Thumbjam could have multiple slots, thus making multiple instances possible (and half the value of an AU) and other IAAs didn’t follow suit. An amazing app.