FabFilter User Forum

Pro Q 3 - Pro Tools - significant automation bugs with Preview and Latch

I am having a lot of issues using pro q 3 in preview/latch mode, and with pro tools automation writing in general, specifically when copying and pasting settings.

There used to be similar, and far less severe, issues in pro q 2, and they were mostly fixed in later updates.

But they seem to be back worse then ever in v3, and make the plugin basically unusable if you are using advanced automation workflows in pro tools.

I can't find any specific rhyme or reason to some of it, but there has been a lot of weirdness with writing automation, and the 2 main issues I have nailed down that have been happening more frequently are:

— basically while working in “preview” mode, certain band numbers will get sticky and just start ignoring preview / latch prime, instead jumping back to whatever their currently written automation playlist values are, as if they were in read mode. it’s super frustrating in practice and workflow killer.

so far it seems totally random when this occurs and what specific bands it happens to. sometimes it affects every parameter for a single band, and sometimes its just frequency or just Q etc.

then, sometimes, when these certain bands start ignoring "previewed" automation changes, they also just start ignoring new automation entirely and won't write or react to any new automation input at all in any mode. they just become permanently sticky, regardless of the automation mode or the transport state.


— secondly, and this bug HAS been super consistent, Pro Q 3 has a strange behavior when utilizing the pro tools function copy and paste settings of the targeted plugin window. (SHIFT+CMD+C and SHIFT+CMD+V). Typically if all parameters are enabled for automation and you are in LATCH PRIME or PREVIEW mode, when you open a plugin and copy and paste settings to it using the above hotkeys, this will cause the targeted plugin to go into an active latch/write or preview state for every single parameter, regardless of what the state of the plugin was before you pasted a setting to it. This is how Pro Q 2 and every other plugin functions.

in pro Q 3, the new behavior when you paste plugin settings to an open instance, is that it ONLY pastes and puts specific parameters in write mode whose values are different from what the current state of the plugin is. For example, if you open an instance of Q3 and quickly copy and paste settings to it while in latch prime or preview without moving the timeline or changing anything, then nothing happens at all, no parameters are pasted or activated into write mode, which is not how these functions are intended to work. Typically this would still cause every parameter to go into preview or latch mode regardless of their values being unchanged.

At first I thought maybe I was having these issues because i imported my presets from V2, but I tested and was able to repro both these bugs in a totally empty session with 1 blank slate new mono instance of Pro Q 3.

There has been some other automation weirdness that I haven’t tracked down yet, maybe its all related, but overall the feeling is that Pro Q 3 is not reliable or ready for prime time when using advanced automation modes in pro tools, something i’ve never experienced this severely with a FF plugin before.

I am a HUGE FF fan, but it’s pretty disappointing this update has made these automation bugs so much worse. Really hope it can be fixed soon be as stable for automation as my other FF plugins. back to pro Q 2 for now.

Anyone who depends on advanced automation modes in pro tools, i would recommend staying clear of this upgrade until these issues are addressed.

Pro Q V3.01
Pro Tools 2018.10
MacOS 10.12.6

Sean

Hi Sean,

Thanks for the extensive report. We're going to investigate and hopefully we can reproduce the issues and fix them. If you find any more information, or a way to consistently reproduce the "sticky" problem, do let us know.

Cheers,

Frederik (FabFilter)
Reply to this topic Go to the forum topic list