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 will probably be a year or two before AU's are fully implemented, bug free and apps are fully upgraded if IAA is anything to go by....
Maybe devs in the know are simply not talking about it much because it may be privilidged information or potentialy even change.
AU would solve our midi clock , sync nightmares.
Sync is going to be solved by something else.
Jesus is coming?
But I havent prepared anything for diner.
I just posted this on Facebook, but I guess it applies to this thread as well, the question on Facebook was if Audio Unit Extensions would make Inter App Audio obsolete:
The future is not just AU. And right now AU are pretty much a nonstarter because of their incompatibility with Apple's built in system audio units, bugs that will most likely take 9.1 to fix, lack of standardization in a visual multitasking scenario, lack of access to full screen resolution and so on...
And of course the usual lack of proper documentation and proper hosts to run in.
From my personal point of view, AU extension have been launched exactly the same way as Bluetooth midi has and IAA has. If we wouldn't have been forced to move to IAA barely anyone would use it today. But Apple cannot ever force anyone to do away with IAA and use AU extensions instead, or at least it would be a disaster, because so many apps wouldn't be able to do it.
Also: Yes, Audio Unit Extensions can have multiple instances. But they are limited with regards to how much RAM they can use. On 32bit devices it'S 300MB and on 64bit devices (pretty much all the recent devices) it's 360MB. So apps that handle samples will have to be very careful not to use more than that or they'll most likely be shut down.
To my latest knowledge this limit applies to every instance, which means that if you have three instances of one audio unit extension, each of them can only use 120 megabytes, which would be severely limiting. I don't think more than two instances of one Audio Unit Extension will be able to run nicely with that limit in place. Maybe Apple will still change that but I'm not counting on it.
thx for the technical background @sebastian.
The RAM limitations look to be pretty restrictive. Could that be got around by freezing tracks?
No. Users freezing tracks cannot be the solution because that would mean they would have to do manual RAM management which is horrible.
Streaming as much as possible from disk would be a workaround but it's not going to be possible for every potential use case, some things just have to be done in ram.
Is it a piece of string with knots tied in it,, you can then drag it across the camera at different speeds for different tempo's ?
He He
who told you?!
I think he said his name was S. Arcasm
@sebastian : Big thanks for the infos on AU.
For the ram limitation... 32bits = 300Mo, 64 bits = 360 Mo. So the ipad pro with 4Go will be useless?
Is it Hardware limitation or OS limitation?
Maybe we were too optimistic about the integration of Audio Unit in ios9
I could overlook the ram limitation with multiple instances if i can at least SAVE and RECALL everything within a project in my IAA host.And without manually ditching the plugins into the digital nirvana every time i close them,.All the tools i need to have multiple times (like EQ's) i already have within auria anyway.So,i prefer to stay carefully optimistic
Here's addition info from apple on the implementation iOS extensions...worth a read:
https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/ExtensibilityPG/index.html
Oooh!!! Please elaborate! :-D
Very interesting! Would samplers be able to get around this limit by disk streaming?
Excellent question!!
Ah... That answers my streaming question.....
I'm still not sure I understand why freezing wouldn't allow for increased AU usage of the same app, since Freezing unloads the app from memory for that particular track.....
Thank you for info about AU..... very interesting and odd at the same time. On an iPad Pro it would be bad to limit such a important feature to just 360 MB. I could not even load a single multi sampled piano or another instrument. Some synths needs more (Nave f.e.).
I think iOS needs another 2-3 years to get there. Seems that will work only with little apps like FX or so?!
The trick here is to supply the perfect name for the S.!
I got nothin'...
Auria Pro, while not AU, will have its own multi instance synth. It will be interesting to see how many instances will be possible.
As it is there are already several multipart apps like iM1 and Thumbjam which are almost as good as having AU.
Is there any ram limit for IAA apps?
...does this involve a chilly day in Hades?
I must have pretty simple workflows, because so far, with Auria, I don't really need this. But I'm mostly doing analog recording in Auria, using the great IAP effects. Now, I'd love it if those effects were things I could have purchased as apps, that I could use on any tool that supported them, which is the big promise of AU. But it's going to be a while for that to come around. All the tech info above does not bode well for this working well, any time soon. Time and better hardware are required. At least the concept is out there.
How did Auria pull this off so far ahead of the curve anyway??
In my non programming understanding, they're not really plugins, they're already a part of auria and just enabled by iap.
That is correct, they worked with the plugin developers and included the code directly in Auria, just waiting to be activated.
Thanks guys. Pretty slick in any case.
Me neither...that's why I stuck with S. LOL