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 in for AUM!
In Audiobus I can have Thesys feeding Arctic synth in one channel and Fugue feeding into Addictive synth next to it. I have not figured out a way to do this in AUM. Am I missing something? I know the midi control page for routing, but is there a way inside AUM?
Comments
Not yet, I use Midiflow.
Fugue machine will have channel options soon.....................................
As will AUM. You can, of course, just continue to use audiobus and feed the AB outs into AUM. This is how I use it mostly.
Otherwise, yep @MIDIFlow.
That's helpful, thanks.
I'm not sure I get it, if you can have Thesys -> Arctic and Fugue -> Addictive in Audiobus, why can't you have it in AUM too? Audiobus does no MIDI routing, so if you can hook the apps up like that in Audiobus, you should be able to do exactly the same in any IAA host, including AUM?
Yeah this confused me too, Audiobus has no midi.
There is midi routing in AUM, but there is no dedicated Midi-AUM-channel. Maybe that's where the confusion starts. So now I must put a midi-only-generating app like Thesys (or Cream, Pro midi, etc.) as Source in an Audio-AUM-channel (with audio-FX-Insert(s) and hardware audio (or mix bus) Output and the audio-app where you want the midi-output from the midi-generator to go to, has to go as Source in another AUM-audio-channel... It would feel more 'natural' when there was a choice for a dedicated Midi-AUM-channel, with the midi generator as Source, midi-FX as Insert(s) and the midi-recieving audio-app (synths, etc.) as Output. The audio-output from that same audio-app then has to go through it's own AUM-audio-channel of course.
Hmm.. well there's no such concept or mechanism in iOS. There's virtual MIDI and there's IAA-MIDI (host to node).
I know some MIDI generator apps has implemented IAA/Audiobus just to be able to sit in the AB session and show up in the AB control panel, even though they actually don't generate any sound. Such apps can be used in AUM too, by adding them on a channel and just removing the output node, just to make it easier to switch to the app.
There was some initiative for a similar switch-between-apps registry for MIDI apps, but now with the iOS 9 URL whitelist safety requirement, that becomes quite hard to work with..