Bug Reports

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

Media encoder is not installed on my device and even upon reinstalling and uninstalling this popup will still appear at random even if Creative Cloud is completely closed and it is not in use at all. I have tried signing out, repairing creative cloud and installing the version it seems to be stuck on (v.26.4.4) but this issue persists even after completely restarting my computer. No matter which option i press it continues to reappear and open the entirety of Creative Clourd Desktop at random.   

After updating my Premiere and Media Encoder, now when I send to Media Encoder to export, the captions disappear in Media Encoder.  I have "Burn Captions" checked and everything and it still doesn't work.

I keep getting this error message (amecommand Initilization error 1), when I try to render a video in Photoshop & Photoshop Beta, both the newest versions.I uninstalled and reinstalled Photoshop, Bridge & Media Encoder, but still doing the same thing. I restarted laptop (macbook pro), restarted the apps, uninistalled the apps then did a laptop restart before reinstalling, and still.. no luck.   I tried to open Bridge to render through there, but Bridge keeps force quitting before it even fully loads the app, so that's of no use. Older versions of Photoshop and Bridge did not work either and produced the same out come (photoshop still gives error message when renderinig video and Bridge force quits when app is is loading up)An Adobe employee responded with this since I originally posted in the Photoshop forum: "When you work in Photoshop, it is just sending the file over the Media Encoder. The error you are seeing is telling us that Media Encoder is no respon

Últimamente Media Encoder no hace más que causarme problemas, pareciera que de forma aleatoria decide renderizar con la CPU en lugar de la GPU. Si renderizo dentro de Premiere, veo en el administrador de tareas que se usa en su mayoria la GPU y el renderizado es rápido. Si renderizo EXACTAMENTE EL MISMO PROYECTO dentro de Media Encoder la mayoría de las veces renderiza usando 100% del CPU y tarda mucho, pero mucho más tiempo. Entonces esa respuesta que leo en todos lados de que "ciertos efectos usan gpu y otros no" no tiene nada que ver. El mismo proyecto pasa de durar 1 hora de renderizado en Premiere a durar casi 6 horas dentro de Media Encoder.

Hi there, Here's what I'm doing:  I have a 4k video of someone talking to camera, so to add variation, I zoom in and out to different fixed positions. (I.e. scale to 100%, to 120% and 140%).  To make things easier for me, I set up different adjustment layers with a transform effect on them (on source) and scale to taste so I can then drop them on the timeline whenever I need to. I name them accordingly, "camera 1", "camera 2", etc... When I render via Premiere, things look all right:  But when I render using Media Encoder, the issue appears:  Media Encoder seems to be scaling from the upper corner of the videos instead of from the center of the videos... So I don't know if it's a bug nor what might be causing the issue. Do any of you have an idea why this might be happening? I'm using Windows 10, the version of Me is 25.1 (Build 65) and Pr is 25.1.0 (Build 73) Best,Mauro.

I do not often use Me and I had no idea this software is so ridiculously slow. Now that I'm looking at the elapsed and estimated times this gives me the impression that Media Encoder does not ustilize CUDA or uses the e-cores of my Intel CPU alone. This is my 48 minutes long project and after I started rendering the video, shows there's 10 (TEN!) hours left to finish. What is wrong with this software? The CUDA is activated, I tried making Me window active - the estimated time does not change at all. My CPU is 50% loaded, my graphics card is barely loaded though I'm rendering out into HEVC-h265.In comparison Premiere Pro rendered the same project out in ONE HOUR yesterday, though it's window was not active - I was watching Youtube during the whole rendering process.   I think there's a bug in it... Adobe, please see to it.Win10 updated, RTX 4080 with 551.61 and an NVIDIA fix driver, i7 13700 KF, 64 Gb, SSD.Premiere Pro 24.2.1, Media Encoder 24.2.1

Hi. I am using AE 2025 and ME 2025 on Windows 10. I was noticing some drops in image quality when rendering in After Effects so I decided to attempt using Media Encoder instead. At first my video seemed pristine once it finished rendering, but upon taking a closer listen, I notice that around the midpoint there is some clicking and popping at certain instances, like you might hear from a dirty or worn vinyl record, or from audio that seeps too much "into the red," aka clipping. As the video goes on this seems to be more frequent of an issue. (Note, these sounds are perhaps not easily noticeable to the average listener, but at louder volumes or perhaps on a second listen it is probably noticeable. Given that the audio for this project is music, this is rather unoptimal. More or less rubbish even still.) This is very upsetting, after waiting a fair amount of time for the video to finally render, after having to restart to fix some issues on my end. However, I am fully confident

i have ame 25.0 installed but the creative cloud not showing the update to 25.1 . i go online and the update says my computer is not compatabile

Every time I'm sending a .aep to a render queue, and then hit play button in AME, I have an issue - 'File doesn't match the source'. Though it cannot apply to the real situation, as all my files is located in one folder and the path in AME definitely matches the real source file path.I use Adobe Media Encoder Version 23.2.1. Build 2.After Effects 23.1.0, Build 83.MacOS BigSur.Please, consider the issue.