[Darryl Ramm]

Basic basic stuff... what IO buffer size and sample rate are you working at? Disk cache size? Recording audio to what make/model drive? What audio interface and driver version (if ASIO4ALL confess that now...).

Start with standard troubleshooting steps under “help us help you” up the top of each DUC web page.

Paying attention to trashing prefs (frequently as you try other stuff), troubleshooting plugins (*always* suspect plugins)—test removing all third party plugin files, putting them back in batches, etc. or looking for a corrupt session. You may also need to print/freeze tracks, reduce long chaining of tracks/busses.

The “conventional fix” is to try all that troubleshooting. No point really posting here until you have done that, and if still stuck describe carefully what you tried.

There is nothing unusual here. Pro Tools really does not “think” or care about what any CPU usage meter says. When internal latency to get things done takes more than the allowable small time then Pro Tools calls this CPU error. Looking at meters rarely helps solve anything, especially with confusion hyperthreading introduces, most CPU problems appear exactly as here.