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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Xequence to BM3 - best setup?
What’s the best setup for sequencing a bank of drums in BM3 using the Xequence drum pads. Direct or via AB3? Can someone detail the setup please?
Ta!
(CC @SevenSystems)
Comments
Why would you want to sequence an already great sequencer?
I find midi easier to work with in Xequence.
Hrmmm. Drums are super simple in BM3. I fear you may be over complicating your workflow if all you want to do is sequence drums.
The step sequencer in BM3 is fluid and fast to use. Not to mention the awesome pads for live input. I’d suggest getting comfortable with BM3 so you can get into flow faster and not mess with setup.
Xequence is great for sequencing AU and IAA instruments in AB3 and AUM or even Gadget or external gear. It just might be overkill in BM3 or Cubasis or Auria, even though it can be done.
Just something to think about since BM3 was designed for sequencing. Sequencing BM3 with Xequence is like putting your Ferrari in a car transporter to drive it. Just drive the Ferrari...but maybe that’s just me.
Been looking at this same issue myself @gusgranite. My conclusion is pretty much what @echoopera said, it’s more trouble than it’s worth when BM3 is pretty great already once you get the hang of it
Check out the nice how tos from Intua

Why would you use the piano roll to sequence drums in BM3, use the step editor (drum sequencer) they work the same in near enough every app ever created for drum sequencing.
That’s what I’m saying man.

I don’t think anyone is discounting Xequence and how nice it is, just that it might be easier and faster to just use BM3 and the step sequencer to lay down drum tracks.
I’d watch the intua videos and ones from Dean. They do a great job of covering workflow in BM3.
Good ol Doug

The three videos i posted should ease any co fusion or friction you might hav towards the built in sequencer in BM3.
“Know what you know by knowing what you don’t know...and you will grow...”
Can i recomend you try any drum editor, they all work exactly the same, if Xequencer doesnt sequence drums the exact same way, it is doing it a very strange way.
I know what you’re saying but it’s not just drums. I’m using Xequence for all my midi tracks in the session. Then I’m using the PolyHymnia module to change things up in parts. I’m also recording all of the CC controller data in Xequence. Importing Rozeta midi snippets, etc.
Currently all of these multiple midi tracks and modulation editing is easier and more stable in Xequence.
I’m using BM3 as a sampler, recorder, and then to mix and arranging the audio stems.
Yep i get it. So can you tell him what to do?
Yep, I appreciate the feedback and maybe I am overworking it. But as @tja says, I am starting to enjoy using Xequence as my midi base for everything.
It can be done. BM3 doesn’t accept AB3 midi, so send direct to it from Xequence whether you put them in AB3 or not or it won’t work. If you do try BM3 in Audiobus for convenience of app switching, be sure to start up BM3 before AB3 or it won’t load.
Set the bank in BM3 to single channel midi mode, input port to all. Then set up a drum pads template in Xequence with C0 as the bottom note and each pad one note higher from there. Once you save the template you don’t need to do that last step again.
It worked in my quick test, but I only set up one pad of the Xequence drum template. If you haven’t been talked out of it yet by the other posters, I could try later to do a full setup.
I also prefer Xequence’s piano roll and overall timeline tools. It’s also useful at times to think of BM3 as a sound module rather than a composition DAW. (Heresy, I know. Hope I don’t get burned at the stake
)
@wim right. I’ve done midi in to BM3 before so was confused but I think hosting Xequence in AB3 was getting in the way and is not necessary in this instance.
BM3 is still my DAW of choice, yo! It’s only going to get better and better. The sampler is the best and the audio is going to get a load of FX layered on etc. I think Xequence is the best app on iOS for midi editing however.
Will report back.
@gusgranite I retract what I said. I’ve tried again and got it stable this time. What I was doing wrong I don’t know lol
I made a bunch of assumptions in that last post in order to get it out quickly. What I described is how I would go about it trying to set up a standard “drum” bank starting at note 0, like the packs from the BM3 store. If you were playing a melodic instrument in BM3, that would be different.
If you get stuck give a shout. I’m kinda interested in exploring this meself.
I’ve set up both BM3 and RC in AB3 now. Playing two AU synths and a drum kit. All working fine now. So yeah, go for it. Here’s some pics that may help:




Gah! It’s that sneaky ‘Route all midi to selected pad’ option in BM3 settings that always trips me up... I always forget to turn it off.
Working great now!
Thanks all
Think I’m getting to like this set up
@Fruitbat1919 @wim
Then you can load up Rozeta in AUM (or probably AB3 also) and point it at Xequence (set it to midi thru) and you can now sequence BM3 with Rozeta again, capture the midi variations in Xequence for tweaking and switch out BM3 pad sounds as you go.
Not a bad setup considering BM3 cannot handle Rozeta AU midi in its current version.
@SevenSystems have you thought about Xequence hosting AU midi and AU midi FX plugins? It would still keep it midi only according to the current Xequence ethos but it would cut out having to sync another host just to load the AU midi plugin.
Yep, I like doing this with or without BM3, using AB3 mostly.
Always interesting to see what kind of setups people are using, and even more interestingly, without too many major issues
maybe that's thanks to the office cat constantly throwing himself on the keyboard during bugfixing 
I haven't looked into that, no... to be honest, I still consider releasing Xequence for other platforms (Android, Windows, etc.), so every bit of code that is platform-specific (AU is of course one!) could be a bit of a waste... but I do of course acknowledge it would be useful. I also have AUv3 instrument / effect hosting on the "potential roadmap for the distant future", including a full mixer and audio tracks... or maybe just the audio tracks (with AB3 and IAA connectivity) -- that's the only real "achilles heel" right now, as currently if you want to record or work with longer vocal / real world recordings, you have to resort to triggering samples or use BM2 synced via MIDI. Not optimal. Oh well, so many options
@Fruitbat1919 why don't you choose a 4x4 layout in Xequence, the same as in BM3? Easier to remember if all pads are in the same spot
Yep that makes sense, thanks
@SevenSystems keeping it cross platform makes sense and I have been following your musings on potential audio hijinks with interest. I just hadn’t seen any requests to capture AU midi data in Xequence and that seems a better immediate fit in the current app. It’s all very new though so will happily wait and see.
Nice work! 👍
Yep nice setup. Having fun with this one as long as I remember to open BM3 first lol