Blackmagic Forum

Hello all,

Recently installed Mavericks & latest version of Resolve (as of Nov 9 / 2013), running on a GTX780.

Every so often, when rendering out from Resolve, I get an error message: "Timeout waiting for frame," along with a frame number. This never happens at the same point in the timeline. I'm rendering R3D's to Prores 422HQ.

Any thoughts?

I'm having the same problem with Blackmagic CinemaDNG files. Sometimes it happens quickly (after only 3000 frames), sometimes it happens less quickly (after 18000 frames), but I've got a concert video that's about 60000 frames. Breaking that up into 20 different 3000 frame segments that I can reassemble later sounds like a crappy work-around.

My system is an early 2011 MacBook Pro with an AMD Radeon 4850 graphics card. I am also running the latest Resolve (released version 10) and Mavericks.

Do you have a screensaver enabled? If yes, try disabling it to prevent "App Nap" from kicking in.

Alternatively, disable App Nap for Resolve using the following instructions:

http://reviews.cnet.com/8301-13727_7-57 ... mavericks/

Yep, disabling App Nap for Resolve fixed it! Thanks

I'm currently running OS X Mountain Lion (10.8.4) and have encountered the same error as well:

"Timeout when waiting for frame [XXXXX] for recording, frame dropped"

This issue is not specifically isolated to OS X Mavericks.

Currently running DaVinci Resolve 10.1.5 in OS X 10.8.4. Computer is MacPro5,1 with 2 x 12-core 3.33 GHz, 96 GB RAM, and GTX Titan (GUI and GPU).

Rendering DNxHD 175x (10-bit), 1920x1080, 23.976 fps. Compression quality set to best, and 8 channels of audio at 16-bit.

I have not run into this issue with shorter timelines, only recently when attempting to render out a 30 min program.

I've restarted, shut down, and attempted to render with only DaVinci Resolve running. The render fails at the same shot every time, however, it is possible to render past the offensive clip if the in and out points are adjusted resulting in a shorter rendered clip.

Thoughts Blackmagic?

As a test, try rendering to a different volume.

What CUDA version are you using?

Hi Dwaine,

Many thanks for the suggestion, but yes, also tried rendering to a different volume (system). Same results unfortunately.

CUDA Driver Version is 6.0.37.

Any other thoughts/suggestions?

As another test, try rendering to a different file format.

I'm having the same problem, any help?
I've tried all the above ...
my equipment: new MacPro Full + UltraStudio 4K
with all the latest updates
socorro, help (((

If you are using OSX 10.9.3 and you have D700 graphics, that would be your issue. You need to use OSX 10.9.2, or try the developer beta of OSX 10.9.4 if that's available to you. Resolve will not work properly on a D700 equipped 6,1 MacPro with OSX 10.9.3, due to an OpenCL issue in 10.9.3.

EDIT: Looking through the posts, I see that Apple has now released OSX 10.9.4. So update to that, and your issue should be gone.

Can I revive this thread?

Mine stops at the same exact frame:



Here are my specs:




Davinci Resolve 14.3.0.014

I am also having this problem on a Windows 10 system. When doing a ProTools export to DNxHD, which involves 2 stages -- video first then audio. It always gets past the video stage, and then gets stuck in the audio stage, although I don't think it's the same frame (I'll watch now). In the audio stage, the FPS is extremely high as I have 2 Quadro P6000s and it's a dual Xeon based workstation. I have checked my disks (used internal and network samba drive), they are extremely fast raid 10s. The network switch is fine.

I'm going to try putting resolve in the highest priority mode to see if that helps. I've only rarely had this problem with H.264 outputs, and given that it is failing on the audio stage I believe it is a priority issue. I don't have a screen saver.