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.
AU parameters working in one host but not another?
Has anyone ever run into a situation where an AUv3 app
A. had midi parameters exposed
B. did NOT respond to any midi CC messages in AUM - and definitely not related to human error
C. DID respond to midi CC messages in another app, say, apeMatrix
What would cause this and what would be needed to fix it?
Comments
Just to clarify, are you referring to AUv3 parameters, or MIDI input messages?
Is it possible that the app is responding directly to Core MIDI and not to MIDI routed by the host?
Can you identify the AUv3 app, so we can test it ourselves?