Bug Reports

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. 

Every time I open Media Encoder 26.2 or send an export from After Effects 26.2 to Media Encoder, ME crashes immediately. Apps are up to date. Tried restarting mac, didn’t work. Tried uninstalling and reinstalling ME, didn’t work. ME preferences were reset to default, cache was cleared, etc., didn’t work.  

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. 

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

Me gustaría saber en detalle cuales son las condiciones pues cumplo con tamaño y definición exigidas. Veo en la categoría ilustración imágenes que en su mayoría son con colores sólidos, sin texturas …. Entiendo que puede ser una tendencia pero deja afuera a otro tipo de ilustraciones en cuyos detalles manuales está la riqueza.  Gracias por su ayuda. 

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?

With the new versions, my graphics card isn't rendering. I don't have a CUDA option. Even though everything worked fine in previous versions.

I'm stacking up a list of MPEG2 VOB files to render to MP4 and I noticed that the "Renderer" reports "Mercury Playback engine Software Only."  And indeed when it's rendering all the business is going on in the processor. The GPUs are idling. I have a brand new nVidia 5080 with the latest studio driver.  Why doesn't  AME think it's there?MisterAdvent_0-1769381163578.png System info    Application: Adobe Media Encoder (Beta) v26.1.1.29    OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

osea que pedo, meten una pinche actualizacion de algo, cagan otra cosa, enserio con ustedes no se puede estar mas de un mes sin alguna cagadera, pinches programas todos estupidos para todo, me quede por una prmocion pitera si ni ya estaria en davinci, mi media encoder no detecta mi gpu siedino una gforce rtx 3080 ti de 12 gb, es una estupides, pago para poder trabajar mes con mes, y ustedes nos usan de conojillos de india, ni siquiera puedo dar clic en donde deveria por que no la detecta.contraten gente que haga las pruebas, no a nosostros que pagamos por trabajar no avientan betas para estar moviendo cosas a cada rato, no sean pendejos o inutiles la beta nunca termina.

I cannot switch renderer to CUDA in latest build. I rolled back to 26.1 and it works fine. GTX 4090Latest NVIDIA Studio Driver

I am running 591.74 (1/5/2025) NVIDIA drivers for GeForce RTX 3080 Ti.  When opening Adobe Media Encoder (Beta) I find that only "Mercury Playback Engine Software Only" is available. Conversely opening Adobe Media Encoder 2025 correctly shows Mercury Playback Engine GPU Acceleration (CUDA) and (OpenCL).  Running the render process in Media Encoder Beta also results in no GPU utilization and render times that are (obviously) 10x slower.  

The Queue window won't appear, even after selecting it in the Window drop down.

Following up on my complaint from months ago, AME beta still crashes mid-render. I'm rendering hourlong recordings of a meeting, Sony FS5 MXF footage, very simple, no edits, just head/tail titles and credits added. Rendering from 2160p to 1080p in HEVC at 10Mbps If I stack 2 or 3 of these, it will generally render one successfully, but the second one will stop midway. Task Manager shows the whole system at idle - no reading, writing or GPU. Pause>restart does nothing.If I stop rendering program still responds.If I duplicate the item and restart, it won't start rendering.If I close the program, it freezes, shows the crash warnings and eventually it goes away after I cancel the "trying to recover your information" dialog. Reopening, duplicating the project then starting the render is a 50/50 chance whether it will work or crash. AME 26.0 (Build 44) Beta - Windows 11 Pro - nVidia 5080

Hello, I tried the new "object mask tool" in Pr Beta (works so great!!) Everything was fine when I exported my video from Pr directly. But when I exported the same video in Media Encoder (beta), the Mask I used in the project did not applied.  System info :    Application: Adobe Media Encoder (Beta) v26.0.0.36    OS: macOS v15.7.2, RAM: 32.00 Go GB, CPUs (logical): 10

this was happening with the older betas, and continues on the newest one. exporting videos with object masks via media encoder gives warning that masks are offline, and exported media does not contain masked layer at all (as if the layer visibility was toggled off). this is not an issue when exporting each video on its own directly thru premiere. System info    Application: Adobe Media Encoder (Beta) v26.0.0.36    OS: macOS v15.6.1, RAM: 16.00 GB GB, CPUs (logical): 8

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