EQ automation and processing delay

[idris]

(Sorry if this has been asked before - I can't find an answer and it's been bugging me for years. Literally.)

When automating EQs (pos other plugins too, but less noticeably), if I have a jump in a parameter right at the start of a clip eg switching in HPF or a change in freq, I invariably get an audible glitch as the plugin seems to sweep to the correct settings. It only takes a tiny fraction of a second but it's enough to be a problem.

My work around is to make sure all parameters are at the correct point a second or so before the start of the appropriate clip. Not a problem, unless I move a clip from one track to another, and forget to double check.

I've got delay compensation switched on (which seems the logical solution) but is there a way to prevent this behavior?

[Frank Kruse]

That's because automation isn't sample accurate in PT10 and older so depending on your session load all automation incl. volume can lag behind. In the old days we even had to move volume graphed de-essing earlier than the actual S to manually compensate for lagging automation.
In 11 it is sample accurate (to enable offline bounce) but some plugins still have a certain reaction time so you still have to do what you're doing. It's way better in 11 and you rarely get these audible sweeps but sometimes you still do.

Having said that, I also wish there was some kind of auto-extend all breakpoints by 10 frames beyond clip margins or something like that which automatically keeps a certain "safety zone" around clips.

Frank.

[idris]

B******! I thought that might be the case. Never mind. Thanks anyway Frank.

[jahtao]

I'm still seeing this problem in PT11.

It happens with the fader and not just plugin automation. Pretty lame.

Can anyone point me to a document that explains if / how it's fixed in PT11. I don't think it is!

Matt : )