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.

AUM channel switching with BlueBoard

Hi all,

I have AUM and tonex. I want my BlueBoard to switch between four audio channels within AUM, each channel having a different instance of tonex and various other effect plugins.

I have programmed each channel to learn to solo or mute. However, when I select a different channel, it does not mute the prior channel I was using.

Any ideas about how I fix this?

Cheers

Comments

  • Use a StreamByter script that "knows" the last channel used, so it can un-solo or mute it before enabling a different channel. Route the BB to it, and send its output to MIDI control.

  • wimwim
    edited December 2023

    @palakpaneer said:
    Hi all,

    I have AUM and tonex. I want my BlueBoard to switch between four audio channels within AUM, each channel having a different instance of tonex and various other effect plugins.

    I have programmed each channel to learn to solo or mute. However, when I select a different channel, it does not mute the prior channel I was using.

    Any ideas about how I fix this?

    Cheers

    Do you have Mozaic, or would you be interested in owning it based on the available scripts you might be able to make use of, or write on your own? If so, I could write a quick Mozaic script that would do the job. All I would need to know is what mode your Blueboard is in (Notes or CC's).

    Streambyter could do it as well, but I'm not as adept at writing Streambyter scripts.

  • Alternatively you could look at MidiMixer for AUM. I think it would also do the job, though I haven't personally tried it.

  • There is a free plugin that will send several messages out in response to one received message. Maybe it is called midi messenger.

    Use it between the Blueboard and AUM midi control. When it receives a message from the blue board have it send the mute cc for the three channels to be muted and solo for the channel to be soloed. Set that up for all four buttons.

  • @espiegel123 said:
    There is a free plugin that will send several messages out in response to one received message. Maybe it is called midi messenger.

    Use it between the Blueboard and AUM midi control. When it receives a message from the blue board have it send the mute cc for the three channels to be muted and solo for the channel to be soloed. Set that up for all four buttons.

    Good call on Midi Messenger! That's way less overkill than MidiMixer, and a way more maintainable than a Mozaic or Streambyter script. And, it's free. 👍🏼

  • Thanks for the suggestion regarding MIDI Messenger. I have installed it and loaded it into AUM. However, I don’t know how to correctly program MIDI messenger from within aum

  • @palakpaneer said:
    Thanks for the suggestion regarding MIDI Messenger. I have installed it and loaded it into AUM. However, I don’t know how to correctly program MIDI messenger from within aum

    Load MIDI Messenger in an AUM MIDI slot. In the AUM MIDI routing matrix (snake icon), route Blueboard to MIDI Messenger, and route its output to MIDI Control. This will send its output to the AUM controls accessed through the hamburger menu in the upper right, then sliders icon (see pic). You'll need to decide on the CC#s to use for the mute and solo actions. Configure MIDI Messenger to send them when it receives a message from Blueboard, and configure AUM to respond to them. Start with a simple test and work up to the full functionality.

  • Thanks. I am wanting to use my BlueBoard in program change mode so each of my channels remain lit up if i tap them more than once (as opposed to toggling on and off like in control change mode).

    I am able to make channel 1 solo, but I can work out how to make the a button mute channels 2, 3 and 4.

  • Looks like you need advice from a MIDI Messenger expert.

    But you might want to use CCs to control AUM, sending 127 for On and 0 for Off; turn off Cycle when configuring the AUM controls. The PC messages are fine for triggers, but awkward for controls, since they have only one state.

  • @palakpaneer said:
    Thanks. I am wanting to use my BlueBoard in program change mode so each of my channels remain lit up if i tap them more than once (as opposed to toggling on and off like in control change mode).

    I am able to make channel 1 solo, but I can work out how to make the a button mute channels 2, 3 and 4.

    As @uncledave says you should set up AUM to respond to CC messages in non-cycle mode to set the channel mute state.

    When midi messenger receives a PC , don’t pass it through. Have it send the CC values. needed to put the channels into the desired state.

    For example if PC0 is for soloing channel 1, have midi messenger send the cc’s to AUM to unmute channel 1, mute channel 2, mute channel 3, mute channel 4

  • @palakpaneer : in case it isn't clear. In MIDI Messenger, you set up the messages to send out (to AUM) and choose a trigger. When a trigger comes in, it is assed along until a message is set to block it.

    Your triggers will be the program changes, but you will want to send CC messages to AUM.

    Let's say you use CCs 0 thru 3 for the commands to AUM. A value of 127 mutes a value of 0 unmutes. Lets say you use program changes 0 thru 3.

    There are a few ways to organize the setup.

    The least number of messages to set up is to have the first four messages be the CCs to mute the channels. Set the trigger to any PC and let the message pass through.

    Then have four messages that unmute a channel. For example CC 0 with value 0. Have that message's trigger be PC 0. Set it to block that message. Do the same for the other channels but set each to the PC that unmutes that channel.

    So, what happens is all channels get muted when a PC comes in and then one channel becomes unmuted.

    You could also set up 16 messages which would let you mute and unmute without redundancy but requires more messages: 4 for each PC.

  • @espiegel123 said:
    @palakpaneer : in case it isn't clear. In MIDI Messenger, you set up the messages to send out (to AUM) and choose a trigger. When a trigger comes in, it is assed along until a message is set to block it.

    Your triggers will be the program changes, but you will want to send CC messages to AUM.

    Let's say you use CCs 0 thru 3 for the commands to AUM. A value of 127 mutes a value of 0 unmutes. Lets say you use program changes 0 thru 3.

    There are a few ways to organize the setup.

    The least number of messages to set up is to have the first four messages be the CCs to mute the channels. Set the trigger to any PC and let the message pass through.

    Then have four messages that unmute a channel. For example CC 0 with value 0. Have that message's trigger be PC 0. Set it to block that message. Do the same for the other channels but set each to the PC that unmutes that channel.

    So, what happens is all channels get muted when a PC comes in and then one channel becomes unmuted.

    You could also set up 16 messages which would let you mute and unmute without redundancy but requires more messages: 4 for each PC.

    Hi there, I am still struggling setting this up.

    With setting up the CCs with a value of 127 mutes and 0 unmutes, should these control the volume in each AUM channel, or do I link these to the solo and mute controls?

  • This is what my settings look like. I can make channel 1 solo using the CC command, but I can’t make the other channels mute

  • @palakpaneer said:

    @espiegel123 said:
    @palakpaneer : in case it isn't clear. In MIDI Messenger, you set up the messages to send out (to AUM) and choose a trigger. When a trigger comes in, it is assed along until a message is set to block it.

    Your triggers will be the program changes, but you will want to send CC messages to AUM.

    Let's say you use CCs 0 thru 3 for the commands to AUM. A value of 127 mutes a value of 0 unmutes. Lets say you use program changes 0 thru 3.

    There are a few ways to organize the setup.

    The least number of messages to set up is to have the first four messages be the CCs to mute the channels. Set the trigger to any PC and let the message pass through.

    Then have four messages that unmute a channel. For example CC 0 with value 0. Have that message's trigger be PC 0. Set it to block that message. Do the same for the other channels but set each to the PC that unmutes that channel.

    So, what happens is all channels get muted when a PC comes in and then one channel becomes unmuted.

    You could also set up 16 messages which would let you mute and unmute without redundancy but requires more messages: 4 for each PC.

    Hi there, I am still struggling setting this up.

    With setting up the CCs with a value of 127 mutes and 0 unmutes, should these control the volume in each AUM channel, or do I link these to the solo and mute controls?

    I believe you use them for the mute controls. Make sure to turn off Cycle in AUM, so the value, 127/0, will mute/unmute. (Cycle in AUM means Toggle, so any CC hit will flip the value.) You won't solo anything, just mute all, then unmute the desired channel. Program "any" PC to mute all, then each specific PC to unmute a selected channel.

    Just to explain, the tricky part of this is not getting one channel to play alone. The problem is knowing which channel was playing when a command comes to enable a different channel. You can use a script to remember this state, or do as suggested by muting all then unmuting one.

  • @palakpaneer said:
    This is what my settings look like. I can make channel 1 solo using the CC command, but I can’t make the other channels mute

    You have “consume matching” turned on for the first event. That means the trigger is consumed. Let it pass through.

  • Hi everyone, thanks for the assistance. I finally got there any got it working correctly with my BlueBoard. For anyone interested configuring this at a later date, I have attached my screenshots of midi messenger.

    Cheers



Sign In or Register to comment.