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.

Using modstep to sequence midi in BM3

I posted this on the BM3 forum but I'm not sure how many of you are on it, so apologies if you're reading this twice. So...

I'm trying to use modstep for all my sequencing, and I see that BM3 has options in the mixer tab for having separate midi channels per pad. So in theory, shouldn't I be able to create tracks in modstep and route each one to different midi channels in BM3? This is what I tried:

Bank A has 4 pads, each pad holds a different sampler instrument that I made. I created 4 tracks in modstep, routed to channels 1-4. In BM3, I set modstep as a midi source, then in the mixer, I chose the 'show pads' option, which allows me to designate which channels each pad should listen to.

However, no matter what I do (and I've tried a bunch of configurations), BM will take any midi input and trigger notes in pad 2. I'm trying to trigger notes in pad 4, which I set to midi channel 4 in both apps, but nope, pad 2 is the only one playing. Is this a bug, or am I doing something incorrectly? I've tried a similar approach using AUM to route midi from modstep to BM3, but it's the same thing. In fact, BM3 doesn't even see AUM as a source.

Comments

  • At the moment, it seems there is a problem with midi input in BM3. I'm not an expert but this is what I've understood from other people here.

    Indeed I would love to sequence BM3 with modstep me too.

    But each time I swap pad or bank, the sending notes from modstep will go to this pad or bank (whatever the channel I've chose in the midi setting of the pad).

    Let's hope for a fix / update soon.

  • edited July 2017

    @8BitSamurai said:
    I posted this on the BM3 forum but I'm not sure how many of you are on it, so apologies if you're reading this twice. So...

    I'm trying to use modstep for all my sequencing, and I see that BM3 has options in the mixer tab for having separate midi channels per pad. So in theory, shouldn't I be able to create tracks in modstep and route each one to different midi channels in BM3? This is what I tried:

    Bank A has 4 pads, each pad holds a different sampler instrument that I made. I created 4 tracks in modstep, routed to channels 1-4. In BM3, I set modstep as a midi source, then in the mixer, I chose the 'show pads' option, which allows me to designate which channels each pad should listen to.

    However, no matter what I do (and I've tried a bunch of configurations), BM will take any midi input and trigger notes in pad 2. I'm trying to trigger notes in pad 4, which I set to midi channel 4 in both apps, but nope, pad 2 is the only one playing. Is this a bug, or am I doing something incorrectly? I've tried a similar approach using AUM to route midi from modstep to BM3, but it's the same thing. In fact, BM3 doesn't even see AUM as a source.

    Bm3's midi input is currently bugged. It basically cannot listen to multiple channels of midi irrespective of the midi settings you set. So till it gets fixed nothing can sequence it the way you want. Not even hardware sequencers like the beatstep pro or circuit. You aren't at fault. Bm3 midi is just broken currently.

    As @kevkevkevz stated it seems to default to sending all midi to the currently selected pad/bank and ignore all other midi settings. I think it's a bug with regards to their focus actions inplementation. It's wonderful when you have a single midi controller but the intended behaviour is that your per bank/pad midi settings is supposed to override it. Currently it doesn't. It's working as intended in the beta builds some of the testers have so I'm pretty confident it will get sorted on a patch.

Sign In or Register to comment.