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.
MIDI Routing Question
Trying to do something in Loopy Pro that's kind of driving me crazy. My keyboard sends on channel 1 and while I can change to other channels its really a pain. I want to just have a button mapped to each auv3 that isolates midi to it.
I created radio buttons mapped to the Enable/Disable MIDI Destination feature which works perfect...I can select one radio button and only send MIDI to Animoog, select the next and it sends to King of FM.
The problem I have is that if I go into the mixer and replace Animoog with another plugin, then the button action is blank and I have to go back and remap it.
Anyone figure a way around this? Ideally Loopy Pro would see that I'd replaced a given Auv3 and just update the button action there, but it doesn't seem to work that way.
Thanks!
Comments
That's odd. I replace plugins all the time with just this kind of action and it works every time.
... oh no, wait. I'm sending the keyboard to a MIDI Color, then the Color to the plugin. That's better for my use because I can record the midi and play it back without changing any routing. In fact my starting template has five "dummy" instruments (Streambyter) already set up with routing. I just replace the Streambyter instances with the plugins I want as I go.
That is what works for me. I tried what you're doing and had the same results as you.
If you don't like the idea of having midi loops visible to get the midi colors available, you could create a new page for the loops to get them out of sight.
The routing I use is: midi source > midi color > plugin > audio color > output. I use the same audio color as the midi color for each to help me keep track.
Thanks for the report. We will look into it. Replace should probably be updating those references.
Thanks for the help...I was able to get this working by sending to the midi color versus the plugin directly. When I swap the plugin the color mapping remains the same.