System Usage

[aftermid]

A curious thing is happening with one of my sessions, that wasn't happening before. The system usage memory CPU is peaking at 100%. I've deactivated all the plug ins in the session and played with cache and ram settings. When I close the session, the CPU is still peaking at 100% with no session open.


If I quit Pro Tools and restart, then the CPU goes back to normal. This anomaly only started happening with this session, even though I haven't added anything to the session. What's stranger is that once the session is closed, the CPU is still peaking at 100%. When this happens Pro Tools is the only program running.


Also, tried deactivating all tracks and putting all plug ins in unused folder. Still same problem. Any ideas?


Computer Specs: Mac Mid 2012 16GB Ram. 3.4Ghz Quad core processor, OSX High Sierra, Pro Tools Ultimate 2020.12.1

[nednednerb]

If you create another session does it happen again?

If not, there is nothing in the session? If there is content, what about Import Session Data into a new session without problem?

If the problem does not occur, I might suppose the session is corrupt and that would be a decent resolution if nothing important is lost and future sessions seem OK.

[Frank Kruse]

I think there was one old version of PT where dynamic plugin processing was broken and PT would not "release" CPU time for non-mono tracks. Not sure which one but I'd try a current version of PT and see if that helps.

[Ben Jenssen]

Any activity in the Task Manager window?
What does Activity Monitor say about PT CPU usage?

[Emi]

Usually when PT starts to do wierd things, first thing I do is delete preferences, empty bin and restart computer.

[aftermid]

I would think, if I close the session, the CPU would go down, but it doesn't. The CPU only goes down, if I quit and restart Pro Tools. Only then, if I open another session, do I get normal CPU levels. If I open the session in question, I get the high CPU levels. If the session is corrupt, shouldn't closing the session bring back the CPU levels back to normal without having to quit Pro Tools?

[albee1952]

Trashing prefs is step #1 for any odd behavior, so start there

[nednednerb]

Originally Posted by aftermid

I would think, if I close the session, the CPU would go down, but it doesn't. The CPU only goes down, if I quit and restart Pro Tools. Only then, if I open another session, do I get normal CPU levels. If I open the session in question, I get the high CPU levels. If the session is corrupt, shouldn't closing the session bring back the CPU levels back to normal without having to quit Pro Tools?

That's just it, if the session was corrupt, how many things could then go wrong? Depends on the nature (potentially random) of the corruption.

[aftermid]

Ok,


Trashed preferences this made no difference. In Pro Tools Ultimate 2020, the preferences are stored in a folder called Pro Tools inside the Avid folder in the library, unlike older versions that had individual preference files like, com.digidesign.protools.plist. Now, this file is still in there, probably left over from when I had Pro Tools 10. Not sure, if that would be relevant.



When I trashed Pro Tools Ultimate preferences, I restarted the computer and opened Pro Tools. Without even opening a session, the system usage was showing already 50%. That was worse than before, when opening Pro Tools with no sessions opened showed a usage of about 5%. When I tried opening the session that's been giving me problems, Pro Tools hangs and the task manager says Pro Tools is not responding.

[Emi]

What about a fresh install?