Adobe Media Encoder

Apple recently announced support for Alpha with HEVC. This is great news. Does anyone know about it being available in Creative Cloud / Media Encoder. Looking forward to a lightweight / compressed codec that supports Alpha.  https://developer.apple.com/videos/play/wwdc2019/506/

Hi everyone,I’m writing a script to automate rendering in Adobe and using addDLToBatch to add files to the render queue. However, if the output file already exists, rendering does not proceed, and I need to manually change the filename or remove the existing file.Here’s the code snippet I’m using:var frontend = app.getFrontend(); if (frontend) { frontend.addEventListener('onItemAddedToBatch', function (eventObj) { $.writeln('frontend.onItemAddedToBatch: success'); }); var batchItemSuccess = frontend.addDLToBatch( projFile.fsName, format, preset, comp.dynamicLinkGUID, file.fsName ); if (batchItemSuccess) { $.writeln('Successfully added: ' + myFile); var encoderHost = app.getEncoderHost(); if (encoderHost) { encoderHost.addEventListener('onItemEncodeComplete', function (eventObj) { $.writeln('Result: ' + eventObj.result); $.writeln('Source: ' + eventObj.sourceFilePath); $.writeln('Output: ' + eventObj.outputFil

Hi, I've created a project in PPro (Beta) v25.2.0 build 117. All my sequences, except one, renders H264 and completes using AME (Beta) 25.2.0 build 117. This sequence renders 100% , but fails to compile the finished file (Audio/aac and video/m4v). It just shuts down AME (Beta) and when I re-open the program the render que has reset and is ready to start again like nothing happened. Prosessor Intel(R) Xeon(R) w7-2495X 2.50 GHzInstalled RAM 192 GBSystemtype 64-bit OSNvidia RTX 4500 Ada Gen driver 553.50 PS The sequence renders just fine in PPro (Beta). Thanks for any help

I have been waiting for more than 30 mins for the final video to be rendered. It's already 40 mins and it's barely 50% rendered. Never had this issue before. My laptop specs are as below and my GPU is RTX 3070. Anyone knows how to solve this sudden issue?     

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

For some reason, I have an untold number of files in my Media Encoder queue.I can't seem to delete them (select all - delete key) and I just keep getting Not Responding.Is there a way to start the program, clean, or force empty the queue?At this point, I can't use Media Encoder at all.JJ

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.  

Al momento de exportar un video en WEBM en Media Encoder la opcion de Alpha (que a lo que recuerdo en otras versiones era la de la foto) no tiene texto y no funciona. Quiero saber si aun funciona esta opcion ya que al momento de usarla ya sea seleccionada o no no funciona el ALPHA. (antes funcionaba)

Wenn ich aus Premiere eine Sequenz an ME weitergebe ist es (nicht immer) möglich, das Exporteinstellungsfenster zu öffnen. Dann ist auch ein Rendern der in die WS eingestellten Sequenz nicht möglich. Ich habe alle Standardvorschläge zur Abhilfe schon ohne Erfolg ausprobiert (MediaCache löschen, Neustarten etc.). Die Frage lautet, gibt es irgendwelche Kriterien für den Export von Sequenzen an ME, dass dann das Exporteinstellungsfenster in ME nicht geöffnet werden kann?

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

Hello everyone, I have a question, how can I use more memory and CPU usage during rendering in the media encoder? When I look at the activity monitor, they are not in high usage, even though everything is ok, I believe that my rendering could be faster if I used more processing power, but I don't know how to do this, can you help me? I will leave the PC specifications and images of the configurations below:Macbook ProM3 Pro18GB RAM*Premiere and media encoder are up to date and so is my operating system

Hello, great and powerful Adobe community.  I'm finding that no matter how I tweak my render settings, my video file sizes seem unreasonably large.  For example, today I rendered a 1hr Premier Pro edit using Media Encoder's YouTube 1080HD export preset, which produced a 1.8Gb file.  When I upload this 1.8Gb file to YouTube and then download it, the downloaded file is only 89Mb.  Seems like a huge disparity considering I'm using an export setting presumably optimized for YouTube specifically.  As you can see from my settings (below) I've got the target bitrates cranked down pretty low, to the point that the video quality already takes a noticable hit.  Any lower and the video quality is just poor.  What is YouTube doing to squish my 1.8Gb file down to 89Mb?  I notice a lot of 1080 video on YouTube looks crystle clear.  How can I acheive these small file sizes and still get acceptable video quality from Adobe Media encoder? - Preset Used:

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?

Good afternoon. I'm struggling with Adobe Media Encoder 2025. I need to deliver multiple file formats of the same video. The way have handled this in the past is to have a watch folder containing 3 ingest presets that would recompress and rename each output.  AME has thrown an error in the past saying I could not use an ingest preset in a watch folder... I managed it anyway. Unfortunately, it doesnt seem to be working any more. This is the process I used before: Render demo.mov from AE to the watch folderAME would process demo.mov using 3 ingest presets to demo_LRES.mp4, demo_HRES.mp4, and demo_MEZ.mp4.I would then copy the 3 mp4s to the projects Delivery folder. I do this for dozens of projects a day, and manually renaming all of them would take up a considerable amount of time.  It would also open the door for naming erros.Does anyone know how to accomplish this without using ingest presets in watch folders?

Hello,I have couple of old video tapes that are on my HDD. They are in VOB format, I wanted to re render them to more usuable mp4 that we could play them on TV. Unfortunately some of them are render badly, audio is completely off and doesn't match the video, I've tried rendering it with MPEG as audio and AAC and its still causing an issue.I'm rendering it using High Quality 1080p HD profile. Original Video is in 4:3 format but its not causing an issue to go 16:9 and higher res. Video is fine, just audio is causing me an issue.

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

Hi all,I just realized that when I use the "add to AME render queue" in After Effects, AME creates a temp folder with copies of the AE project in it when it renders. The folder names all have _AME appended to them, and the .aep files inside all have tmpAEtoAMEProject-compname as prefixes. After I've rendered successfully, is it OK do delete these folders and files? They are taking up a LOT of space. I'm guessing that it's fine to delete them, but wanted to check just to make sure. I'm curious if there is any reason to keep them.Cheers,Lori

Something is there I've been concerned about My PC is configured with Ryzen 5500 and GPU is Intel Arc A380 and 16GB RAMWhenever I export my video,encoder barely uses my gpuAnd it takes too much time to export since I use the stock cooler in my cpuThe first one takes maybe 3mins to be rendered but next ones gets really laggyWhat should I do? Is there any settings that I have to configure so it can use my GPU?I have already selected Mercury Playback Engine OpenGL