Skip to main content
K
Kastermaster
Participating Frequently
March 24, 2023

Adobe Media Encoder 23.2.1 slow media rendering/crashes

  • March 24, 2023
  • 6 replies
  • 319 views

Hello,

 

Since the update to AME 23.2.1 encoding of H264 video is very, VERY slow. I noticed that the media browser is also messed up since the newest version. Literally nothing shows up there. Also, trying to rename your output files (woich SHOULD bring up an explorer window) frewezes AME for minutes. Preparing the audio/video files seems to crash the app, but if you wait for more than an hour you'll find out it's just REALLY slow. Rendering after that, works just fine.

 

Reverting to v23.2 fixed the problem on my laptop, but not on my desktop.

 

I'm running W11 with the latest updates on both systems.

6 replies

K
KastermasterAuthor
Participating Frequently
August 7, 2023

It could be a very specific bug. The first part of the bug seems fixed. The second part, where the PREPARE part is really slow, still occurs occasionally. Some, but not all the times, killing the processes for One Drive and Teams and restarting them helps. After the PREPARE stage (which takes hours) the decoding is fast as usual (I capturd a bugged decoding progress in the screenshot).

E
Adobe Employee
eckiAMETeam
Adobe Employee
July 20, 2023

I successfully exported a Premiere Pro (Beta) 23.6.0.56 sequence to Adobe Media Encoder (Beta) 23.6.0.58 while Microsoft Teams 1.6.00.16472 (64 bit) was running on my Windows 11 21H2 machine.

E
Adobe Employee
eckiAMETeam
Adobe Employee
July 18, 2023

I'll try to repro on Windows 11.

K
KastermasterAuthor
Participating Frequently
July 17, 2023

Windows 11 21H2. Latest versions of Media Encoder (23.5) and Premiere (23.5.0) as well as Teams (1.6.00.18681, 64-bits).

E
Adobe Employee
eckiAMETeam
Adobe Employee
July 14, 2023

Interesting. Can you send me your system specs? This would be a really weird bug.

K
KastermasterAuthor
Participating Frequently
July 14, 2023

I have to add: this probably is a bug in M$ Teams as I am working in a Teams environment. Closing Teams and restarting it most times resolves the problem.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices