Some reports concerning
Fabfilter Pro-Q3 v3.17, VST2.4 and VST3 version, on Windows 10 Pro x64, Resolve 17.4.1.
VST 2.4When automating this plugin from a blank slate, which is the default state, I've had the frequency of bands move as I add bands later down the line. This done click+dragging in an empty area. I have no idea what Pro-Q3 VST2.4 is doing, but Resolve is not taking it well. Just today a band turned in to a low-pass filter after writing a preview-built equalize setting, as if existing automation was applied to a different parameter of the plugin.
Dear devs, it may be worth investigating this.
For now, I will enable and setup bands ahead of time and write a clean pass, careful to NEVER, EVER add bands. That said, Fabfilter always run 24 bands. You just don't see them when they're not used and not made visible with the click-drag-in-empty-area method.
VST3Just labeled Pro-Q3, which was a 10 second waste of time
.
More importantly the analyzer reacts to the audio, but the output of the plugin is not making it out, which is easy to spot with nothing happening the audio on changing any band.