Exciting! Will try out ASAP 
For sure! It’s still on the massive to-do list. The general theme of this update was optimizations (huge push on Josh’s part) and anything not involving UI/UX redesign. MIDI Export and Output are still the two biggest and most frequent requests. Output is really simple from a code standpoint and the scaffolding is already in place, but there are tons of design considerations. Is it on the Mixer page, or is there a MIDI Out engine? The Mixer page (or a new MIDI tab) would be more static, but would let you use a generator and a MIDI output simultaneously. The engine would replace a sound source, but then you can modulate, variate, and perform the output. If it is an engine, the Pitch knob would be pretty clear, and one of the parameters would likely be channel (and another octave offset since the Pitch knob isn’t 128 values), but are the remaining knobs CCs? Which ones? Hard coded or variable? Or instead of it being an engine, it could be a tab on the voice page, but then you have tabs inside of tabs and then… etc.
As you can see, new features have a lot of considerations, and there are still UI/UX things that we want to clean up before we put more in. All that said, Battalion is still our active project and we are very much working on all of this!
11 Likes
Appreciate the response and the insight into how these things are never as simple as they seem 
great work, thanks!
2 Likes
Pumped about the update. Going to try and map this to my tr8. Faders to volume and then knobs to macros. Could be an epic controller for batalllion. Not sure if any of you have tried this.
4 Likes
Hi @trickyflemming is it still planned to bring Battalion to iOS? Cheers 
8 Likes
cheers for all of this . the CPU load in the new beta is drastically improved , like night and day much better . it does seem to audibly glitch a little bit whenever I open the gui but if you just leave it open, prob solved .
thanks for adding the midi preset switching aswell - are there any plans to expand on this? - would be really good to be able to map specific presets to specific notes … .
sorry to moan about anything as I’m really enjoying using it, regardless of any issues - but ,… it only sporadically seems to remember which preset folder I have been working out of when I enter the save preset dialog , more often than not, it jumps out to the main folder, and that can be a bit clunky . have been caning battalion recently though , & finding loads of stuff I like in there , ace work !
1 Like
I posted over at KVR but this seems to be the better place for dev interaction so I’ll post here:
First impressions - awesome work! Everything feels very much “lighter” and snappier. CPU reduction is noticeable and greatly appreciated.
However, I still get the “MIDI Overflow” warning in Reason 12 when randomizing or occasionally changing presets.
There is also a momentary audio drop-out when opening the Battalion GUI as another poster has mentioned.
Not sure if this one is a bug, but: on the PERFORM page, double-clicking the big GLOBAL “Depth” knob results in the knob jumping to 100% whereas I would expect it to jump to 0.
This is all in Reason 12 running 10.13.6
1 Like
Thanks parma. Is the GUI dropout bug new/worse with the update or the same as it was previously? I haven’t had Reason installed for a while but it’d be fun to get running again to see that beautiful cable bounce. What are the specs on your computer, if you don’t mind sharing? (here or through a DM) I run an old system to make sure it’s compatible with slower machines but hadn’t noticed the gui open glitch. I’ll try to replicate both.
for me it has had the momentary audio glitch when opening the GUI since v1 - it doesn’t seem to have got any worse with new beta - i’m using live 12 as the host on a M2 MacBook Pro with 8gb Ram running Sonoma - hope this helps
Audio dropout is the same as the previous version. I just tested it in Live 11 Lite and it drops out there too. The MIDI Overflow warning is (unfortunately) unique to Reason. Randomization in Live 11 takes a few moments to update the Battalion GUI but it doesn’t interrupt the audio flow. The thing that stinks about the Reason MIDI warning is that it stops the transport which is quite annoying. I’m guessing this is more a Reason problem than it is an Unfiltered Audio problem. I’d be interested to see if anybody running the new Reason 13 has had this issue. My machine is out of spec so I can’t test it.
My specs:
I tried Reason at different buffer sizes and it made no difference
That’s a very old spec machine, so may be the cause of your issues. I’m running an M2 Pro Mac Mini and it doesn’t experience any of these drop outs in Logic or Ableton, as far as I have noticed so far.
Will the sequencer be updated to have more than 16 steps?
The manual sequencer currently has 64 steps, but there are interface improvements we would like to add since it becomes a bit unwieldy. The manual sequencer length is on the right under SETTINGS while the auto-sequencer is on the left under GENERATE. The manual and auto sequencers are tied together using the SNAP control. A more detailed description of how their lengths interact is in the manual.
3 Likes
Yes, absolutely! The performance updates were a big part of this. The remaining hurdle is getting clearance for distributing the sample library.
Yes! NI just shipped me the newest Komplete Kontrol board so that I can add full NKS 2.0 support. The think the first page will map to the Performance Page, and then the next pages will map to the mixer and the macros.
We want to add a full pattern system, but we need to design it first. It will be less hacky than switching the entire preset.
I just tested it and it’s still occurring in Reason 13 on my higher-spec processor and on my Windows machine, so it’s likely universal to all Reason users. I need to think of how to deal with this and whether we can cram a fix into the current beta. Battalion has a couple thousand parameters (since each modulation depth target is a separate parameter). We might need to check if the plugin is running inside of Reason, and then do either a more minimal randomization, or a staggered randomization (i.e. one channel per audio buffer or something), but that might have audible side effects.
18 Likes
Yep. I told the UA guys in the past that if any time my issues are just that my machine is too old they can tell me and I’ll live with it.
2 Likes
Note, however, that NI’s Maschine software only sends on a single midi channel (channel 1 if I don’t say anything stupid) to the vst, so if all the parameters are listed in NKS it’s obviously great, but will the midi parameters on the other midi channels also be accessible in NKS? I’m thinking of preset changes in particular!
Thx for your wonderful software !
Thx thx thx 
Honestly I’d love to support machines that old. Our plugins ran quickly on them back then so no reason they should be slow now. Thanks for the info it’s helpful. Good to know it’s the same as before, not worse. Not sure I can improve it much more but I’ll check more thoroughly on my dev machine, which is close to what you posted (see screenshot). I’m trying to get a version of Reason running here to test the midi overflow thing but it’s not being friendly.
Edit: saw Mike’s note about Reason on his newer system so it’s not the age of the machine.
4 Likes
Yes, my bad 
Good (bad?) to hear the Reason thing is universal to Reason and not just my setup. I’ve been tinkering around with music gear/software for the past almost 30 years and I feel tired of always chasing the new thing. I’ve got things more or less the way I like them with my current setup so I’m not in a hurry to upgrade. Eventually something will come out that will push me to get a new system but for now I’m content.
1 Like