Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere Pro heavy Freeze spikes during rendering using CUDA mercury

  • Premiere Pro heavy Freeze spikes during rendering using CUDA mercury

    Posted by John Mayer on October 27, 2014 at 12:10 am

    When I am rendering a movie with Mercury CUDA in premiere, it makes my computer literally unusable. Freeze spikes that I cannot move the mouse at all for like a minute or two. Using render preview as Software is more bearable, no freezes and render time is now half.

    I think it have to do with Sli setup, but I’m not sure as I had a single card Titan not long ago and I changed to Sli GTX680 recently at the same time Premiere was moving to 2014.1.

    I have upgraded to the latest nV drivers and the issue remain.

    John Mayer replied 11 years, 6 months ago 3 Members · 9 Replies
  • 9 Replies
  • Kevin Monahan

    October 27, 2014 at 6:32 pm

    Hi Jon,

    [JonZ MarZ] “When I am rendering a movie with Mercury CUDA in premiere, it makes my computer literally unusable. “

    By “rendering” do you mean exporting? Is there a difference if you press Queue rather than Export?

    Thanks,
    Kevin

    Kevin Monahan
    Support Product Manager—DVA
    Adobe After Effects
    Adobe Premiere Pro
    Adobe
    Follow Me on Twitter!

  • John Mayer

    October 27, 2014 at 6:40 pm

    yes, I mean exporting. I don’t know if it because of the codec, I use mainly h.264 to export. I don’t use queue because I don’t have AME. It not the action that freeze the computer, but the rendering process, it start slowly then when it getting a bit deeper in the process, it start freezing badly, I can’t move the mouse at all until that spike goes away.

    So every time I have to export, I have to switch the rendering engine to software Mercury engine.

  • Kevin Monahan

    October 27, 2014 at 6:56 pm

    Hi Jon,

    [JonZ MarZ] ” don’t use queue because I don’t have AME.”

    Reinstall Premiere Pro. All installations of Premiere Pro simultaneously install AME. You need AME for export components to work correctly.

    Thanks,
    Kevin

    Kevin Monahan
    Support Product Manager—DVA
    Adobe After Effects
    Adobe Premiere Pro
    Adobe
    Follow Me on Twitter!

  • John Mayer

    October 27, 2014 at 7:41 pm

    It doesn’t solve the issue.

  • Kevin Monahan

    October 28, 2014 at 8:39 pm

    Hi Jon,
    What happens if you use “Queue” not export? Can you try importing the sequence into AME directly?

    Thanks,
    Kevin

    Kevin Monahan
    Support Product Manager—DVA
    Adobe After Effects
    Adobe Premiere Pro
    Adobe
    Follow Me on Twitter!

  • John Mayer

    October 29, 2014 at 2:36 am

    It have the same symptoms. I did a couple of presets and different codecs, and the symptoms differs from a codec to another. I tried with AVI lagarith and it was the one that was less harsh on the system, but still have system hang. Worst, switching to Mercury software renderer doesn’t seem to affect the choice I made, it have the same symptoms of CUDA rendering. I have to switch back to Mercury Software rendering inside PP to make it work right.

  • Kevin Monahan

    October 29, 2014 at 4:10 pm

    Hi Jon,
    Sorry for all these problems. Can you open a case with my colleagues in support? https://helpx.adobe.com/contact.html Make sure to get a case number so we can track what’s going on.

    Thanks,
    Kevin

    Kevin Monahan
    Support Product Manager—DVA
    Adobe After Effects
    Adobe Premiere Pro
    Adobe
    Follow Me on Twitter!

  • Ericbowen

    October 29, 2014 at 4:19 pm

    What are the specs of the system btw?

    Eric-ADK
    Tech Manager
    support@adkvideoediting.com

  • John Mayer

    October 29, 2014 at 8:54 pm

    It a i4770k with 16gb of ram, and like I mentionned above it coupled with GTX680 Sli mode. After discussing about the situation with my employers, I decided to change my hardware and new equipment will arrive next week (not because of this reason, other reasons too). Will see if the problem still persist. Thanks for the help.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy