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.
AUM users - question about MIDI routing!
Hey guys, just a quick one. So I'm trying to set up my Air 2 to be like a multi-timbral sound module through AUM (multiple MIDI channels on my laptop controlling various instruments). Question is, do I have to manually reconfigure each instruments MIDI input options every session, or is possible to control MIDI channel assignment through AUM? I've filtered the incoming MIDI channels to my various synths but they're all receiving notes from channel 1. I'd rather not have to go changing MIDI preferences for each app individually as it'd render session recall in AUM more or less useless unless I always use certain instruments on certain channels.
Thanks!
Comments
If you route all your intended apps in AudioBus first, with AUM as the output, the apps will to a session save if you save that session in AudioBus. This means that you then can set them to various midi channels etc, and they will remember it when you load that AB session. All of the above obviously need the apps themselves to support session save.
In AUM you can store your routing too, but that will only remember it as far as AUM is concerned. What I normally do is to start with opening MidiFlow (which I use for main routing/control of my keyboard) recalling a session, then start AudioBus with recalling a setting (often named the same as in MidiFlow), which then loads all the apps/instruments I intend to use incl AUM, then flip to AUM and recall that session (again, named as the other two apps settings). In AUM I then have all my faders/controls bound to my midi keyboard and only in a few apps do I need to change the midi settings (some don't fully save the session, some only store the preset used and its settings, not the midi settings) which usually means turning off midi controllers going in.
I used to use AUM that way, but I couldn't figure out a way to do it within AUM. The best solution I found was to buy another app: MidiFlow. You can save a preset in MIDIFlow which will do all of the MIDI routing for you. Basically, you make "channel strips" in MidiFlow which tells it stuff like: send incoming channel 1 MIDI from my MIDI keyboard to Korg iM1 and don't send it anywhere else, send incoming channel 2 MIDI from my USB MIDI interface to Animoog and don't send it anywhere else, convert channel 3's incoming mod wheel messages to expression CC and send to AUM for channel fader control, etc.
I think this is another example where AU apps are useful as you can route and filter the MIDI each AU instance receives and have it saved as an AUM file you can recall later. Unfortunately there's a lot of variation in IAA apps with respect to how they use MIDI, and being able to save their MIDI setups from project to project.
I agree with the others that at times Midiflow can definitely be a useful tool for setups where AUM's MIDI capabilities and the IAA apps you're using won't be sufficient.
Even some AU MIDI implementations can be problematic. For example, I wanted to sequence several instances of Troublemaker using MIDI note and CC output from Patterning. Unfortunately, Patterning uses CC 10 for panning and Troublemaker uses it for selecting the waveform. I wanted to use CC 10 for panning so I had to use Midiflow to filter out CC from Patterning and send notes only to the Troublemaker instances. I then sent the Patterning MIDI to AUM's MIDI Control port so I could use CC 10 to control panning via AUM's built in stereo panning effect and used CC 74 to control filter cutoff for the Troublemaker Cutoff parameter. It's always nice to be able to set and adjust MIDI settings in an app but rarely are we given the ability to do this let alone save and recall them.
An app like Midiflow can definitely come in handy for bridging the gap between how developers envisioned people using their app versus how you want to use it.
MIDI on the iPad drives me to drink.
I agree with this statement haha. I mean, it's not essential I get this working, but it's just nice to have different ways of working. Different setups to inspire different ideas. I grappled with it a bit last night but, as usual, I just ended up using the synths in my DAW. It's a shame though cos there's the potential to do some really interesting things like create poly synths using a voice distributor addressing different IAA synths per voice. I guess if I really wanted that I could just set it up for a specific session. It's just a bit of a pain. Or I could just use Gadget. The synths in that are pretty decent and everything is recalled perfectly. Oh well! Thanks for the suggestions anyway. I'll check out MIDIflow and see if it works for me