Starting time of ProTools 2024.10 has increased significantly

[Franklyn]

I have noticed that since PT 2024.6 or .10 the program start time has increased significantly. I was happy that on my M1 in native mode Pt 2024.3 only took 30 seconds to start. But the latest version 2024.10 (maybe this began with 2024.6) requires 1:15 with the same plug-ins installed.
This is 2,5 times longer.
In particular, the process “Plug IN cache is being prepared” and “Plug ins are being loaded” takes a very long time. At this process some plug-ins are scanned on every start.

(all results are 2nd, ... start after booting the Mac)

[Darryl Ramm]

Have you tried trashing prefs? and comparing results after that? Make sure you are trashing the new style plugin caches correctly, or even better just use the latest PT Prefs 2 utility. See if that helps stop any repeat scanning.

What macOS version? Running native or via Rosetta? Is it always the same plugins that seem to be rebuilding their caches? There have been significant changes to the plugin cache and other code since 2023.12, and that may well break things or individual plugins. If you remove those plugins from the plugin folder does everything get back to speed again? If so I would contact the plugin vendor support and Avid support.

The Pro Tools log file will likely help you with info here, maybe you are already looking at that.

[tope d]

Originally Posted by Franklyn

I have noticed that since PT 2024.6 or .10 the program start time has increased significantly. I was happy that on my M1 in native mode Pt 2024.3 only took 30 seconds to start. But the latest version 2024.10 (maybe this began with 2024.6) requires 1:15 with the same plug-ins installed.
This is 2,5 times longer.
In particular, the process “Plug IN cache is being prepared” and “Plug ins are being loaded” takes a very long time. At this process some plug-ins are scanned on every start.

(all results are 2nd, ... start after booting the Mac)

Best to optimize your computer for Pro Tools use, there might be debris from previous versions.
You can check https://avidtech.my.salesforce-sites...oting/en367983 for more info and steps on specific Operating Systems and OS versions

[Franklyn]

Originally Posted by Darryl Ramm

Have you tried trashing prefs? and comparing results after that? Make sure you are trashing the new style plugin caches correctly, or even better just use the latest PT Prefs 2 utility. See if that helps stop any repeat scanning.

What macOS version? Running native or via Rosetta? Is it always the same plugins that seem to be rebuilding their caches? There have been significant changes to the plugin cache and other code since 2023.12, and that may well break things or individual plugins. If you remove those plugins from the plugin folder does everything get back to speed again? If so I would contact the plugin vendor support and Avid support.

The Pro Tools log file will likely help you with info here, maybe you are already looking at that.

thanx Darryl,

as I wrote I work silicon native. PT Ultimate 2024.10.2
M1, OSX 12.7.6

approx. 80 Plug Ins are rebuilding the cache. and approx. 100 are scanned.
The wave shells are one of the scanned ones and I thing t-racks plug ins.

I work nearly 30 years with protools and all these optimization things never sold any of my problems. It must be a change in the scanning process as you say.


I will try to delete prefs. But I done like to loose my settings.
Maybe I start with deleting the plug in caches the new way.

Darryl, can you measure how long your ProTools needs for starting?
Or any other one of you?
That would help to find out if I am out of the normal range.

[K Roche]

Mine on my intel iMac system below is taking about 35- 40 seconds from clicking PT icon to Dashboard

[Franklyn]

Originally Posted by K Roche

Mine on my intel iMac system below is taking about 35- 40 seconds from clicking PT icon to Dashboard

thanx, yes that's what it should be.

[Franklyn]

For rescanning all Plug Ins. is it enough to delete the new plug In cache?
in /Users/Shared/ProTools/AAXPlugInCache.
Complete folder with all individual files ?
(dont want to loose my settings)

[Darryl Ramm]

Originally Posted by Franklyn

For rescanning all Plug Ins. is it enough to delete the new plug In cache?
in /Users/Shared/ProTools/AAXPlugInCache.
Complete folder with all individual files ?
(dont want to loose my settings)

Yes I'd try that first. I would delete all the files in /Users/Shared/Pro Tools/AAXPlugInCache and let Pro Tools try to rebuild them all.

You can also use PT Prefs 2 Advanced option and delete that with one button push.

You can also use PT Prefs 2 to backup all prefs, delete them all and just see if that ever solves a problem. Restore them if it does not. I would just get used to doing that as trashing prefs can be a useful test.

[Franklyn]

Originally Posted by Darryl Ramm

Yes I'd try that first. I would delete all the files in /Users/Shared/Pro Tools/AAXPlugInCache and let Pro Tools try to rebuild them all.

You can also use PT Prefs 2 Advanced option and delete that with one button push.

You can also use PT Prefs 2 to backup all prefs, delete them all and just see if that ever solves a problem. Restore them if it does not. I would just get used to doing that as trashing prefs can be a useful test.

Thank you. I did that and now it's better. (55 seconds, only 25 build new cache and 46 will be rescanned).

But it's normal for a few plugins to be scanned every time they start, right? Or you don't have a plug scan at all again when you start

[Darryl Ramm]

Originally Posted by Franklyn

Thank you. I did that and now it's better. (55 seconds, only 25 build new cache and 46 will be rescanned).

But it's normal for a few plugins to be scanned every time they start, right? Or you don't have a plug scan at all again when you start

'scanned' is not a clear meaning, all plugins are scanned even those that are cached. What you want are plugins being properly cached.

Only new plugins installed since the last time Pro Tools was started should not be cached. Previously installed plugins should be cached. With the recent changes even plugins installed on a running Pro Tools system should get cached. Who knows what was going on in your case. Sometimes the caches fail to load and need to get rebuilt, sometimes they may fail to get saved. Again there has just been lots of plugin related instability caused by changes starting in 2023.12. Things happen too fast with modern Pro Tools to see much of what is going on with plugins on the startup/splash screen so the Pro Tools log files ~/Library/Logs/Avid/Pro_Tools*.txt are very handy, and oh I've seen lots of seemingly bad error messages there with plugin caches in the last few major Pro Tools releases. Again lots of changes obviously going on in the code base.