Repeated Render Errors - Code -1609629695

[Chris Colton]

Over the past week or two I'm having a ton of render failures in Adobe Media Encoder with the error code -1609629695. Last night 5 different renders all failed. I've tried switching the renderer to Software Only and it didn't help. I've pasted some of the error messages below. Several of these sequences have failed dozens of times. One particular sequence has failed so many times that its version number is now 42 - and it's the first cut sent to the client. Or, I should say, not sent, because it still hasn't worked.

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

- Encoding Time: 00:57:29

12/04/2017 12:42:34 AM : Encoding Failed

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

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: HEVC (H.265)

Writing to file: \\?\B:\IW\IW14 Christine Allwine\Exports\IW14A Christine Allwine Feature Length Video v06-01.mp4

Writing file type: HEVC

Around timecode: 00:11:05:01 - 00:11:05:17

Rendering at offset: 665.707 seconds

Component: HEVC (H.265) of type Exporter

Selector: 9

Error code: -1609629695

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

- Encoding Time: 00:58:05

12/04/2017 01:41:28 AM : Encoding Failed

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

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: DNxHR/DNxHD MXF OP1a

Writing to file: B:\IW\IW14 Christine Allwine\Exports\IW14A Christine Allwine Feature Length Video v06-01_1.mxf

Around timecode: 00:11:05:01 - 00:11:05:06

Rendering at offset: 665.707 seconds

Component: DNxHR/DNxHD MXF OP1a of type Exporter

Selector: 9

Error code: -1609629695

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

- Encoding Time: 00:05:10

12/04/2017 01:46:40 AM : Encoding Failed

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

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: DNxHR/DNxHD MXF OP1a

Writing to file: B:\ps\ps12\Exports\PS12A Testimonials v03-03.mxf

Around timecode: 00;01;30;22 - 00;01;30;27

Rendering at offset: 90.757 seconds

Component: DNxHR/DNxHD MXF OP1a of type Exporter

Selector: 9

Error code: -1609629695

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

[AxelMatt]

Do you have installed the latest update. It seems that there were a bug in the previous version.

What you can try too is to deactivate the GPU support (Mercury Playback Engine) and render with the setting "Mercury Playback Engine - Software only".

Axel

[Chris Colton]

As I said in my original post, deactivating my GPU had no effect. I'm running 12.0 (CC 2018), the most recent version

[excited_Genie16B8]

Two of the exports failed in the same spot.  Take a look to see what's there on the timeline.

[Chris Colton]

At that point in the timeline a new clip starts, but it only has Lumetri

applied to it and it's just like the rest of the files in the sequence. I

just tried rendering that section on its own and it worked, oddly enough.

ᐧ

[excited_Genie16B8]

OK.  If you're using Cineform Previews (with Max Bit Depth checked), try using those previews for export.

[Chris Colton]

All those exports were actually using DNxHD HQX at maximum bit depth and

render quality

[excited_Genie16B8]

No no, previews.  If the previews you just made were good enough, you can use them during export without worrisome degradation.

[Chris Colton]

Sorry, I should've been clearer; all those exports had some previews

rendered as DNx, and "Use Previews" was checked for all of them as well.

ᐧ

[excited_Genie16B8]

OK but now you've got the troublesome section of the sequence rendered into new previews.  I'm suggesting you try exporting again, now that the problem section is handled.

[Chris Colton]

I can try that, but rendering that section on its own without previews

worked just now too. So strange!

ᐧ

[Chris Colton]

I've also received error code 1609629695 dozens of times over the past few years. I wish support had an error code definintions page!

[Chris Colton]

I just talked to Adobe Support. First, the guy tried to explain to me what the word "renderer" means. I've been editing full time on Premiere for 5 years, I know what it means. Then he said he has no information on what the error code means, and he disconnected the chat. Ridiculous.

For the record this is a Windows 10 system, quad core i7 processor, 32GB RAM, NVIDIA  Quadro K3000M, Premiere Pro CC 2018 (12.0)

[excited_Genie16B8]

That's not so surprising, unfortunately.

[Chris Colton]

Yeah, from my past experience I'm not surprised in the least. Support

almost never solves my problems but I thought they were worth a shot. Maybe

not.

ᐧ

[Chris Colton]

Support remoted into my computer and disabled accelerated intel H.264 decoding in Premiere and AME and told me to try again. Those steps took the guy 25 minutes to complete after insisting that he remotely access my computer and it would have taken me maybe 3 minutes. Rendering again now.

[Chris Colton]

Disabling intel accelerated decoding had no effect

[Kevin-Monahan]

Hey Colton Media Productions,

What kind of source footage is this?

Are you connected to any network storage?

Do you experience this problem with a new project?

What happens if you import this item into a new project?

What happens if you copy/paste these items in a new sequence?

Have you tried removing any of the effects on the clip at this location?

Have you tried placing a different clip at this location?

Thanks,
Kevin

[Chris Colton]

Hi Kevin, Source footage is H.264 in an MOV wrapper, AVCHD, and WAV audio.

This is all on one local USB3.0 4TB hard drive. I haven't tested a new

project yet but importing the failing projects into a new project doesn't

help. I can try copying and pasting into a new sequence. I also just got

done reinstalling all my Adobe CC products (uninstalled then used the CC

Cleaner Tool, then reinstalled).

ᐧ

[Kevin-Monahan]

Chris,

My sense is that it may have something to do with the fact that this is an updated project. I would test similar material in a new project. If it works OK, perhaps you can finish off these projects in CC2017.

Thanks,
Kevin

[Chris Colton]

This project was originally created in 2018 so it's not upgraded, and

unless I go via XML and lose all of my color and audio effects work, I

can't edit it in 2017.

ᐧ

[Holubfilm]

Dear Adobe,

I am also getting the following error message:  PLEASE EMAIL ME BACK [personal info deleted by mod, forum policy]

Error Compiling movie.

gpu render error

unable to process frame.

writing with Quicktime

rendering effect: AE.ADBE Lumetri

Component: Effect filter of type GPUVideoFilter

Selection:9

error code: -160962695

[Chris Colton]

Here is a screenshot of an event error log from one of the recent crashes. None of this means much to me but here it is in case it helps.

[Holubfilm]

Dear Adobe,

I am also getting the following error message:  PLEASE EMAIL ME BACK . [personal info deleted by mod]

Error Compiling movie.

gpu render error

unable to process frame.

writing with Quicktime

rendering effect: AE.ADBE Lumetri

Component: Effect filter of type GPUVideoFilter

Selection:9

error code: -160962695

[Holubfilm]

Dear Adobe,

I am also getting the following error message:  PLEASE EMAIL ME BACK . [personal info deleted]

Error Compiling movie.

gpu render error

unable to process frame.

writing with Quicktime

rendering effect: AE.ADBE Lumetri

Component: Effect filter of type GPUVideoFilter

Selection:9

error code: -160962695