Avid DNxHD 1080 render fails

Weldon wrote on 5/5/2013, 1:48 PM
Over the past few weeks, VP12 has become damn near worthless for me. I have been using it since beta with no problems until this recent update to build 563. I can't work in the program for more than a few seconds without a "not responding" fail. I turned off GPU acceleration which seems to have corrected that problem though now I am unable to render out to the Avid DNxHD codec I have been using with VP for years. The project will get a few frames into the render and I get the Sony Vegas has stopped working popup. This is the second straight project I have had this happen. My footage is 1080i AVCHD with minor color correction. The project prior to this one, that also failed, had considerable graphics from Gimp and I thought that may have caused the Avid fail. Anyone else seeing problems with 563? I have had no new software installed and did a clean install of VP12 after doing a system restore to a known good point.


musicvid10 wrote on 5/5/2013, 4:14 PM
Are you using DNxHD 2.3.8?
Show us your render settings for DNxHD. As with all MOV formats, it doesn't like anamorphic.
Weldon wrote on 5/5/2013, 5:47 PM
I am not sure what version DNxHD I am using. I had to reload last year when VP12 came out. I have used it for quite a few projects with VP12. Did something change with the 563 build?
Do you want me to post a screen shot or are there specific settings you want to see?
It looks like I am using version 2.1.0 of the dnxhd.
Seth wrote on 6/5/2013, 11:17 AM
Sorry I didn't see this post earlier. I've been having trouble recently in setting up the 'perfect' DNxHD render to deliver a project, but finally got through to completion. Here's what I did:

1. Updated Quicktime to 7.7.3
2. Updated Avid Codecs to 2.8.2
3. Turned off GPU acceleration of timeline [which sucked because it basically doubled the render time with all the effects I had running]
4. Set render settings to Project defaults and adjusted quality/3D settings through the project properties window instead.

A 37 minute timeline took nearly 60 hours to render. ALL cpu, little-to-no multi-threading, from what I could see in Windows task manager.. But I got the job done.