Bug Reports

Hi, We're having an issue in AME when selecting "Match Source (Rewrap)" as it sets the audio export settings to stereo, 16-bit as default despite the source file actually having 4 discrete channels with 24 bit audio.  The source file is ProRes 422 HQ. We pulled the file into Media Encoder so that we could trim the file and we wanted the export to match the source settings hence why "Match Source (Rewrap)" was selected. Do you know what could be causing this?  We have a workaround in place but the Match Source (Rewrap) should be reliable in matching the source settings.  Thanks

Media Encoder 24.0 (Build 54)Windows 11 Pro - 22H2 Build 22621.2428Encoding stops when the window loses focus. It starts again when the window gains focus.To recreate:1. Set any video encoding - i have tried prores to h264 and h264 to h264. 2. Click on a different winow, wait a bit - observe ME has stopped3. Click back on ME - observe that it picks up where it's left off.I went away for a few minutes the first time this happened, it really does stop encoding, not just stop updating the UI.  

Ver23の途中あたりからだったと思いますが、エンコード時に「最高レンダリング品質を使用」にチェックを入れても、チェックを入れていないのと同様の画質でエンコードされます。 たとえば4K30pで撮影した素材をPremiereの4K30pのシーケンスに読み込み、スケール200に拡大するような編集をしたとします。 これをBlu-ray（1920*1080）やDVD(720*480)用の解像度でエンコードするとき、Ver23.0までは「最高レンダリング品質を使用」にチェックを入れていれば綺麗な画質でエンコードできていました。 しかしVer23の途中から、「最高レンダリング品質を使用」にチェックを入れても、チェックを入れていないときのようにギザギザの画素不足のような画質でエンコードされます。（※Premiereのプレビュー画面では画素不足のようにはなっていません。） なお、ソフトウェアエンコーディングでエンコードすると正常に「最高レンダリング品質を使用」の画質でエンコードされます。 構成の異なる5台のPCでいずれも同様の症状が出ますので、GPUの問題ではなくMediaEncoder側のバグだと思われます。

I love Media Encoder for fast cutting or joining videos, and versions, etc. Sometimes, I won't open it for weeks, but then the next time I do, there's a bug chance it happens AFTER any update (I'm not even mentioning daily beta updates), and even after the install check sum verification it still takes a few minutes to launch. I have 0 plugins and since my usual need is a quick cut, it's VERY furstrating.   Would you have any idea to ease my pain ? Like "sort" my most frequent codecs, and load the rest in the background once my tasks are done, not everything at startup…Then it sounds more like and idea and feature request than a bug, but… well…

So we've all previously commented on the fact that Media Encoder 2023 will just stop encoding (not crash, mind you, just literally stop in the middle of an encode with no errors, no message, nothing). The workaround that we all found was to pause the encode, force-close AfterFX, and then resume the export.It happened a lot in ME2023, but it's happening even faster in ME2024. The solution is apparently the same, but this is not acceptable because it requires me to literally babysit an hourslong encode to keep doing this. And As I discovered in ME2023, restarting AfterFX doesn't always get Media Encoder running again. Yet, I've never had any meaningful message traffic from Adobe on this.Adobe: PLEASE FIX THIS RATHER EGREGIOUS BUG! Tell me what log files I can provide or what steps I can take to capture information that would lead to fixing this. Problems like this are why I still have to use ME2021 for all of my project encodes; on average it's not quite as fast as the more recent versio

Adobe Media Encoder keeps showing Bebas font missing. Sometimes it doesn't cause a problem sometimes it does. And this is really disrupting my workflow and has been a problem for like a year. I've reported it before and Adobe said "it is a known problem" but that was like a f!#%#ing year ago. If I preview it via encoder you can see the fonts actually look correct. But, in premiere it looks complete f!!@#$ing different! Is this a joke? I mean, I'm paying a lot of money for this chronically broken software. 

Hi, I am rendering the AE comp through the media encoder. A small part of the video from left side is appearing at the right side of video. While, the content is fine in AE source. It looks like it is mirroring in the form of a strip. Do anybody know about this issue? Please help me out of this error.

Han reducido el uso de las GPU sin razón alguna. Ahora tarda mucho más en exportar y no se aprovecha mi computadora como debería. Es ridículo que haga un render en el doble de tiempo que antes, y deje la GPU sin usar. ¿Están poniendo fallas para obligar a los usuarios a comprar la nueva generación de procesadores y tarjetas gráficas? porque es increíble que de un momento a otro vaya empeorando el rendimiento.

Immer noch Probleme mit der Hardwareunterstützung für H.264 Exports (Selektor: 9Fehlercode: 3). Ist da eine Lösung in Sicht?

So I've been using Media Encoder to render my animation but for some reason when I attempt to encode it gives me this type error non and it refuses to encode anything for me.

I am currently in the process of creating proxies for a doco using Premiere's create proxies workflow and once in media encoder it will get about 30 or so clips in before it compeltely crashes my entire computer.Step by Step: - I import MXF footage from FX6- Select all the footage in Card 1 and 'create proxies' - I choose Quicktime ProRes (high bitrate) and begin proxy process- It opens up Media encoder and begins creating proxies without issue and will randomly drop out no matter which proxy settings I chooseI have used this workflow multiple times for other cameras and never had an issue. Does anyone know if this is an update issue? an MXF issue? Or my computer? How do I fix this? Specs: iMac Pro (2017)Processor: 3.2 GHz 8-Core INtel Xeon WMemory: 32 GB 2666 MHz DDR4Graphics Radeon Pro Vega 56 8 GGMedia Encoder v22.5Premiere Pro v22.5

Just another in the long list of awful changes 2023 PP and ME has made. I encode multiple videos from one long sequence. Before, it used to encode all of them sequentially and add _* (* denoting whatever number file it's up to when exporting). Now it just replaces the old one.Firstly, why change this? Yet another thing that's been fine for YEARS that gets changed at the drop of a hat. Secondly, how do I change it BACK? Once again I see no options for a stupidly changed feature to be moved back. 

AMD Ryzen 9 3950X 16-Core Processor 3.49 GHz, 64 GB RAM,  Windows 10 Pro, NVIDIA RTX-3080 GPU AME V23.6, up to date;    PP 23.5  Media Encoder totally freezes pc at random points while encoding a particular project; also happens when exporting directly from PP. I have to hard-stop the pc and reboot. Have also had pc reboot on its own while encoding the project in AME. When the freeze occurs, I can do nothing at all with the pc, can't even move the mouse cursor or get any response whatsoever from the keyboard. This is happening with an old project that I'm making changes to. Originally, the project was on the internal drive. Now, it's stored on an external USB drive... I've edited the project on that USB drive, and all seems ok in Premiere. But when I export the project from PP, or encode it in AME, the freeze-up happens after some apparently random period of time. The destination output .mp4 file is to the internal SSD; H.264 mp4, 4K 59.94fps I h

“Adobe Media Encoder 2023” is damaged and can't be opened. You should move it to the Bin.I deleted the app (AME 23. 6) and installed it again, didn't work. I have installed two older versions, didn't work. I followed another thread on this site that suggested to go to Applications, Media Encoder, right-click on Open, and agree on the security dialog. But couldn't go that far; as soon as I right-click Open, I get the error again. Running MacOS Ventura 13.5.2 with Apple M1 chip. Any ideas?

Using Premiere 23.6.0 and Media Encoder 23.6. Mac OS Ventura 12.5.2When I select multiple sequences in Premiere to render using Media Encoder, the dialog pops up where you enter your output destination, preset, and format. Click send to Media Encoder. ME opens and shows the sequences with your encode settings.The problem is, the render destination doesn't pass even though it was just entered in PP.It defaults to the last destination used. That is understandable if I open Media Encoder on its own to drop some files.... but is annoying when I specify a destination in PP.This workflow used to work in previous versions of PP and ME. I am not sure exactly when this issue crept in, but it is annoying to end up with renders in unexpected places and retrace my steps to see where they went.The workaround is:When ME opens, select all (CMD+A) (or Lasso all) of your outputs and specify the location again.  Seems like it should be a simple fix for the developers. 

I have a project which I've been working on for years.  It's 1 hour 42 minutes, 1920x1080, 29.97 FPS, and pretty complex, with a lot of nested sequences, After Effects includes (just some pretty basic animated diagrams), titles, etc.Up until about 8 days ago all was well.  I would edit, export, and watch on my TV. I last did this just around 8 day ago, no problem.But now, as I'm trying to make the FINAL render after some last tweaks, it's completely failing.  The video still edits fine in PP, plays fine, no problem.  But when I export, the exported video is just black -- audio is OK, but video is black.  ALMOST every time. I am using PP 23.4.0 on Windows 10.  Computer is a laptop, but pretty beefy, 64GB RAM, Nvidia 2070. I have tried:CUDA, OpenCL, and software renderers in project settings.CUDA, OpenCL, and software renderers in Media EncoderDirect export from Premiere (not using Media Encoder)Shutting down and restarting PP / MERebooting compute

  

Media Encoder was only exporting completely black video from premiere. The Audio was still in it. Updated everything so dont ask. The only way I got it to work was to browse for the sequence inside of media encoders self browser and lauch the export from there. Every other way possible didn't work. Support is useless and so is this program so hopefully this helps someone running into the same problem as me taking two hours to find out how to simply get this program to work even though youre paying for it.

Ran into a series of bad exports when trying to use Frame.io and sending Export nobs from Premiere to Media Encoder. Video was black, despite using presets where "video" was clearly enabled. Audio was normal. Turned out it would happen each time I sent exports to the Media Encoder queue from Premiere. Only disabling the "Import sequences natively" option in the Settings fixed this.    Both Premiere and ME are v23.6. Using an M1 Ultra Studio with 64GB of RAM, 20 core CPU and 48 core GPU, 2TB internal storage. Exporting to internal drive. Initially used Frame.io and "upload sequence" to send to ME, later just used regular Export to ME command in Export window (same results).

Hello everyone. I'm having a problem on saving files in mp4 in photoshop. States always the same: An error ocurred on Adobe Media Encoder. I've tried:- unistall and install the program;- make the file from scratch and with a different name;- saving the file to different locations;- used the Creative Cloud Cleaner Tool;- try to simplify the animation; Nothing changes or happens. Yesterday it was working smooth and properly but not today and this feature is needed for my everyday work. Version of Photoshop 2023: V. 24.7Version of Media Encoder 2023: 23.6 (Build 62) Thanks for any help.

Hi! Trying to create proxies for 4K footage from Canon C70, using the method of right-clicking my files in Premiere, choosing Create Proxies, and then Quicktime/Low Res ProRes (I'm on a Mac). Footage is from a 2-camera shoot; all of the files on one camera have proxied just fine except ONE file; all files from the other camera keep failing, with the below error log. I'm using the 2021 Premiere/Media Encoder version, I am resistant to constant updates and also won't be surprised if the answer here is just... to update. still! Any insight helpful! Footage is too big to edit without proxies on my current setup. Here's my error message log copy pasted exactly:- Source File: /Volumes/Saturn 1/230819 ASTEROID BELT/STAGE RIGHT/CanonA003/CONTENTS/CLIPS001/A003C003_230819EJ_CANON.MXF- Output File: /Volumes/Saturn 1/230819 ASTEROID BELT/98_Proxies/A003C003_230819EJ_CANON.mp4- Preset Used: Custom- Video: 4096x2160 (1.0), 23.976 fps, Progressive, Software Encoding, 00:40:13:00-

Issue; Media Encoder maxing CPU utilization even if the app is closed and no renders are happening in premiere proSpecs:OS; Windows 10 Virtual MachineCPU: Intel Xeon Gold 8248R at 3.00GHz24 CoresHave determined that update to 23.6 solves the issue

On Windows 10, Windows 11, Mac OS 13.2 Whenever you select a composition in the file browser in AME it still brings up the window to re-select the composition from the encompassing project. However when you make any selection (correct or incorrect) the window vanishes before you can hit okay it loads the correct composition anyway. Here is the order of events-User opens AME-Selects Ae project from file browser-AME file browser shows enclosed compositions within the project-User selects a composition from the file browser-New window pops up inviting the user to select any composition from inside the Ae project-user clicks on ANY of the options-window disappears before user can click 'okay'-composition originally selected in the AME file browser is loaded to the queue 

Over the last couple of days, Media Encoder has been distorting my After Effects shots on export. So far, either my 4K shots are exporting out cropped in, or in my 2K shots, part of the image is on the wrong side. This has happened both exporting ProRes and H.264, but for whatever reason, this effect doesn't happen when I export DNxHR. It also doesn't happen when I send my After Effects shots through the render queue. When I noticed this issue, I updated to the latest version of Media Encoder, but this has been of no help. Any advice? I've attached a screenshot of the glitch.

When I render any video using encoder (haven't tried direct renders from After Effects) The footage is shifted as seen here Video example