Skip to main content
Known Participant
May 3, 2018
Answered

Media Encoder hangs rendering a prores proxy under OSX/macOS

  • May 3, 2018
  • 19 replies
  • 11346 views

System:

Version: Media Encoder 2.1.1 (build 12)

OS: macOS High Sierra 10.13.4

HW: MacBook Pro (Retina, 15-inch, Mid 2015)

GPU:  AMD Radeon R9 M370X 2048 MB /  Intel Iris Pro 1536 MB

Settings:

source file: 3840x2160 h264 in quicktime container, 25fps, 4:2:0 8-bit colour, approx 1hr long

Target format: Quicktime / 1024x540 AppleProRes 422 (Proxy)

Renderer: Mercury Playback Engine GPU Acceleration (OpenCL)

When invoking "create proxies" under premiere, with the above system/settings, Media Encoder stalls and becomes unresponsive roughly 25% of the way through - though it continues to utilise very high amounts of CPU.  Both source and target files are on the local system disc.  The system is set up to NOT sleep when running of mains power.

Given that the estimated transcode time is 4 hours, it's especially painful to lose an hour's time when it dies

    This topic has been closed for replies.
    Correct answer Dmitri Graf

    Hi all,

    We are aware of the issue and working on a fix.

    Sorry for the inconvenience, but please stay patient.

    19 replies

    Participant
    January 7, 2022

    Still having this issue in 2022

    Inspiring
    July 19, 2022

    same

    Participant
    October 27, 2019

    Just came here to express my frustration

    jakeprice
    Known Participant
    September 16, 2019

    What's maddening here is that Abobe says they know what's wrong, are working on it and a year later...nothing!?!!?

     

    It's much more than an inconvieniance.

     

    What worked for me was switching the Mercury Playback Engine to Software Only.

    Participant
    July 3, 2019

    I just started having this issue.

    I am using AME 13.1

    Matt Peter Waltt
    Participating Frequently
    August 27, 2018

    Hello Adobe, are you still working on this bog or did you consider it solved, cause for me it's not.

    Dmitri Graf
    Adobe Employee
    Adobe Employee
    August 27, 2018

    Matt, what version of AME and PPro are you using?

    Known Participant
    August 17, 2018

    Add me to the list of users needing a fix for this please. I'm on a new imac pro and AME is useless for creating prores proxy batches. constantly freezing. This has been happening for months. H264 encodes are no problem.

    This issue is not listed under the new version's bug fixes, so I'm hesitant to update. See attached.

    Dmitri Graf
    Adobe Employee
    Adobe Employee
    August 20, 2018

    Jesse, this issue is fixed in 12.1.2 so please update.

    We have many different lists so this bug just didn't make it into this list, but I verified personally that it's fixed in 12.1.2.

    Cheers,

    Known Participant
    August 27, 2018

    Since updating to the AME 12.1.2, my batch encodes are working fine.

    I also have a huge tip for anyone suffering from your display not waking up after a long batch export. Download caffeine and make sure it's on before beginning your exports. I use it for my overnight encodes and just turn my screen brightness down to low to save the monitor life. This solved that problem.

    Participating Frequently
    July 24, 2018

    Just batch converted a two day shoot last night - no problems!

    Participating Frequently
    July 6, 2018

    Hi Folks,

    Also preventing from losing all my hair due to this new AME feature (save us some disk space by not creating too many proxy files!!). On my end here I'm just moving on:

    1) Open ACTIVITY MONITOR, the go to the WINDOW menu, and open GPU history. Depending on your Mac setup, it will show one or 2 rows.

    2) Open a finder window showing the location of your proxy files

    3) Open your Premiere project, and go create your proxies. It will fire up AME, and start doing it's thing.

    4) By the 3rd clip (probably), it will crash. But WAIT - it didnt crash. It's still running. Keep an eye on the GPU HISTORY.

    5) When the GPU history gets idle, you latest proxy file is ready.

    6) FORCE QUIT AME, and sometimes FORCE QUIT Premiere as well, since it can happen that PR will crash too.

    7) If Premiere didn't crash, good. Just save the project, and ATTACH the PROXY just created (but not showed to us).

    8) If Premiere crashed together with AME, the restart it and check for missing (not attached) proxies, and re-attach them.

    9) Clean Media Cache and Delete Unused Caches, to keep things as clean as feasible.

    10) Go to the next files needing Proxies, and create them, and just keep looking at the GPU history and your proxy folder. And on and on...

    I've been doing this for 3 weeks now. It works. Once you have your proxies, your are good to go to your editing. Just to make sure: I have two Macs - MacBook Air 8 GB RAM (brand new) and MacBook Pro 16 GB RAM, Touch Bar and a nice GPU. The problem happens exactly the same o both machines, with several different projects. Even creating from scratch.

    Never thought Adobe engineers would allow such a nightmare land on one of the most sensitive aspect of our workflow. I used to let my computer running overnight with dozens of files, and by the morning all proxies created, and good to go. Now I spend almost 2 days babysitting this process. I have 5 big projects do delivery by the end of the month. Will have to stay up awake for several nights to make it happen. At age of 50, not very healthy. Thanks Adobe!

    Participating Frequently
    July 13, 2018

    I have fixed I think - it's a little ugly - but trash newest version of AME and then from Cloud installer got to Media Encoder other versions and install version 12.1 instead.. Just testing now but seems to be working! 

    This bug has been around so long!!

    mattiasg20167126
    Participant
    June 29, 2018

    I have the same issue now. All proxy making from 4K to a lower resolution has worked fine in the past, but when I started making proxies from the material out of my new Gopro Hero 6, then I have this exact issue. Halfway through the making of the proxy it freezes. Sometimes it also freezes before getting started.

    This sucks! Looks like the bug has been there fore more than a month now and I have no way of completing my current job until the bug is resolved! =(

    Participating Frequently
    June 29, 2018

    Another (very painful) workaround is to use CC17 media encoder. It works for me. The painful part is having to set each clip up by hand, and then attach by hand. Not ideal, but in a pinch it can work.

    Iskandar Bwefar
    Inspiring
    June 25, 2018

    I’m having the same issue. Trying to encode proxy files captured with my Panasonic EVA1. It’s about 80 minutes of footage. ME get’s stuck after a while and then I have to manually restart it.

    System:

    Version: Media Encoder 12.1.1 (build 12)

    OS: macOS High Sierra 10.13.5

    HW: MacBook Pro 2016

    GPU:  Radeon Pro 460 4096 MB

    Settings:

    Source file: 4096x2160 h264 in Quicktime container, 25fps, 4:2:2 10-bit color

    Target format: Quicktime / 1024x540 AppleProRes 422 (Proxy)

    Renderer: Mercury Playback Engine GPU Acceleration (OpenCL)