Skip to main content
Known Participant
February 5, 2019
Question

Can't export... Crashing every time.

  • February 5, 2019
  • 2 replies
  • 863 views

I've now tried 4 times.  3 in AME and 1 in Premiere.

I just updated to the latest NVidia drivers, didn't help.  I have many crashes with Premiere, but haven't hit a wall like this for a while.  Crash seems to happen at different points in the sequence.  Second attempt got the furthest.... about 75 percent complete.

Very simple sequence.  1 video track of MP4 files (rendered by Premiere), a watermark PNG, a text version number, and an adjustment layer with timecode.  The project is 1 hour and 45 minutes in length.

I've rendered this sequence before, but not with the timecode.  The composer for our film NEEDS the timecode, so I can't drop it. 

I'm now dropping the CUDA render and switching to software, because most of the Premiere bugs I encounter relate to it's inability to use hardware acceleration with any semblance of stability.

My render times are now increased from 28 minutes to about 60 minutes..... but after wasting nearly 2 hours with 4 failed export attempts, 60 minutes seems like the only course of action.

Wish me luck.

    This topic has been closed for replies.

    2 replies

    Kevin J. Monahan Jr.
    Community Manager
    Community Manager
    February 5, 2019

    VanLazarus,

    Try copy/pasting the clips into a brand new sequence. Your sequence might be corrupted. I believe there may be a bug in certain combinations of GPU accelerated effects and output codecs. The Timecode effect is a GPU accelerated one, BTW, so it will tap your GPU. What kind is it again? Are you scaling 4K down to 1080, as well? That info might help.

    Trying to seek out a potential fix.

    Normally, I would suggest rendering your sequence out as ProRes, then exporting as ProRes (using previews). That also seems to be a solid workaround for a related issue, running your GPU out of VRAM. However, I have observed a few cases where copy/pasting into a new sequence fixes the issue for some people.

    Please let us know if that advice assists you at all. I do apologize for the frustration and always appreciate your candid feedback.Hope we can help. Thanks to Shivangi for trying to help.

    Regards,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Known Participant
    February 5, 2019

    Thanks Kevin.  I will try these suggestions next time.  So I can now export ProRes files on a PC?  Haven't tried that yet.

    My system specs are:

    i7 5960X

    32gb RAM

    Nvidia GTX 1070

    OS drive: 240gb SSD

    Project drive: 27tb local Raid 0

    Kevin J. Monahan Jr.
    Community Manager
    Community Manager
    February 5, 2019

    Thanks Kevin.  I will try these suggestions next time.  So I can now export ProRes files on a PC?  Haven't tried that yet.

    My system specs are:

    i7 5960X

    32gb RAM

    Nvidia GTX 1070

    OS drive: 240gb SSD

    Project drive: 27tb local Raid 0

    • Yes, VanLaz, ProRes is good to go on 13.0.2 or later.
    • Info on your GPU
    • Are you scaling down from 4K to 1080 on this sequence?
    • Any frame rate conversions?
    • Any color grades on that Adjustment Layer?

    Hope we can assist you!

    Thanks,Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    gupta shivangi
    Legend
    February 5, 2019

    Hi vanlazarus2013,

    We're sorry for the trouble. Sometimes it happens that there is some particular effect or clip which does not let export to complete. In this scenario, I would recommend you to check if the crash happens around a particular timecode. You can also refer to this article: How to fix issues that cause errors when rendering or exporting

    Also, try changing the video renderer FAQ: How to change the Video Renderer in Premiere Pro?  and then check the export.

    Let us know if it helps.

    Thanks,

    Shivangi

    Known Participant
    February 5, 2019

    Sorry Shivangi, but I'm not sure you read my post thoroughly...

    1) The crash is not happening in the same place.

    2) I do not have any effects applied aside from the 'timecode' effect.  I detailed the content of the sequence I'm rendering in my post.

    3) I explained that I was switching the video renderer (to software).

    On a positive note, I was able to render without crashing by using software rendering.  Just took over twice as long to render.

    Just unfortunate that this 'professional' editor can't use my hardware.  Probably the best work-around for preventing crashes in Premiere is to shoot on film and cut them the old-fashioned way.