Error (SOLVED): Timeout when waiting for frame

Hi there,

I have been getting an error (Timeout when waiting for frame xxx for recording, frame dropped) when trying to create an output render (see attached examples). I have noted that others have mentioned this error on the forum, and seems like it has been due to connectivity issues with hard-drives. When the render stops, the error message is displayed. I press the render stop button, but the software is unresponsive except top menu. I must then use the menu Quit option twice to get DR to exit. I am not always able to restart the software without rebooting.

Drive Hardware: -

Input Seagate external drives are connected straight into the computer USB 3.1 ports.
Output and scratch drives are internal EVO 960 M.2 SSD drives.

Some observations: -

This error can happen anywhere from ten minutes into rendering at 5% to 1.5 hours in at 80%.
The frame number reported changes each time.
I have checked the log files, but cannot see any actual problem reported at the time of stopping.
I have checked the Windows OS error logs, and nothing shows at the time of failure.
GPU is usually running below 40% load, and 50% memory. CPU is usually at 80-90%.
Disk drive reads are down at 10-30% of the time. Disk drive writes are 10%.
There are no spikes in memory, processor or disk usage at the time of error.

So far, things I have tried: -

Use back-up source drive instead
Change interface type from USB A to USB C and though a hub.
Changed output render file types, size etc.
Change from using optimized to not.
Tried changing to lower rendering speeds.

Any suggestions?

What version are you on? This bug was present for a few years, but it seems that it was actually finally fixed in 15.1.1.


Sent from my iPhone using Tapatalk

Hi Seth, so, I was on the latest version 15.1.2, but I am back on 15.0.1 due to another issue, which no one has managed to help me with (viewtopic.php?f=21&t=80204).

I re-installed v 15.1.2, and yes, I no longer get the Timeout issue. Thank you.

Any chance you could have a quick peak at my other problem then?

What version are you on? This bug was present for a few years, but it seems that it was actually finally fixed in 15.1.1.


Sent from my iPhone using Tapatalk

I am on 15.1.25.0 and I have same problem.

Just downloaded DaVinci Resolve 16 and having the same problem.

I am now also having this issue-- I recently updated to Davinci Resolve 16.2.0.054 that was released in the last week.

Is this a issue that others are having & may be fixed in a update? I recently bought a new laptop with 16 gb (from 8 gb that had many crashes with DV) so I am frustrated to now have this problem. I had a couple good renders with NO issues and then updated to the new version and am now having this issue...

My computer stats:
MD Ryzen 7 (AMD 2nd Generation Ryzen 7, 3700U)
16GB Memory
AMD Radeon RX Vega 10
1TB HDD

Thanks for any assist/s!!!

Me too also having this issue. I recently updated to Davinci Resolve 16.2.0.054 that was released in the last week.
Does someone having the same problem with the latest release?
Any fix coming? Any workaround suggested?

Thanks
Sergio

Over in viewtopic.php?f=21&t=101529&p=584734&hilit=timeout+when+waiting+for+recording%2C+frame+dropped+frame#p584734 it was suggested to change the Render rate down from Maximum to 10. While that's admittedly painful, it did let me get some renders out that were consistently dying previously.

Why has this been tagged as solved?

I'm now fighting this issue...16.2 .tried different drives..no dice...

[Dwaine Maggart]

It was marked solved because the OP was using an old version of Resolve that had this issue, then updated to a newer version that fixed the issue.

It might help to post 16.2 specific issues in a new thread instead of a year and a half old thread relating to a different version.

We would also need all the normally requested info here:

viewtopic.php?f=21&t=90190

Including your system info, a Resolve log, and a Project Export .drp of a project having the render issue.

I read many posts with this same error while trying to find a solution. I'm replying here cause this one even if it is not solved it says it is so I guess it will get read more often from people with same error.
The only way I can generate proxys without this error is turning of cuda and switch it to openGL. my workstation has 3x3090 nvidia cards.

I hope this helps someone with same problem
Cheers

That sounds like a GP driver issue.