Bug Reports

The text and subtitle font in the video exported via Media Encoder looks different (this is not the case when exporting from Adobe Premiere) example: subtitles with Truculenta font in the video exported via Media Encoder become Times New Roman font

When I export video in any of the mentioned apps the apps crashes. It's been happening for weeks and I've tried reinstalling all of them as well as reseting the preferences. The interesting thing is that it works normally with the beta versions. Any suggestion?

Hi There, Versions of Media Coder after 2023 render out WebM files as a green video at a very small file size.  I've seen this reported before but it is still happening on newer versions of Media Encoder.  Please correct this before removing 2023 versions of the program. I can't attach my video file for proof because the format is not supported by your website so here's a screenshot for reference.  This was created on Version 25.1 Media Encoder 23.6.8 works perfectly. Thank you,Bobby

03/17/2025 02:27:38 PM : Queue Started- Source File: C:\Users\user\AppData\Local\Temp\Dying Light Part 6_5.prproj- Output File: C:\Users\user\Documents\Adobe\Premiere Pro\25.0\DYING LIGHT 2\Sequence 02_1.mp4- Preset Used:- Video: 3840x2160 (1.0), 60 fps, Progressive, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 01:39:44:01- Audio: AAC, 320 kbps, 48 kHz, Stereo- Bitrate: VBR, 1 pass, Target 80.00 Mbps- Encoding Time: 00:59:4103/17/2025 03:27:20 PM : File Encoded with warning------------------------------------------------------------Adobe Media EncoderCould not write XMP data in output file.------------------------------------------------------------***PLEASE ADOBE HELP***

Im working on a video in After Effects made from multiple assets (including other videos). One of these assets needed to be replaced, so i replaced the original file with the new one. When i try to export the newest version of my video, it will include the old assets that i have already replaced long ago. I have tried all of these things to get Media Encoder to export the right version:- Save the project before exporting- Close and reopen AE before exporting- Replace the asset again- Import a second copy of the asset and rebuild it (same position etc.) as it should look and delete the other version.- Clear and purge everything that can be cleared/purged in After Effects and Media Encoder- Export without that asset enabled and later do another export with the asset enabled- Many more things It didnt matter what i did, the part of the video with the replaced accet ALWAYS showed up as the old version.  The obvious thing that worked in the end was to go to the folder of the

1. 미디어 인코더에서 파일 이름과 경로를 지정하고, 사용자 정의를 클릭하여 인코딩 옵션을 변경하고 인코딩을 시작하면 마음대로 저장 파일 이름이 변경되는 문제가 있습니다. 2. 미디어 인코더에서 사용자 정의 옵션에서 비트전송율을 변경하면 지정해둔 저장 파일 이름이 마음대로 변경되는 문제가 있습니다. 버젼 25.1(빌드65) 

Hello, I have a complex MOGRT using heavy expressions and nested essential properties to build a calendar using JS calculations. This MOGRT renders and exports perfectly in Premiere Pro 25.1.0. However, when using Media Encoder 25.1, all calculations are broken and the calendar fails to build.So I figured : "well, let's prerender this part in Pr and ask Me to rely on prerendered files". But the results is the same, so I presume Media Encoder 25.1 doesn't use properly prerendered files when it is asked to. This may be a serious issue for editors relying on this feature to speed up their exports. Computer : Mac Studio 2023 - 32 GB RAM - 512 GB SSDMacOS Sequoia 15.3.2 Thanks for your support,

This is seriously urgent issue, I am trying to render a video but media encoder is not using my GPUI have RTX 3080TI laptop GPU of Nvidia & i am using Asus rog strix scar 15 laptop  I have tried exporting with & without maximum depth also with CUDA Adobe please help me 

Over the past couple years I've exported dozens of long (1-2 hr) 4K 60fps videos with both Premiere Pro and Media Encoder.  Rendering times were basically the same (about 3 hours per hour of video), so I usually exported with Media Encoder because it was easier to run in the background while doing other things (including working on new projects in Premiere Pro). After Abobe updated Premiere Pro and Media Encoder to the 2025 version, Media Encoder has become ridiculously slow.  Exporting a 2hr 4K60 directly from Premiere Pro takes about 6 hours, but exporting that same video with Media Encoder is estimated to take 320 hours!!!  And no, that's not just a time estimation bug; I once let it run for a few hours and come back to confirm that it had only rendered a minute or two of video. I've read that other people are having the same problem with the 2025 version, and that for now the only "solution" is to roll back Media Encoder and Premiere Pro to their 2024 versi

After updating to Sequia and the latest Adobe suite I've encountered a strange problem ingesting BRAW footage. We have a suite of Mac computers which are remotely managed so most users log in to standard accounts.In premiere Pro the ingest settings action is Copy and create proxies. If a user imports or drops a file into their Premiere Pro project it gets parsed to Media Encoder to be copied and a proxy created for it. This has worked well in the past, but now with the update and recently introduced BRAW plugin a problem has arisen. Whenever Media Encoder attempts to copy a BRAW file from the camera card an error occurs with the Copy of the file, the proxy is created fine but the original file is not copied. If the BRAW file is moved to a new location before adding to the workflow everyrthing works as expected. MOV files on the card will also copy and Proxy without issue. If an admin user uses the workflow, no errors occur. It appears to be a permissions e

Hello! I often do batch exports for my clients and I use some export presets. Recently, I noticed that "use maximum render quality" is left uncheck when I open the configuration, although it should be checked as the preset does have it checked. I have to manually open each configuration and re-check "use maximum render quality". Rest of config preset is fine. If anyon can fix the bug or has a solution, thanks!

Since updating to the latest version of both Encoder and Premiere, Premiere freezes when performing a batch export to media encoder. This happens whether Media Encoder is already launched or launched by Premiere. It will add the first video to the queue and then freeze, thereby requireing a force quit. A full computer restart will fix the issue only temporarily for one batch export, and then go back to freezing.  

Pseudo code const fileName = `${chapterMarker.name.replace(/\s/g, '_')}.png`; const outputPath = join(outputDir.fsName, fileName); const pngPreset = new File(presetPath); app.encoder.encodeSequence(sequence, outputPath, pngPreset.fsName, app.encoder.ENCODE_IN_TO_OUT, 0); expected result  `MPF_Scene_7_Shot_46_Frame_1255.png` 

I'm using Media encoder for 3 years. I cannot startup anymore. I always get this message. I tries deleting it. Reinstall. Older versions. Nothing works. 

Recently updated Premiere and Media Encoder to CC2025. Sending to Media Encoder, exporting is now 10x longer than just exporting straight from Premiere. Both have CUDA enabled. Any ideas?

When exporting projects from After Effects using Adobe Media Encoder (AME) to H.264 (MP4), the rendered output is tagged as Rec. 709 with a gamma of 2.4 (the TV broadcast standard) even when the project is set up and previewed with a 2.2 gamma (computer display) setting. Although the Preferences → Color setting in AME allows me to adjust the preview from 2.4 to 2.2, this change is not reflected in the final exported file.Steps to Reproduce:Set up an After Effects project in Rec. 709 with a desired gamma of 2.2 (for computer display).Export the project directly from After Effects to MP4 – the output appears correct.Export the same project via Adobe Media Encoder (AME) to H.264 MP4.In AME, adjust Preferences → Color (switching from “broadcast” 2.4 to “computer” 2.2) – note that the preview reflects the change.However, the rendered output remains tagged with a 2.4 gamma, resulting in a noticeable shift (e.g., darker shadows or a “white halo” in some areas).Workaround:Re-encoding the file

I originally posted this in the Pr forum, because I thought at first that that was the issue. After detective work, it became apparent that it's actually an issue in Media Encoder. The short version: When a comp has the Rotobrush effect on it and is rendered Prores 4444 + alpha through Me... and then later, the same comp has more roto refinements added... when the render is reattempted, Me will NOT render the new roto refinements. Every export of the new improved comp is identical to the original render. The details and an example: https://community.adobe.com/t5/premiere-pro-discussions/why-doesn-t-pr-reflect-ae-changes-rendered/td-p/15152634  This affects 2024 versions of the app (I explain why I still am using those in the original post.)Windows 11

This issue occurs in the latest version of Media Encoder and the one before that. Screenshots attached. When I render in Premiere, my RTX 4080 S is at ~80% usage, intel iGPU at ~20%, and i9 14900k at ~30%. When I render the EXACT SAME sequence in Media Encoder, the RTX is at less than 10%, no iGPU usage, and slightly less CPU usage. Exporting to a MP4 UHD 30mgbp file, Windows 11, footage is on a Samsung T7. P.S. The Renderer is set to CUDA and I set the encoder/decoder settings in the preferences to ON. This issue with render speeds came up recently without me changing any of the settings. Also, there's barely any effects on the timeline. It's just a few Lumetri Color effects and a logo with a blur.  

Media Encoder 2025 (25.1), WindowsUnwanted behaviour/bug. -Media Encoder Automatic Shutdown will turn off computer if the user presses STOP on their queue.I think it's safe to assume if the user is interacting with the program, to STOP it, that they do not want to shutdown their machine. At the very least it should ask the user if they wish to shutdown."STOP" button ≠ Queue Complete

I'm having a real doozy of a problem, and of course it's happening a couple of days before I have to send in a bunch of deliverables... On my current project, whenever I try to output anything, Media Encoder quickly uses up all my dedicated GPU memory, at which point it basically stops rendering. If I'm sending out multiple smaller outputs, each one eats up a chunk of GPU memory, and then the next one eats up another chunk - i.e. the usage increases step by step, instead of going up for one output, then down when that's finished, and up again for the next. The only way I can clear the GPU memory back to zero is to quit Media Encoder (and After Effects), so I pretty much can't queue up more than one output at a time - overnight batch renders are definitely out. Any thoughts? It's driving me a little crazy at this point. Switching to software-only in Media Encoder doesn't seem to help. One possibility: I'm working with ArriRaw footage - any bugs around that? We're in finis

I've created a lower third template on After Effects to use it on premiere pro, so I can change the name, etc. But when I send it to Media Econder, the effects that I put on the lower third (a neon effect) does not render on the video, just the forms of the lower third. But when I export on premiere pro the video come out just fine.

Hey everybody, I've been exporting video's in H.264 with NVENC Hardware Encoding for a couple years now, and it always has been working fine. But since today it suddenly doesn't work anymore. I've tried anything, I've updated my Nvidia-drivers to both the Game Ready and Studio Drivers, I've installed an earlier version of Premiere Pro and Media Encoder etc. etc. but nothing works. My hardware is:AMD Ryzen 9 5900XNvidia GeForce RTX 2080 Super32GB DDR4 RAMSamsung 990 Pro SSD And my encoder settings are:H.2643840x2160p 25fpsProgressiveVBR 1-Pass (35 Mbps target with 45Mbps max) Look, It's never been asn issue, and now when I wanna export a video with the exact same settings it suddenly doesn't work anymore, and I've also tried on other videos which I previously rendered. Now they suddenly don't. Even more curiously. For some reason, when I wanna export an After Effects-project with those settings in After Effects it does work, but than when I wanna use Media Encod

Adobe Animate/Adobe Media Encoder Headache :   So on a Mac running Monterey, Media Encoder 25 is incompatible. There are no older versions listed for download.   On a Mac running Sequoia Adobe Animate (Formally Flash) is also incompatible, even if Media Encoder works...THEY NEED TO WORK TOGETHER.  Animate/Flash is not even listed as a compatible programe "with bugs" as some others are, that's how unuseable it is on Sequoia.  So Adobe, we're paying for this legacy laggard .  Would you like to give me back access to a compatible version of Media encoder, since, you know. We're paying for it?

I am having a problem with Media Encoder 2025. I tried to redering my video and it gave me the following error I tried a second time and the same thing happened. Export ErrorError compiling movie. Accelerated Renderer Error Unable to produce frame. Writing with exporter: H.264Writing to file: D:\ΒΙΝΤΕΟ SONY CANON\My child.mp4Writing file type: H264Around timecode: 00:00:00:09Rendering at offset: 0,000 secondsComponent: H.264 of type ExporterSelector: 9Error code: -1609629695

IssueWhen exporting a 59.49 timeline to 29,97 the  source range indicator wrongly suggests i have only part of my timeline selected. See attached screenshot.Adobe Media Encoder version number: 251 (Build 65)Operating system: Windows 11 v.10.0.26100.1Steps to reproduceExport a 59.49 timeline to 29,97 have no in and outputs in the timeline.Perhaps add a second outputExpected result Source range indicator indicates complete timeline is selected for exportActual resultSource range indicator indicates part of the timeline is selected for export