Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve Failed to encode video frame

  • Failed to encode video frame

    Posted by Peter Berg on April 28, 2011 at 8:28 pm

    Has anyone got this error before? When I am rendering out, I get the message “Failed to encode video frame” and the application will crash. I am trying to create a H264 quicktime. I have done it before in the past and it usually works fine. I can play though the sequence and it looks good in the Resolve. All conflicts have been resolved. I can export out as DPX or Avid MXF media with no problems.

    Any ideas?

    -Peter

    Mikhail Puzyrev replied 15 years, 2 months ago 3 Members · 6 Replies
  • 6 Replies
  • Mikhail Puzyrev

    April 28, 2011 at 8:40 pm

    I’ve had this error after upgrading the cuda driver to version 4. The second reason could be lack of disk space. rolled back to version 3 – error gone

  • Peter Berg

    April 29, 2011 at 8:57 am

    Thanks for the info. I do have lots of free space on the render drive.

    I am currently running CUDA driver 3.2.17. I never did the upgrade to the version 4 driver. I did restart the application a few times (well it did crash every time). I eventually exported as a Prores file and that worked fine. A little frustrating.

    -Peter

  • Rohit Gupta

    April 29, 2011 at 9:09 am

    What is the size of your project – number of timelines, length of each timeline, and number of clips in each timeline?

  • Peter Berg

    April 29, 2011 at 9:14 am

    Hello,

    I have about 25 timelines in my project. 9 of them are longer (about 12000 frames each). The rest are short (about 2000 frames each). The one I was trying to render out is 945 frames. Does the H264 require more resources (and thus might fail with big projects)?

    Are there performance guidelines about how many timelines, files in the media pool, etc?

    Thanks,
    Peter

  • Rohit Gupta

    April 29, 2011 at 10:36 am

    Yes, normally we recommend breaking up projects in less than 20 minute chunks.

    Also – try removing away as many timelines as you can to free up some memory.

    Yes H264 is a major resource hog.

  • Mikhail Puzyrev

    April 29, 2011 at 12:47 pm

    You can also check system drive for free space as the database usually sits there. The workaround could be to render anything from image sequence to uncompressed qt and then use MPEGStreamclip (free) to convert it to h264.

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