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.

Can't map Combustor controls in AUM

I can't figure out how to properly map CC values from my controller to the parameters for Combustor. I learn the values and they seem to map fine but the dials in the app jitter all over the place and though they move when I move my controller dials, they continue to jitter and don't seem to actually affect the parameter value. Any ideas greatly appreciated!

Greg

Comments

  • @gkillmaster said:
    I can't figure out how to properly map CC values from my controller to the parameters for Combustor. I learn the values and they seem to map fine but the dials in the app jitter all over the place and though they move when I move my controller dials, they continue to jitter and don't seem to actually affect the parameter value. Any ideas greatly appreciated!

    Greg

    What kind of controller? Are you mapping relative encoders or absolute controls? If you send the controller output to a midi monitor, are you getting a constant stream of a single value when you turn the knob, or are you getting increasing or decreasing values.

    The behavior seems like you may be trying to use relative encoders. AUM doesn't support that.
    Just a guess.

  • @wim said:

    @gkillmaster said:
    I can't figure out how to properly map CC values from my controller to the parameters for Combustor. I learn the values and they seem to map fine but the dials in the app jitter all over the place and though they move when I move my controller dials, they continue to jitter and don't seem to actually affect the parameter value. Any ideas greatly appreciated!

    Greg

    What kind of controller? Are you mapping relative encoders or absolute controls? If you send the controller output to a midi monitor, are you getting a constant stream of a single value when you turn the knob, or are you getting increasing or decreasing values.

    The behavior seems like you may be trying to use relative encoders. AUM doesn't support that.
    Just a guess.

    Hi @wim ; Using launchkey MINI Mk3. Using midi monitor the values increment and decrement from 0 to 127. Bitwig shows it as absolute. So I'm sending the values through my MIDI interface to my iPad.

  • edited January 2024

    @gkillmaster You might want to try mapping your controller knobs in Drambo first. If one of the incremental CC types work then it's what @wim and me suspect.
    Can your controller be switched to absolute CC mode?

  • @gkillmaster said:

    @wim said:

    @gkillmaster said:
    I can't figure out how to properly map CC values from my controller to the parameters for Combustor. I learn the values and they seem to map fine but the dials in the app jitter all over the place and though they move when I move my controller dials, they continue to jitter and don't seem to actually affect the parameter value. Any ideas greatly appreciated!

    Greg

    What kind of controller? Are you mapping relative encoders or absolute controls? If you send the controller output to a midi monitor, are you getting a constant stream of a single value when you turn the knob, or are you getting increasing or decreasing values.

    The behavior seems like you may be trying to use relative encoders. AUM doesn't support that.
    Just a guess.

    Hi @wim ; Using launchkey MINI Mk3. Using midi monitor the values increment and decrement from 0 to 127. Bitwig shows it as absolute. So I'm sending the values through my MIDI interface to my iPad.

    OK. That's odd.

    Yeh, I just tried in AUM and it's the same for me. Off to try in other hosts...

  • wimwim
    edited January 2024

    @rs2000 - No there's something hosed for Combustor parameter mapping. I'm definitely using absolute controllers and see what @gkillmaster is seeing.

    In Drambo I can't get anything to map at all for Combustor. The controls get added using the map button, but the knobs don't respond.

  • @wim said:
    @rs2000 - No there's something hosed for Combustor parameter mapping. I'm definitely using absolute controllers and see what @gkillmaster is seeing.

    In Drambo I can't get anything to map at all for Combustor. The controls get added using the map button, but the knobs don't respond.

    thanks for checking it! I just reported it to BeepStreet.

  • wimwim
    edited January 2024

    It's working fine in Loopy Pro.

  • Think there might be discussion about this on last few pages of original Combustor thread, sorry don’t know how to link.

  • wimwim
    edited January 2024

    @rs2000 - my bad re: Drambo. It's working fine there. Takeover mode faked me out.

  • wimwim
    edited January 2024

    @Zerozerozero said:
    Think there might be discussion about this on last few pages of original Combustor thread, sorry don’t know how to link.

    Yup. Same cast of characters too...

    https://forum.audiob.us/discussion/comment/1225057/#Comment_1225057

    (To link to a post, long-press the date of the post and then copy the URL to the clipboard.)

  • wimwim
    edited January 2024

    I bumped the earlier post acknowledging the problem over on the BeepStreet forum. The problem is only in AUM as far as I know.

Sign In or Register to comment.