Quote:
Originally Posted by Darryl Ramm
No. As always, it's possible it's an interaction between a specific version of Pro Tools and a specific version of plugins. And you are also changing computers here, even if one may be faster on paper, you have to troubleshoot stuff when you have a problem. You don't know what it is until you do some testing. This stuff should be second nature to Pro Tools users, do some testing then you can have much better suspicion what it is.
"it does not work for me" or what you "think" is the problem does not help make progress. What you can *show* is the problem would make progress. All that will happen here is your comments will likely get ignored unless you do some basic troubleshooting.
If Pro Tools is breaking compatibility with a specific plugin, Avid and the plugin vendor need to know what that is and get to work on fixing the problem. If it can be shown it is not a third party plugin then thats great info.
Pro Tools is a wide open runtime framework that third party plugins connect into. Slight changes in code within a plugin or Pro Tools can affect compatibility. For real time performance reasons there is effectively little/no internal checking of what those plugins can do to potentially mess with anything. Avid tries, but there is no blanket compatibility testing guaranteed with arbitrary third party plugins before a Pro Tools release. Ultimately we the users do that compatibility testing.
|
You're absolutely right. I'm aware that Pro Tools doesn't guarantee permanent compatibility with every version of every plugin ever made, and I'm sure it's a particular plugin or two that is causing CPU sadness.
That said, I'm a front end developer for a living and spend my my days debugging React apps and node module churn–I don't want to spend my music time in debug mode, though it seems necessary at this point.
Maybe if I used PT 2019.5 on a virgin OS with only stock AVID plugins it would be flawless. I just don't want to spend a day ferreting out the problem... I'd rather five minutes griping on the DUC while Pro Tools restarts, and wait for Native Instruments and the rest to get their ***** together with an update.