Pops from ADC question/issue

[Frank Kruse]

Originally Posted by dr sound

NAMM Update: FabFilter only had a local rep and not someone from the company at the show today. I discussed the issue with him and he promised me to let FabFilter know about the issue.

Thanks for that!

I had contacted FF earlier and they know about it. They fully understand the danger and they said they would take out any latency changing parameters from automation functionality.

What's confusing with FF plugins (not only the De-Esser) is that you can automate just about every setting including global GUi settings like the analyzer type and the side chain audition so when you listen to your de-esser side-chain to adjust your settings the plugin will write that to an automation lane. This often goes unnoticed when you have PT set to "plugins default to all parameters enabled".

So every time you open an instance of a FF plugin you have to go in and manually remove any things that are simply helpers too set the plugin from being automated.

I haven't seen the plugin go into write unintentionally but I have often automated parameters like audition trigger which doesn't make sense at all.

I have asked them to remove any parameters like that from the automation functionality. IMO, it's pointless to automate the audition trigger or the resolution of the analyzer in the pro-Q2.

In the de-esser the look-ahead value, on/off, oversampling and wide and split band setting will change the latency and can cause your entire session to click and pop. Similar settings exist in their other plugins. Mainly the EQ type setting and oversampling settings.

I think the pro-MB has at least 10 or more parameters that are totally pointless for automation (analyzer settings, phase type, oversampling, lookahead, pre/post/sc analyzer, analyzer resolution, speed, tilt etc. etc. etc.)

The annoyance is that you have find and de-select them every time you put one in your project.

Frank.

[Top Jimmy]

Originally Posted by Frank Kruse

FabFilter have responded saying that they will look into making latency changing parameters non-automate-able in the future.

Frank.

Having beta tested for some other devs, this issue was discovered in beta and the solution was exactly as fabfilter has decided. Controls that change the delay compensation time like over sampling or look ahead were removed from the automatable parameters.

[Brandonx1]

Or plug ins could have a maximum delay option where you can automate everything and the plug in is always in it's max delay setting.

[Top Jimmy]

Originally Posted by Brandonx1

Or plug ins could have a maximum delay option where you can automate everything and the plug in is always in it's max delay setting.

Which would require a developer doing a lot of work to guarantee seamless transitioning for parameters that have absolutely no useful need for being automatable.

[Frank Kruse]

Originally Posted by Top Jimmy

Which would require a developer doing a lot of work to guarantee seamless transitioning for parameters that have absolutely no useful need for being automatable.

To be fair there are a ton of de-essers out there that allow you to switch and automate between split and wide-band mode without changing the latency and causing clicks and pops in the entire session.

This isn't possible with the PRO-DS.

And the Nugen ISL has a lookahead setting that doesn't change the overall latency.

Just to name a few examples.

hm...

[Mischdepp]

Thanks Frank (:

I experienced this issue with Izotope's Alloy 2 some time ago while mixing a documentary with alloy on nearly all the tracks in the session...
I also found out that the problem was related to the plug-in but never checked the delay comp values. Izo support was no big help in this case - the said it was due to the complexity of the plug-in...
So I ended up with a "save-as" and started from scratch with the 7 band EQ and the dyn3 de-esser.

Just re-opened the original session and took a look at the delay times - same issue - clicks are related to the delay changes...
With Alloy the values change even if you just toggle bypass on/off on the Plug in modules (EQ/DeEsser etc).

So it's not a FabFilter issue but a general one

Matthias