always getting errors / crashes when rendering

[Dan Powers]

First thing is do not export to your desktop. An old story I was told is that the desktop files are in some way system cached and a over a few gigs on the desktop is a performance hit. Dont know if that is true, but it is sloppy media management at best.

Next what is happening at 2:19? Is it a previously rendered file?

Mark an In and OUT around that problem and render just that section to narrow down what is happening.
I had a similar thing yesterday, and for no reason the renderer would not compile one tiny simple clip.
I changed the scale size slightly as a test and it rendered. Then I reset the scale back to normal and the bug did not come back. May be a different deal with your issue, but the point is to narrow down what is happening.

It could be your source file is wanked. (technical term).
Another option is to Export out the timeline to something other than H264, like pro res or something. Check your sequence settings and see what your native render format is currently set to.

[Todd Perchert]

I’ve had similar things happen that usually involve a large graphic or a third party plugin. I’ve also had Media Encoder do something similar, but worked rendering out from PPro. So best to look at what happens at 2:19:21. Can’t say that rendering to a different codec will help, never did in my case.
TC

[Peter Garaway]

Hey Mike,

Sorry for the trouble. What everyone said is pretty spot on. If you’re on a time crunch, rather than trying to figure out the cause you might want to try exporting the sequence in Software rendering mode. This should allow you to get the export out.

Once you get your sequence exported, we can try to figure out what’s going on.

Peter Garaway
Adobe
Premiere Pro

[Daniel Waldron]

I have also run into this. Usually if you render your entire sequence (Render In to Out) in Premiere, you will see the green bar appearing over your clips as it is rendering, then it will fail and you will get an error message at wherever the issue is. This will help you narrow it down to whatever clip/effect is causing the problem.

[Mike Tyler]

thanks so much guys for the quick responses…

I tried all of your suggestions and they all come in handy – also managed to solve the issue.
And will know what to do next time when something similar happens ☺

Was actually a third party plugin causing the issue..

Peter, how would I go about rendering in software mode ? Never heard of that actually… and google didn’t return much either.

Cheers.

[Peter Garaway]

Glad you got it figured out.

To render in software (using the CPU only) go to File> Project Settings > General. From the Video Rendering and Playback dropdown menu, select ‘Mercury Playback Engine Software only’

If you want to learn more details on rendering in Premiere Pro there’s lots and lots of info here:

https://blogs.adobe.com/creativecloud/cuda-mercury-playback-engine-and-adobe-premiere-pro/

Peter Garaway
Adobe
Premiere Pro

[Mike Tyler]

when we’re talking about format…
I’ve now tried to render out ProRes 422… and compared side by side to h264 with relatively high settings.

And couldn’t see any difference at all.. the h264 seemed to look even better in terms of sharpness.

But I know that people are talking about ProRes 422 being superior in quality compared to h264.

[Brad Coulter]

Thank you for this!!

I get this error often. In the past, I would make sure I had the latest graphic card driver and would clear the project cache. This worked about 12.27% of the time and failed, according to my math, around 87.73%. Generally, I’d end up rendering in software only and that can take forever while making my hard drive and processor sound like a ’82 Chevy Monza with a bad timing belt.

After reading your post today, I found the offending clip/transition where the error occurred, went into Premiere and rendered just that clip/transition, then sent the whole thing back out to Media Encoder.

BOOM! Fixed.

Now I’m not sure what to do with all this extra free time I have.