Bug Reports

Steps to reproduce: 1. Complete queue2. Click X to close Result: App hangsExpected: App to close System info    Application: Adobe Media Encoder (Beta) v25.6.0.66    OS: Windows v10.0.26100, RAM: 63.79 GB GB, CPUs (logical): 16

I had to crash out AME after it stopped rendering a long queue midway. When it came back (after a restart for good measure), all the remaining queue items were gone. The only ones left were ones I had manually stopped because there's some kind of glitch in the source. System info    Application: Adobe Media Encoder (Beta) v25.6.0.62    OS: Windows v10.0.26100, RAM: 63.79 GB GB, CPUs (logical): 16

I'm rendering a whole bunch of clips to h.265 from a timeline. Sources are mostly ProRes but some are MP4. When I started the batch (about 30 clips, each about 10 minutes long), it was running quickly. Now near the end it's running at just about, if not slower than realtime.  Looking at task manager, the nVidia RTX5080 is running at 5%, the Intel GPU at 8%, and processor at 24%. This is much slower than normal. I know it's not drive speed because it's a NVMe array capable of over 1GB/s, and it's logging 1% write What gives? System info    Application: Adobe Media Encoder (Beta) v25.6.0.62    OS: Windows v10.0.26100, RAM: 63.79 GB GB, CPUs (logical): 16

Steps to reproduce:1. Export project to AME2. Click preset link to change export attributses Result: ... "File Import Error - Could not read from source. Please check setting and try again."Expected: ... Settings dialog to open System info    Application: Adobe Media Encoder (Beta) v25.6.0.52    OS: Windows v10.0.26100, RAM: 63.79 GB GB, CPUs (logical): 16

An error occurs when exporting from Nikon's NEV media encoder.The original file is not being referenced (cannot be found).in japanese,ソースから読み取れませんでした。移動または削除されていないか確認してください。

Downloaded the most recent beta versions of Premiere and Media Encoder. I'm encountering a bug that is preventing me from sending files from Premiere to Media Encoder to have Media Encoder render them. Every time I try to start the queue in media encoder, it fails immediately and tells me "could not read from the source. Please check if it has moved or been deleted." I can render the files directly in Premiere with no issues. 

The computer is scheduled to sleep when unused for 30 minutes. Today I racked up a bunch of renders for it to do and went to lunch. When I came back the machine was asleep, and on wake I found the machine had slept with several more in the queue to go. The queue restarted without intervention, which is good. But, AME should alert the OS that it's busy and prevent sleep until the last job in the queue is finished.  Steps to reproduce:    1. Set machine to sleep after a period of unuse2. Start a render queue that will last longer than the above period Result: ... Machine sleeps without finishing queueExpected: ... Machine to sleep AFTER finishing queue PS. I do not expect to use the "Auto Computer Shutdown" feature since I sleep the machine rather than shut it down. That way it does updates automatically, and it spins up faster. Would be good to have a sleep option alongside the shutdown option. System info    Applicat

Hey Team, I used this plugin https://aescripts.com/odometer/ in Ae Beta and in my viewport it looked good:but when I render it through Media Encoder Beta I get a white shape: I tried to export this as H.264 with 4mbit VBR 2.I tried also to render it only in AE Beta and I had no white shape. The Plugin is not running in Demo mode, I have a valid license. In Ae normal it works even though in Media encoder.Best GreetingsMischel 

I have a queue full of many after effects outputs I need rendered. My renders get to the end but appear to never finish, in the encoding windoe times elapsed and remaining do not advance, until I pause and unpause the queue. At that point, the file finishes and it moves onto the next item in the queue.This happens both with h264 and prores outputs so it's not output dependant. I an using AME to queue renders from multiple AE projects so I don't know if it happens for a stright encoding process.  I have many items in the queue and was hoping that these could all progress overnight so having to manually advance after each render is a huge inconvience.This happens in AME beta 25.1 build 38 on Windows 10 but is not exclusive to this build.  I experenced a similar bug (filed) in a previous beta build earlier this month.  

See discussion in release PR forum: https://community.adobe.com/t5/premiere-pro-bugs/problem-with-caption-encoded-file-exported-from-premiere-pro-to-encoder/idi-p/15287602   Steps to reproduce:1 Import an asset with embedded captions. (My asset is a VERY short MXF file previously created in PR with embedded 608 and 708 captions.) 2 Create sequence from it and export as MXF with embedded captions. 3 Queue to AME  Result: Shows warning "offline media is detected and will be encoded with the offline media graphic" and indicates my source file as missing.  Creates a file with embedded captions, Media offline visual, and no audio. When reimported to PR and a sequence created, it has both 608 and 708 captions embedded. I had "import natively" set, and if changed, I saw no warning, but it encodes with Media offline visual, no audio, and only 708 captions on reimport to PR.   It exports correctly from PR.   Expected: Exports with video, audio, and captions em

Steps to reproduce:    1. Apply Metadata burn-in in Premiere    2. Send sequence to MediaEncoder    3. Preview the preset in Premiere Result: Timecode burn-ins have #nbsp at the head, but this does not appear in Premiere.Expected: See the burn-ins as they exist in Premiere.  System info    Application: Adobe Media Encoder (Beta) v24.6.0.8    OS: macOS v14.6.0, RAM: 64.00 GB GB, CPUs (logical): 24

Steps to reproduce:    1. Import an MPEG 2 VOB file.2. Export to any of the standard "match source" settings Result: ... Render is extremely slowExpected: ... Render to be speedyWorkaround: Use release 25.1 build 65.  MP2>MP4 is very speedy. System info    Application: Adobe Media Encoder (Beta) v25.2.0.101    OS: Windows v10.0.22631, RAM: 63.82 GB GB, CPUs (logical): 16

old Me is working, new Me is garbage!  

Just a note to thank the team for fixing the problem where the machine would sleep while rendering a long queue.  It now finishes the queue, no matter how long, and then allows the machine to sleep. Bravo!!!

I've upgraded the machine with SSDs that are capable of 10GB/sec. But I'm rendering SD DV SDI to SD DV MP4 at around 12KB/s - when it writes.  It's "chunking,"  little write bursts that corresspond to 3D activity on the nVidia GPU and CPU.  Nothing happens on the Intel GPU.  Latest nVidia driver on a 2080ti. This used to render quickly.  What has changed?AME 25.2 build 74 Beta 

Most current build won't install. Installation failed error. Don't know which build as I un installed previous build to see it that would help: did not.

I'm getting LOG-looking footage (grey, washed out) from Media Encoder, even though my colour settings in Premiere appear to be correct? I have a Canon EOS C80 and recording Canon XF AVC S files in C-Log 2. Seems like the colour output info is not getting to ME? In Premiere, under the settings tab in Lumetri Colour: Media Colour Space: C-LOG 2 / Wide GamutColour Setup: Wide Gamut (tone mapped)Output Colour Space: Rec.709 Oddly, if I don't export the footage to ME, and just use Premiere's encoding, the footage looks fine.

I'm using Media Encoder to queue multiple after effects projects that each have a particularly long time-per-frame. Normally, I can see the queue's progress but media encoder seems to get stuck visually with the time elapsed counter, progress bar, and other visual information stuck.  Resizing the window doesn't normally fix it but resizing the encoding panel usually does. This was concerning me because it appeared that my render had hung on the last frame of a file for 20 minutes while in actuality the file was complete and the next project in the queue was already rendering. After jiggling the interface a bit it updated. I suspect it's not a bug with media encoder function, just the GUI display. System info Application: Adobe Media Encoder (Beta) v25.1.0.34 OS: Windows v10.0.19045, RAM: 63.93 GB GB, CPUs (logical): 8 

DV AVI files captured in CS6 are taking FOREVER to load into AME.Steps to reproduce:    1. Drag & drop a 2-hour DV AVI file into AME2. Wait Result: ... Nothing happens for 5-6 minutes. Nothing shows on drive activity. Eventually it loads and can work, however if you have to open settings to make an adjustment, that waits a good long time too.Expected: ... Within a few seconds  system will be responsive. System info    Application: Adobe Media Encoder (Beta) v25.0.0.44    OS: Windows v10.0.22631, RAM: 63.83 GB GB, CPUs (logical): 16

As you can see in this screengrab, when using "Darkest" mode in AME (beta 24.6x52), it's impossible to distinguish selected items from non-selected items:...believe it or not, four of the rows in that screengrab are actually "selected". Who at Adobe QC didn't notice this?!Here's a massive close-up, showing the black (unselected) row versus the 8% brightness selected row: I am definitely not a fan of  the "spectrum" way of showing highlighted/selected things throughout the Adobe apps; changing the background from dark grey to imperceptibly-less-dark-grey is just stupid. Use that cyan colour to highlight selected things, please! Or does whoever programs these things have their monitor's contrast turned waaaay up, exactly the opposite of how every graphics professional works?! Workaround: Don't use "Darkest" mode.

I'm attempting to render some very large DV AVI files to MP4. Some are 10-15 minutes long, but others are in the 1-2 hour range, and one even 6 hours. (SLP VHS transfer). I do not remember AME taking forever to read the files as they are imported, and then when opening the Preset to trim the endpoint, it takes a long time before the editor even appears, and then it  tells me it's rendering for a long time. I was watching Task Manager and found it's reading the source file as fast as the drive array will go (600+MB/sec), but it's still taking forever to load. Is this a new behavior since the last time I did this a few months ago? Source files are DV codec at about 30Mbps. Once the render queue starts, they are rendering briskly as I would expect.  It's load times that is annoying. BTW, I tested the release version, not the beta, and it did the same thing. System info    Application: Adobe Media Encoder (Beta) v24.6.0.30 &n

L'export s'arrête après quelques minutes et ne progresse plus.  J'ai redémarré la machine, essayé sur une autre, et essayé avec un autre disque dur. 

Steps to reproduce: edit  an existing Media Encoder preset Apply the preset to a queud After Effects composition Result: output preview states the original preset's res and rateExpected: preview correctly reports the currently rendering file's res and rate. System info    Application: Adobe Media Encoder (Beta) v24.5.0.24    OS: Windows v10.0.19045, RAM: 63.91 GB GB, CPUs (logical): 12

Hello friends,  I am an editor and director and have been using Premiere to edit documentaries for nearly two decades. Trying out the new Beta vesrsion of Media Encoder to generate some proxies today, I ran into some issues. First, I want to say that I love the design of the new GUI. At least my first impression was that it's clean, minimal and utilitarian. I find it promising after years of bypassing Media Encoder and opting for third party apps like the bygone Mpeg Streamclip for batch transcoding. Great work on the design!  So, the bug. I loaded a bunch of clips into the queue, dragged and dropped. They're MXF's in 4K (4096 x 2160) shot on a Canon C70. I didn't see a proxy preset to suit my needs, so after some poking around, decided to creat my own. I selected ProRes 422 Proxy. I wanted to make them half the resolution of the original (for speed and efficiency). There was no option to simply make them a half or quarter resolution (a handy feature which

after effects beta doesnt sync with media encoder