Render issues - error code: -1609629695

Community Beginner ,
Oct 11, 2018

Copy link to clipboard

Copied

I have issues with exporting clips I edited some months ago. I have these issues in Premiere Pro as well as with the Media Encoder.

 

  • Interestingly, Premiere and Encoder are sometimes able to render the clips, sometimes not.
  • When I export the material in full HD, the video looks OK, but when I export in HD the video looks grainy
  • When the Media Encoder is unable to render the video, closing & reopening seems to help sometimes. However, after one or two clips, I get the issue again.

 

Unfortunately, I have to export about 25 clips and will have to export them several times for iterations.

 

Fehler beim Export

Fehler beim Kompilieren des Films.

 

Fehler bei beschleunigtem Renderer

 

Frame kann nicht produziert werden.

 

Schreiben mit Exporter: H.264

Schreiben in Datei: \\?\F:\Export\02 - Genium EN.mp4

Dateityp wird geschrieben: H264

Um Timecode: 00:00:06:15 - 00:00:06:21

Rendering bei Offset: 8,880 Sekunden

Komponente: H.264 vom Typ Exporter

Selektor: 9

Fehlercode: -1609629695

 

I tried:

  • switching to CPU rendering only
  • copying the content of a sequence to a new sequence
  • downgrading premiere and encoder, but then I was unable to open the document because I already saved it with the newest Premiere version.
  • Removing Lumetri Color correction

 

System: Win 10, i7-7700, Nvidia Gtx 1060

 

Thanks!

TOPICS
Crash, Export

Views

48.0K

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

1 Correct Answer

Adobe Employee , Jul 29, 2019
Kevin-Monahan Adobe Employee , Jul 29, 2019
Ellen,What troubleshooting have you tried so far?First of all, look at the warning dialog box. What's going on at 1:38 in your sequence as indicated in the dialog box? You might have a corrupt render file.If you re-render the clip in that area, can you render then?You might have a corrupt clip. If you swap out the chosen clip with a clip from, say, another take, can you render then?You might be running out of VRAM at that point in your sequence. If you change the renderer in File > Project Setti...

Likes

Translate

Translate
Jump to answer Jump to answer
Adobe Community Professional ,
Oct 11, 2018

Copy link to clipboard

Copied

You need to fix whatever is on the timeline at the given time in the error message.

Can be anything: faulty clip, transition, effect, audio, you name it.

Remove clip from timeline.

Add it again and redo the effects.

If that does not help, export to intermediate file (e.g. CF) and put that on the timeline.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Community Beginner ,
Oct 15, 2018

Copy link to clipboard

Copied

Thank you for your answer, but I found the solution.

It's a software bug that took me ages to find. I am working on two computers and I switch to my notebook while I am exporting on my PC. Windows locks the screen after some minutes and when I unlock the screen the Media Encoder seems to either continue the rendering process or it shows that all exports in the queue have failed.

This bug was so difficult to find because when Windows locks the screen and I unlock it immediately, the Media Encoder seems to continue rendering as if there was no problem. However, the export eventually fails. After this, every export fails until I close and reopen the Media Encoder again.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Dec 03, 2020

Copy link to clipboard

Copied

There is no answer here...

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
mlk65822879 AUTHOR LATEST
Community Beginner ,
Jan 03, 2021

Copy link to clipboard

Copied

Hi Brennan, see my answer below. You can change that windows locks/turns off the screen in the "Power & Sleep" Settings in the Window settings. 

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Dec 27, 2020

Copy link to clipboard

Copied

What is the bug? how do you solve it?

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Community Beginner ,
Jan 03, 2021

Copy link to clipboard

Copied

In my case, the bug was - as described - that the Media Encoder cannot handle the screen locking.

Thus you should prevent that Windows locks the screen. 

 

In the Windows settings, set "turn off after" to "never"

3.png

 

Or go to your power plan settings in windows ...

1.PNG...and set it to never:

 

2.PNG

 

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Apr 01, 2019

Copy link to clipboard

Copied

Can you please explain EXACTLY what you did to fix this? I have been receiving this error code on every export attempt and am absolutely desperate at this point to get it resolved.

PLEASE, if you have the answer, help me out.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Community Beginner ,
Jul 29, 2019

Copy link to clipboard

Copied

I have the same error exporting from Premiere, it started getting it, after I upgraded to the latest version 13.1.

error.png


Still can't fix it

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Employee ,
Jul 29, 2019

Copy link to clipboard

Copied

Ellen,

What troubleshooting have you tried so far?

First of all, look at the warning dialog box. What's going on at 1:38 in your sequence as indicated in the dialog box?

  • You might have a corrupt render file.
    • If you re-render the clip in that area, can you render then?
  • You might have a corrupt clip.
    • If you swap out the chosen clip with a clip from, say, another take, can you render then?
  • You might be running out of VRAM at that point in your sequence.
    • If you change the renderer in File > Project Settings to: Mercury Playback Engine GPU Acceleration (Software Only), can you render then?

Let us know what's going on.

Thanks,
Kevin

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Community Beginner ,
Jul 30, 2019

Copy link to clipboard

Copied

I  have tried different projects to render, all of them fail, with the same error.
It started happening after the upgrade of Premiere.

The only way for me to render is through the Media Encoder.
I'll have to downgrade back to the previous version of Premiere.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Sep 27, 2019

Copy link to clipboard

Copied

"If you change the renderer in File > Project Settings to: Mercury Playback Engine GPU Acceleration (Software Only), can you render then?" Thanks for the solution. It worked really well!

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Nov 10, 2019

Copy link to clipboard

Copied

This worked thanks.

"If you change the renderer in File > Project Settings to: Mercury Playback Engine GPU Acceleration (Software Only), can you render then?"

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Nov 10, 2019

Copy link to clipboard

Copied

I need to delete my last post as it is showing my email address, kindly assist. Thanks.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Explorer ,
Nov 18, 2020

Copy link to clipboard

Copied

Changing the renderer to Software Only also worked for me.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Dec 16, 2020

Copy link to clipboard

Copied

You are my hero. Changing it to 'Software only' is the ONLY solution that has worked. This issue has been plaguing me for months! Thank you!!! 

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Apr 23, 2020

Copy link to clipboard

Copied

This error will occur sometimes because of the "effects & presents" that you apply to the footage like picture or video. I experienced the same. After removing that effect, everything becomes normal while rendering.

 

Effects I used: Shadow/Highlights and Curves

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Employee ,
Jun 15, 2020

Copy link to clipboard

Copied

Note to Rakesh and the Community:

 

Shadow Highlight & RGB Curves are "Obsolete Effects"

 

It would be wise to discontiue use of any Obsolete Effects in current workflows. These effects are intended for use for restoring legacy projects, not for use in new sequences. 

The same could be said for "Legacy Titler." 

 

If you have a problem with discontinuig use of obsolete effects or Legacy Titlter for whatever reason you have, please let the Premiere Pro Development Team know on User Voice.

 

Thanks,
Kevin

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Dec 19, 2020

Copy link to clipboard

Copied

Hey, i have with the Curves the 1 color black and white effect added to my project because it looks cool. Is there a way to do that effect without the curves? (because you said earlyer that the Curves a 'outdated effect is. I have also trouble with the render using this effect.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Community Beginner ,
Nov 08, 2019

Copy link to clipboard

Copied

I"m working in AE - was getting the same cursed error, but my google search led me here. Ann's answer gave me an idea, so..In case someone else stumbles across this who was like me, my fix was:

Reading some other forums I found that the combination of the Hue/Saturation effect and blur can effect the encoder (or sometimes just Hue/Saturation on its own). By using the search feature in the layers panel - I click+drag turned off all of the Hue/Sat effects on my layers, let the preview refresh a frame, then turned them all back on again. For whatever reason - now exporting to encoder isn't crashing with this error.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Employee ,
Nov 10, 2019

Copy link to clipboard

Copied

Cyrene,

Sorry about this.

 

"I click+drag turned off all of the Hue/Sat effects on my layers, let the preview refresh a frame, then turned them all back on again. For whatever reason - now exporting to encoder isn't crashing with this error."

 

Sounds like a corrupt preview file. It happens from time to time. Glad you solved it. Ann Bens is correct. Always inspect clips where the Timecode indicates an error. Good tip.

 

Kevin

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Explorer ,
Jan 30, 2020

Copy link to clipboard

Copied

same problem here, and the timecode indicated in the error msg is NOT even part of the exported area... it is AFTER the export area, and in fact the timeline is empty there.

 

  • I tried removing an HLS efftct - no help. changed to "Mercury Playback Engine GPU Acceleration - Software Only" - no help.
  • deleted all media cache and preview files - still doesnt work.
  • one section on the timeline has a linked AE comp where there is a Wigglerama effect.
    • deleted the effect (even though it does exist in other exports) -
    • finally it is exporting.

 

Premiere is just a time-sucking-bug-filled software and if they carry on this way ppl will abandon ship the moment there is a decent alternative to the suite, and its just a matter of time.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Dec 15, 2020

Copy link to clipboard

Copied

This was my problem! Thanks a lot!

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Nov 22, 2019

Copy link to clipboard

Copied

Hi,

I've faced this exact error code today with CC 2020. Was using AE to export many with the same preset but with different index.

After messing around a while, my issue was a corrupted render cache file, which I've resetted and cleared them all. This simply fixed my issue. 

I guess, there are some conflict with the versions render cache and the old ones were simply not matching with the fixed effects and stuff. (Got so many effects on some layers so I did not disable/enable them one by one.

Hope this helps.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
New Here ,
Jan 07, 2020

Copy link to clipboard

Copied

I had the same issue when trying to export from After Effects with AME no matter the format I chose. 

I finally managed to make it work. I watched all rendering and saw where it stopped, then I went to the timeline and removed whatever effect was at that exact time (turned out to be caused by a glitch effect that I used from a paid transition pack). 

 

I hope this helps. Good luck

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more