• Global community
    • Language:
      • Deutsch
      • English
      • EspaƱol
      • FranƧais
      • PortuguĆŖs
  • ę—„ęœ¬čŖžć‚³ćƒŸćƒ„ćƒ‹ćƒ†ć‚£
    Dedicated community for Japanese speakers
  • ķ•œźµ­ ģ»¤ė®¤ė‹ˆķ‹°
    Dedicated community for Korean speakers
Exit
0

Media Encoder keeps crashing since latest updates

Explorer ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

Hi 

I have spent most of this morning trying to export a video as a 4K Youtube video but my media ancoder keeps crashing at the same point.  I previously got this error on a older PC but have upgraded my PC in May using GPU acceraltion and have not since had any issues with most 4K renders of about 15min videos taking about 30mins.  

Today the estimated time for full render is more than 10 hours to start with and the rendering crashes at the same piont almost an hour into the rendering and only 5:20min into the video I am trying to render.

 

After the 2 failed attempts at rendering in 4K, I am not attempting to do a HD version (as I have to upload the video today still!) but am still getting an estimate of more that 6 hours on the video.  My GPU is running absolutely flat out and I cannot do any work on the PC while rendering - which I could previously do quite easily.

 

What has changed with the update and what can I do to improve these render times and be able to render in 4K again?

TOPICS
Error or problem , Hardware or GPU

Views

652

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

Even the HD render fails at the same point. I am at my wits end on what to do having wasted almost 4 hours now trying to get this one video rendered and I have a second video that needs to be completed by tomorrow that will probably take even longer to render!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

I have reverted to 15.1 and hope that will work better because in my opinion 22 is broken...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

OK that doesnt work as the projects are not backwards compatible šŸ˜ž

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

first, there are techniques to make the project compatible with earlier versions of premiere.  Just do some searching here.  Of course any new features that are part of the project will not transfer.

Please tell us your system specs: OS version, Premiere version, amount of RAM, Hardware specs including graphics card and your source properties and sequence settings including frame rate and codec.  

Software updates often put great demands on your hardware so never a good idea to start editing in the update until you're sure it's working properly.   

And are any of your sources from screen captures or recorded on a smartphone.  If so, the problem may be caused by clips with variable frame rates which can cause inconsistent and unpredictable problems....

Here's how to confirm this diagnosis and fix it.use mediainfo to determine whether your source is variable or constant frame rate
https://mediaarea.net/en/MediaInfo/Download
if it's variable use handbrake to convert to constant frame rate setting the quality slider in the video panel to maximum
https://handbrake.fr
and here's a tutorial on how to use handbrake
https://www.youtube.com/watch?time_continue=34&v=xlvxgVREX-Y

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

The failure point had a jpeg picture inserted on Video track 3 over the video - however this is an edit I do all the time in many of my past videos so it has not been a problem until the update.  Will I still need to do this handbrake and then will i need to do it for each and every photo I add into the videos?

I am running the latest Premier Pro and Media Encoder - 22

I have Windows 10 Pro installed V21H1 

I am running a AMD Ryzen 5 PRO 4650G with Radeon Graphics 3.70 GHz and 32GB ram and Nvidia Geforce GT 710 2gb Graphics Card 

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

are you using any iphone or screen recordings?  If so, yes you need to convert to constant frame rate.  As I said vfr "can cause inconsistent and unpredictable problems...." so just cause they didn't happen before...  

 

what happens if you remove the jpeg?  If it exports then to a robust highquality format like prores hq, bring that exported file back into premiere into a new sequence and try adding the jpeg. 

 

Your sequence can also be corrupt...  create a new sequence with the same settings and select all in the old sequence and copy and then paste into the new sequence...

 

 

 

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 30, 2021 Oct 30, 2021

Copy link to clipboard

Copied

Its not the sequence - I exported directly from Pr as suggested in another post on the topic and the project renders completely without any issues - the problem seems to reside in the Media Encoder 

However, while this work around is a solution to my issue it does mean not being able to use Pr for any other projects while the render completes and makes the Media encoder and the benefits of it redundant.

 

The clips I was using was a single GoPro 10 recording in 4K30, no iphone or screen recordings. And I overlayed parts of the clip with pictures I had taken with my Sony camera.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Apr 16, 2022 Apr 16, 2022

Copy link to clipboard

Copied

after the latest update, april 2022 , i'm having same issues. when ME is running, after a while PC crashes. all Drivers are the latest version.when i export directly from premiere it works. this is so frustrating. in the last 6-7 years never had issues with adobe. this time this seems very bad. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Apr 16, 2022 Apr 16, 2022

Copy link to clipboard

Copied

LATEST

I've also had issues with ME.  Since October I have not used ME until this week when exporting straight from PR started giving similar GPU acceleration errors.  I decided to update ME and try to render there but the estimate moved to 16 or 17 hours from the usual 30-45mins.  I eventually played around with CUDA vs Open CL - I have an AMD system with Nvidia graphics card so CUDA should work but switching to Open CL seemed to have allowed the video to finally render after multiple attempts since Tuesday evening.  

Also try deleting cache memory - don't know if it helps or not but I was desparate and tried it a couple times.  I even redid the whole edit yesterday afternoon and left out warp stabilistion so not sure what it was that eventually made it work but it did late last night...

Votes

Translate

Translate

Report

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