-
Media Encoder UI goes unresponsive on latest version
Hey all. I have 5 Mac Pros (3.1 and above with a minimum of 24GB RAM) running OSes from El Capitan up to Sierra driven by either GTX 970s or 980s (all 4GB) flashed for Mac. I have never had issues with these in the past. They’re all running the latest NVIDIA web drivers and CUDA drivers, rendering on both open CL and CUDA (while I was trying to find the solution), and Media Encoder seems to be doing this weird thing where it will show an active encode for about 5 minutes, and then the UI freezes.
If I check my render destination folder, the files continue to be generated, but AME is unresponsive giving the spinning beach ball (the image below is of the frozen UI at exactly 5 minutes. The finder had completed the first file about 10 minutes before I took this screen shot) Additionally, there seems to be a huge gap between when one file ends and another begins.
The computer I first noticed this on was originally running an ATI Radeon 1GB card producing the exact results I posted above so I thought maybe it just wasn’t powerful enough. I swapped it out with a GTX 970 and still got the issue. Split the job up across 5 systems and they all seems to have the same issue.
Has anyone else had this issue on the latest version? Should I try to just install 2017 and see if that works? Problem is I already have a PP2018 started and I am creating proxies. AFAIK there’s no way to use AME 2017 to create PP2018 proxies. Rebooting doesn’t seem to do anything either. Any help would be appreciated!
David Parke
Editor
http://www.dparke.com -
6 Replies
-
I wonder if it’s related to the issue I posted last night. https://forums.creativecow.net/readpost/351/2132
[no flash-frames where none intended]
-
It’s a sort of “creeping crud” problem. With the previous 2017 release of Premiere, attempting to send a Quicktime compression to ME resulted in the spinning beachball, and the creation of a file header or something (a name, a generic icon, and zero KB). Oddly enough, my regular h264 and MXF compressions would encode. However, with this latest release, nothing happens…I queue to ME, ME launches…and sits there like a bump on a log doing nothing. There are 5 of us working regularly with this software version, on Mac Pros, Towers, and iMacs, and nobody can make the queue to ME work currently.
-
Thanks Laura and Mike.
Yeah, I saw your post, Laura, and hoped that this would be a slightly different issue since I am using AME to process proxies of my raw media. I don’t even have an edit yet! haha.
Mike – I haven’t had an issue sending to AME, it’ll launch and populate just fine – I can even drag media into it to manually create my proxies. It’s what happens 5 minutes in that really gets me. The UI just freezes. The processes continue in the BG though, although very slowly. I can monitor the destination folder and the files are created without issue. It’s just the UI that takes a dump and I just don’t know why.
Bummer.
David Parke
Editor
http://www.dparke.com -
EDIT: To make matters stranger, when I command-tab into other apps, the progress bar seems to advance in the app icon – one of my favorite adobe features. Still super slow but it does seem to be more responsive than the app UI. The output file was still complete, though. It’s a whole thing that’s not making much sense to me. UI frozen, app icon slow, actual computing process works but is slow to start the next file. Am I the only one having this issue? That it’s on several systems across several OS versions seems strange.
David Parke
Editor
http://www.dparke.com -
UPDATE: I ran Preference Manager and trashed all adobe preferences on one of the 5 systems and I am 10 minutes into a queue of a couple hundred clips. These are different clips than I was encoding previously but this batch was having the same UI issues. Will let these go overnight and see what I come in to tomorrow morning.
David Parke
Editor
http://www.dparke.com -
For those following, looks like my fears are confirmed in this thread: https://forums.adobe.com/thread/2482907
There’s very much an issue with the current version of AME when it relates to batches/ proxies but Adobe knows about it and hopefully they’ll get an update/ fix out shortly!
David Parke
Editor
http://www.dparke.com
Reply to this Discussion! Login or Sign Up