Bug Reports

A whole lot of wasted productivity here...ME 23.2.1, Premiere 23.212.6.3 Monterey   

Hi, I've exported a sequence from Premiere to be rendered in AME. No missing or offline files are reported in Premiere, but when AME opens I get a warning."offline media detected and will be encoded using proxies"I don't know why this happenes, but the files are not offline and I can render the sequence just fine from Premiere. But AME use the proxies files when it renders. There is no reason for them to be "offline" in AME and not Premiere.Please help, thanks!

Has anyone else had any exporting issues with Media Encoder 2023? The first issue is either the audio, visuals or sometimes both, will glitch when exporting a After Effects comp through Media Encoder. The result is a distorted export, but the file itself isn't broken. My current workaround is exporting direct from AE (then using Encoder afterwards) which isn't ideal time-wise. I've also noticed that i'm getting a large discrepency in MP4 sizes. A 15 second clip at 10mbps came out to 71MB, while a 19 second clip with the same bitrate came out at 25MB. So I'm having to export sometimes twice to get it to a required spec.

Hello all, I've been encoding several Premiere Pro sequences using Adobe Media Encoder 2023.  Granted, this was before the most recent 23.2 update, but here's what's happening:I am sending multiple sequences from Premiere Pro directly to AME 2023 23.1 and, before I start the queue encoding,  I close Premiere Pro.  The only Adobe product running when I press the Start Queue button is AME.  I then make sure that the Encoding panel is selected (or in focus).  If I switch to any other window (such as my browser or a Windows explorer), AME will run for about 10 more seconds and then stop encoding.  It doesn't officially stop or pause the encoding (there is no "Pause" indicator in the Queue panel on the item currently encoding), it just hangs there until the Encoding panel is selected (or in focus) again.  The Encode Preview just continues to display the most recent frame encoded and the Elapsed Time and Time to Completion timers don't move. 

When I export the project in premiere pro it works however because I queue our projects in media encoder I get the following errors, Fehler beim Export Fehler beim Kompilieren des Films. Fehler beim GPU-Rendering Frame kann nicht verarbeitet werden. Schreiben mit Exporter: H.264 Schreiben in Datei: xxx Dateityp wird geschrieben: H264 Um Timecode: 00;00;32;16 - 00;00;32;25 Rendering-Effekt: AE.ADBE Opacity Rendering bei Offset: 32,299 Sekunden Komponente: EffectFilter vom Typ GPUVideoFilter Selektor: 9 Fehlercode: -1609629681 Also don't know whey media encoder is in german preset is set to english. However, the only way to render with media encoder currently is setting to software render only. Which is not optimal.Also using currently all the latest versions of PP and ME, also the current studio driver. Tried it with an old studio driver, same problem.

When I open Media Encoder it doesn't work and I get the following message:Adobe Media Encoder Error Adobe Media Encoder has encountered an unexpected error and cannot continue.I've uninstalled while resetting the presets and intalled it again and everything is up to date.What's happening and what can I do to fix it? I noticed that the error comes when the program is loading "ImporterQuickTimeBundle". I don't know if that's relevant... Other info:Version of the app -> 23.2Platform and OS version -> macOS Monterrey Thanks

On my 2021 MacBook Pro (Apple M1 Max) I am completly unable to encode any video in HEVC (H.265).It always instantly fails.The Error log says "Error during export. Encoder could not be created." (translated from german) And this error happens on multible macbook pro's with any video whatssoever.The workflow is to import a ProRes or H.264 Video and encode it in many different codecs. 2 ov which are H.265 (4k and FHD). Both fail instantly as described above.Even disabeling the Mercury Playback Engine does not help. Any tips?Thank you!

Hello!In the latest version of media encoder (23.2.0.63), the problem with non-english MP4 filenames has been fixed.But the error persisted if the MXF contains non-english filenames.I am attaching a video of the error.

Hi Everyone,With the new exciting tome mapping just make sure that the media encoder is also enabled to detect log footage as well.Premiere will carry on the auto tone mapping fine but you do need to do this for media encoder manually before hand.I just had to re-export my project couple of times to figure this out.   Hope it saves some time and build some quick search for others &#x1f605  

I have character animator sequence imported ino after effects and it shows ok in the composition but when I send a composition out to Media Encoder, the Ch sequence is missing and it's only rendering the artwork from Ae. I'm exporting as H264. Has anyone encounter the same problem?

When we want to export a Video from Premiere Pro it always says that the media is not available and Exports it with the Media pending graphic, when we change the folder and or file name to a name without umlauts it works fine again. It was no problem before the recent Update and a similar bug happens when importing files to After Effects from a Umlaut Folder  

Sending closed captions to OP1a 50mbit files as Embedded with both 608 & 708 streams doesn't work via Media Encoder (PC) v22.4. It does work correctly directly out of Premiere (PC) v2022. If you have a sequence with just 608, or just 708, it outputs correctly through AME. If you have both 608 & 708 tracks, only the 608 track is in the final file. AME keeps telling me "PProHeadless has encountered a problem and needs to close"

Hi Tried to open Media Encoder version 23.2 (latest version), but it stops half way, says 'Media Encoder has encounted an unexpected error and cannot continue'. Running on an iMac  (2017) Intel with Big Sur 11.6.2 operating system, Any ideas how to fix this. Thanks. 

On an M1 Max, when trying to export H.264 on AME 23.2 with hardware encoding enabled, it forces me to keep the audio track. When I disable audio, Performance changes to Software Encoding, and when I re-enable adio, Performance reverts to Hardware Encoding. I'd like to be able to do hardware encoded H.264/5 with audio disabled, and since both Handbrake and Compressor allow for this, it would be nice if AME did as well. AME 23.2, MacBook Pro 16" M1 Max 64GB, macOS Ventura 13.1

Media Encoder y After Effects en su actualización 23.2, no admite archivos MXF. Es un error o es con conocimiento?

As in the subject line, I am experiencing repeated pervasive crashes when exporting small ProRes proxy files in AME 23.2While rendering a queue of proxies, AME hard crashes the system, causing full restart. This doesn't happen each time I try to render proxies - but *almost* every time. Some file renders are successful, then out of nowhere, SYSTEM CRASH + REBOOT.I am running all updated Adobe CC apps on a maxed out 2019 MBP 16" with 64GB RAMMacOS Ventura 13.2.1Exporting to an external G-Drive 20TB HDD with Thunderbold 3 connector. The drive also holds the original 4K media; I am exporting to a proxy folder next to the original material. The crash happens also with other external drives.The relevant part of the most recent AME crash log is attached.

We recently got Macs with M1 Max inside, and I found that Apple Compressor exports ProRes 422 two to four times faster than AME can do with hardware acceleration enabled. My guess is AME only uses one of the two available Media Engines on the Max, possibly for both encode and decode. This also seems to only affect ProRes exports, as the H264/5 exports in AME are a bit faster than Compressor. I've attached a screenshot of the GPU history during both exports; you can see that AME appears to be utilizing about half while Compressor maxes out. AME exported at the same speed whether plugged in or on battery power. Source file: 6:36, 4K, H.264, 23.976, 12Mb/sAME v23.2 ProRes 422 export: 1:03Compressor v4.6.3 ProRes 422 export: 0:16MacBook Pro 16" M1 Max 64GB, macOS Ventura 13.1, 52GB alotted to AME  

If I export in Premiere Pro (ver 23.1), the rendered file looks good. However, if I send the sequence over to Media Encoder (ver 23.1) to export (and don't change any settings - i.e. no presets applied or export settings changed), the resulting file is massively over exposed. I have re-installed Media Encoder, resetting all preferences, and am still experiencing the issue. (Exporting H.264 file). Any idea why the massive difference between exporting in Premiere vs Media Encoder? Please see the screenshots attached for reference. Using MacOS (ver 12.5). Thank you.   

I've noticed that the close caption options are greyed out (disabled) in the MXFOP1a settings in Media Encoder. This is very problematic as that is one of the few file formats that allow for embedded captions and I rely on it heavily in Broadcast workflows.This can be worked around currently by rendering directly out of Premiere. But those caption options should also be accessible in Media Encoder.CC has been available for MXF files for years, and we've relied on them essentially as long as Premiere has been able to output Closed Captions. I think they got overlooked in the new Export implementations. If this bug can be corrected it would be very helpful.Thanks 

Die neue Version (23.2 unter Windows 10) findet beim Export aus Premiere Pro die Inhalte aus der Timeline nicht. Laut Media Encoder sind das alles Offline-Medien.

I just got the new M2 Mac MacBook Pro and start to work, but I start my media encoder it freeze on the importquicktime.bundle. And I also tried to open premiere and after effects, also show the beachball and no response. Is anybody have the same issue?

Hi everyone, I saw that when I export a sequence from AME with markers, I don't have them in the file after export and this is causing issues when I import files inside frame.io cause I don't see any comments on the app online and my team cannot either see anything

Had this issue running ME 2020 as well as ME 2022 (22.6.1 build 2) off of a shared server environment on a Mac (os 10.15.7).When sending an output to ME from PP, it will OCCASIONALLY mess up the music edit, especially if there's a cross dissolve involved.Edits that sound perfectly smooth on Premiere or when output directly from Premiere sound fine, but if I send to ME, the incoming music starts at the wrong timecode and sounds completely off.Music is generally mp3 and most often invovles a crossfade at the edit point.The fact that it's unpredictable makes it annoying - it could work 10 times in a row and then on the 11th, the music edit is wrong.***IN EXAMPLES BELOW, listen to crossfade around :29 - this is not even a music edit - just added a cut to change audio levels and added a crossfade betweeen softer and louder sections to simulate a fadeup. Works perfectly in Premiere version, not in Media Encoder version***

Bonjour,Lorsque que j'encode une vidéo, le son est coupé par moment. Des fois, l'encore est nickel mais parfois, ca arrive sur plusieurs vidéos. J'ai réinstallé la totalité d'adobe mais rien n'y fait. Avez-vous une idée? Config PC : disque dur : SSDProcesseur : AMD Ryzen 5 3600Carte Graphique : RTX 3080 FERAM : 4*8GB Corsair Vengeance LPXCG : MSI B450 Tomahawk Max https://www.youtube.com/watch?v=cWMFAHaCglU&ab_channel=TediShiro 31 minute

I'm having the issue with AE-ME for years already: occasionally, when sending a comp from AE to ME, some of the media, like sound in my more recent occurance of this problem, is not passed updated and previous version of the media is used. I observed it many times, even reported it once. My most recent problem is the followingI have a comp with WAV file on a sound layer.I make changes to WAV, I even make sure to manually update the linked media in Project tab in AEWhen I send the comp fomr AE to ME and render it out — the output is still with the previous version of the WAV file.I tripple-checked: AE links to the WAV file that was really updated, when I open it in AE as Footage preview — it plays the updated version, and even the Waveform of the layer reflects that it was updated (like I can visually see that extreme beat is I removed is gone from the spectrum), and if I render out the comp in AE — it uses this right media. But Media Encoder somehow continues to render out the comp wit