Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro RenderAs crash pattern with GPU detected – workaround found

  • RenderAs crash pattern with GPU detected – workaround found

    Posted by Mark Barton on April 20, 2013 at 3:56 pm

    I was rendering some slide shows with the MainConcept AVC/AAC Internet 480p template with a higher bitrate configured and was noticing it would hang at around 40% and the GPU utilization went to 0% (as shown by a third party utility).

    I also noticed if I ended Sony Vegas Pro 12 with the task manager and launch it again only opening the project file and immediately going to RenderAs, it would complete the task successfully. Once I got my two slideshows done, I came back to do a test.

    If I open a project and play it in the video preview window for a minute or so and then choose RenderAs, the task will not complete and the GPU utilization goes to 0 again. If I do the RenderAs as the first task of my Sony Vegas session then it completes just fine.

    I suspect it might have to do with how the memory buffers and/or the GPU cores are initialized for viewing/rendering. So now I will save my project and exit Sony Vegas before I do a render and see if I avoid the hangs. I did try the CPU only render, but it did take twice as long (40min vs 20min).

    David Alfredo replied 13 years ago 3 Members · 2 Replies
  • 2 Replies
  • Michael j Toffan

    April 20, 2013 at 4:51 pm

    Mark, very interesting observations, thanks for sharing.

    Fortunately it has been awhile since I have run into a hang during rendering (knock on wood). When it does happen, I end up bailing out and re-doing the render. I am going to bookmark your comments and try your work around next time I run into that issue.

    Hopefully your observations are also insightful for the Sony Software team.

  • David Alfredo

    April 22, 2013 at 8:36 am

    seems like a drivers issue to me, once some of their functions are invoked. Try updating or rolling back to a previous version and check again.

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