When was sample accurate automation introduced?

[Sonopolis]

Hi all,

the title says it. When was sample accurate automation introduced in Pro Tools? I mean the fact that automation jumps on the edge of clips could no longer introduce audible pops. This was an issue with PT for a long time but it's gone for some versions now. However im dealing with a session now that was made on an old system and I'm confronted with this issue again.

[Frank Kruse]

I don't think it has ever been 100% sample accurate except when doing offline bounces. (I think it was introduced when offline bounce came to PT)
If at all I'd say only volume and pan but clearly not for plugins.
Altiverb for example sometimes need several seconds to load a huge IR so if you place a setting change on a scene edge it won't recall sample accurately. This is even true for some EQ plugins in massive sessions.
I still write automation changes with at least a second of "handle" before each clip to avoid odd pops and ramps.

Frank.

[unkJE]

Pro Tools 11
https://www.pro-tools-expert.com/hom...ost-users.html
4.
Sample accurate Automation - For post users this is so helpful. Before I could never trust Pro Tools to manage automation changes at exactly the right point, but now that even automation point is time stamped just like the audio files we can be confident that it will do the right thing at the right time.



However, in Pro Tools 12.5.1
https://avid.secure.force.com/pkb/ar...-Release-Notes
Bug Fixes
• Fixed an unexpected volume change that intermittently occurred when using non-HDX playback engines and starting playback from directly on top of a mute automation event



To be sure to be sure – in Pro Tools 12.5.2
https://avid.secure.force.com/pkb/ar...-Release-Notes
Bug Fixes
HDX
• Fixed an intermittent issue affecting HDX systems which would cause a crackling sound after making changes to the HDX mixer

[Frank Kruse]

Originally Posted by unkJE

Pro Tools 11
https://www.pro-tools-expert.com/hom...ost-users.html
4.
Sample accurate Automation - For post users this is so helpful. Before I could never trust Pro Tools to manage automation changes at exactly the right point, but now that even automation point is time stamped just like the audio files we can be confident that it will do the right thing at the right time.



However, in Pro Tools 12.5.1
https://avid.secure.force.com/pkb/ar...-Release-Notes
Bug Fixes
• Fixed an unexpected volume change that intermittently occurred when using non-HDX playback engines and starting playback from directly on top of a mute automation event



To be sure to be sure – in Pro Tools 12.5.2
https://avid.secure.force.com/pkb/ar...-Release-Notes
Bug Fixes
HDX
• Fixed an intermittent issue affecting HDX systems which would cause a crackling sound after making changes to the HDX mixer

Hm, the automation itself might be sample accurate but some plugins themselves have reaction times. I can hear this in every large post-session I work in in recent PT versions (and every one before). I still avoid abrupt automation changes on clip boundaries just like before PT11. It depends on session size, CPU speed etc.

[unkJE]

Originally Posted by Sonopolis

...audible pops ... I'm confronted with this issue again.

“Even-more-sure” protection from pops/clicks/noise-blasts:
If you have a VST host like BlueCat Audio’s PatchWork, insert the free “Ice9” VST on the Master Track
https://freevstplugins.net/cerberus-...ice9-automute/

“Ice9 Automute’s soft-muting function will begin to attenuate the gain before a single sample over the threshold has passed. Instantaneous radical attenuation will occur if the threshold is exceeded by a severe and potentially dangerous amount.
This update features an increased threshold range for matching levels commonly used with digital/analog hybrid signal chains. It also fixes an important functional issue for Windows users, and introduces internal improvements for Mac users.
Changes in Ice9 Automute v1.1
Increased threshold range to -12dB, adjustable in 1dB increments.
Windows: auto reset was not working on some systems. Fixed.
OS X: Recompiled with Apple LLVM C++ compiler (brings stability and performance improvements).”

Downloads - scroll down to orange/red type:
Ice9_1.1.0_Windows ( 11.6 MB )
Ice9_1.1.1_OSX_Installer ( 13.2 MB )
Close the ensuing pop-up and the download begins

[Rich Breen]

Originally Posted by Sonopolis

...automation jumps on the edge of clips could no longer introduce audible pops....

Unless I'm misunderstanding you, this has little to do with the "sample accuracy" of automation. *Any* instantaneous level change during program will cause a pop - this is physics, not pro tools - it will be worse with material with significant low end, but really, instantaneous level changes should be avoided. That said, there is a "steep breakpoint smoothing time" preference in the "mixing" tab that should address such issues - not sure when it was added but it was perhaps 2 or 3 versions ago.

[Sonopolis]

Originally Posted by Rich Breen

Unless I'm misunderstanding you, this has little to do with the "sample accuracy" of automation. *Any* instantaneous level change during program will cause a pop - this is physics, not pro tools - it will be worse with material with significant low end, but really, instantaneous level changes should be avoided. That said, there is a "steep breakpoint smoothing time" preference in the "mixing" tab that should address such issues - not sure when it was added but it was perhaps 2 or 3 versions ago.

Yes, sorry you misunderstood. I meant fader level automation jumps when no program material is present of cause. Unless it's not accurate, so there is program material playing.
Concerning the preference, I was working on a PT version that didn't have this yet.

I don't think it has ever been 100% sample accurate except when doing offline bounces. (I think it was introduced when offline bounce came to PT)
If at all I'd say only volume and pan but clearly not for plugins.
Altiverb for example sometimes need several seconds to load a huge IR so if you place a setting change on a scene edge it won't recall sample accurately. This is even true for some EQ plugins in massive sessions.
I still write automation changes with at least a second of "handle" before each clip to avoid odd pops and ramps.

Yes, Frank, you're right. I even filed a ticket last year because I had major issues with some plug-ins. But I haven't had issues with volume automation for a long time now until I was working on that session that was originally created with PT 2018.