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.

How to deal with drum pads controller mapping and all those differently working iOS drum plugins?

I stumbled about this questions as i re-activated the classic machines in Cubasis lately. When i first used them, i did not use an external controller. But now that i have the miniLab with its drumpads (witch i acually just use with ruismaker), i realized that other drum modules, that have no midi learn options like those classics in Cubasis, need extra mapping. And as i mentioned in this thread:
https://forums.steinberg.net/t/classic-machines-inconsistent-mapping/862996/2
these classic machines midi notes are somehow wired.

I do not want only rant about it but rather find a good solution or workaround. Could think of a routing via mozaic and something that can transpose notes in realtime.

I would like to know how you deal with your drumpads and different drum plugins (not only the cubasis stuff)

Comments

  • I use mfxConvert. Route the midi to it, then route it to the app. Engage the learn button then press a pad. Now set the output note needed for the app you're controlling. Repeat for every pad you need. Save the preset for future use.

  • edited August 2023

    If I don’t know what midi notes trigger what pads, I sometimes send the midi out from a drum plugin to a midi piano roll like Atom 2 or other, then simply play the pads in order, and record the midi output. Then look at Atom 2 and you will see what notes trigger what pads.

    You can also connect a midi piano roll like atom 2, to the drum app, turn the speaker on, and tap the keys on the left side of the piano roll, until you hear the pads you want, then you know what notes trigger what pads.

    Lots of apps have their midi mapping listed in the manual, or in the settings.

    Some drum sequencers (ie Octachron) and pads (ie Xequence AU Pads) have drum app presets already mapped for you so you can look at those for the info if needed.

  • @wim said:
    I use mfxConvert. Route the midi to it, then route it to the app. Engage the learn button then press a pad. Now set the output note needed for the app you're controlling. Repeat for every pad you need. Save the preset for future use.

    Thank you!! Looks like a very useful tool and i will try it.

Sign In or Register to comment.