Ugh, that is a hell of a week, for sure. Our school cannot even keep the kids there without a water main break (2 early dismissals this week, two days off next week. GO. TO. SCHOOL!! 
).
Good luck with the hunt and, as always, thank you for your responsiveness!
Yes, wasn’t complaining just noting it’s a wider problem.
Am able to use the AUM preset picker in the meantime, or standalone. Super fun for generating samples to go into my Tonverk.
Nope! I didn’t think you were complaining or anything. I appreciate the reports. I was more noting why I haven’t responded in a few days.
Samhain!
Any news on when there’ll be patterns for the sequencer?
Hello mate!
I’m slowly experimenting with this.
The ‘Slices’ parameter, this would be very handy if instead of showing the %, it could show the number of slices it’s dividing into.
What is the maximum number of slices? Eg if you turn ‘Slices’ all the way to 100%?
I’m going to record myself saying the numbers 1 to 128, in a chain, and try and make things happen with Battalion!
EDIT: Also the Algo knob, would be good if it divided neatly into the 5 Algos for clarity.
Is the price for this around Black Friday likely to go below the current £61? I already bought the iPad version a few months ago, so I’d like to go as low as possible for the Mac one (sorry, UA!).
Okay, I got 32 slices working well!
I used the same chain of 128 kicks.
I set slices to 100%. Chance to 0%. Window to 0%. Algo irrelevant.
I send MIDI CC to the Start parameter, the CC is sent as 0, 4, 8, 12, 16, and so on.
Then it seems to play every 4th slice correctly, allowing the 32 slices as you said!
Would be fantastic if we could have the full 128 available one day, correctly responding to MIDI CC!
Anyway, Battalion is fantastic, thank you so much!
Anyone know how to get Battalion to respond to velocity difference over MIDI?
Not sure how to get it working. Assigning stuff via the ‘Velocity’ modulator I think only affects internally sequenced notes.
This is fixed in the latest beta. We’ve added a global option to disable having the external notes follow sequencer data. We will add further tweaks in the next beta.
Thanks so much!
Battalion is the dog’s bollocks!
Mate, please forgive me for being a greedy bastard and asking for the moon-on-a-stick… I have to ask though, Battalion is so good and I want more.
That said… would it be possible one day, to have the modulation buttons available to the DAW for mapping?
And if so, then incoming CC’s which control the onscreen knob, automatically control the knob which appears when the modulation button is pink?
I’m dreaming of a mouse-less workflow, you press a button remotely, turn a knob, and have control to set modulations.
Would you like to see a little video of my Battalion integration?
We have something like this already. It might not be exactly what you describe, but all modulation depth controls are available as DAW automation parameters. If you move the modulation depth of a control, you should see it with your DAW’s “last touched” automation.
Sure, and it’s stunning to have all the parameters available like that!
The thing is, I don’t ever look at or modify (or even create) the actual automation on the DAW (I’m sequencing on a Hapax).
So, right now, if I understand correctly, each onscreen knob actually has many hidden parameters (representing modulation amounts).
Would be amazing if a single incoming CC could be directed to a specific hidden parameter, by pressing the relevant modulation button and sending the CC (so eg MIDI CC74 always controls the Cutoff knob, and if a modulation button is pressed, CC74 will then set the amount of modulation to the Cutoff instead).
The reason is, Ableton will only let you access 128 parameters per instance. I’m already running 8 Battalions, one for each drum, to get round it.
So it wouldn’t be possible to add so many different CC’s! It’s definitely possible to script my TouchOSC layout to send different OSC messages, but Ableton really doesn’t handle OSC well when sound is playing! It gives a lot of clicks and buzzes etc. It’s fine for setting parameters when not jamming live, but otherwise it has to be MIDI.
Which beta please? Not working in 1.2.0 I think. I’ll check again later today!
My bad, it’s the iOS 1.2.0 beta. I’ll post new Windows/Mac builds today or tomorrow. We’re adding some additional tweaks to the external MIDI work.
Sorry for the delay. The 1.2.0 beta 2 is now available, with the options toggle to change the behavior of external triggers. More tweaks will be available soon:
@trickyflemming would it be possible to get a command, or an option, to make the Global Depth control reset/lock to 0% instead of it just being 100%?
I don’t know what has changed with this latest beta but I’m very happy to report that I no longer get the “MIDI Overflow” warning in Reason when randomizing or switching presets! Really stoked about this. Thanks for the work UA guys!
As happy as I am to hear it, it probably means some other OS or DAW is now broken, so we celebrate today, but remain worried. 
Thanks for letting us know- we really appreciate it.
True! For now though, me and the four other people that use Reason will celebrate 