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
    June 10, 2018

    Still remaining patient but it's been quite a while since Adobe was aware of the problem.

    When will it be fixed?

    Dmitri Graf
    Adobe Employee
    Adobe Employee
    June 11, 2018

    I can't comment on release schedule, but soon.

    Angry_Beards
    Participant
    June 24, 2018

    Hi Dima, thanks for the update.

    This issue is really starting to disrupt my schedule now. I've lost a great deal of time due to it and I'm sure I can't be the only one expecting compensation?

    Participant
    June 2, 2018

    Me too, I have the same setup and the same problem. Reverting to Davinci Resolve...

    Participant
    May 24, 2018

    Also having the same issues with 4K .mxf files on AME.  Using both Macbook Pro 2015 and Mac Pro (late 2013) - same problem each time.  Tried different target formats including 1024x540 Pro Res (proxy) / 1024x540 GoPro CineForm.  Tried multiple times, always AME hanging after around 10 minutes of encoding without problem.

    Did the same thing a month ago without any issues. 

    Thanks

    Dmitri Graf
    Adobe Employee
    Dmitri GrafCorrect answer
    Adobe Employee
    May 16, 2018

    Hi all,

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

    Sorry for the inconvenience, but please stay patient.

    Known Participant
    May 17, 2018

    Thanks Dima!

    If you've already identified the underlying cause, as a developer myself, I'd be very curious to know what it is.

    Known Participant
    May 15, 2018

    I've now had my support case for this issue closed as "needs engineering"

    Adobe right now have no idea what the problem is, and they've been able to internally process my files without problem.

    I've been officially advised to generate proxies via another route as a workaround.  In my case, that's with ffmpeg

    For anyone else suffering this problem, please feel free to use the ffmpeg script that I posted above.

    Participating Frequently
    May 15, 2018

    I will say that I have 2 computers at my location to try and convert on. One works as expected with no issue (Mac Pro 5,1). The other one (Mac Pro 4,1) is the one that always fails. Both have the same software on the same versions, the only difference is the hardware????

    I don't get it.

    Participating Frequently
    May 14, 2018

    I'm having the same issue. I'm on a mac pro 4,1. OS 10.11.6. Latest version of media encoder and premiere.

    I can't get it to go past 9:36 of encoding. After that time I get a beachball. No matter what I've tried so far 9:36 and beachball crash.

    Source files are UHD from Sony FS7, trying to create 1024x540 ProRes 422 (Proxy) files?????

    Can't figure this one out. Have done a bunch of retting permissions, trashing databases, etc.....nothing changes. 9:36-crash!

    Participating Frequently
    May 14, 2018

    You probably have long files so this might not help, but I have been doing in them in batches which helps. Also be careful that you don't just start again after a crash. Check your proxy folder. correct any files that have _1_ in them, sometimes it makes duplicates and Pr does not recognize those files. Clean up and do one at a time if you have to...

    Known Participant
    May 8, 2018

    I can further add that Media Encoder also fails when launched directly (not via Premiere) and set to scale down and transcode to AppleProRes 422 (Proxy), and that I now have an open ticket with Adobe for this issue.

    Not a true answer, but a workaround, is to use ffmpeg, via the sample command:

    ffmpeg -i INPUTFILE -vf scale=1280:720 -codec:a copy -codec:v prores -profile:v 0 OUTPUTFILE

    I've wrapped this in a shell script adds a progress indicator and less verbose output, runnable as "proresproxy.sh INPUTFILE"

    source for the file is here: https://gist.github.com/kevinwright/24baf2470d4fbd1d12b5cd1118e7d680

    Participating Frequently
    May 8, 2018

    System:

    Version: Media Encoder 2.1.1 (build 12)

    OS: macOS Sierra 10.12.6

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

    Radeon Pro 460 4096 MB

    Intel HD Graphics 530 1536 MB

    Settings:

    source file: GH5

    Target format: Quicktime / 1920x1080 AppleProRes 422 (Proxy)

    Renderer:  (OpenCL)

    Luckily, at this time I do not have huge files to transcode to proxies. That being said, Media Encoder just plain crashes some time into the ‘make proxy’ process. This was not happening to me on the last Pr/ME versions. I have taken to doing the proxies in batches, ten or 15 files at a time. I have had crashes during the process and at the end. It completes the last proxy and crashes. Now I get about 1 out of 3 batches without a crash…. not so good.

    What I find really clumsy is that if you select a clip that already has  a proxy at a specific resolution it Pr still makes another proxy. So now I have to look at the proxy folder to see whats next if I don’t make a note. Making duplicate proxies is silly you already have one.

    Anyway Adobe, please get on it or give us a work around or something.

    Participant
    May 4, 2018

    Following this.  I am having the EXACT same issue.