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.
Is Logic AU Multi-out routing broken?
Every time someone asks me about how to route Patterning Multiout in Logic Mobile it takes me a half hour to re-figure it out.
But this time I can't figure it out at all - and it seems like it might even be broken.
Does anyone know how to do this?

Comments
What usually needs to be done once (per plug-in to validate it) or after reseting Logic settings, is to load the AUv3 (with multi-out capability) to a track in the project, close/restart Logic (with the project open).
After the project is re-loaded 'replace' the plug-in and select the multi-out option (ie. change from stereo to multi-out).
LogicPro for iPad also an automatic disable plug-in 'feature' if a plug-in crashes too many times and the only way to get it back is to reset logic settings (There's no plug-in manager in the iPad version where plug-ins can be enabled/disabled or 'validated') and yea, this means all Multi-Out AUv3's have to be manually validated all over again using the procedure as mentioned...
I urge all developers to bombard Apple with feedback regarding handling of AUv3 plug-in's in LogicPro for iPad, it's very mildly put a total sh*t show.
I've done my share of bug-reporting (to a degree were I won't bother to post more feedback until the already reported issues are sorted out) but the development progress is way to slow for a subscription based software...
(I'll very, very likely not renew my subscription when it's set to renew at the end of June).
Glad to know it's not just me finding this to be frustrating.