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.

Pre-mapped MIDI bindings and widgets

oscillotusoscillotus
edited October 2025 in Loopy Pro

It would be a tremendous QoL improvement to have the ability to link MIDI mapping profiles to specific AUv3s. For example, when I MIDI map a synth to my Midi Fighter Twister and I load up a second instance of the synth, then I need to copy the profile and remap all the bindings, which kills much of the flow. Same thing when I load up an already mapped synth to a new project. Instead, when I load up the synth (or any AUv3), there could be an option to also load up a MIDI mapping profile with it with all the bindings linked to it.

Along the same lines, it would be great to be able to load up a group of widgets already mapped to an AUv3 along said AUv3.

The reason behind this is I look to move away from hardware devices to Loopy Pro + MIDI controllers, but always having to remap stuff makes me question this. Removing this inconvenience would make it so much easier!

🪷

Comments

  • PapaBPoppinPapaBPoppin

    @oscillotus said:
    It would be a tremendous QoL improvement to have the ability to link MIDI mapping profiles to specific AUv3s. For example, when I MIDI map a synth to my Midi Fighter Twister and I load up a second instance of the synth, then I need to copy the profile and remap all the bindings, which kills much of the flow. Same thing when I load up an already mapped synth to a new project. Instead, when I load up the synth (or any AUv3), there could be an option to also load up a MIDI mapping profile with it with all the bindings linked to it.

    Along the same lines, it would be great to be able to load up a group of widgets already mapped to an AUv3 along said AUv3.

    🪷

    Forgive my ignorance, but can you not save it as a Loopy Preset with the cc bindings and when loading a new instance of said plugin, just load that preset?

    Or is midi binding not saved via that base-level Loopy preset saving?

    (Im not at a place to test right now)

  • oscillotusoscillotus

    @PapaBPoppin said:

    @oscillotus said:
    It would be a tremendous QoL improvement to have the ability to link MIDI mapping profiles to specific AUv3s. For example, when I MIDI map a synth to my Midi Fighter Twister and I load up a second instance of the synth, then I need to copy the profile and remap all the bindings, which kills much of the flow. Same thing when I load up an already mapped synth to a new project. Instead, when I load up the synth (or any AUv3), there could be an option to also load up a MIDI mapping profile with it with all the bindings linked to it.

    Along the same lines, it would be great to be able to load up a group of widgets already mapped to an AUv3 along said AUv3.

    🪷

    Forgive my ignorance, but can you not save it as a Loopy Preset with the cc bindings and when loading a new instance of said plugin, just load that preset?

    Or is midi binding not saved via that base-level Loopy preset saving?

    (Im not at a place to test right now)

    I thought that the preset system was solely for the parameters, not the CC bindings? And the CC bindings are in the Control Settings > Project/Global Profiles.

  • wimwim

    You should create a feature request on the Roadmap Site. I did a brief search, and I don't see any existing request like that yet. If you do create one, post a link here to get some upvotes on it.

    Audiobus had (has) that feature and it was useful.

  • oscillotusoscillotus

    @wim said:
    You should create a feature request on the Roadmap Site. I did a brief search, and I don't see any existing request like that yet. If you do create one, post a link here to get some upvotes on it.

    Audiobus had (has) that feature and it was useful.

    Will have a look, thanks @wim!

    Should I make 2 different feature requests for the MIDI mapping and the widget groups separately?

  • wimwim

    @oscillotus said:
    Should I make 2 different feature requests for the MIDI mapping and the widget groups separately?

    🤷🏼‍♂️

Sign In or Register to comment.