Bug Reports

Not sure what happened to my other post, looks like it was deleted? CUDA is not selectable as renderer on latest build. Tried rolling back and still the same issue. 

Steps to reproduce:    1. .Use the New AI Masking tool in a sequence    2. Export > Send to Media Encoder Result: Render ignores layer with mask Expected: Final product should have masking System info    Application: Adobe Media Encoder (Beta) v25.6.0.80    OS: macOS v15.7.1, RAM: 32,00 GB GB, CPUs (logical): 8__________ Previous beta version had a warning "Some Object Masks are Offline and will be ignored" That version was only ignoring the mask, not the layer itself. I've saved the project differently and updated to the latest beta version of the After Effects Beta. Now there is no warning but render preview shows that layer with the new AI masking is ignored completely. 

Hey Guys, when I go to export my sequence I did in premiere Pro Beta, using the latest "Mask" tool, as soon as I import to AME it display the warning saying "Masks are offline so won't be rendered". These mask are the subject masks made with the new function in Premiere Pro Beta. How do I fix it?

I’m currently using Premiere Pro Beta v26.0 along with Media Encoder Beta v26.0.After completing a mask operation in Premiere Pro Beta, I tried to render the project through Media Encoder Beta.However, the following warning appeared:“Media Encoder Beta: Some object masks are offline and are therefore ignored.”As a result, the masked areas are not rendered properly.When I use Premiere Pro Beta’s built-in render system, the mask exports correctly, but when I send the project to Media Encoder Beta, the mask data doesn’t transfer.Window 10Premiere Pro Beta v26.0Media Encoder Beta v26.0

It won't let me export because it gives crash or gets cut off, and it doesn't read the masking when you put a title or a graphic in the background. When exporting, it reads Layer 1 as if it were Layer 2.  Im working with Beta version, premiere pro. (In the time line every thing is good but whwn is exporting make it wrong)

Since the update to Adobe Premiere Pro Beta v26.0 around November 7, double-clicking a caption in the Preview window causes the application to crash unexpectedly. Please consider this for a bug fix. 

I am unable to open the queue window in the encoder beta after exporting a file from the premiere pro beta. When I click the window tab, and then queue nothing happens and I can't see what is to be exported. I have updated everything and also uninstalled/reinstalled encoder.

Steps to reproduce:    1. Send a project to AME from Premier2. Start the render  Result: Midway through the render everything stops. It keeps machine from sleeping. Have to stop the queue, then it sometimes hangs. If it clears, I can duplicate the project and it will render completely. Often after this happens, when I go to close AME, it will freeze and crash, requiring end task or machine restart.Expected: For the project to render without hanging or crashing. System info    Application: Adobe Media Encoder (Beta) v26.0.0.10    OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

Hi everyone,I’m currently using the beta versions of the following apps:Adobe Media Encoder 25.6After Effects 26.0Premiere Pro 26.0However, when I try to send a composition from After Effects to Adobe Media Encoder, I get a message saying that Media Encoder is not installed — even though it actually is, and works fine when opened directly.I’ve already tried restarting both apps and my system, but the issue persists.Does anyone know how to fix this?Thanks in advance for your help!

When rendering timelines from Premier, AME will occasionallly stop rendering.  I can end the queue, duplicate the item, then start rendering again and it will usually complete.This leaves an incomplete pair of files (.aac & .mp4) in the destination folder.I can't delete those filels unless AME is closed, BUT when I go to close AME, it hangs and has to be force closed. Once closed those orphan  files can be deleted.Log just says "encoding failed." No clue why.Log shows 27 of these events since 9/16/25.  System info    Application: Adobe Media Encoder (Beta) v25.6.0.85    OS: Windows v10.0.26100, RAM: 63.79 GB GB, CPUs (logical): 16.nVidia 5080 gpu 8.1.968-1 driver

While I can see the Caption track is selected in Media Encoder's export settings, it is not being encoded.I can export the same sequence with captions directly from Premiere Pro. Steps to reproduce:Export a sequence with a captions track from Premiere Pro in Media Encoder with Burned In Captions selected Result: No captionsExpected: Video with captions  System info    Application: Adobe Media Encoder (Beta) v25.6.0.84    OS: macOS v15.6.1, RAM: 128.00 GB GB, CPUs (logical): 16

Media Encoder Beta - Überwachter Ordner funktioniert nicht. Projekt Datei in den Ordner gepeichert, aber Verarbeitung startet nicht.

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!