The dev is adding features like crazy. People wanted patterns and less than a week later we had patterns.
The sound engines in Battalion are much better, however. I’d still love patterns in Battalion but I’ve resigned myself to the possibility that it just might not happen.
Thanks, y’all. And yes, that reminds me that 1.2.0 isn’t “officially” released (although the beta version hasn’t had any further major bug reports, so I’m calling it stable and submitting it).
Please don’t flag people to protect our feelings. Patterns have been slow. The code is pretty much finished, but we need to sit down and finish the UI. We haven’t been in that creative headspace yet, and we’re focused 100% on getting our new license server off the ground. We’ve had a few completed plugins that were rejected by PA, some of which have been sitting for a very long time. However, all of the NI news has us rattled, especially because we found out about it as a rumor on the NAMM floor. After we get these few defensive lifeboats launched, we will be back on it.
Thanks for the link, unfortunately, I’m the weirdo on pro tools and there’s no AAX version (that I could see). No plans to buy the wrappers or a second daw at the moment.
And for clarity, my main reason for not using battalion lately is cos I bought a bunch of eurorack modules and disappeared down a really deep rabbit hole…
Really appreciate your response. I only posted because I’ve been considering buying it this week but was just concerned after following the progress in this thread since release. I’ll buy it with the knowledge that patterns haven’t been scrapped.
Very glad to hear you guys are taking proactive steps with the situation. If my business depended on PA, I don’t think the “Trust us, this isn’t going to affect anything” would do much to make me feel confident. I also find it interesting they get to “nope” plugins. I clearly misunderstood how I thought the business relationship worked. I assumed they were a distribution hub more than a senior partner who got veto decisions.
Regardless, I look forward to seeing whatever else you guys make and I’m very much looking forward to seeing v12 when you think it’s ready to go.
Thanks for being such a good communicator here. It makes me want to engage with the plugins a lot more. It’s nice to know the folks behind them are active, engaged and working hard to keep them moving forward.
Did I miss it or is Midi CC’ing track volume an pan from a controller not possible at the moment (stand alone on iPad). Would love to use the old Novation Launch Control S for Battalion. Thanks!
1.5.0 is in active development. Patterns are far along. We just implemented a new preset browser that adds tagging, favorites, filters, ratings, etc. that will make its way to the other iOS-compatible plugins (Bass Mint on forward). MIDI Out is in this update as well.
I had to double back to 1.2.0 last week and just posted a new beta for iOS Testflight. We had a bunch of reports spring up all at once that the latest Logic Pro release broke the multi-channel AUv3, but that’s been fixed.
anything you can share on the new license server and if you’ll be continuing with PIA? (I get that any change to the latter will likely have to wait for a “proper” release but, in case I missed that…)
We’re still on Plugin Alliance, but the new license server is close to ready. Our private beta testers are currently testing three of the new plugins entirely through the new license server system, and we haven’t heard of any issues yet.
I may have asked this before, if so I apologize , is there a way to midi learn parameters in the iOS version? I know when using it with Aum it shows all parameters but not sure in standalone mode or when using in other apps.
The iPhone version is now out with 1.2.0 and should be included with the iPad purchase. I’ve seen instances where it takes a day or so for the new platform to roll out to existing purchasers. Please know that we do not want to charge you twice for the iOS version. I’ve been getting a lot of emails this morning regarding this.
Standalone does not currently have this feature, and the AUv3 version is more the “true” version that we’ve designed for. I’ve had a few requests to add MIDI Mapping to Standalone. I like the idea, but it’s currently lower priority than patterns, MIDI Out, etc.