Questions

When running ME in darkest mode, it's nearly impossible to see if you have an item in the queue selected as shown in the screenshots. This also does not mirror the color of a selected item in PP as shown in the screenshot. When you shift to dark mode, the selected color is confusing to me since it just blends in with the rest of the iterface. 

Steps to reproduce:  Add item to Media Encoder queue.  Sign into Vimeo from within Media Encoder (and enter title, etc.).  Encode queue item and wait for upload.  Add a new item to Media Encoder queue.  Sign out of Vimeo from within Media Encoder.  Sign into a new/different Vimeo account from within Media Encoder (and add title, etc.).  Encode queue item and wait for upload. Result: Both items were completed but uploaded to the same Vimeo account - the first one that was signed into. The second queue item showed the correct Vimeo account information for the second Vimeo account signed into, but uploaded to the first account.Expected: Both items should be completed, but the first one should be uploaded to the first account and the second item to the second account. System info    Application: Adobe Media Encoder (Beta) v24.3.0.39    OS: Windows v10.0.22621, RAM: 31.88 GB GB, CPUs (logical): 8

newest beta AND updated 24.3 can't normally export.only 24.2  still working properly.

This is really a question about best practices to improve AME Beta opening after an update. Current specs below. The most recent context is testing a PR export with caption sidecar problem: https://community.adobe.com/t5/premiere-pro-beta-bugs/pp-beta-hangs-when-exporting-mp4/idc-p/14569420#M2574   For many versions, AME Beta fails to open when queued from PR Beta. And if I open it first with a preferences reset, that may or may not work.   Today I updated PR Beta to 24.5.0.16 and AME Beta to 24.5.0.14. Throwing caution to the winds, I queued from PR without starting AME separately. No splash screen; I did see AME Beta running under PR in task manager but not in its own process.   Restarted PC. Opened AME Beta with Shift modifier; no splash screen.   Restarted PC. Opened AME Beta with Shift modifier; got the splash screen and preferences reset. Reset all. Opened.   Left it open. Started PR Beta. Queued successfully.   I posted several times in th

Media Encoder Beta keeps crashing which I click the Output Files link when I want to renmae or changed final save location.

I have 4 different custom encode presets, and none work now after the latest update

Files won't encode, has been stuck for 10 hours

 

Because of enhance speech and a few processing effects (I assume) it's taking 10 minutes to export a 45 second video. I'm on a M1 Pro Macbook - this would normally take 15 seconds. But it's rendering audio files for 10 minutes each before finally exporting the video. Really awful.

I have a M2 13' Macbook Pro. When i run the audio enhancement on premiere pro my cpu load shows up in the high 10% to low 20%, but my cpu temps stay in the low to mid 70°C. When rendering said video with enhanced audio, using  Adobe Media Encoder (Beta), i got CPU loads of low 20%, but with concerningly high CPU temperatures of as much as 86°C!!!! please look into this as these high temps are very detrimental to the life of CPUs. if there is any information i could provide to help recreate the problem, please don’t hesitate to let me know!

When rendering a video file in HD or 4K in AME the render stack on the last frame from 10-15 min up to couple of hours. I'm working on a new and powerful computer so no issues of hardware out of date. The problem is with all latest version of AME and I heard this problem from others as well.

Steps to reproduce:    1. ...I have about a 2 hour and 40 minute 4k video to render, and it takes about 14 hours, so doing this overnight is ideal.  I have been storing my files on a QNAP with a fast connection (including thunderbolt), but putting my temp files on a local drive. Result: ...Expected: ...I expect the job to finish, however I get a code 3 error.  It has taken a good moment, but I finally figured out that my ME job ended at the same time as my backup was scheduled on QNAP, at 5am.  Running the ME job during the day succeeded, which avoids the QNAP backup. System info    Application: Adobe Media Encoder (Beta) v24.1.0.38    OS: Windows v10.0.22621, RAM: 63.68 GB GB, CPUs (logical): 20

Media Encoder (beta v22.0 build 42) with Renderer: Mercury Playback Engine GPU Acceleration (Metal) freezes after start of encoding (H.264 Match Source - High bitrate), timing of freeze varies with every file attempted. MFR enabled. After Effects (beta v22 build 60) freezes at the same time. Issue began with AE beta v.22 build 56. Files to big to attach.iMac Pro Catalina 10.15.73 Ghz 10-Core Intel Xeon W64 GB 2666 MHz DDR4Radeon Pro Vega 64 16 GB

We will update our system requirements with the next major release of our video applications. This includes the 24.0 versions of After Effects, Audition, Character Animator, Media Encoder, and Premiere Pro.   This change goes into effect with today’s Beta build.   We update our system requirements each year, which allows Adobe Media Encoder to take full advantage of these platforms and helps ensure optimal performance for you.   Minimum OS Requirements To run Adobe Media Encoder Beta version 24.0, Mac users need to be on macOS Monterey (version 12) or later. Windows users need to be on Windows 10 (64-bit) v22H2 or Windows 11.We recommend running our applications on the latest operating systems:       macOS Ventura (version 13)        Windows 10 (64-bit) v22H2 or Windows 11 V22H2 Please note that support for macOS Big Sur (version 11) will be discontinued. It will not be possible to install the 2

If I attach a LUT in the export settings the LUT isn't applied if I send to media encoder. If I just hit export directly from premiere it is applied. This seems like a new issue (maybe just started with todays update).

'This is the rendered element and suddenly all these boxes appeared out of nowhere. I composed my main composition using a few compositions that have 3D in them. Please let me know how to fix this. 

Just wanted to drop a quick comment/observation that in my first few hours of testing the Beta, I'm already seeing significantly better stability and interoperability between PP and AME on Windows. I was accustomed to getting a PP crash and subsequent crash report prompt literally every time I sent a project from PP to AME on my AMD Windows 10 workstation, but thus far I've already done half a dozen renders and have yet to crash once. I still reflexively save my project immediately before every render out of habit and an abundance of caution, but so far I've had no interop issues at all. Seems like a great step forward.

AME Beta 23.3 (Build 35) fails to render AE Comp from:After Effects  Composition previews fine in AE.After Effects com is one layer: an EXR image sequence, zip compression. OCIO colour management.Add Comp to Media Encoder wirks as expecetd. AME opens and item is added to the queue. On opening the Custom Settings window the visual preview shows as missing - ie: the color bar placeholder.  If rendering is attempted the render completes - but with the color bar placeholder for every frame.

This morning AME Beta 23.2 crashed.  It starts to boot then says it has encountered an unexpected error and cannot continue. I noticed that 23.3 was available so downloaded it.  It's doing the same thing. This is after a computer restart.    OS: Windows v10.0.22621, RAM: 63.80 GB GB, CPUs (logical): 16 

Un changement de couleur via un effet "Teinte/Saturation" sur AE semble rendre impossible un rendu très simple de 12 secondes. Celui ci s'arrête juste avant la fin et fais planter Media Encoder.

Steps to reproduce:    1. Noticed a problem. When rendering on Google Drive, the file size at the end of the render is 24 bytes. When rendering to a local drive (which is in a network environment), the render is correct. On the other computer, this problem occurred when rendering a file from both Premier and Encoder, but the other computer could not render even to the local drive. Therefore, the second computer had to downgrade to version 23.0.My colleagues at the company I work for also have the same problem.Translated with DeepL Result: The result is a defective file of 24 bytes.------------------------------------------------------------- Encoding Time: 00:00:1012/21/2022 11:13:25 AM : Encoding Failed------------------------------------------------------------Export ErrorError compiling movie.Export ErrorError finishing encode.Writing with exporter: H.264Writing to file: I:\Общие диски\[1203494483989220] [5 Minute Crafts] [JA] incredible kids room makeo

I am trying to render after effects simple pojects. but it taking more than 60 hours to render 6 minutes AE project

This is happening all over my project. The combination of warp stabilizer and H.264 enccoding is causing a failure. Removing stabilizing in underwater cinematography makes ruins the experience. I keep getting this error. Some time it blows up and sometimes it does not depending on the clip. Due to color production issues I have been forced use the beta on my new Mac. Stabilization is a critcical part of video making and this needs to be fixed. The situation is creating a big backup on my YouTube channel. In fact, warp stabilizer may be my biggest source of pain form release to release of premier and media encoder.Please fix this. ------------------------------------------------------------- Encoding Time: 00:00:4109/07/2022 07:22:00 AM : Encoding Failed------------------------------------------------------------Export ErrorError compiling movie.Accelerated Renderer ErrorUnable to produce frame.Writing with exporter: H.264Writing to file: /Volumes/Seagate Backup Plus Drive/Premier

keeps loading but not rendering

Hi there,When I use Adobe Media Encoder (beta) 22.4 build 4 on MacBook Pro (16-inch, 2021) mac osX12.4.The Render is fund until last frame it just stops. This usally happens if this is the second export and the best workaround I've found is to log in and out.ThanksJohn