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.

Volt and MIDI Map

papertigerpapertiger
edited January 2020 in General App Discussion

I’m having a very strange problem with Volt in AUM.

I can use my LCXL to send MIDI CCs to other apps (e.g. Lagrange, Tardigrain) in AUM via their own internal MIDI Learn and/or MIDI mapping functions, but I can’t do the same with Volt. The only way I can get Volt to receive MIDI CCs from the LCXL is through AUM’s internal MIDI control routing. This result doesn’t seem normal.

I hope someone can tell me what I’m doing wrong, because if this is an issue it seems surprising that no one else would have run into it before me.

Thanks in advance!

Comments

  • papertigerpapertiger

    Has anyone been able to get Volts MIDI map to work in AUM or Cubasis 2?

    I’ve loaded it up in both hosts and no matter what combination I try, I can’t get my MIDI controller, which has been mapped to certain Volt parameters, to work with Volt. The mapping works fine standalone. I’m at a loss.

  • wimwim

    @papertiger said:
    Has anyone been able to get Volts MIDI map to work in AUM or Cubasis 2?

    I’ve loaded it up in both hosts and no matter what combination I try, I can’t get my MIDI controller, which has been mapped to certain Volt parameters, to work with Volt. The mapping works fine standalone. I’m at a loss.

    Are you using the AU or the IAA in AUM?

  • papertigerpapertiger

    AUv3

    Thanks for asking for clarification. I forgot to specify. I’m just so blown away that I’m having this issue. Kai/Numerical’s apps have always been solid for me.

  • wimwim
    edited January 2020

    I’m pretty sure that you will need to map your cc’s to the AU parameters. I don’t think the AU responds to CC’s. Most AU apps don’t since the AU parameters are the usual way to control them.

    I wouldn’t call that a bug. It’s more of an unexpected consequence of having both an AU and an IAA version of an app.

  • papertigerpapertiger

    I am using AUs in both hosts. As I explained above, other AUs respond as expected, including Shockwave, which is also by Numerical. Of course, the MIDI CC engine was improved in that app/AU to add MIDI learn. Maybe during that process Numerical changed something in the code that solves the issue I’m experiencing with Volt.

    Thanks for trying to help, @wim , but I think there is an issue with Volt MIDI mapping. I’m super bummed but I’ll reach out to Kai as I’ve worked with him on a couple of other issues (before the baby was born, though! Lol :smile: ).

Sign In or Register to comment.