![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
Sorry if this is the wrong place for this question,
What determines the delay compensation for a plug in/track? Is it the host computers performance, or is it a predetermined number that the plug in tells pro tools what its delay is? For the same exact plugin would you experience a lower delay comp on a more powerful computer versus a less powerful computer? thanks! |
#2
|
|||
|
|||
![]()
It has nothing to do with CPU performance, audio latency is happening many orders of magnitude slower than CPUs work at. Latency is caused by the internal plugin algorithm, if the plugin is deliberately delaying all or part of the signal (e.g. to perform look ahead for a limiter), if it’s doing frequency up conversion, etc. it will have latency from doing that. The latency varies at different sample rates. The plugin knows what that latency is, the set of latency vs sample rate data is hard coded into the plugin by the developer and Pro Tools queries the plugin to get that data. Yes there are very occasional mistakes.
CPU performance and overall systems optimization determines how large a session with how many plugins you can run but not any of the plugin latency numbers themselves. The moment Pro Tools gets close to being unable to keep up with keeping everything running with sample accurate time alignment it deliberately crashes itself with an AAE CPU error. Last edited by Darryl Ramm; 10-05-2022 at 11:09 AM. |
#3
|
|||
|
|||
![]()
And depending on what you mean by track latency, the IO buffer or disk playback buffer also add latency at input and output. As do latencies in the analog to digital and digital to analog conversions, and some additional latency interfacing to device drivers. All of which Pro Tools takes care of automatically. (you get that without enabling "delay compensation").
DSP based HDX (and older TDM) systems using HDX (or TDM) plugins don't utilize an IO buffer, except when converting back to use native plugins and back again to the DSP based mixer. HDX (or TDM) plugins are not guaranteed zero latency, any that perform look ahead or up conversion etc. will add latency. Especially true of mastering bus/limiting plugins with deliberate high look-ahead. Last edited by Darryl Ramm; 10-05-2022 at 11:41 AM. |
#4
|
|||
|
|||
![]()
Darryl,
These are great explanations. Easy for us less technical folks to understand. Thank you. |
#5
|
||||
|
||||
![]()
Yes thank you! Good to grok.
__________________
___ >> me: nednednerB // ||main gig: editing audio & testing software / 2nd gig: music software tutoring // ||software: Ventura 13.2.1 | PT Studio 2023.3 | Ableton Live 11 | iZotope RX, Ozone, Neutron | Arturia Pigments | Auto-Tune | Dubler2 // ||system: iMac (Retina 5K, 27", 2020) 10-Core-i9 | 128GB-DDR4 | 5700-XT-16GB // ||devices: Focusrite Clarett 2Pre | some AT condenser mics | SM58 | Ableton Push 2 | 32" 4k LG secondary display // ||automation: SoundFlow | Keyboard Maestro | SteerMouse // |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
help fixing plugin delay and delay compensation disaster | prestonhavill | macOS | 14 | 12-24-2014 03:35 PM |
When do you NEED plugin delay compensation? | JonnyGinese | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 6 | 03-17-2006 09:28 PM |
Plugin Delay Compensation | kurt | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 34 | 12-20-2005 11:51 PM |
Will PT7 LE have plugin delay compensation? | Matiz | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 0 | 09-17-2005 01:27 PM |
plugin delay compensation? | vieris | Pro Tools M-Powered (Win) | 1 | 06-19-2005 03:25 AM |