Premier Pro will not export to H.2643/mp4 after Pro 2022 update

[R0BB_M]

I always export my video to the mp4 format (H.264 in Premier Pro) but since the 2022 update it fails and gives me an error message. 

Previously, it was no problem. I notice that the new update defai=ulted to .avi, which is a crap format. so like WTF?

Anyone else having this problem?

Thanks

Robb

[caroline_edits]

Hey Robb – what's the error message it's showing you?

You could try rendering on Software Only mode to see if that helps: https://community.adobe.com/t5/premiere-pro/faq-how-to-change-the-video-renderer-in-premiere-pro/td-...

Caroline

[R0BB_M]

Hi Caroline

sry for the delay in reply, was travelling last wwekend and away from the home base. here's the error message I get:

None of the other formats I tried have a problem exporting... I did both .AVI and .MPG

Tried it on a couple other projects to see if maybe it was the source files being corrupted, but no. for some reason the H264 encoder doesn't work for me anymore, with the 2022 update. 

Robb

[R0BB_M]

Hi Again Caroline. I just tried what you suggested, but my Video Rendering was already set to "Mercury Playback Engine Software Only" I tried the GPU acceleration (CUDA) setting but that failed as well.

thoughts?

thanks

Robb

[Kevin-Monahan · Accepted solution]

Hi Robb,

 Can you try Software Rendering as opposed to Hardware Rendering? That's the option in the Video tab of your Export Settings dialog box, not  the option for your GPU in Project Settings. That has helped others.

Thank You,
Kevin

[R0BB_M]

Hi Kevin 

Setting the export to "software encoding" worked, and I was able to export successfully to H.264 format. 

Still, I feel like the Premier Pro 2022 update should not have caused a problem, since the previous version worked fine. 

Thanks for your help!

Robb

[Kevin-Monahan]

Hi Robb,

Sorry about that.  I had no issues with my system. Problems on updating are somewhat avoidable, but there are pitfalls with certain legacy projects and hardware which cannot be foreseen at launch. Glad we could find a workaround for now. Please check the Beta version to see if your bug has been fixed.

Thanks,
Kevin