Please add CUDA support back into Media Encoder 2020 for macOS. I use a Mac Pro Mid 2012 tower with an NVIDIA GTX 970 and 64GB of RAM. Only being allowed to use Metal as a renderer increases my export time to more than than 4x for the same sequences from ME 2019. I've tried using Premiere with Windows and Boot Camp, but can't properly edit multicam sequences in Windows on this thing because of constant audio drop outs and delays, so right now my best option is to edit in macOS, then boot into Windows for exporting with CUDA support, which is faster than exporting my sequences directly in macOS. I'll be switching back to Premiere 2019 on my next project and hope CUDA support is added back in in the future.

Can AME offer some kind of 'output monitoring'? For example, often I will have a batch of proxies or sequences queued up to export. Sometimes AME won't fail exporting (give the yellow ! error), it will just hang and stop encoding. This is extremely annoying in its own right, but when it stops early on in an overnight batch encode only to see 4 or 5 out of 20 actually encoded in the morning, it is beyond frustrating that I let my computer run 8 hours doing nothing.

Can AME offer some kind of monitoring that if it is not currently exporting for say, 20minutes it restarts the current encode with a _1 added to the file name?

I will add, stopping and restarting the encode queue after this event always hangs as well. I must restart AME entirely to re-establish the output module or whatever is behind the scenes getting frozen.

This seems to have been introduces with the latest update. I have a preset to render an H264 file with file name and timecode visually burned in. Before updating it worked fine. Now it shows a number(I assume framecount) rather than TC. If I switch to generate rather than source, then it shows TC. But if I save the preset on "generate," it saves the starting time as well, so the TC is not accurate. If I create a new preset, the first application works as expected, but once I apply from the saved preset it fails in the same way.

Bug Report
Media Encoder CC2019 13.1 build 173 on Mac OS X 10.13.6

1. Queue a sequence from PP CC2019 to Media Encoder.


2. Use a preset that has Publish enabled (FTP in my case - account has been tested, and the same preset worked successfully on an earlier render.)


3. The encoding completed successfully with a good file, but the FTP publish step is stuck indefinitely on "Waiting for encoding" (see picture). I have waited 20 minutes.

Log attached in reply message.

Update: After writing this I open the setting and tested the FTP connection.
AME hanged (beachballed). Let it sit for 8 minutes before force-quitting it.
Restarted AME, tested the FTP connection setting again, passed immediately.

I have a bunch of videos being converted to smaller files. I run them when I'm not in the office. Well, the thing is every little while the Adobe window pops up asking if it is still me and I have to click "continue" to stay signed in and every time the window pops up the Adobe programs stop what they are doing so only a couple videos get done. The sign in window is messing up our work flow. It is going to be a real pain if all semester you have to stay with the computer or come back to it every few minutes in order to keep the videos exporting and converting. After a user logs in to Creative Cloud a timer starts and after every 90 minutes a pop-up is shown to the user to continue or sign-in with a different account. We need to be able to set the timer for longer period of time.

See This wasted a whole day of rendering because even though I visually verified that the "Video is VR" checkbox was unselected, it still rendered with VR metadata.
Steps used to recreate:

1. Take two Gear 360 (2016) videos and drop into AME. See droptostitch.png


2. Verify that Export Settings->Video->"Video is VR" is unselected without making any changes.


3. Observe that the video is set to render as "Match source - high bitrate". At this point if left to render it will render with the "Video is VR" metadata injected. See result.png


4. To fix this issue you currently have to go in and manually check and uncheck the "Video is VR" box. Now returning to the main screen you'll see that instead of being "Match source - High bitrate" it will render as "Custom". Now the video will render as expected, sequencing the source clips together without injecting the Video is VR metadata. See expectedresult.png