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.
Current state of Korg Gadget MIDI control?
I found some older posts but nothing current or for v3…
Is there some magic method to control mixer (vol, sends, mute) via regular midi, or is that being done via some magic handshake with Korg’s own hardware?
I know you can midi map individually for each gadget, but not seeing any midi learn for the higher level functions.
Does the nano (key and studio) actually support mixer control, track selection etc? If so, do we know if it’s just via plain midi?
Comments
It's a proprietary handshake. You can turn off "native mode" in iOS Settings > Gadget if you prefer
That's correct. You can't control the mixer via standard midi.
I think the NanoKONTROL supports mixer control. But I honestly don't know. NanoKEY Studio does not.
Seems to be sysex to identify the device. After that it's CC messages, but they're routed internally to whichever Gadget has the focus. I tested by setting up MidiFire to listen to both the NanoKEY Studio and to Gadget, then turning the NKS off and back on. There's a sysex handshake, then CC's sent from the knobs on channel 16.
I don't have a NanoKONTROL to test with, so I can't verify what it can do or observe the MIDI streams. If someone can do that though, it might be possible to mimic the handshake and to fake native mode.
Thanks for confirming for me. Korg is “interesting” in how they prioritize stuff… To me, having midi control over the meta level stuff (track volume and sends, track selection, etc)make more sense than midi mapping per gadget, especially since recording automation via midi controller results in unusable automation lanes as it jumps all over because it seems to read automation data, before it reads midi controller, the seems to write the new position after the original stored position, so you get knobs that just spaz out.
Gadget in general almost seems like it was designed to frustrate people. Heavily used ui elements are like 4 pixels wide, it there’s plenty of easy to use stuff that never gets used…
Just weird…