gpu render error "unable to process frames" linked to opacitiy keyframe being "on"
Several users on the U2U forum have reported having exports fail with the message "GPU render error" unable to process frames" with the typical time-code of the error.
But the only way to 'fix' this is to go into the Effects Control Panel, and check the blue watch key-frame icon so that it turns charcoal in the "off" setting.
Then their export exports properly. As in the following thread:
Ian Leopold commented
I just had this issue. The rendered effect was a four color gradient I used. I fixed it by exporting the one clip that was giving the issue, putting it back in its original space and exporting. A simple workaround, but hopefully won't ever be necessary again.
Richard Schwerdtfeger commented
I have this problem with Premier Pro 14.6. Even if I delete the clips in around the area of the crash it still crashes in th same spot there there is no clip at all. I also turned off the GPU acceleration feature. It always crashes in the same spot. I am writing with Premier Pro exporter vs. Media Encoder because the queue will not launch with this latest update: H.264. The rendering effect is the subpacestabilizer (even when I remove the clips). I get selector: 9 and error code -1609622965. I am totally stumped. My YouTube channel development is basically stuck and has been for over a day now because of this problem. My video was mostly done. I looked at the solution here and it makes no sense if there is no clip in around the location of the crash. Please help.
зачем доступ закрыл, мудила?