Hello, can I just ask again if there is going to be an additional Black Friday sale on this, or whether the already discounted price is ‘the price’ for the rest of the month?
The iOS version is on sale until 2026 (no further drops). I’m not publicly allowed to comment on Plugin Alliance’s sale plans.
OK, thanks. I have the iOS version already and love it, so am going to buy the Mac version too. I’ll hang around until next week to see if there is a further sale, and if not I’ll just buy anyway!
When I first looked at the App Store when becoming aware of the app, I saw the $40 price tag and said ‘you’re crazy!’
Then it went on sale for $30 and I said ‘not too crazy though…’ and I bought it.
Well, I am now the proud owner of Mac Battalion, which joins the iOS version I already own. I’m massively looking forward to the patterns functionality when that starts hitting beta, as it will be the missing link in what is already an incredible drum machine.
This is working for me now! Thanks very much!
Battalion is now far more expressive… can play it from e-drums and it’s so much more fun now!
If possible at some point please, could we have Battalion remember which drum it was last on.
Eg, you’re editing drum 3. You close the DAW. Reload the project. Battalion is still showing drum 3.
This would be a time saver cos at the moment I have to select all 8 to the right drum when I open my projects!
One more feature request please ![]()
This one I want more than any of the other ones:
Select a kit remotely via Program Change message
Maybe we can have a folder ‘MIDI Presets’. Can save up to 128 kits in there. Then sending a PC message to Battalion selects the relevant kit?
Cheers for all the hard work!
Just bought this, very excited to sit down and play with it!
Guess this is a first fix, but, would it be possible without extreme amounts of work to have that selectable per instance (or even better, per channel) instead? I can see per-instance select of sequencer-affecting-incoming-notes to be good enough (even though not optimal), but not being able to have two battalions, one set for sequencer and one for midi response for say pitched midi playing, is a bit of a bummer. And, having to change a global setting means it messes up project load if I have one project using internal sequencer and another using midi notes for pitch/velocity. Then I have to remember what it should be set to for each project loaded.
Is there a midi mapping option on the IOS standalone version? I usually just use it with Aum which I can then see exposed parameters.
Hey everyone! Been a minute… haha
Loving how active the thread is… seems like Battalion is really clicking with people big time ![]()
Figured I’d share a bit out of a larger project I’m preparing for an installation I’m doing in a few days. There will be a couple other artists all exploring some element of experimental/contemporary sound. For my project I created a version of my main rig designed to interface with an external UI running on an iPad. I might post some videos of the full rig once everything is set up.
Cool thing about the whole project is all the sound apart from a few tiny home-made fm modules (not present in the video) is coming from Battalion and being processed by exclusively by UA plugins, specifically SpecOps and SandmanPro.
I’ll share a longer version in case anyone is interested
I’m still surprised at what Battalion can do and I’ve been using it every single day for months now. MaxMsp ft. Battalion
I was going to file ”velocity from external midi not working at all” as a bug, but after reading this I realized to set on ”MIDI Triggers Ignore Sequencer Data”, now it works!
So feedback: one wouldn’t expect a drum machine to require such a mystical setting (at least not with that name) to be switched on before external velocities do anything.
Another feedback: all text and some of the clustered icons are really small and crammed together on a 10.5” (ancient 2017) iPad pro, I assume also on the newer, similarly sized 11” models?
For example the tip of my index finger is wide enough to overlap both the < > arrows and half of the eraser button, horizontally, on the Voice presets menu. So it is quite difficult to hit the > arrow succesfully ![]()
Meanwhile, in full screen there is about 1 centimeter of un-used vertical black empty space at both the top and bottom. And maybe some of the horizontal margins between things could be decreased in size, although of course at the cost of clarity between sections.
The crammed UI is initially what turned me away from the app, but after forcing myself to use it a bit and check out some of the presets, I’m liking the sounds so much I’m tolerating the UI… Using a pencil helps a bit.
Thanks for the support! I appreciate your comment. Maybe we should make it opposite by default. You might have missed it but there’s kind of a history to this and I’ll tell it in a stupid, funny way:
Originally, long ago, external midi was pure and ignored all sequencer data. Two entirely separate systems existed and the world was simple. External was external and internal was internal. There was peace upon the land.
Then out in the distance a voice was heard: “The sequencer is so fun, shouldn’t we be able to use it with external notes? Why should they be blocked from the dance of the sequenced row data?” The crowd heard this question and agreed. Shouts of “obvious! Of course! It should have always been! For shame!” were cast in the direction of the makers.
The makers heard these calls and considered what to do. Edge cases and complications were everywhere. It was for no small reason that they had avoided doing it in the first place.
But the cries of the crowd were undeniable and unrelenting. Consensus had been reached. Add it they decided they must, and add it they did.
And when the happy day came, and when they released it to the crowd, after short rounds of praise, the makers looked on to see the crowd quickly divide into two, and then each two split into two more, and two more, and on and on. Each fraction screamed a different complaint. “Most of this is right, except this part which is obviously wrong! Completely unusable! Counterintuitive, backwards, half-thought-out trash! You should be ashamed!”
The makers heard a cacophony of “sequencer first!” and “always external first!” “except velocity- no variation- no pitch!” and “give me the choice per voice per note per session with probability and automation and a button on the performance page to override it all on command!” and “guess my intent! You must! Isn’t it obvious which I want, where, and when?!”
The makers, both sad, decided to call it a day, so returned home via a short drive on the parkway. They were hot in the car but didn’t know whether that meant they should turn up the AC or turn down the AC, so they just left it alone until they finally reached their home and parked in the driveway.
The world seemed completely counter-intuitive. Maybe it was they themselves that were backwards.
–
(Seriously though, this community is amazing and I really appreciate you all helping us to figure out the best way or least-worst way Battalion should be designed! We’re trying to add some options and sort it out, generally, related to pitch, velocity, and probability. We think we have a decent solution. Thanks all around. )
I thought this would be obvious but it isn’t (for me, anyway!): how do I sync the UA Battalion sequencer to start and stop with Ableton Live’s transport?
![]()
Hilarious mate! Love it!
I feel like this a metaphor for life on the deepest level ![]()
if not already posted, thought this might be of interest…battalion and waymaker
This video is a pretty good advertisement for Waymaker, I have to say
Interesting how the Popular People’s Front for Battalion Patterns has been marginalized…
(Not to be confused with the Pattern Liberation Army, splitters)
Where’s the patterns ![]()
Ahem!