Master the art of compression, share and learn.
Recently active
What’s New in Adobe Media Encoder 26.2The April 2026 (26.2) release of Adobe Media Encoder introduces an important update focused on Content Credentials at export, giving creators more control over how attribution and identity information travels with their video content. 🔍 TL;DRNew in 26.2: Apply Content Credentials preferences directly when exporting Configure and save preferences in the Export Settings panel Choose what information is included, including linked social media accounts See the official Help documentation for more details here. 🎬 Apply Content Credentials preferences at export Adobe Media Encoder showing the Content Credentials tab with options to apply preferences at export.Adobe Media Encoder now lets you customize and apply Content Credentials during export, directly from the Export Settings panel.In the Content Credentials section, you can:Open the preferences webpage using Set preferences Choose what information is included in your exported video Optionally li
Welcome to the Adobe Community! For an effective community experience, here are a few things to keep in mind while posting on the community that will help us assist you better.❶ First, make sure that you use the Search this community area on top to see if a similar topic already exists on the community before posting a new one (It can be an Issue, a Bug, or a Feature Request). ❷ When you hit the Post to Community button on a community board, you will be in the editing mode that looks like this: ❸ Choose the Conversation Type that you think best describes what you are writing about. Discussion: Any topic that is not a bug or an idea is considered a discussion. If you want to know how a feature works or if you want to report an issue, or you want to start a conversation with other community members, don't be shy: use Discussion as your conversation type. Bug: This conversation type empo
After Effects and Adobe Media Encoder 2020 are rendering h264 codec MP4s too bright. The colors are washed out slightly and what I'm assuming is a gamma shift. I'm using Windows 10, After Effects v17.1.4, Adobe Media Encoder v14.4, and Nvidia driver 451.77. This issue does not exist on After Effects 2019 and Adobe Media Encoder 2019. The MP4s look as you would expect, using identical settings for export.One additional finding was that using After Codecs plugin, I'm able to export an MP4 using the x264 codec and the colors are correct. That is also using AE and AME 2020. So, from what I'm gathering there is definitely an issue with AME 2020. I find this annoying issue with nearly every release of AME, and have had it pop up off and on since 2004. This is not an issue with playback between video players, but specifically a color shift in the actual render. I'm not using any display profiles, and have After Effects set to not use a Workspace color profile in Project settings. Have also te
I'm having a problem with video, exported as MP4 - the colors appear to be washed out.However, when using After Effects for exporting, the colors appear correct (black as #0C0C0C, which is close enough to the real color, which is #0D0D0D)I have read other posts in this community and tried exporting software- and hardware, configuring LUT etc. but no cigar. Initially, I thought it was the player, since the same video appeared different in QuickTime player and VLC, but as mentioned, it can be solved by exporting from AE.When exporting as .MOV from AME, it's almost spot-on.However, I would very much like to continue using AME, since it contains a lot of functionality that I take advantage of and gives me a boost in production. Any ideas?
As we prepare for our upcoming version 27.0 release of Adobe Premiere, After Effects, Media Encoder, and Audition, we are sharing an important update regarding Macintosh hardware compatibility. Beginning with version 27.0, our video and audio applications on the Mac platform will require Apple silicon (M1 or later) processors. Intel-based Mac systems will no longer be supported for v27.0 and future updates. What Macintosh Users Need to Know Intel-Based Macs: You can continue installing and using version 26.x. Security updates for v26.x will continue per our standard support lifecycle. To update to v27.0 upon release, an Apple silicon Macintosh will be required. Apple silicon Macs (M1 or newer): No action needed. You can update to v27.0 as normal. Moving exclusively to Apple silicon on macOS allows us to focus on modern architecture and hardware acceleration across our video and audio applications. This update also aligns our roadmap with Apple’s transition roadmap: Apple has announced
Media Encoder 26.3.1 – ProRes 4444 exports black/transparent video while Premiere Pro exports correctlySummaryAdobe Media Encoder 26.3.1 fails to export valid video when encoding a Premiere Pro sequence to Apple ProRes 4444.The exported file contains valid audio, but the video is either completely black or appears as transparent (empty RGB channels).The exact same sequence exports correctly when exported directly from Premiere Pro.The issue only started after updating to the 2026 versions of Premiere Pro and Media Encoder.System ConfigurationOperating SystemmacOS (Apple Silicon)Hardware testedMac Studio M1 Ultra MacBook Pro M2The issue is reproducible on both systems.Adobe versionsPremiere Pro 26.3.0 Media Encoder 26.3.1Source MediaApple ProRes 4444 Generated by an animation software No alpha channel in the source footageThe sequence also contains a few graphics/images with transparency, but those are rendered correctly when exporting directly from Premiere Pro.Steps to ReproduceOpen t
Hello,Since updating to Media Encoder 2026, I have encountered an issue when exporting vertical videos (using a blurred background layer to fill the 16:9 frame) to MXF OP1a.The exported video results in a black or very dark artifact/edge on the left side of the frame.Additional Details: This issue does not occur when exporting directly from Premiere Pro using the exact same project settings. This issue did not happen in Media Encoder 2025 using the same sequence settings, project files, and export presets. Disabling "Enable Smart Rendering codec" in the export settings does not resolve the problem. Could the team please look into how the 2026 version handles color management or rendering on MXF OP1a containers for vertical compositions?Thank you!
Hey, this is my first time editing in After Effects, im using the 2024 version and i only have 5 plugins installed; sapphire, bcc, universe, topaz and twixtor. Ive been trying to export my project for about 4 days now and it doesnt seem to work, i always get the same crash message, at first it was only during a certain part of the video but now its happening in different timelines too. Ive changed the format from H.264 to QuickTime and the renderer to MPESO, since i heard that could fix it, still nothing.Im using my gaming PC to edit my videos, my graphics card is an NVIDIA 4060 and i have 32gb of RAM, ive tried rendering in the AE queue and in the media encoder, both dont work.Is there any way i can export it? Is it some plugin causing the crash? Thanks.
I am not asking for AV1 to replace intraframe editing codecs, but basic decode/import support is long overdue and would immediately improve real-world workflows for a large portion of your user base.Please prioritize adding native AV1 support to Premiere Pro. It is a modern standard, and its absence in 2026 is increasingly difficult to justify.
I have some serious issues trying to manage the queue in Media Encoder (v26.3.1). I loaded 250-odd items into the ME queue. After a couple has processed, I changed my mind and stopped processing the queue (red Stop Queue button). I then closed ME down for the day.Next day, I restarted ME and I found that the Queue pane was empty with the status saying 2 of 252 items processed, a bad sign IMHO. The Start Queue and Stop Queue buttons were greyed out. I dropped another file into the Queue pane and Start Queue turned green. I clicked Start Queue to start the conversion. ME then started processing the original queue contents from the previous night. Not what I wanted and a bit unexpected.It seems I need to clear out the old queue. There must be a way to do this but I can't find it. I can't select the files and remove them individually as the old queue members are not visible since I restarted ME.So, two questions:1) How do I clear the ME queue?2) How do I redisplay the queue members after
Hi all, I am currently experiencing an issue when batch exporting from Premiere Pro; When I batch export sequences using Media Encoder, they all seem to have the music levels way too loud - and does not accurately reflect the timeline. I’m certain the issue is with Media Encoder, as when I export my video within Premiere Pro, the audio levels are all correct. I’m not sure what’s causing this but I’d appreciate any advice on solving the issue as my job requires a lot of batch exporting.I have tried reinstalling both Media Encoder and Premiere Pro, but the issue persists.It is strange how it’s always the music track that seems to be the one boosted.For context, I am running Premiere Pro Version 26.0.1 (build 3) and Media Encoder 26.0 (build 60) on a MacBook Pro (Nov 2024) w/48 GB Memory on macOS Tahoe 26.3.It may be worth noting that I do run plugins in Premiere Pro, such as Artlist.io, Premiere Composer, and a select few from Knights of the Editing Table - Not sure if this could cause i
Not sure how to resolve this, but ME takes up gobs of memory during the encoding process no matter what I seem to do to alleviate it in Premiere. You can see screenshots below (but total memory was up to 98.63 GB when it finished). In general, I've been trying to export a 1-hour long video. Originally shot on iPhone (.mov) and encoding to MP4. My system would either crash after an hour or so of encoding. I think converted the MOVs to MP4s and tried that approach before encoding, but same issue. I had to cut the video to 30 minutes just to get an export to work. There has to be a way to improve the memory usage on my system for this task.I'm running an M2 Mac, 24 GB, Ventura (can't upgrade just yet). I had all applications closed and only using ME. I was also using Hardware encoding (Metal). I tried Software encoding but it crashed on that as well (and 10 times longer to encode). I even tried medium bitrate but didn't make much difference.It seems like ME is super inefficient with
Media Encoder Version 26.2.2 (Build 3) Renderer menu is greyed out with Mercury Playback Engine Software Only selected. System Compatibility Report shows “No conflicts to report”.Tested with NVIDIA Quadro RTX 5000 driver versions 596.36 (most current) and 582.53 (previous) with identical results.Media Encoder Version 26.3 (Beta) has the same problem.
I'm being pushed more and more into Davinci Resolve due to Adobe's inability to compete and stay up to date and keep us in their walled garden. We need AV1 support. Intel and Nvidia have had hardware AV1 encoding support for quite some time now. If I need to use AV1, I have to export as prores, then convert to AV1, doubling the export time. I shoot long videos, between 1-3 hours in length, and converting takes an insame amount of time. The filesize and quality AV1 provides is crucial so some of my workflows.
I am migrating to a newer version of Adobe Media Encoder on my MAC (14.9 Build 48 to 24.6.1). I want to backup /migrate ALL Settings, Presets, workspaces, keyboard shortcuts, plugins, templates, scripts etc. I found a few steps from a google search but want to check with an expert to make sure I am not missing any other files/folders that I should migrate over. Also, since I am migrating from an old version to new version ensure that I am copying over only the files needed to ensure a smooth transition to newer version. Thank you in advance! Here’s the steps I found:1. ~/Documents/Adobe/Adobe Media Encoder/[Old_Version]/This is the single most critical folder for Media Encoder. This directory holds your actual, custom-created Encoding and Ingest Presets (like custom YouTube, ProRes, or client-specific export configurations). [1, 2]What to copy: Look for a folder simply named Presets. Inside, you will see a collection of .epr files. Note: If you have ever used Adobe's Cloud Sync featur
Hi everyone,I'm facing a ridiculous issue with Adobe Media Encoder where it completely refuses to use GPU Hardware Decoding for Sony footage, even though the new RTX 50-series hardware natively supports it.My Specs: CPU: Intel Core i9-13900K GPU: NVIDIA GeForce RTX 5070 Ti Driver: NVIDIA Studio Driver 610.62 (Latest) OS: Windows 11 The Problem: When exporting or creating proxies from Sony A7V source files recorded in XAVC S 4K 50fps (H.264 / AVC, High 4:2:2 Profile, 10-bit), Premiere Pro handles the footage fine, but Media Encoder completely drops GPU Decoding.Inside Media Encoder, Encoding is done via NVIDIA NVENC (GPU), but Decoding defaults entirely to the CPU.What I've tried: Hardware Decoding for H.264/HEVC and NVIDIA is explicitly checked in Preferences -> Media. Renderer is set to Mercury Playback Engine (CUDA). If I drop the XAVC S file directly into Media Encoder (bypassing Dynamic Link), it still ignores NVDEC. If I force-disable software decoding in the Consol
Quite often when I export a batch of videos from Premiere through Media Encoder, Media Encoder will export versions where the dynamic link from After Effects to Premiere hasn’t been updated. How can I fix this?
TitleAfter Effects 26.3.0 + Media Encoder 26.3.1 fail to export projects stored on SMB NAS unless Media Encoder is started first after rebootSystem InformationMac Studio M2 Max 64 GB RAM macOS Sequoia 15.7.7 After Effects 26.3.0 Media Encoder 26.3.1IssueSince updating to After Effects 26.3.0 and Media Encoder 26.3.1, exporting an After Effects composition to Media Encoder fails consistently when the project is stored on an SMB network share (NAS).The exact same workflow worked correctly before updating.Projects stored on the internal SSD export normally.Steps to reproduceRestart the Mac. Open After Effects first. Open a project located on an SMB NAS. Send a composition to Media Encoder. Start encoding.Actual resultMedia Encoder immediately fails with:"Output could not be created. Check whether the output is write-protected or locked."Sometimes the log also reports that the temporary After Effects project cannot be read.WorkaroundAfter every Mac restart:Start Media Encoder first. Clear
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
Upload from Premiere Pro to YouTube has only worked exactly *1* time. Every other time it gives me a “publish error”. I tried following the advice in forums, including this one (which itself had a bug letting me log in where it repeatedly gave me a JSON error saying “user not found.”) The other thread complaining about this problem is 8 years old, and it still seems like the problem hasn’t been fixed. I have tried signing out from Premiere and signing back in. That didn’t work. I tried signing out of YouTube on my browser and then signing back in. That didn’t work either. This continues to be a persistent problem.
Ever since I updated Premiere and Media Encoder, when I send my finished sequences to Media Encoder, for some reason the captions won't export with the video. They will only export through Premiere. I have my "Burn subtitles into video" option on and everything. Help.
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.
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.