Bug Reports

Ayer queria exportar unos videos por media encore pero la aplicacion no se abre, espere 15 minutos y sigue igual. alguna falla en la actualizacion o como lo soluciono?

I am running the newest release of Media Encoder 2023 (23.0 build 57) on windows and I'm running into an audio mixdown issue when converting a video file. What I do is I take a 16 channel auido track .mov recording from a Blackmagic Hyperdeck and want to convert it to a H.264. Audio lives on channels 1 and 2 in the .mov and 3-16 are blank. In the previous version of Media Encoder (22.6.1 Build 2) the audio would mix down channels 1 and 2 to a stereo track. However when using the most recent version (23.0 build 57) channels 1 and 2 are being mixed down to just the left channel in the stereo mix. I went back to the previous version to export my video and got my expected stereo mix just now. Let me know if I am missing anything. Thanks.

Adobe ME version 22.0 through 22.6.1PC Platform,  Windows Server 2019 I've seen this in a couple of locations.  We have ME running both as a application, and as a service.  On specific hosts, ME fails to launch with GPUSniffer errors.  When I tried to uninstall and reinstall ME on these machines, the installer failed with: Exit Code: 184 -------------------------------------- Summary -------------------------------------- - 2 fatal error(s), 2 error(s), 5 warnings(s) FATAL: Error (Code = 184) executing in command 'MoveFileCommand' for package: 'AdobeMediaEncoder22AllTrial', version:22.1.1.25 FATAL: Error occurred in install of package (Name: AdobeMediaEncoder22AllTrial Version: 22.1.1.25). Error code: '184' ERROR: CopyPrimitiveEx | GetAnyOperationsAborted failed with error: 0 ERROR: CopyPrimitiveEx | GetAnyOperationsAborted failed with error: 0 WARN: File C:\Program Files\Adobe\Adobe Media Encoder 2022\typesupport\cmaps\WP-Symbol locked with Process GPU

Have been trying to export some raw video that I chopped up in premiere. Using the settings of h.264 and match source adaptive medium bit rate. Two files exported no problem. The rest will take hours to encode then only give me a 24mb file that is unplayable. I have more than enough open storage and have not change the setting at all. Does anyone have any recommendations before I lose my mind?

Just updated, did nothing to fix this problem... every sequence I drop into the que instatnly becomes a .wav file... usually the .wav file that is the audio for the project, the file in the same folder as the whole project. What is the FIX? Getting really sick of this from Adobe. Media Encoder is supposed to make things faster not send me down a rabbit whole of trouble shooting... I could have exported the 3 sequences separately by now 

Hello, I have recently upgraded my Mac OS to Monterey, and I get an error message when starting to encode ProRes (mov) videos from an external harddrive source in Media Encoder.This used to not be an issue and no problems in the past.Could we please accomodate to have this bug fixed? Thank you 

helloi have updated my premiere and media encoder to 23.its very very slow to encode files.  

 Hello, I have just upgraded my Mac OS to Monterey, and did the required updates for all of my Adobe Creative Cloud Apps.When I tried to test encode a ProRes (MOV) video today, I get this error message. Anyone else currently experiencing this? Is it a known issue with the latest update? Thank you

 Hello, I have recently upgraded to Mac Monterey, and now I am getting this error message everytime I try to encode ProRes videos in Media Encoder. Any bug fixes on this? Thank you

After the last major CC update to the current version, all personal encoding sets on the server are overwritten in the media encoder. After the update, you cannot select whether a down- or upload should take place, an UPLOAD is triggered immediately. Afterwards they are no longer accessible on any computer. Why does ADOBE make such errors?? This is a lot of work!! (An export was available, but unfortunately not up to date).

I have just updated my Media Encoder this morning and I have found an issues with the new version. Yesterday, I exported totally good but this morning, I exported 1 simple 3D logo with the same preset (Prores 4444 alpha + animation codec or prores 444 but the video was glitched. You can check the video here.ERROR 

Is it just me, or the media encoder 2022 has gotten extremely heavier. It even takes a lot longer to open.

Hi, I'm using Adobe ME version 22.6.1 and Adobe AE version 22.6.0. When I select 'Add to Adobe Media Encoder Render Queue' from the Composition Menu or when I select 'Queue in AME' from the Render Queue in Afer Effects, there's nothing coming up in AME for render. For the last few files, I'm having to first render an uncompressed extremely heavy file in AE and then drag that output video file in AME and use H-264 to compress it. This is quite a hassle. It used to happen in earlier versions, then it got fixed, now it's started happening again. Please resolve this soon!

estoy con inconvenientes para abrir la aplicacion. con otros de photoshop e illustrator

App Version: 22.6.1 (Build 2)OS: Windows 11 Pro 22H2 (22621.674)CPU: AMD Ryzen 9 5950XGPU: NVIDIA RTX 2080 (Driver 522.25) Media Encoder causes a full system crash as soon as the Quene is started.  This occurs whether the quene has 1 item or 100+ items.  This happens regardless of Hardware Acceleration enabled or disabled.  This happens with all Renderer options.  Changing the output format has no effect, it always crashes.  It is a full system crash, immediatly black screens and reboot.  Frequently this results in a need for the windows bootloader to repair the C drive. The logs seem to be useless but I have attached them, it is curious it logs errors about a non-genuine Intel CPU when the system is in fact an AMD CPU so of course it's not genuine Intel... The entire Adobe suite is useless to me when I cannot export my work...  This also occurs in the Beta version of Media Encoder...  I've ruled out all hardware problems as f

Error message:"Could not connect to Adobe After Effects 2022. Please verify that Adobe After Effects 2022 is installed." I started getting this message after both AE and AME were updated to 22.6. Both programs are on the same version. I tried going back to a previous version (22.4) for both AE and AME, but I'm still recieving that error message when I try to add an AE project to the queue. When sending the render from AE to AME, AME launches but no comps appear in the queue. Something even stranger, After Effects doesn't show up on the list of installed apps on the CC app. After Effects is definitely installed. Any ideas on why AE won't show up on the CC app? Any ideas on how to fix the dynamic link problem? Not sure if this matters but I'm on a Mac Studio running Monterey (12.6)

When I render the AEP file which I sent in the wetransfer link. The Macbook Pro (16-inch, M1, 2021) 16 GM RAM renders it in 30-37 minutes, but MacBook Pro (13-inch, M1, 2020) 16 GB RAM renders it in 13 minutes maximum. There seems to be a problem here.https://we.tl/t-lfgr0BH23nWhen we brought the 16 inch device to the Apple service for performance issues. They sent it back to us saying that there is no problems with the device.I am sending both of the devices' log files. Although we have no errors in the 13 inch device, we recevive this error in the 16 inch one:We have timed out on an async source. This probably shouldn't happen and will result in performance problemsWhen we continue using Adobe After Effects, the device becomes slower. When we restart it. The render time usually goes down but still has a huge gap between the older device.

I was strugglign with major blocking issues in some transitions when rendering in ME from PR.  I was using settings in PR that resulted in a pop-up message saying that my hardwarew woudl not support the combo and PR stayed on Software only for the encoding.  I then export to ME.  In ME I am set in the dropdown in the encoding window to use hardware.  Even though PR said to render with software, ME followed the settign in the dropdown and used hardware.  Once I noticed this disconnect I changed ME to use software and then the blocking on transitions went away.  In particular I was using a VBR  2-pass encoding that the hardware option does not support.  Should ME have an option to follow whatever PR says to use instead of using somethign that does not work?  Since ME can queue up lots of renders, not all of which will work with hardware, it seems wrong to override what PR indicates and use the default in the ME window.  

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

Hey all, I can't start media encoder. I have already restarted my macbook and mediaencoder is up to date. Does anybody know how to solve it?

The new versions of the Media encoder (22.6) are insanely slow and render AE project scenes incredibly long on Mac M1 chips. I've tested on several scenes working with multiple 3D versions, lights, bitmaps and what 22.6 renders in 20 hours, build 22.3 renders in 20 minutes! Isn't it possible to do something about it?

Hey folks. It does not make sense, but since one of the latest updates CC2022 some of my exported files have artifacts (digital hits) and audio drop outs.Smart rendering shoud prevent from additional QC, but Premiere and/or AME does not do the job very well. We recognized 1 frame audio outs and digital video artifaces.There are no render processes (output parameters are exectly the same like input (resolution, codec, color space, ...) and there is no preview), so I have no clue why this happens. Right now we are back on CC2021, because the errors are completely random. I found no other users, but we tested different workstations. So it seems to be a software problem. We are on iMacPro MacOS 10.15.7 and used the latest version of Premiere and AME.

when i export a video from after effects with media encoder it failed and it shows an error code -1609629695please help me to solve this problem  - Encoding Time: 00:00:2210/04/2022 03:04:55 PM : Encoding Failed------------------------------------------------------------Export ErrorError compiling movie.Render ErrorRender returned error.Writing with exporter: H.264Writing to file: \\?\D:\download d drive\Lightning-pack-1036826\Lightning Pack\Untitled Project2_AME\ik lamha final_3.mp4Writing file type: H264Around timecode: 00:00:00:24Rendering at offset: 0.000 secondsComponent: H.264 of type ExporterSelector: 9Error code: -1609629695------------------------------------------------------------

Lately when I've been rendering directly from AE to AME, the renders finish as if normally, but when I go to play them back large chunks of the end of the render are missing. (Yes, I have in and out points set correctly in both my AE comps and in AME.) When I render from AE render queue I don't get this issue.This is extremely annoying for many reasons, one of which is that in order to make all the formats NOT supported anymore in AE (MXF, H264 etc etc) I have to use AME. Even when I pre-render from AE and then try to use AME to encode to other formats, it still happens. Quitting and restarting helps one out of two times. Adobe no longer seems to care about making tools that professionals can rely on.

For months it would fail to write the XML data, now it's writing extra .M4V files and freezing mid-render. No problem output from within Premiere, I'm giving up on AME.