Skip to main content
Inspiring
April 22, 2017
Question

H.264 High Bitrate Encoding Fail at 0%

  • April 22, 2017
  • 1 reply
  • 759 views

Okay, so I went to encode a video today using the newest version of Premiere Pro CC (2017.1) and it kept failing. I was trying to use a previously saved preset.

After a lot of fiddling, it turns out that setting the bitrate too high was what was causing it to immediately fail with this error:

Error compiling movie.

Export Error

Failed to create encoder.

Writing with exporter: H.264

Writing to file: \\?\C:\Users\Tim\Desktop\Sequence 01.mp4

Writing file type: H264

Around timecode: 00:00:00:00

Component: H.264 of type Exporter

Selector: 9

Error code: 3

Here are the details:

Sequence

Sequence Dimensions: 3200x1600

Sequence Framerate: 59.97

Encoding:

Format: H.264

Preset to use as a basis: Match Source: High Bitrate

Note: The profile and level are auto-set to Main and 5.2 respectively automatically

CBR: 240 (the maximum)

Try to encode, either right within Premiere or in AME and it will fail almost instantaneously.

Any bitrate over 192 seems to fail immediately.

I'm using Windows 10 (fully updated)

Can someone else test this out and make sure it isn't just my machines having this issue? I've tried it on 3 machines.

PS: I seem to notice at least one bug almost immediately after a new release is launched (check my track record). What does it take to become a beta tester?

@Kevin-Monahan

@Reg Santo Tomas

This topic has been closed for replies.

1 reply

kulpreet singh
Inspiring
May 18, 2017

Hi TeeKayCC,

Sorry for this trouble, but I am not able to reproduce this issue at my end.

I am assuming that you have already tried these troubleshooting steps: How to fix issues that cause errors when rendering or exporting

Are you experiencing the same issue with the latest update (11.1.1)?

Thanks,

Kulpreet Singh

TeeKayCCAuthor
Inspiring
June 8, 2017

A colleague "MMeguro" over in the Adobe Media Encoder forums was able to reproduce:

https://forums.adobe.com/thread/2307768

I do believe this was fixed in the latest incremental update from 11.1 to 11.1.1