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.
AB3 - CC messages not received
I'm using the Torso T-1 hardware controller to send CC messages into AU plugins running on AB3. Although the MIDI learning function correctly captures the CC message number and the MIDI channel, the actual changes in CC values when I move the knobs are not received by the plugin. I tried it on Sunrizer as an AU. The interesting thing is that when I run Sunrizer standalone, the CC values are correctly received. I also double checked on MidiWrench and everything appears to be in order.
On AUM, the exact same mapping works flawlessly.
Screenshots:
[(https://forum.audiob.us/uploads/editor/7q/411w82qn9cyz.jpg "")
Comments
Hi. This "works for me". Try creating a MIDI lane in AB3 and routing the T-1 MIDI into StreamByter (free) as MIDI effect. Use its MIDI monitor (magnifier at the bottom) to see the MIDI messages coming in. This will confirm they are actually reaching AB3.
I don't see parameter "VCA DECAY" in the AUv3 parameters for Sunrizer. Could you name the app you were using, or post a Sunrizer example? And note that, when Sunrizer runs stand-alone, it works completely differently. It receives CoreMIDI and applies its internal MIDI mapping rules. While, when it runs as AUv3, AB3 maps the MIDI to AUv3 parameters published by the app. If the problem continues, you could simply route the T-1 to Sunrizer, and use its internal MIDI mappings.
And please change your title to include "AB3 MIDI Learn" or similar. This forum covers a lot more than just Audiobus, so the current title could apply to anything.
In that particular case I was actually using the Ruismaker Noir drum machine. I've tried it on other plugins as well, with the same result.
I will use the plug-in that you recommend to intercept the CC messages.
I tried VCA DECAY in Ruismaker Noir, and it maps with no problem. I suspect the problem is with the MIDI coming in to AB3, not the mapping itself. Note that you may need to turn off MIDI learn for the controls to take effect.
As you can see. There is definitely CC messages being sent. And still, no changes happen in the receiving plugin, be it Ruismaker Noir or any other.
I'm running out of ideas.
I just set up MIDI CC control (from my Launchkey MINI) of Sunrizer AU's filter using the AudioBus 3 MIDI Learn.
Can you screen record the creation of your session and show it in use?
Here is me using AB3 to control Sunrizer's filter. Note that I connect my MIDI keyboard on the MIDI page - but that isn't necessary -- it just let me play the synth from the keyboard. If I play from Sunrizer's keyboard the CC still works with no such routing.
I fully understand now what was happening. There was nothing wrong with the routing. I just forgot to buy the midi learn add-on after the trial period and therefore the CC messages were not reaching their destination