Adobe Media Encoder (Beta)

From PR Beta or opening directly, I just get "Press okay after attaching the debugger." Clicking ok just results in nothing.   Stan System info (from PR beta; cannot open AME)    Application: Premiere Pro (Beta) v22.5.0.28    OS: Windows v10.0.19043, RAM: 63.80 GB GB, CPUs (logical): 16

Reset all preferences and deleted all cache. Previous issue with message to attach debugger. See this thread: https://community.adobe.com/t5/adobe-media-encoder-beta-bugs/ame-22-5-0-build-25-won-t-open-attach-debugger/idi-p/12945193   This new problem occurs when a) queuing from PR Beta 22.6.0.44, b) openeing AME and opening PR project (without opening PR), and c) opening AME and adding simple video file.   Steps to reproduce:    1. Add item to AME queue.     2. Click on link to edit preset options. Result: Crash with error report. (3 reports sent)Expected: Edit preset dialogue would open. System info    Application: Adobe Media Encoder (Beta) v22.6.0.43    OS: Windows v10.0.19043, RAM: 63.80 GB GB, CPUs (logical): 16

Steps to reproduce:    1. Quit Media Encoder BetaResult: "Sorry, an error occured" crash dialog. Preferences are not saved and encoder queue is not cleared.Expected: Quit System info    Application: Adobe Media Encoder (Beta) v22.6.0.38    OS: macOS v12.4.0, RAM: 64.00 GB GB, CPUs (logical): 10

After effects project is not an option to add to watch folder for encoder render queue

Steps to reproduce:    1. ...Export project from Premier  Result: ...AME reports WARNING and lists two files that are missing.  Go to Premier and they're there. Check on  File Explorer and they play OK.  If exported the two files show with the "missing asset" warning graphic.Expected: ...AME to not throw warnings Workaround: Export directly from Premier. It works.  System info    Application: Adobe Media Encoder (Beta) v22.3.0.30    OS: Windows v10.0.22000, RAM: 63.80 GB GB, CPUs (logical): 16

Updated to the lastest versions of the After Effects BETA and Media Encoder BETA and when I try to send my compositions to the media encoder quueue. the composition never appears. Please help

(Version 22.4 Build 38)When exiting media encoder it seems that files are not removed from the queue on exit. I did check my preferences as well. Thanks!  Johann

Steps to reproduce:    1. ...Rendering a project that is 2048x1536 4:3 to 1920x1080 16:9, letterboxed. using any number of combinations of preset or custom settings Result: ... Rendering nearly completes then system hangs - no mouse, no keyboard, have to crash out, leaves sizable temporary files in destination folder.Expected: ... Rendering to complete without crash System info    Application: Adobe Media Encoder (Beta) v22.4.0.19    OS: Windows v10.0.22000, RAM: 63.80 GB GB, CPUs (logical): 16

Steps to reproduce:    1. Apple ProRes 422 file recorded at 74.93 fps - exported in AME as h.264 "Match Source - High bitrate"  Result: Exporting at 60 fpsExpected: I would expect match to match or at least alert me.  This was noticed while creating proxies. I have attempted through premiere beta and 22.2.0 (Build 128) "create proxies." with a user created preset. Also attempted with an adobe preset and on a last attempt brought the .mov file directly into AME   System info    Application: Adobe Media Encoder (Beta) v22.3.0.56    OS: macOS v12.2.1, RAM: 64.00 GB GB, CPUs (logical): 8

Rendering a 60second video in Media Encoder results in choppy motion, easily visible in first few seconds. Rendering same clip with AE first, using "Best Settings", then re-encoding using AME results in smooth motion. In ME, I tried multiple presets, including "YouTube 1080p Full HD". All result in same choppy motion. Videos are too large to attach here. 

When exporting files from Premiere through Media encoder, if overwriting existing files it is appending '_1' to files, even if I have already selected OK to replacing the file in Premiere pre-arrving at Media Encoder.

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

In the latest beta of AME (22.0x50) and PPro (22.3.0x102) it is impossible to export a ProRes with audio, because it always fails with the error "Incompatible Audio Codec found in the preset. Preset load failed.". I cannot load my project into an older version of PPro (I konw about editing the version number and all that) because it refuses to load, so I am royally screwed. Looks like this error was last around in 2018. And it's back with a vengeance. No workarounds possible...except I'm fooflishly going to update my beloved PPro version 21 (public release) to 22.2 in the hope that that will work 🤞. I am now exporting, seemingly successfully, using PPro 22.2.0 (Build 128) and AME 22.2 (Build 64)....so far, fingers crossed!

AME wont export to Prores 4444 when audio is turned off in preset. Incompatible audio codec found. When audio is checked it exports as expected.    

Adding my comp to the Media encoder opens Media encoder, but does nothing afterwards

When I hit Send to Media Encoder a second time in the same project AME stays in the background. Have to bring AME to the foreground in order to hit Start Queue.   Premiere build 82, AME build 30    

AME won't run unless system is rebooted. Obviously it's not closing cleanly. Steps to reproduce:    1. Start computer2. Run AME and render some footage3. Close AME4. Restart AME Result: Nothing happensExpected: AME to run  Workaround: Reboot computer System info    Application: Adobe Media Encoder (Beta) v22.3.0.8    OS: Windows v10.0.22000, RAM: 63.80 GB GB, CPUs (logical): 16

To reproduce the error:Close AME.No transcodes running. Log file attached.

AME Beta v22.3 (build 😎 not responding when it is quit. MacOS Catalina 10.15.7. This version of AME Beta performs as expected during encoding of After Effects Beta v 22.3.0 (Build 37) files but does not shut down when quit, instead showing as not responding in Activity Monitor. This occures with every encoding session.

Steps to reproduce:1. Open AME2. Render something3. Close AME4. Open AME again, or have Premier try to invoke it Result: ...NothingExpected: ... Program to start Workaround (other than restart): go to Task Manager, find and end AME process. Then program will launch. System info    Application: Adobe Media Encoder (Beta) v22.3.0.8    OS: Windows v10.0.22000, RAM: 63.80 GB GB, CPUs (logical): 16

When i hit stop on a render - i want it to stop. dont keep asking me if i really want to stop. just let me stop the render.

I have a long list of files to render, but AME is not preventing the machine from sleeping.  It shut down mid-render.Fortunately nothing was lost, but it should keep the machine from sleeping while it is actively rendering.

Outside of Beta, when I export a project to ME from PP and I give the item the same name as an existing file, PP prompts me to replace or rename (I select replace), it then goes to ME, I hit go and the file is replaced. Insdie of Beta, the same thing happens in Premiere, but when I hit go in ME, it creates a _1 version. Am I doing something wrong, has the experience changed or is this a bug?

In the latest beta release of Adobe Media Encoder, we’ve made some changes to the user interface, and we’d like your feedback. The changes are not major – you might not even notice them right away – but if you see something odd, we’d like to know!     The changes in Adobe Media Encoder are coming as part of an update to the tools that Adobe uses to manage the user interface of many of our products. These tools help to make the interface of our products more consistent.     We want to know what you think. Please join the conversation below.  

I am fairly new to Adobe Media Encoder.  I am looking to save several items to the encodeing queue, but I want to limit the program to run them in sequene to avoid having any hardware issues.  I am using GPU rendering to help speed, but each time I click on run, it starts running multiple items at once. Please help.  This community has been great helping me already - thanks!