There was an issue with the initial state of the plugin, not matching what the GUI was showing.
Also an issue with presets not using their non-normalized values as they should from the start.
The FFTW wisdom file had the wrong signature on Dwarf, leading to it not being loaded and thus not be as performant as it could be.
We detected the problem while investigating something else, and promptly fixed it.
We found that under some specific conditions, a rounding error was causing the plugin to jump internally in its timeline and trigger notes where it shouldn’t.
Very weirdly, under the same exact conditions, the bug happens on ARM but does not happen on regular (intel/amd) 64bit machines.
It is not clearly understood why this happens at all (even by Robin, the author of the plugin).
But in any case we have a workaround now.
This brings abGate to the latest official upstream release.
Nothing changed on the plugin processing code side, the new releases were meant to fix meta-data and other details.
We noticed a few inconsistencies on this meta-data and fixed them (missing units, corrected “brand” name, version information was missing and homepage URL pointed to an empty page)
The small things havebeenreportedupstream.
This is the start of something we are going to try to push from now on, give 1 plugin (or collection) some nice needed attention, around 1 plugin every 2 weeks.
Eventually we will go through the entire collection.
MOD Arpeggiator updated to 1.2-4
Some small fixes related to memory issues and also handling of the MIDI input.
Coming from these set of changes from @BramGiesen, the author of the plugin.
OpenAV ArtyFX plugins have been updated to 2.0-2
Makes it fully up to date with the official desktop version, which has many fixes since we last updated it (couple of years ago).
In the spirit of giving attention to plugins one at a time, we verified these ones to be working well.
Additionally this update brings “Bitta” to stable (we did not have a bitcrusher effect on the stable store yet, and this one works well).
We modified the original plugin a bit here to use real parameter values (1 to 16, in bits) instead of the original 0-1 normalized range.
Please note that if you have ArtyFX installed from the beta plugins you MUST update the plugins first before installing Bitta.
Also worth noting is that installing Filta, Kuiza or Roomy will not automatically install Bitta.
We split the new plugin into a separate bundle so one can have only the wanted plugins installed (but the previous 3 remain together as to not break existing setups).
Oh and we took the chance to give it a little nice visual update.
It follows the original author theme a bit, and now keeps the GUIs in a consistent style.
Calf updated to 60.0-11
No real functional changes besides preparing for (hopefully’s) next week 1.11-RC3 where we will add an option for plugins to bundle with their own documentation.
This is mostly a requirement for Looperlative (as it is a somewhat complex plugin), but Calf is serving as an initial test case.
Basically on a few plugins you will start to see a “See documentation” button near the usual ones, like so:
GxCreamMachine updated to 36.1-12
No real changes here either, we just corrected the thumbnail which was absurdly tiny. It was a workaround for a < v1.10 issue where the thumbnail would take more space than it should.
Since that was corrected, there is no need to keep the old tiny thumbnail anymore.
DIE Fluid Synth updated to 2.2-6
The usage of “HMI Widgets” API was updated to the latest v1.11 release and, related to this, fixed the LED not blinking if an addressing was made while the plugin was already loading an SF2 file.
IR loader cabsim updated to 1.0-17
This update brings many optimizations, and now uses system-wide fftw wisdom files from v1.11 for better performance.
With the performance gains we bumped the IR file limit of 256 samples to 2048 samples (which is roughly 42.7 ms)
For the best possible performance please update to v1.11.1
MOD Pitchshifters updated to 0.4-14
This update makes use of the system-wide fftw files before attempting to load plugin-specific ones.
It acts as a transition between shipping these files with individual plugins vs using system-wide ones.
For now we will allow both, but eventually after everyone is on v1.11.1 or above, we will remove the plugin-specific files.