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.

Exposing module controls in Drambo as auv3 parameters

Is this possible? My specific use case is loading drambo into NS2 and being able to map the NS2 knobs and xy pad to midi cc modulators in Drambo. I only see “parameter 1” available in NS2. What am I missing?

Comments

  • edited April 2021

    Cant you map via drambo?

    Use midi map in Drambo instead of ns2. If you can route controllers to Drambo.

  • @sigma79 said:
    Cant you map via drambo?

    Use midi map in Drambo instead of ns2. If you can route controllers to Drambo.

    That’s the problem. You can’t route cc directly in NS2. You map them to a set of internal knobs and pads and then you map those to whatever auv3 parameters the synth exposes. Drambo sees notes and pb but not cc’s.

  • @boomer said:

    @sigma79 said:
    Cant you map via drambo?

    Use midi map in Drambo instead of ns2. If you can route controllers to Drambo.

    That’s the problem. You can’t route cc directly in NS2. You map them to a set of internal knobs and pads and then you map those to whatever auv3 parameters the synth exposes. Drambo sees notes and pb but not cc’s.

    Dont know then Boomer. Hope it gets sorted

  • Looks like a Drambo AUv3 issue when using CC inside NS2. I've reported it.

  • @rs2000 said:
    Looks like a Drambo AUv3 issue when using CC inside NS2. I've reported it.

    Thanks rs2000. As an FYI. There are no exposed parameters when loading Drambo as an auv3 into AUM either. Thinking about it, what would Drambo expose? There are almost infinite possibilities. Drambo would have to provide a mechanism for users to customize which controls within their patch to expose. Maybe a fixed set of exposed reusable parameters the user could route to whatever controls they wanted.

  • @boomer said:

    @rs2000 said:
    Looks like a Drambo AUv3 issue when using CC inside NS2. I've reported it.

    Thanks rs2000. As an FYI. There are no exposed parameters when loading Drambo as an auv3 into AUM either. Thinking about it, what would Drambo expose? There are almost infinite possibilities. Drambo would have to provide a mechanism for users to customize which controls within their patch to expose. Maybe a fixed set of exposed reusable parameters the user could route to whatever controls they wanted.

    It's not about Drambo exposing any parameters but rather about receiving MIDI CC that can then be mapped freely inside Drambo.

Sign In or Register to comment.