Skip to main content
Inspiring
November 5, 2022

Media Encoder 2023 Renders Freezing/Hanging

  • November 5, 2022
  • 1 reply
  • 253 views

Hi all,

 

I'm finding Media Encoder 2023 is having an issue where my renders frequently freeze/hang.  I'll set up a large queue, let it run, and at some point in the queue it'll just get stuck at a random point in a file and then just hold there for indefinitely.  I also have an issue where it'll just sit there forever trying to connect to dynamic link but never start the render. There's a trick folks recommend online, to go into task manager, select After Effects from the background processes and hit "end task."  This works to some extent, but not every time and often I'll have to end task multiple times for media encoder to fix itself and continue working.

 

I have done some (though limited) research into my project files itself to see if there's a specific effect or animation happening on the specific frame that's causing media encoder to hang, and I'm fairly certain there's not. I think this is an issue with media encoder itself.  One argument in support of this is the fact that when media encoder hangs and then I "end task" the AE background process, media encoder will sometimes start back up and finish the file out.  So it's not like media encoder can't get past a specific frame or moment in the animation. It just gets hung up, essentially goes to sleep, and needs a jolt to get going again.

 

These are problems folks mentioned with 2022 as well -- it seems to be an issue across multiple machines (both my laptop and desktop) and cross platform (a freelancer of mine on mac has had the connecting to dynamic link issue as well). I have also tried uninstalling and reinstalling AE and AME to no avail.

While I appreciate that the "end task" option seems to jolt the program back into existence, I hardly would say this problem is "solved." Nor do I think suggestions that we should just render in AE directly are a solve either.  The ability to leave media encoder rendering while you continue to work is key and hasn't been an issue for years.  Even as recently as AME 2021 I don't think there were nearly as many issues with rendering speed and media encoder bugs as I've found in 2022 and 2023 so far.

 

Unfortunately, while downgrading back to 2021 has been a band-aid where the softwares run as they should for us, we run into issues where if anyone accidentally opens a project in 2023 and saves it, we then can no longer open that project in 2021 and we're locked back into 2023.

 

While I appreciate the effort Adobe has put into these UI updates for colored keyframes and a better track matte system, it certainly shouldn't be at the expense of a Media Encoder that works.

 

Adobe, if you have any suggestions of how to troubleshoot this issue or permanently resolve it, let me know.

 

(Running Windows 10 Pro on an MSI laptop and AVA Direct custom desktop.)

1 reply

Inspiring
November 18, 2022

FYI this issue seems to persist into 23.0.1. One video hung and sat rendering for 3 hours -- I restarted AME and it rendered fine in under 5 minutes without any changes to the file, just resetting it in the queue and restarting.  The next file ran for roughly 10 minutes then failed.  I quit AME, restarted and the same file just by resetting and starting the queue again rendered in about 2 minutes.  Another file was stuck "connecting to dynamic link" and no amount of task managering off After Effects in the background process would solve the issue. Quit AME, start again and it works. But obviously a major hassle to be constantly monitoring a queue and constantly task managing things off and restarting the app to make it work.

 

I've also found sometimes when things hang After Effects isn't running the background processes. Not sure if that's good or bad or what.

 

Just a note, this version of 23.0.1 should be totally fresh, since I believe I fully uninstalled AE 2023 and Media Encoder 2023, then fully reinstalled them with the 23.0.1 media encoder.

 

Am I alone with this issue despite the fact that it's happening across multiple machines on my end?