Bug Reports

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

Steps to reproduce:    1. Go to Export tab of PRo Beta project and click on "Send to Media Encoder" button.  Result: It opens Media Encoder window, however no Project is loaded and listed in the Queue and no Render is being performed.Expected: Project being automaticaly preloaded and listed in the Queue waiting to start render. System info    Application: Adobe Media Encoder (Beta) v24.5.0.17Adobe Premiere Pro (Beta) v24.5.0.21    OS: Windows v10.0.19045, RAM: 63.83 GB GB, CPUs (logical): 16

quando lancio l' export da premiere pro (beta), si apre mediaencore (beta) ma nella lista dei file non mi compare nulle e per tanto non posso eseguire il rendering

Steps to reproduce: Select (clipname) in Premiere Pro and Create Proxies... Choose ProRes QuickTime Proxy (Quarter size was what I tested), no watermark (not sure if that matters), next to original media Result: Media Encoder creates a file labeled "clipname_Proxymov.mov" The proxy badge shows red "offline" in Premiere and is not attached. Manual attachment does work but cannot be batched. Expected: the extra "mov" in the Proxy name is unecessary and may be throwing off the process. Proxies should automatically attach and it does not. System info    Application: Adobe Media Encoder (Beta) v24.5.0.10    OS: macOS v14.4.1, RAM: 64.00 GB GB, CPUs (logical): 20

Buenas tardes, El problema tengo con Enoder es cuando voy a especificar un nombre al archivo se cierra completo el programa, no se porque.¿En qué me pueden ayudar? Gracias.

 - Source File: /Users/benjamindevries/Library/Application Support/MisterHorse/PremiereTemp/Preview 20240214_173038_000001.mhbricks- Output File: /Volumes/Temp/EP351 Lectric XPeak/Proxy/Preview 20240214_173038_000001_Proxy.mov- Preset Used: Custom- Video: 1920x1080 (1.0), 23.976 fps, Progressive, 203 (75% HLG, 58% PQ), Quality 100, Apple ProRes 422 Proxy, 00:00:00:06- Audio: Uncompressed, 44100 Hz, Mono, 32 bit float- Bitrate:- Encoding Time: 00:00:0002/14/2024 12:30:42 PM : Encoding Failed-------------------------------------The Operation was interrupted by user-------------------------------------- Source File: /Users/benjamindevries/Library/Application Support/MisterHorse/PremiereTemp/Preview 20240214_173038_000001.mhbricks- Output File: /Volumes/Temp/EP351 Lectric XPeak/Proxy/Preview 20240214_173038_000001_Proxy.mov- Preset Used: Custom- Video: 1920x1080 (1.0), 23.976 fps, Progressive, 203 (75% HLG, 58% PQ), Quality 100, Apple ProRes 422 Proxy, 00:00:00:06- Audio: Uncompressed

The Green Play button was missing to begin the export. I did however hit the enter button and that began the export so that helped. Steps to reproduce:    1. ... sent media to export with the Media encoder Result: ... no green play button to begin exportExpected: ... System info    Application: Adobe Media Encoder (Beta) v24.4.0.1    OS: macOS v14.3.1, RAM: 64.00 GB GB, CPUs (logical): 20

I have rendered on different cpu and both media encoder have stopped exporting audio to my files. when I export directly from Premier Audio is included in the exported file please fix asap.

Hi all,it seems that after latest update AME (Beta) is not loading projects smoothly anymore. Well, it's not loading projects anymore strucking at around 70-75% each time.It's been useless rebooting the PC or even forcing quitting through Activity Monitor.Now I'm in a rush for rendering videos and I can't do it sending to AME and I'm not even sure it works from Premiere.Trying to open the files to render through the multimedia browser gives me no error but strucking on opening (see attached picture). It's not for the single project since it happens on several projects I tried to managed over there.Any hint on how to solve it ASAP?

La versipon de Encoder normal se demora 5 minutos en exportar un video en baja y la versión beta dice una hora!! Imposible. 

Mdeia Encoder Beta is not outputing audio.

When exporting subtitles as an .srt sidecar file Premiere pro/mediaencoder gives the .srt the wrong filename. If the movie is called "filename.mp4" the srt file is named  "filename.mp4.srt" instead of  "filename.srt" 

Media Encoder na última atualização está com este bug.Renderiza uma lista de coisas que não existe