Just tried out the Battalion modules and they rock!
But here’s some small things about them that I don’t like:
Tone module:
When changing the routing, it would be nice if the ins and outs (and their labeling) would change with the routing - the way it works now, you still have to change four cables if you want to listen to the new routing, would be much nicer if you didn’ have to change cables at all to switch the order of distortion and filter.
Bypass doesn’t work
Battalion module:
would greatly benefit from exponential knobs for the envelope (hard to dial in precise short values with linear knobs, would be better with more room for those short values) exponential response for the modulation inputs would be better, too.
I don’t like that the bassdrum does not have control over phase position and reset, causes uncontrollable clicks (but this isn’t much of a problem once running it through Tone and/or Output - in the end it usually sounds fine, just wanted to mention that, think everyone should have phase control in their kick generators, but many don’t)
What is really amazing though, is how all modules start to work perfectly together when running everything through the Output module - That OTT but clear and punchy type of sound together with some clipping in the end really turns it into one amazing sounding machine. CPU is a bit high on that one, but the sound of everything together seems totally worth it.
Damn, I’m just finishing editing a tutorial on the Battle FX plugin, and this drops in the library too!
I already have the Battalion VST but I’m going to have to dig out the credit card, because it’s way more useful to me to have these as native VCV modules. I’m probably more interested in the effects than the drum sounds, Shatter Delay is great for ambient guitar. I’m guessing it’s built on Instant Delay because it sounds very similar, but adds some really useful features like the tilt filter and sample rate control. I discovered you can make a really nice octave delay by modulating sample rate on the Battle FX plugin with alternating 5v and 10v signals, again this is going to be easier with the native version.
Once we get polyphony as well, it’s going to be absolute chaos for extreme sound design.
@trickyflemming When you’re back, major issue using modules in VCV VST3 or CLAP. Can’t re-open instances of plugin without plugin or DAW crashing. This happened in Maschine 2 (VST3) and Bitwig (CLAP), loaded Drum Synth module, saved DAW session. Maschine crashes on reloading the project or NKSF preset, and the VCV plugin crashes in Bitwig when loading the Bitwig preset with the Drum Synth module. Replicated with Shatter Delay module as well.
But I’m getting a crash in Ableton 12 (12.4.1, MacOS 14.4, MBP-14 M3) every time I use them. I can open a blank VCV patch and populate it with Battalion modules no problem. But when I go to reopen any saved Set in Ableton that has those modules it instantly crashes. Hopefully this gets sorted, because I’ve already made dozens of patches with these modules. They sound amazing!
Hola Michael & co
I can’t seem to get the battalion collection to load on linux mint… it’s stuck in a loop where it says “all downloaded, now restart vcv” but then nothing, and soon the red dot appears again and it tries to download/install …again!
I dont know s&%t about coding so i don’t know where to start troubleshootin
thanx + bestest,
PD
Most modules have a link in their right click module you can use to contact the developer and report the issue with their module. If it’s an open source one, you can usually open an issue on their repository.
So far these modules have been a blast, but I’m surprised the battalion sampler is missing, hope that will be added since it definitely is a big part of battalion and it not being there makes the bundle incomplete… still gonna crush the heck out of the drum synth module with the effects while I wait for an update!
Sorry for the delayed response! I was out of town at a high school reunion. The crash in loading a saved plugin project is my major priority for tomorrow (@auxmux@Apex@Schabbes) . I have no clue why it’s loading fine in Standalone, but loaded projects are crashing the plugin. I have an email thread that VCV Support opened with me, so I will try my best to submit new builds on Tuesday.
@PDfinlandia which version of Linux Mint? I’ve seen that behavior before with other plugins. I’ll ask VCV Support if that’s something on their end or mine.
@shawnbortree19 I still have a lot of design things to figure out for the sampler, but it’s definitely in the cards.
I just hope you’ll include all the factory samples but the biggest problem would be managing the download, like maybe there could be a right click option to download sample content in case you need it but have it empty in case you only need your existing samples and don’t need the factory library. If Befaco can give us the Iroi free for existing license owners of Oneiroi, you can update the battalion bundle with a new module and complete the set later. We’ll be fine while we wait… just gotta keep my experiments from distorting too much!
Yes, the sampler will be part of the same bundle for no extra charge once it’s added.
This, unfortunately, can’t be done since the samples are owned by Native Instruments. What I could do is check if you already have the Battalion Sample Library installed and add it as a path.
Oh, ok that explains something… I definitely will have the plugin installed soon on desktop since I only have the iOS version so far, if I install say the windows version would the samples be stored somewhere I can use them in external samplers too and as a wav? Cause it could be they might just be hidden as a compressed binary or embedded in something
Yep! They are in %APPDATA%\UnfilteredAudio\Sample Library
That folder will be shared between other plugins that we release that have sample access. We’ll release an update to Silo so that you can save frozen buffers to that folder.
Certainly! The screen on each module was calling this in the screen’s constructor (itself called by the module’s widget constructor):
font = APP->window->loadFont(asset::system("res/fonts/ShareTechMono-Regular.ttf"));
Now, there’s instead a simple function called in the draw() functions before anything that uses the font:
I’m not entirely sure why initializing the font in the module constructor was causing the crash in a DAW loading situation (as compared to a clean init), but that was the line where my debugger halted. I wish I had a bit more insight to provide.
