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.
Why the same AU apps not performing the same on different AU Hosts? AU or Host issue?
Some AU app/units can be indentified on Host A but not on Host B, or not functioning the same after being hosted. May I know this is mostly an AU instrument/plug-in issue or an AU Host issue?
Comments
It can be either/both. Also if you mention Apple has horrible documentation that doesn't help the situation, you get to see devs fight, some of which back you up and others who accuse you of going after a 'hot take'. Fun for all!
Without providing details , it is hard to speculate what the cause might be.
It is rare for the same AU to be available in some hosts but not others.
Is this really that case still (horrible documentation) in almost mid-2024, or, just a thing dancing around on internet?
Perhaps we can get a new statement from our king & queen developer here?
Just sayin', documentation doesn't normally improve with age. It just gets more out-of-date. Improve documentation is not generally a priority for software managers.
A friend that writes both host and AU code has recently remarked on how poorly documented this stuff all is…and the Apple APIs are buggy.
Okidoki!
I’m not saying it’s the case with you, but often it comes down to not knowing where to look in the host. In the case of GarageBand though, there’s the whole class of Midi AU FX that aren’t supported.
If you could be more specific, we can give better answers.
Honest I don't own many AUv3 Hosts. Only EG Nodes and Garageband. For instance, Geoshred Control can be hosted perfectly on EG Nodes even it is not an instrument just a controller, but it is not showing up on Garageband.
Seems it's safe to say most likely Garageband issue?
Edit: typo
As already mentioned, GarageBand does not support AUv3 MIDI FX. So, yes, a GB issue.
Thanks all for help