Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Davinci Resolve 16.1 Final Release Version

I had the same error error 77 in win 10
I had to completely disable the REDROCKET and assign all the redcode to the GPUs.
Hope this can help you.
 
Thanks Luigi For the info above!


Premiere Pro to Davinci Resolve Color Grading Workflow (EASY!)


By Jay Lippman




The Best Music For Your Videos (Get 2 Months Free!!)*: http://bit.ly/jl_artlist

Get High Quality Stock Footage For Your Projects (2 Months Free!)*: http://bit.ly/jl_artgrid
 
Last edited:
MBS 478: Using Remote Grades in DaVinci Resolve

By Ripple Training


Want to Learn Fast Grading Workflows in DaVinci Resolve? Check out Mark's 6 hour Blackmagic Design Certified Color Grading Course: http://bit.ly/Resolve-Color
 
Last edited:
<chiming in the Resolve issue>

I have tried to draw the Blackmagic Dev team into reviewing the reason why there code is waking up more than 300 times a second (seemingly) try and get an exclusive lock on resource ... that is not yet available.

In the diagnostic info (from someone who shared their OS logs - they were hitting >45,000 wake ups per second before Kernel was killing the offending Resolve Thread).

(My guess) This issue might be symptomatic of a race hazzard in multi thread resource atomicity.

AJ
 
Back
Top