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.
Dumb midi question: how to set midi channel for 2 different controllers in AUM
I am trying to use a nanoKontrol for mixer/transport controls, and a midi fighter twister for in-app controls (Enso, specifically). Both devices are set to channel 1, so slider 1of the nano and knob 1 of the mft are tied together... How do I get around this. Seems like it should be easy, so sorry for the dumb q if it is...
Comments
Are you sending both of those controllers to MIDI Control in the routing matrix? If you are then you’ll need to use some kind of utility to change the channel coming from one of them. MfxStrip is a good one for this. Route one of the controllers to mfxStrip, and change the channel, then route mfxStrip to MIDI Control.
Note below how I have the NanoKEY Studio routed to mfxStrip, then mfxStrip to MIDI Control. MfxStrip is converting to channel 2. Sensel Morph is going direct. Both controllers are set to ch. 1, but the end result to MIDI Control is ch. 1 and ch. 2.
Some controls in Enso can only be reached by going direct to the app, not through MIDI Control. If you need one of the controllers to go direct to Enso, then you just need to route them each differently, and you don’t need mfxConvert.
Note how one controller goes to Enso and one to MIDI Control. There’s no channel conflict because each goes to a different destination.
Thank you for this. I haven’t had a chance to try yet but I imagine both of these solutions should solve the problem. And yes, I was routing via midi ctrl.
Enso control really odd by iOS standards. Some parameters can be automated only through AU Parameters and some can only be automated by mapping CC's within the app. I know of no other app like that in iOS.
So, you may run into needing to map the same controller to both MIDI Control and to Enso directly. This is fine, but you'll need to convert the channel of one of the controllers like in the first example.
Normally, choosing one or the other: AU Parameter automation, or (if the app provides it) directly with mappable cc's, is best. Enso muddies those waters. Lucky you ... chose the most confusing plugin possible to cut your teeth on.
Sorry - forgot to link to mfxStrip on the App Store earlier. I also recommend mfxConvert. They're both inexpensive, and situations needing those two apps seem to come up all the time.