Adobe Media Encoder

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.

I just got my new MacBook Pro and clean install my creative cloud programs. I launch media encoder 2023, it stuck at loading importerquicktime.bundle for almost 8 mins to go in. Is this version have bug on it ?

Trying to Encode a video that was digitally transferred from a VHS to an MOV. I need it to Encode to MPEG-2 but the file is not encoding only audio when I start the encoder and the output is in black. Picture below. Please and thanks for the help in advance.

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  

So I just want to ask if it's normal that Media Encoder become practicly impossible to select, move and do anything to the file list when there is a lot of media in it. I mean if I want to select all the clips it it's almost impossible because is so slow. Thanks in advance. Windows 11Media Encoder 23.1 (also hapen in the 22-23)32gb Ram, i7 10th, GTX 2070.

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?

I'm making some SD h264 mp4 files in Premiere from some Youtube rips, and AME insists on preparing 42 audio files before making the (mono) audio output. It goes through each of the 42 quite quickly but it massively increases the processing time.  Whatever the codec the Youtube files may have had originally, they have been rendered out into Adobe Audition beforehand so they are standard wav files.  Why is it doing this with these particular files? It doesn't normally, when processing similar SD video files using the same settings. thanks

Every clip in my video exported from premiere pro is played back as a still image (video and render settings posted)

It appears that encoder 2021 was uninstalled and 2023 was installed. But no other 2023 products. Where can I get 2021? I still have After effects 2021, this was not uninstalled but is now useless as I have programs that integrate with media encoder. I get a different set of problems using After effects\media encoder 2022. Not least of all the dreadfull Visual Studio implementation and application performance.  

Before the latest update, when I sent something to the Media Encoder, it would automatically pop up in front of Premiere. Now, it stays in the background and I have to command-tab to get it to the front. Is there a setting to fix this???

I'm looking to encode animations I've created on a combination of Illustrator, Character Animator, Animate and After Effects but to save time I'm hoping to move the appropriate files to a USB drive and encode on another computer using Media Encoder to keep working on my main computer.  Is this possible and if so, which files should I move to the USB drive and how do I open them in Media Encoder after?Thank you  🙂

Please someone help when I'm getting towards the end of my render on media encoder it just says failed because of acceleration render or something I need help please 

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

I tried to use a command like the one described at the top here."C:\Program Files\Adobe\Adobe Media Encoder 2023\Adobe Media Encoder.exe" --console es.processFile "D:\EventVid\Media Encoder\constructionVid.jsx"I do not get any error, however Media Encoder does nothing. I am using Media Encoder Version 23.2(Build 63). Can someone shed some light on this. Thanks

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

I have to convert lots of XAVC footage from a Sony FX9 to h264 for my client and everytime I queue in media encoder it start fast but after 30 clips or so the CPU are overloading and media encoder become slow up to the point it make my Mac pro crash. The GPU doesn't seems to be use at all even if the preset says it should use hardware material. At that point the only way to make the CPU slow down is to close or restart AME Here are tthe specs from our Mac Pro 7,13,3 GHz Intel Xeon W 12 cores (not the fastest I know)364 go RamAMD Radeon Pro vega II 32 gofootage is on a NVME raid 0 and cache is on a separate sata ssd drive On another thread about slow premiere @Kevin-Monahan  said that he suspect a bug with these Xeon CPUs and that specific format.  Any developpement about that?  I am at the point that I will need to use another encoding software if I want to queue a big batch of clips without having to wait until the computer crash to restart the queue

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.

Bonjour,J'ai un petit souci lors de l'exportation de ma vidéo. Comme vous pouvez le voir sur les screens suivant, le résultat de l'export me donne un fichier de 1 Ko (il devrait faire environ 80 Mo) que je ne peux pas ouvrir. Pourtant les caractéristiques du logiciel me semblent bonnes...Avez-vous une idée ?Merci d'avance !

I am trying to export a one hour fifty minute Wraptor DCP at 250 mbps and I two in and encoder hangs up. I am using GPU accelerator (cuda). Dumped cache in premiere.The bitrate is 250 mbps which seems a large file at 1.3 TB. I have the compter power on high performance so it's not going to sleep. Other rendering seems fine except for this format.any Idea of what to try next?

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  

I've got a process using PP + AME that is ALMOST ideal for me. But there's one detail that requires an "O(n)" effort task, meaning the time & effort are linearly proportional to the number of files created. Bugger! When I make subclips from In & Out points PP appends "Subclipxxx" to the end of the name. When AME receives all of the subclips for rendering, it defaults to a filename with the "Subclipxxx" suffix stripped off and replaced with ".mp4". Now that all of the output filenames, by default, are identical, all of the renders but the first will fail! (screenshot below) I checked through the preferences in both PP and AME but could not find any options for changing the default file names for either. Photoshop has a rather robust feature set for dealing with filenames when batch processing, by comparison. Defaults that yield failed renders without manual intervention should typically fall in to the "Bug" category. But I wanted to give the community an opportunity to shar