Wagner Cursino

My feedback

  1. 9 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Media Encoder » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Wagner Cursino commented  · 

    Hi Larry, did the test. No difference whatsoever. Anyways, this is kept disabled. HOWEVER... Found something interesting -->>> If I click on the AME App window, making it the FOCUS of Mac OS - the active app - then there's NO ISSUES. It simply works as expected. So I click in the App, make it the active app on Mac OS, and just forget it. If, however, I go to another app, Safari, Finder, and leave the computer that way, then the 180 hours comes back. If I open 10 apps, no matter how heavy they are, but before leaving my computer, I click on AME window, it works fine. If I have only AME and Finder, nothing else open, but forget to click on AME window, letting Finder be the 'active' App, before leaving my computer, then the 180 hours are back.

    An error occurred while saving the comment
    Wagner Cursino commented  · 

    Hi Larry. Here we go:

    - Mac OS Mojave. Latest.
    - MacBook Pro 2016 15" - AMD Radeon Pro 455 GPU
    - Source file: Premiere sequence - 1h25min video.
    - Renderer: same than previous version - OPENCL. Tested also by changing to METAL. No improvement whatsoever.
    - Export: H.264, 23.976fps, 1080p, 10mbit/s, Variable Frame Rate, 1 Pass, Hardware Encoding Enabled.

    IMPORTANT: If my computer is active and rendering - not in sleep, screen saver or blank screen - it works normally. If I let it alone, and the screen saver kicks in - and by the way, my screen saver is only the clock, not heavy 3d animations - then it starts to crawl to 10 to 20 times slower than normal. I would love to disable the screen saver, but my corporate profile set it to a maximum of 30 minutes. Anyways, this issue didn't happen with the previous version. So my folks at Adobe, here we go again.

    Wagner Cursino shared this idea  · 
  2. 30 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    20 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Wagner Cursino commented  · 

    Brian - Indeed. Using Premiere while rendering speeds AME. Stupid but hey - computers where exact machines only before the discovery of Quantum Physics. ;-)

    An error occurred while saving the comment
    Wagner Cursino commented  · 

    Just adding - I'm talking about Adobe Media Encoder CC 2019. And I noted that it defaulted the RENDERER to METAL. Yesterday AME was on OpenCL.

    An error occurred while saving the comment
    Wagner Cursino commented  · 

    Same here - just that it is taking 180 hours to render, while the normal would be 6 hours. HOWEVER there is a CATCH: This slowness came while the computer was NOT being used - overnight, in screen saver/standby mode. When I came in the morning and started using it, the 'Remaining' info in AME started to drop dramatically. Now it is about 78 hours to finish, and dropping. Doing some calculations here, it might finish in the 6-7 hour estimate, as long as I don't let the computer alone, I'm assuming. IMPORTANT to note: I did the same thing yesterday, same video, same computer, same overnight rendering. It took 6 hours.

    Wagner Cursino supported this idea  · 

Feedback and Knowledge Base