GPU Render Error (-1609629695) for Simple Caption Motion Graphic

[Micah Snacks]

I am constantly getting the following error when I go to export. What is so strange is that I am not exactly exporting anything complicated - a simple caption that I upgraded to motion graphic is causing the dreaded export bug. The caption simply floats around slowly. How do I fix this error?? It has totally ruined my workflow and is making me late for deadliens as I type this . . . 

Tried doing QuickTime instead of 264, exporting timeline to a new projecrt, quiting out of Premiere and reopening it, reinstalling Premiere, etc and nothing works. On a Apple M1 Pro chip (so I cannot switch out of Metal renderer) and programs / os updated.

THANK YOU.

[Micah Snacks]

Nobody has a possible solution?  😞 

[Kevin-Monahan]

Hello @Micah Snacks,

Thanks for posting your bug report. Sorry for the lack of a response so far. Please give the team more details in the following format for best results in fixing the issue: How do I write a bug report?

I hope that the community, support, or developers can assist you with this problem.

Sorry for the frustration.

Take Care,
Kevin
Adobe Support and Community

[Micah Snacks]

@Kevin-Monahan Please see completed bug report. Thank you!

• Issue - Simple motion graphic of text causes GPU Render Error (-1609629695)
• Adobe Premiere Pro version number: Version 24.3.0 (Build 59)
• Operating system - macOS Ventura 13.6
• System Info: CPU, GPU, RAM, HD:

  • CPU Apple M1 Pro (10 Cores - 8 performance and 2 efficiency)

  • GPU and Driver Version (Please see attached screenshots for specs)

  • RAM 16 GB

  • Hard Drive SAMSUNG T7 Shield 2TB, Portable SSD, up-to 1050MB/s, USB 3.2 Gen2

• Video format: MP4/MOV H.264 4:2:0 (Full Range); 3840 x 2160; 23.976 frame rate; 1.0 pixel aspect ratio; Rec. 709 color space; 48000 Hz 32 bit floating point stero 
• Workflow details: One cam talking head
• Steps to reproduce - Upgrade text to motion graphic of 10 seconds or longer. Use Transform and keyframes with Anchor Point, Position and Scale to move and change size of motion graphic (Please see attached screenshot)
  
• Expected result - What should have happened after the last step? The video shown on the timeline should export.
• Actual result -  What did happen after the previous step? The video shown on the timeline does not export because of the GPU Render Error. In addition, somtimes the blackback has one or two black frames. When the motion graphic described above is removed, then the video exports, but I need the motion graphic.

[Kevin-Monahan]

Hi @Micah Snacks,
Is it possible to share the .mogrt so the team can inspect it for issues? Let me know.

Thanks!
Kevin

[Stan Jones]

Are you exporting directly from PR or queuing to Adobe Media Encoder?

If you export in to out, and set the out-point to 14 seconds, do you get the error?

Stan

[Micah Snacks]

Hi @Kevin-Monahan here is a link to the .MOGRT thanks so much for your help: 

https://drive.google.com/file/d/1E0px1E-DtAuRhbMxXxVYIoQVuSuIuVJk/view?usp=share_link

This is causing the GPU Render Error and the last 20 frames of video to go black in Adobe Premiere playback. Here is a look at my simple timeline:

[Kevin-Monahan]

Thank you, @Micah Snacks; I have informed the team and given them the file.

Cheers,
Kevin

[Micah Snacks]

Hi @Stan Jones I am exporting directly from Adobe Premiere. 

I tried Render In to Out for the first 14 seconds and did not get an error:

I then tried Render In to Out for the whole timeline and got the error:

Here is a link to the motion graphic which seems to be causing the error:

https://drive.google.com/file/d/1E0px1E-DtAuRhbMxXxVYIoQVuSuIuVJk/view?usp=share_link

Thank you so much for your help.

[Micah Snacks]

Many thanks @Kevin-Monahan when can I expect a proposed solution?

[Kevin-Monahan]

Hello @Micah Snacks,

I am a mere moderator and not part of the product team. "When" questions are almost impossible for me to answer. I will stay on top of the issue and act as your advocate, though. Unfortunately, I have to ask for your patience. I hope soon, though!

Thanks,
Kevin

[Micah Snacks]

@Kevin-Monahan Thank you! A good advocate on this matter sounds great! 🙂 

[ESTLL]

Same issue here 😞 But it is wrap stabilizer effects that seem to be in cause. Any solution? :((((