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.
Apple AUs on iOS (please help to improve music making on iOS)
Why haven't they been ported to iOS yet?
Apple made so many ads with music creating but they are not putting out these tools that live inside every mac. They are pulling our leg.
See page 3 of the thread
- Better the day before today.15 votes
- Sure why doesn't this happen.80.00%
- I have no idea what's going on.20.00%
Comments
Which ones are you referring to specifically?
They're mostly all there. It's up to the host to expose them.
32 band graphic eq, all the other eqs, filters and dynamic tools,
It's about 15 (?)AUs
There also is the Au sampler and the Au Matrix reverb ...
And what do we get on iOS?!?
My mac just died and I really miss this stuff.
They are already there, in your iPad. Waiting for a host to make them available to you:
We're talking about these?
Yes.
@brambos
Im not sure I understand,
Are you saying no host makes them available?
You can use them in zMors Modular. AFAIK, it's the only app supporting those AUs
Indeed. These are AUv2 plugins (which is not an 'extension' format). This means they have been part of the system for a long time, but they need to be explicitly exposed or encapsulated by a host or another app to become available to the user.
However, not many apps or hosts do this. I suspect this is because hosts are typically multiplatform and therefore they prefer using their own effect libraries which can be easily ported to other operating systems (without being tied to one specific Apple OS).
If I recall correctly Cubasis will at some point 'expose' the system AUs to the user.
From what I know there is no 'Default UI' on the iOS versions of the AU's so a host needs to provide that?!
The AUSampler could be used as a soundfont player as an example...
The AUPitch would be neat to automate to do some fake auto-tune on vocals and things like that.
For the AUs to be truly useable we'd need a host that is able to fully automate them.
Interesting, I'd like to use the pitch one. Maybe @j_liljedahl could expose them for AUM.
So who's door do we need to kick in?
Apples or every hosts?
The last option is pure madness?
They were not meant to be used by end-users. They're just building blocks audio apps can use to quickly and painlessly implement sophisticated audio dsp. Hence (as Samu also mentioned) they don't have a UI. Essentially they're just an API rather than plugins.
If you need them in a particular host, you should ask the host to expose them for you and provide a UI.
This is really weird.
UI can't be that hard, it's just a few sliders...
I want them everywhere just like on the mac ...
They sound really good.
On macOS some of the AU's have a 'built-in' UI. On iOS they don't even if the functions are there.
Renoise (My favourite 'Tracker') supports AU's some with just 'parameter list' while some use the Apple-Provided UI.



The AUSampler in particular is pretty capable
What annoys me is that iOS Garageband has a lot of capable synths under the hood but they are not fully exposed to the user. Retrosynth, ESX24 and Ultrabeat are just a few of them...
I know
@brambos
So all that would be needed is lifting from version 2 to version 3 by apple ?
Hello, let's type up a storm to apple.
Exposed? As in........... like implemented, utilized, used by a host app???? I can't wrap my head around what exposed means, and what needs to happen to use these things?
Exposed as in 'made visible and useable to the end-user'.
It's up to the developer(s) to do the custom UI and utilise the API's in their apps.
They're basically just the DSP functionality. "Exposing" them would require someone to make a GUI for them to interact with the available parameters, handle the incoming/outgoing audio stream formats, manage memory, handle the incoming (midi) events, manage presets, provide access to host tempo/timeline data, handle error states, and a number of other small household tasks. It's not rocket science, but not trivial either.
Yep. Many of the AUs are used in apps that aren't hosts already as part of the audio engine. Soundprism does that.
This is getting more and more interesting.
I'm getting some really cynical thoughts about this, I better don't talk about
All of this has been taken care of on the mac.
So I repeat the question:
All apple needs to do is lift from version 2 to version 3?
They are pulling our leg.
They're not. They're simply providing a toolbox for developers.
Could I load the zMors Modular into effect slot of Audiobus and load the AUPitch into zMors Modular to treat the audio from Audiobus input with it?
Nope, they are providing a toolbox for everybody on the mac.
No need to do Xcode voodoo.
None coding simpletons like me are invited to use them.
The Mac supports AUv2 plugins. iOS does not (at leat not without Xcode voodoo).
Aha.
So better talk to apple than go on everybody's nerves, me thinks.
It does not support AudioBus, only IAA
For me AU/AUv3 'support' is a similar 'process' as getting developers to adopt other standard iOS features such as iCloudDrive/iOS-DocumentPicker.
So if we as a community want to see AU/AUv3 support we need to drive the issues and requests forward to the developers as Apple is highly unlikely to do so...(I would be pleasantly surprised if GarageBand evolved into a fully featured AUv3 capable host with full automation and other mumbo-jumbo).
There was a discussion here some time ago where the ZMors modular developer mentioned making 'AUv3 Wrappers' for the system AUs. Don't know what happened to that? Meaning ZMors would act as a 'container' for for all system AUs with custom UIs and make them available as AUv3 Extensions. (I wonder if Apple would approve the app as it would be like selling repackaged system features).
Then again we don't know what Apple has planned for iOS during WWDC'17 other than the 'next iOS'.