Blackmagic Forum

Resolve has been amazingly stable since I switched from Premiere almost two years ago. However a couple of days ago I started running into issues when rendering a large two hour project. The render would "time out while waiting for frame". It happens on multiple computers. Originally it was happening at around the 10 percent mark or less. Today I actually made it all the way to 41 percent and yesterday I had one make it to 28 percent.

Looking through the forums I saw a lot of people having the same problems say that it was probably a hard drive issue. I'm using an external usb 3 raid for my footage and rendering to standard internal drive. I switched things up and moved the footage to the internal drive and switched the render location to the SSD. Still no dice. Then I moved the project to a different computer and tried a few drive configurations. None of them worked. I tried dropping the render speed to 10fps...still a no go. I tried rendering to different formats...no help.

I'm kinda running out of ideas, I think I need professional help

The only thing I can think of that's different on this project is that the footage is Prores. The Prores was exported from a Mac Premiere project. This is the first time I've used Prores in Resolve.

DETAILS...
It's a very simple project. The project footage is a single Prores file split up with an EDL. There are some film grain files composited on top. The client wants Prores or Prores equivalent renders. I'm trying to render to DNxHD although I have also tried DNxHR and even H.264.

Computers I've tried
DESKTOP - newer i7, 1080ti, internal drives and external usb drives
LAPTOP - MSI GT72, i7, 980m, internal drives, external drives, and SSD raid.

Here's a link to a folder with the logs for both computers.
https://drive.google.com/open?id=1loYgC ... P5K61otWfj

Any ideas would be appreciated. Thanks.
Michael

I've experienced the same problems as Michael... The problem occurs with me when I'm exporting several sections of a timeline as separate MP4 files. Unfortunately, when it happens, Resolve becomes frozen on my mac requiring a forced quit of the program. (I've learned to always save right before I render.) After the program is re-started, the same sections of the timeline will usually render without problems. I'm using all Sandisk Extreme Pro SSD's and Resolve Studio is operating on Sierra OS X 10.12.6. Otherwise, Resolve 14.2 is very, very stable.

I had some freezing problems initially like Glenn but I found out Resolve wouldn't freeze on me as long as I saved right before I started a render. But whenever I exited Resolve I would have to manually shut down the resolve.exe in Windows task manager before I could start Resolve back up. For some reason it didn't shut down properly after having those render issues.

I came up with a solution in order to finish the project. I ended up dividing the timeline into 11 different sections. Only had two failures at the new shorter length, and they both worked the second time. Fortunately the client was fine with putting the thing back together manually in post.

Still not sure what the problem was but hopefully I never run into it again.

I’m still having these random problems for maybe 1 in 3 renders, across three different machines. I had hoped 14.3 might solve this, but it didn’t.


Sent from my iPhone using Tapatalk

I think I might have figured out a fix for this, at least for macOS 10.12 and macOS 10.13 environments with SMB server shares.

Admittedly, I tried two things at once, so I can't say for sure what fixed everything.

First, I manually disabled local SMB directory enumeration caching. This is different for 10.12 and 10.13.

10.12: https://support.apple.com/en-us/HT207520
10.13: https://support.apple.com/en-us/HT208209

If I had to guess, I'd say Resolve probably wasn't coded to deal with items disappearing from Finder arbitrarily. Thanks, Apple!

The second thing I did was reset the NVRAM on the affected clients.

I hope this helps someone!

I'm still regularly having these different "waiting for frames" problems in 14.3 on three different workstations: a MacPro5,1 running 10.12.6, a MacPro6,1 running 10.12.6, and an iMac running 10.13.3.

I had a fairly unproductive call with Apple, suspecting possible GPU thermal issues--but the word passed down from Apple Engineering is that, after looking at some logs that I sent Apple, that Resolve is just "using too much CPU and RAM." They said with or without more modern hardware in an iMac Pro, the app shouldn't be designed in such a way to cripple the system.

They essentially blamed this on bad app development on the part of Blackmagic Design.

I don't really know where to go from here, if Blackmagic Design is pointing fingers are Apple, and Apple is pointing fingers at Blackmagic Design.

I'm fairly certain I've figured this out. Turns out I was having fairly nasty PostgreSQL errors due to what I think was some routing table RAM that had gone bad in my 1 GbE network switch. When I replaced the switch, my remote renders became reliable again.

I'm sorry to say that this nasty little issue has followed me to CentOS.

It doesn't matter if my data is coming through SMB or NFS, with direct I/O enabled or not. I can't render out a roll of dailies--it's quite maddening. I would have guessed that this might be an issue with my storage, but Media Encoder over on Windows is working just fine, from the same server.

Seth, for diagnostic purposes, try read and write to direct attached and non usb raid.
Which exact OS?

Had the same problem on a PC. I was working/grading stills for my portfolio. (Lightroom only goes so far) I had 233 still images all with different grades and Delivering tifs always stopped at various points. Trying to render a 233frame mp4 never completed successfully. On the net found some suggestions that this was just a disk drive read/write Couldn't Keep Up problem. They suggested reading the files from one disk drive and writing to another. Didn't help much for me.

Resolve always got as far as it could and I just picked up on the DELIVER PAGE starting just after the last file rendered correctly. I got all 233 tifs done. I have to admit I was asking the COLOR page for a ton of math on each image and some of them were 12,000 by 18,000 pixel composited images. Once the tifs were done I imported them and Resolve sailed through making a 8 second 233 frame mp4. So my theory is the the Disk Transfer Rate/Heavy COLOR PAGE Math Causing Disk Timeout Theory...

Well, I’m impressed it handles such large stills at all!
Wouldn’t suggest it as a future standard for moving images

Peter Chamberlain wrote:Seth, for diagnostic purposes, try read and write to direct attached and non usb raid.
Which exact OS?

I'm afraid I don't have any cards that aren't either 10GbE or USB. This is CentOS 7; 3.10.0-862.2.3.el7.x86_64.

I've been playing around with a lot of NFS options in /etc/fstab, to no avail.

Just wanted to update. I think there's an issue with my storage. Seeing similar drop-outs unrelated to Resolve--such as with a large rsync transfer.

Working on ironing this out.