Render error code: -1609629690

[tanjas95445528]

Hi,

I'm having a serious issue with exporting media. Please help me!

--------------

Export Error

Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264

Writing to file: /Volumes/G-Drive/004_GGZ Wageningen_2018-11-27/02_Export/1.4 Edit- Volwassenen GGZ-_2.mp4

Writing file type: H264

Around timecode: 00:01:21:31 - 00:01:21:47

Rendering at offset: 81,620 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629690

------------------

This is the situation:

I'm working in a project which is a long-term project of 3 movies. I created the project last december and finished already 2 movies early january. For the 3rd film I had to wait for some extra shooting and I started editing about 2 weeks ago. From this extra material I used some for the elder movies, which I edited earlier, and re edit them.

Exporting the latest movie, with the new clips, doesn't give this error. But the other two movies just won't export! It makes me go mad!  I have been trying for hours to find a solution for this error/ bug

I tried lots of different things:

restart

export to quicktime (while rendering my computer freezes and crash)

relink the media

import the MOGRT files again

duplicate the project.

Put the project on the HDD of my IMAC. For my edit I use a G-drive external HDD

Update premiere to version 13.03

Please, help me fix this error!

[Videopixel]

That's cool, but, how did you color corrected it? Replaced Lumetri tweaks on another color correction effect? From the basis?

[gustavw45976950]

i solved the problem for me. in my case there was a problem with png's. yes, it's a issue with the grafic card. the problem happens if you got medias with a resolution bigger than the maximum resolution of yout grafic card.

i used illustrator to pull down the resolution of the png's. now its working.

[MRowan]

Check this Solution  - hope it works for you.

".....So the video eventualy rendered by doing this:

toggle all the video/ audio targets OFF>

then try export as usual

hope this works for you.."

[Summit22069854j5jq · Accepted solution]

Had the same issue, tried all the below methods, none worked. Finally figured it out myself.

Solution: Open task manager, close all the Adobe creative cloud services running in the background. Reopen the premiere project, select Cuda in the project settings. It should properly work now. 

Issue was the Creative cloud Coresync running in the backgroud, just end all creative cloud services running in the beackground. Good luck. 

[SerifCreativeLLC]

Thank you! This solved my problem as well. Premiere has been giving me this issue out of the blue for the past few days. I updated all software and graphics drivers, thought it fixed it, but it started doing it again after working in the project for a few hours today. Adobe, don't tell me my GTX 1080 isn't powerful enough to render a timeline because I know better. Please fix your software you charge us an arm and a leg for.

[onehunerdpercent]

This. I have an RTX 3080 and was like there's no way this is my GPU. 

[Kevin-Monahan]

Hi, onehunerdpercent,

Thank you for letting us know. I included this solution on our newish FAQ on error compiling movie. I hope it helps others.

Bye,
Kevin

[briand52466702]

This did it, THANK YOU!

[jamila25253791pamq]

If anyone is still having this problem, this is how I fixed it. I copied all clips that I wanted to export. I created a new sequence, and pasted all the clips (including effects, audio, et cetera). Then I selected it all, and nested it. Then I exported it again and it worked. So basically I told Premiere: not today, satan, not today. Good luck!

[Kevin-Monahan]

Thanks for reporting on that one, jamila. It appears that may have been a corrupt sequence, which happens occasionally. Glad you were able to solve it! 

Thanks,
Kevin

[Ahmad27636601ie9s]

I tried this as well and it worked for me but only if I didn't reanalyze warp stabilizer on my clips. The moment I tried applying the stabilizer the new sequence would report the same error code to me. 

[Kevin-Monahan]

Thanks for the added info, Ahmad. Odd tidbit there, but perhaps the effect was the thing that became corrupt. Noted. Have a wonderful holiday season.

Thanks,
Kevin

[Ahmad27636601ie9s]

Thanks for your reply. 

Is there any recommendation for how to resolve the corruption? 

[Ahmad27636601ie9s]

I spent about an hour with a support agent. They took over my screen and spent their time trying different rendering options. Nothing worked except for swithcing from CUDA to software rendering. This is a temporary fix but obviously slows down the editing process for me and is quite frustrating. I have a 3070 GPU so was not expecting a weak performance on premier. I am now reaching out to the manufacturer to see if theres a way to confirm that my GPU is in fact the problem. Judging by the different solutions seen here on this page it seems like my GPU could be the issue. 

[Aaron27831075sdmh]

I also had this issue, I changed the renderer to software only and had to rename the exported file. I think this happens when you have previously exported or your source file is in the same folder. 

[Stindu30931521yzwv]

This solution wasn't working for me, it only worked for me when I cleared my recycling bin
try that if you're still having this issue after trying other stuff

[Colourbus Media]

Warp Stabilizer was causing this error for me. Didn't analyze properly and had some frames drop. Unfortunately reanalyzing didn't fix the problem. Had to delete warp stabilizer all together for that clip. Works fine on a lot of other clips. Working on a 16" 2019 Macbook Pro with Monterey 12.7.