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.

SOLVED: Switch Issue with Blueboard - anyone else?

2»

Comments

  • wimwim

    For routing, what works for me is to route the Blueboard to a separate MIDI Bus for each app. Then route the midi busses to the Drummer apps. Each MIDI Bus will have an enable/disable toggle next to it. Disable the ones you don't want and enable the one you do. No MIDI channel changes needed.

    In the Drummer apps, don't set AUM or the Blueboard as MIDI input. The midi is going to the drummer apps virtual port already.

    Here's the routing matrix I used:

  • pax-eternapax-eterna
    edited April 2023

    Woohoo!!! That works thanks!
    Not sure why there is such an issue with CCs - perhaps it is the way IK have built the BB - in that it sends the CC as an on and off in one press and no option to alter that.

  • espiegel123espiegel123

    @pax-eterna said:
    Woohoo!!! That works thanks!
    Not sure why there is such an issue with CCs - perhaps it is the way IK have built the BB - in that it sends the CC as an on and off in one press and no option to alter that.

    There is no problem with the Blueboard. Notes and CC mode work the same. Your issue is becausenthe LUMBEATS apps treat notes and ccs differently apparently.

  • pax-eternapax-eterna

    @espiegel123 said:

    @pax-eterna said:
    Woohoo!!! That works thanks!
    Not sure why there is such an issue with CCs - perhaps it is the way IK have built the BB - in that it sends the CC as an on and off in one press and no option to alter that.

    There is no problem with the Blueboard. Notes and CC mode work the same. Your issue is becausenthe LUMBEATS apps treat notes and ccs differently apparently.

    ahh, ok fair!

  • pax-eternapax-eterna

    @wim said:
    For routing, what works for me is to route the Blueboard to a separate MIDI Bus for each app. Then route the midi busses to the Drummer apps. Each MIDI Bus will have an enable/disable toggle next to it. Disable the ones you don't want and enable the one you do. No MIDI channel changes needed.

    In the Drummer apps, don't set AUM or the Blueboard as MIDI input. The midi is going to the drummer apps virtual port already.

    Here's the routing matrix I used:

    Thanks I'll have a play with that....I was just now looking at the AUM Manual to see how I can re-map the BB MIDI ch 1 to the other channels I have the other drum apps set to...I sorta kinda recall reading somewhere that it (AUM) could now do re-mapping...but I haven't found it yet.

  • wimwim

    Using midi busses is going to be more effective IMO, but only you can decide what works best for you.
    I could be wrong but I don't believe AUM will remap midi channels for you. I think it only does filtering. mfxStrip is a quick and easy plugin to do channel switching duties.

    Good luck!

  • pax-eternapax-eterna

    Do you have all the MIDI Busses in each session? IE does that routing matrix get saved to all the different sessions using a different drum app version?

  • pax-eternapax-eterna

    @wim said:
    Using midi busses is going to be more effective IMO, but only you can decide what works best for you.
    I could be wrong but I don't believe AUM will remap midi channels for you. I think it only does filtering. mfxStrip is a quick and easy plugin to do channel switching duties.

    Good luck!

    cool thx!

  • pax-eternapax-eterna

    Thanks to WIM and espiegel123 for the help. Much appreicated!

  • wimwim
    edited April 2023

    @pax-eterna said:
    Do you have all the MIDI Busses in each session? IE does that routing matrix get saved to all the different sessions using a different drum app version?

    I'm not sure I fully understand the question.

    The purpose of sending the Blueboard to midi busses is so that they can be disabled for the Lumbeats apps that you have running but don't want to use, and enabled for the one that you do.

    Set up one bus for each Lumbeat app, route the Blueboard to all the busses. Route the busses to the Lumbeats apps. Enable the one you want to control and disable the ones you don't. Yes, they should be in each session. The routing should persist and it should just work. You'll need to re-establish the Blueboard connection to AUM once when you switch off the Blueboard or the iPad.

  • pax-eternapax-eterna

    @wim said:

    @pax-eterna said:
    Do you have all the MIDI Busses in each session? IE does that routing matrix get saved to all the different sessions using a different drum app version?

    I'm not sure I fully understand the question.

    The purpose of sending the Blueboard to midi busses is so that they can be disabled for the Lumbeats apps that you have running but don't want to use, and enabled for the one that you do.

    Set up one bus for each Lumbeat app, route the Blueboard to all the busses. Route the busses to the Lumbeats apps. Enable the one you want to control and disable the ones you don't. Yes, they should be in each session. The routing should persist and it should just work. You'll need to re-establish the Blueboard connection to AUM once when you switch off the Blueboard or the iPad.

    Lovely, thanks!

Sign In or Register to comment.

© Vanilla Keystone Theme 2025