Master the art of compression, share and learn.
Recently active
When using (most) adobe apps, I get tooltips that appear on my current window from background windows. An example of this:I click the ‘output file’ path in media encoder. It opens an explorer window. The tooltip for hovering over the ‘output file' path then appears from the previous window on top of the current window (basically displaying the full path). I cannot interact with anything within the grey tooltip box, as it is from a previous window, and each time this renders that part of my screen useless until I close, and re-open the window to reove the hover tooltip. This happens only with Adobe apps, on After Effects, Premiere Pro, and Media Encoder. The tooltips are broken and often appear during ‘hang times’ or loading events between windows.The only way to solve this is to just ‘hope’ it doesn’t happen when I reload it again, or try navigate ‘around’ the grey tooltip box until I go back to the inactive window.
I have tried a dozen different ideas from the forums and can't find a solution.Windows 10, i7-7600 cpu @ 2.80GHz8gb ramAME CC 2017 (version 11.1.2.35 of AME)Created a video in Premiere and AME just stops and hangs when it reaches a certain part of the video. Premiere won't export it either. I have created dozens of videos so I have no idea what's different this time. The video is about 10 minutes of 4k drone footage with a music back - super simple.I have reset Premiere (shift-alt on startup) and deleted all the cache files. I rendered the clip where encoder hangs and then added it back, then I deleted the clip entirely, then I deleted the clip and the music track and no matter - it stops in the same place every time (about 14% done with Premiere, and about 14 minutes in on what AME estimates is a 2 hour job).I read a few places that people had a "bad clip" in their video, and once they removed it it worked - how on earth am I supposed to find the one "bad" clip if premiere previews fi
I am unable to successfully render from Premiere to AME, timeline is very basic with one gaussian blur and lower third mogrts. It says failed, or it just stops and restarts rendering.This is one error I snapshotted.Since it shows GPU error, I cleared all premiere cache with no open file and restarting the program (full cache clear) and I exported using CUDA with fail, and OpenGL with fail.I then uninstalled Nvidia app completely, reinstalled and installed a fresh studio driver, rebooted, no luck.I also couldn’t collect and render on a backup machine because it said it couldn’t find a file that was online, located and working.The only way I managed to render was a direct export from Premiere SPECSIntel Core Ultra 9 275HXNVIDIA GeForce RTX 508064GB DDR5 RAM2TB M2 SSD [OS, ADOBE, PPRO PROJECT FILE, AE FULL PROJECT]2TB M2 SSD [PPRO FOOTAGE, CACHE]All latest Adobe 2026/Win11Home/and Nvidia Studio DriverAlienware AW2725DM 27"DELL SE2419HR 24" I also have 100s of these in the log:Have it Fixe
Right now there's no way to know a render is done without sitting at my computer watching the progress bar. Since renders can take anywhere from a few minutes to several hours, I'd love a push notification to the Creative Cloud mobile app when an export completes so I can step away from my desk and get pinged the moment it's ready.Ideally the notification would tell whether the render succeeded or failed and include the file name and total render time. A simple toggle in preferences to turn it on or off would be perfect.
There is a critical bug in the Premiere Pro / Media Encoder API (app.encoder) where attempting to programmatically queue a sequence using an HEVC (H.265) preset fails entirely. While the API seamlessly processes H.264, ProRes, and WAV presets, passing an HEVC preset results in a silent failure—Media Encoder simply drops the request without adding the item to the queue or returning an error code.Scope of ImpactThis is not an isolated plugin issue. This API defect completely breaks the core functionality of major industry-standard automation extensions, including: Excalibur (by Knights of the Editing Table) RenderSegments Blinkl.io Any workflow or custom JSX script utilizing the Adobe API to automate exports to HEVC is currently non-functional.The Inefficient WorkaroundCurrently, editors are forced to use a highly disruptive workaround: Trigger the scripted export using an H.264 or ProRes preset to successfully force the item into the Media Encoder queue. Manually select the queued
This has been happening for about two years now but it’s inconsistent so I have no idea what’s causing it. Basically the entire comps is exported in the upper left corner and the rest is black. Happens with different projects, different pixel sizes, different frame rates, different plugins used. I mainly use Media Encoder from After Effects, so I have no idea if it happens with Premiere too. The only thing that seems to be consistent is that it generally happens on bigger projects, where there’s a lot of materials, although the exported comp might not necessarily be heavy or complex.In AE the comp exports just fine.I realized that the bug appears in the preview as well, and if I change the pixel size of the export inside Media Encoder even of just 1px then it goes back to normal. Changing the export to Mp4 or to Quicktime doesn’t solve it, nor changing the bitrate. Both After Effects and Media Encoder are up to date, right now it’s AE 26.2.1 and ME 26.2I’m on Mac Os Tahoe 26.3.132 GB
As the headline says you can have the same profile with different settings.Problem is that ME is not overwriting the current settings if you change a setting and then save it as the same name.
The order of the Media Encoder queue has been reversed. Items are now added bottom-to-top and the queue runs in that reversed direction too. There is no option that I can see to revert this back. I assume this is a bug, as nobody would have requested this as a feature.
Hello,I am seeing what looks like a reproducible issue with H.264 Blu-ray export in Adobe Media Encoder on Apple Silicon Macs.I tested this on the following machines, and all of them showed the same problem:Mac mini (M4 Pro) Mac mini (M4) MacBook Air (M4)OS:macOS SequoiaAME versions tested:AME 2024 AME 2026Using the factory H.264 Blu-ray preset, Media Encoder creates an .m4v file that is not playable even in VLC. Because it already fails there, this seems to be a problem with the exported file itself, not just a Blu-ray authoring issue.I have not tested older Mac generations yet, but I can confirm that the same version of AME on Windows exports correctly.My current workaround is to export a high-bitrate AVC file on Mac, move it to Windows, and re-encode it there before authoring. That works, but it is not practical for long-form projects.I also checked one of the exported files with ffprobe, and it was detected as raw h264 with Duration: N/A and inconsistent timing information, which m
I'm trying to convert ProRes 4444 with alpha to a HEVC H265 with Alpha. I'm on an M1 Mac Studio (running Ventura 13.2.1). I've seen people say "hardware encoding" needs to be selected in Media Encoder (23.2.1), but it is not selectable. I've tried this conversion using Premiere and in also Mac finder using "Encode Selected Files"; everything seems to work correctly, but when I test the finished HEVC in AE or Pr, they never have alpha channels. Just black where there should be transparency. What am I doing wrong? Thanks.
The new masking feature is great imo, but they sometimes break / disappear when exporting through Media Encoder. I have experienced this when using the object mask tool to then copy a mask into “opacity” to essentially create a layout roto. Hoping this will work soon, or there is some solution to this, because I mainly use Encoder to render, as I have to do a lot of bulk exports.
Hi there, I work as a video editor, and usually create videos in bulk on my home PC. To make rendering easier, I queue all the videos I edit with AME. I've been having issues with AME, however. Because I usually stack a lot of videos up at once, I'd still like to use my PC to do other stuff, such as playing games or watching videos on YouTube. Doing this, as well as editing videos with Premiere while the queue is running, seem to make the GPU driver crash. Whenever it crashes, rendering won't work until I restart my PC.I can't remember when exactly this started happening, but I'm pretty sure switching to Windows 11 had nothing to do with it. I've run both the Studio and Game Ready NVIDIA drivers, both resulting in the exact same problem. Could this just be a sign of my GPU failing, or is something else going on? I've attached my AMEEncodingErrorLog in the attachments. Hope someone can help me out here. I get very frustrated whenever this happens, and fixing it would save me a
Hello Adobe Team,I would love to suggest adding a built-in LTC timecode embedding feature to Adobe Media Encoder, similar to the functionality offered by Tentacle Timecode Tool.It would be extremely useful to have the ability to automatically detect and embed LTC timecode directly into video files during the encoding process inside Media Encoder. This would simplify post-production workflows, save time, and reduce the need for external software.For professionals working with multi-camera productions and audio synchronization, this feature would be a huge improvement to the Adobe ecosystem.Thank you for considering this feature request.Best regards,Mario Ponce
Files are being removed from queue when I Quit Media Encoder, but my ME Settings/General/Remove completed files from queue on exit box is unchecked.I often want to modify a render setting, or view the log for one, and will have quit ME first.MacOS 15.6.1Media Encoder 26.2.2 build 2Macbook M1 16”
Dear Adobe,Media Encoder is called Media Encoder, not Media Encoder But Only If You Don’t Need Professional Image Sequence Naming.Please add advanced filename token support for image sequences:[####], ####, %04d, {frame:04}Expected output:SHOT010_KING.0001.pngSHOT010_KING.0002.pngCurrent goblin output:SHOT010_KING.[####]01.pngThis breaks pipeline cleanliness, batch workflows, farm handoffs, conform logic, and the sanity of anyone who has ever touched a render queue.Suggested fix:Add a preference called:Enable advanced image sequence filename tokensHide it under Advanced if you must. Put a skull icon next to it. Make us sign a waiver. But please let professional users name frames like professional users.Respectfully,Every TD, compositor, editor, and sleep-deprived human exporting PNG sequences
When I launch AME (directly or when it is launched from ingest settings for a Premiere project), the renderer defaults to to “Mercury Playback Engine Software Only” with no option to change it to any hardware acceleration option. If I open Preferences and clean the Media Cache database, the renderer will give me the Hardware Acceleration options (CUDA or OpenGL). I have verified all my perferences/settings favor hardware acceleration, cleaned/remapped media cache and cache database folder destinations for all adobe programs, clean install of latest NVIDIA studio driver, reset AME preferences, performed Windows updates, verified the GPUSniffer is identifying my GPU (it is), reinstalled AME. None of these solutions have solved it. The issue does resolve when I clean my media cache database within AME, but I must do this each time I launch AME, which is not ideal. System: Intel Ultra 9 285HX64GB RAMNVIDIA RTX PRO5000 Blackwell GPUOS Drive: 1TB M.2 SSDMedia and Cache Drive: 2 TB M.2 SSD
just 1 hour video just one hour. please help its too slow
Take Control of Your Video Attribution with Content Credentials at Export Adobe Media Encoder 26.2 (April 2026) makes it easier to ensure your videos carry the right creator information when they leave your pipeline. With Content Credentials applied directly at export, you can define who you are, how your content can be used, and what information travels with your media—all from within Export Settings. 🔍 TL;DRApply Content Credentials preferences at export Choose which creator details are included, including verified name and social media accounts Specify Generative AI training and usage preferences Review what’s embedded directly in the Output Summary✨ Why this mattersContent moves fast—and once it’s out in the world, attribution and intent can get lost. Content Credentials help ensure your exported videos include:Trusted creator identification Linked social media presence Clear preferences around generative AI training and usageWith Media Encoder 26.2, this information is applied au
It would be very helpful to have a keyboard shortcut which clears the media cache of Media Encoder. I often have to clear the cache for changes made in After Effects to be reflected in Media Encoder. As of now the only way I can see to do this is from the menu or in Finder.It’s not a huge deal but it would remove a few extra steps which I’m doing multiple times a day.Thanks!
It would be nice for Adobe Media Encoder to have naming tokens just like within the After Effects Renderer, for example when exporting a composition named [projectName]-[width]x[height]-[YYYY-MM-DD] it will automatically name your export to the project name + size of the composition + the render date.
I would like to append a custom name to the end or beginning of a file name on export. Yes, I know you can select an option saying "Append preset name to filename on export", but I don't need this all the time. It would be much simpler if this was an option that is chosen within the preset itself. This would create much more flexibility when exporting.
Exporting a 10 minute, most R3D footage with AE comps and third party fx. The plugins used is digital anarchy flicker free and deep glow—never have issues with either. Renders usually take about 25-30 min. Today on the latest build, it took 5 hours and then once I came back, it had restarted the render and made a duplicate.Since downgrading to 26, it seems more stable except render times are still 2-3 hours. Ryzen 59050x64 DDR4RTX 4070ti4tb NVME
Hi, I am trying to use a watch folder to export out hundreds of proxies during a shoot day. The workflow is like this: Action filmed -> Copied off camera card to Hard drive -> *Hard drive folder will be a designated "Watch folder"* -> AME will be auto encoder this raw footage to a proxy preset that will live locally on the comp for quick edits during the shoot.This all works amazingly well, however when i copy over multiple clips into the Watch folder, AME encodes them, then places each "source" clip, into its our folder. Please see screenshot below Is there any way to change it so that they all dont appear in their own subfolder? Many thanks! [Moderator note: moved to proper forum.]
When I export a video directly from Premiere Pro, all captions and text graphics render correctly.However, when I send the same sequence to Adobe Media Encoder (using batch export), the captions and text elements are missing in the final render.I’ve already tried:Using different fonts Reinstalling Premiere Pro and Media Encoder Trying different versions of Adobe softwareBut the issue keeps happening only when exporting via Media Encoder. version: 26.0.2
I have a project. In Premiere I can render it for 20 minutes, but in Encoder, it’s 60 minutes. Why?Why would anyone deliberately slow down my work? I notice this sometimes in different projects and different software versions. I thought the rendering time would be the same or even faster than in Premiere
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.