Master the art of compression, share and learn.
Recently active
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.
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.
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.
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.
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
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.