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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Setting up Korg Nanokey Studio for iOS AU3 hosts?

I picked up a Nanokey Studio (NKS) a short time ago - this thing has a really nice set of features and works great with Gadget, but isn't set up great for other iOS AU3 hosts like AUM, Loopy Pro, Drambo, etc. It is however massively configurable; you can remap (nearly?) everything on it to send whatever MIDI notes, channels, CCs you want from the various knobs, keys and pads. There's 8 different "scenes" on the NKS, which essentially means it can store and recall 8 different sets of mappings of knobs, keys, pads.

Has anyone come up with a set of mappings for NKS that work well with AUM, Loop Pro, Drambo and/or any other other iOS AU3 hosts? There seems to be 3 three paths:
1. Find someone who's already done all the hard work of setting up their NKS for iOS AU3 hosts, and beg for a copy of their setup or some tips on how to go about it. Maybe someone like @jakoB_haQ has some thoughts
2. Go through the effort of working out the best way to map knobs/keys/pads for each of the AU3 hosts I use, and implementing each of those in different scenes on the NKS. Then I'd simply switch scenes depending on which AU3 host I was using at the time
3. Leave the NKS config at the default settings, and use either Mozaic or StreamByter to convert the default output of the NKS for whatever AU3 host I want to use. As usual there's pros and cons to both Mozaic and StreamByter, but this feels like the best/most flexible option as well as the most work

This is me exploring option 1 - the laziest possible option... :grin:

Comments

  • wimwim
    edited February 18

    Option 3 is probably the least work, but generally you shouldn't need scripts except for specialized things.

    Most hosts don't have fixed CC mappings for the things that they can control. So you end up using "Midi Learn" to set them up. So, since you have to set those mappings up anyway, no matter what the NKS is sending, there's no advantage to changing what is sent.

    You're going to find that not all things that you think should be controllable via midi in every host are controllable, unfortunately.

  • wimwim
    edited February 18

    The only thing I use the NKS scenes for is to change the midi channel that the keyboard and the pads send on. That allows me to play different synths by changing scenes. I do have one scene where the drum pads are set up for the unusual notes that Bram Bos drum apps use, since I use those apps so often.

  • When you do need to do remapping, mfxConvert can often be used to avoid needing to script. This is especially handy for drum remapping, where you could use it to convert the notes sent by the pads to whatever notes a drum app might use. A quick run through of the 8 pads and save as a preset is all you need to do.

  • @monch1962 said:
    I picked up a Nanokey Studio (NKS) a short time ago - this thing has a really nice set of features and works great with Gadget, but isn't set up great for other iOS AU3 hosts like AUM, Loopy Pro, Drambo, etc. It is however massively configurable; you can remap (nearly?) everything on it to send whatever MIDI notes, channels, CCs you want from the various knobs, keys and pads. There's 8 different "scenes" on the NKS, which essentially means it can store and recall 8 different sets of mappings of knobs, keys, pads.

    Has anyone come up with a set of mappings for NKS that work well with AUM, Loop Pro, Drambo and/or any other other iOS AU3 hosts? There seems to be 3 three paths:
    1. Find someone who's already done all the hard work of setting up their NKS for iOS AU3 hosts, and beg for a copy of their setup or some tips on how to go about it. Maybe someone like @jakoB_haQ has some thoughts
    2. Go through the effort of working out the best way to map knobs/keys/pads for each of the AU3 hosts I use, and implementing each of those in different scenes on the NKS. Then I'd simply switch scenes depending on which AU3 host I was using at the time
    3. Leave the NKS config at the default settings, and use either Mozaic or StreamByter to convert the default output of the NKS for whatever AU3 host I want to use. As usual there's pros and cons to both Mozaic and StreamByter, but this feels like the best/most flexible option as well as the most work

    This is me exploring option 1 - the laziest possible option... :grin:

    Option 4: leave the nks as it is, midi learn in your host of choice. Loopy Pro, for example, doesn't have built in mappings. So there is no need to reconfigure a controller. MIDI Learning in Loopy Pro is as simple as turning in MIDI Learn, tapping what you want to control, touching the control on your controller.

  • Thanks everyone. Strangely using MIDI learn never even crossed my mind...

Sign In or Register to comment.