Pro Tools bugs

Make faulty plugin RED after CPU error!

We've all been there... A CPU error stops playback and then the CPU meter is peaking, rendering the session unusable until we find the problem plugin(s). Usually it's ONE plugin that is malfunctioning. BUT, to find that plugin can take dozens of minutes! Is it possible to automatically colour the likely culprit(s) RED after a CPU error? This would be such a time saver for so, so many of us. Of course, we'd prefer no ...more »

Submitted by (@yvovangemert)
1 comment

Opertaing System(s) : Windows 10, Windows 8, Windows 7, macOS 10.12, OS X 10.11, OS X 10.10, OS X 10.9, OS X 10.8, OS X 10.7, OS X 10.6

Voting

29 votes

Pro Tools bugs

Assertion Errors when importing audio - Using 'Clear Find' as a 'Solution'

I would sometimes have "Assertion Errors" when importing audio into Pro Tools from the Workspace Browser, starting in PT 11 and still happening in PT 12. It wouldn't always happen, and seemed to sometimes be fixed, then come back. This has been happening the last few years. Recently when using Pro Tools Field Recorder Workflow in Post Production, I suddenly had an assertion error(Attachment 01) crop up when trying to ...more »

Submitted by (@gwhatley)
Add your comment

Opertaing System(s) : OS X 10.11, OS X 10.10

Voting

9 votes

Pro Tools bugs

Out of CPU Power and Plugins

Please fix the way the PT 11 engine handles plugins. It is very inefficient and produces "Out of CPU" DAW errors long before the CPU maximum is reached.

 

VI's such as Kontakt and PLAY struggle considerably within Pro Tools.

Submitted by (@notedmusic)
4 comments

Opertaing System(s) : n/a

Voting

33 votes