Pro Tools 2020.9.1 GUI bug
 

I've had this issue for several versions now, across 2 different computers, and 3 different GPUs.
Periodically and seemingly without consistent cause, the Pro Tools GUI will distort and flash nonsense: partial windows and GUI components on the screen. During this time pro tools will also become unresponsive to mouse or keyboard input. I've attached a photo here. I spoke with Avid tech support on the phone. The rep told me he had never seen this issue and would escalate. I have followed up 2x and submitted a new ticket, but it seems Avid support is ignoring me at this point. Has anyone has this issue or can a mod let me know if this issue actually is a confirmed bug?

Re: Pro Tools 2020.9.1 GUI bug
 

Lots of views... is no one having this issue?

Re: Pro Tools 2020.9.1 GUI bug
 

I'm getting it occasionally on sessions that contain video.

Re: Pro Tools 2020.9.1 GUI bug
 

Thanks for speaking up, Dazzler. Have you contacted Avid about the issue? I did and they stopped responding to me.

Re: Pro Tools 2020.9.1 GUI bug
 

Speak of the devil!

Re: Pro Tools 2020.9.1 GUI bug
 

This was a simple session with no video.
Are you using Processor Affinity settings Dry?

Re: Pro Tools 2020.9.1 GUI bug
 

I have not tried messing with Processor Affinity, but I will now. And yes, that screen is a familiar sight :(

Re: Pro Tools 2020.9.1 GUI bug
 

Just to add, most of my GUI glitches start with a Bounce to Disk. The counter window will show as solid black where the numbers usually tick over. It will complete the bounce, but Pro Tools will be unusable from that point and needs to be quit or forced stopped.

Re: Pro Tools 2020.9.1 GUI bug
 

Yep. The same thing happens to me. I was able to show the Avid rep I spoke with. Unfortunately I haven’t heard anything back and I don’t know if the issue has been officially recognized.

Re: Pro Tools 2020.9.1 GUI bug
 

Another, but not during bounce, and it spat me this when I exited.

Could not complete the Exit command because Access violation occurred, unable to read location: 0x0000000000000010