Welcome to our community

Be a part of something great, join today!

Log in
  • 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 9.0.1 update

P

Peter Chamberlain

Well-known member
Joined
Apr 26, 2009
Messages
482
Reaction score
5
Points
18
Location
Singapore
Website
www.blackmagic-design.com
Hello, we have just posted a DaVinci Resolve 9.0.1 update which includes general performance improvements, SStP 12bit codec support and also a new CinemaDNG highlight recovery option.

If you have a CinemaDNG clip that is quite over exposed, and you are using the exposure control to bring back details in the highlights, in the CameraRaw palette on the Color page you can select 'Highlight Recovery' and Resolve will act to recover as much of the overexposed image as it can.

Be sure to update to the correct CUDA version 5.0.24 if you have recently updated your Mac OS X to 10.7.5 or 10.8.2 for NVIDIA GPU based systems. For ATI card OpenCL based systems, we strongly recommend updating to 10.8.2.

thanks
Peter
 
Peter,

Just thought I'd mention that in the Windows version, Help still seems to do nothing and the standard Windows' window resizing opperations are not available.
 
Peter - Resolve is and always was a full-screen tool. It's not designed to be resized. To access other windows just alt-tab or dual-monitors. Personally I do not want to see resources allocated to windows management in Resolve when it's critical that all resources go to performance & accuracy. Everything has a cost...

JT
 
John,

It should at least be able to be minimized, otherwise there is no way, AFAICT, to see the desktop underneath.
 
Peter Moretti said:
John,

It should at least be able to be minimized, otherwise there is no way, AFAICT, to see the desktop underneath.
Click to expand...

Can't you hide the Resolve app on Windows OS? At least that's how it's done on a Mac, if you don't want Resolve to be on the top of everything else. There is a reason, why Resolve doesn't conform to the usual OS conventions. It's done, so it ilooks exactly the same, regardless of the platform. This way there is no need to redesign interface for all other platforms. That goes the same for the operation of Resolve.
 
I am not aware of a way to hide Resolve in Windows.
 
Thanks much for the tip! :)
 
Peter Chamberlain said:
For ATI card OpenCL based systems, we strongly recommend updating to 10.8.2.
thanks
Peter
Click to expand...

Is the issue with ATI cards restricted to highlight clipping warning being baked into the render, or is it larger than that? I'm not seeing parity between my RCX image/parade scope, and the Davinci image/parade scope when exported from RCX as DNxHD MXF 175 10-bit and brought into Davinci Resolve Lite 9.0.1.

Here's a link to the issue - http://www.reduser.net/forum/showth...g-Warning-Is-Being-Baked-Into-My-Final-Render
 
It sounds like you have a separate issue. The link seems to send me to a third.

Is your current problem, scopes related? Do the scopes show different levels or what is the difference that concerns you.
Peter
 
Peter Chamberlain said:
It sounds like you have a separate issue. The link seems to send me to a third.

Is your current problem, scopes related? Do the scopes show different levels or what is the difference that concerns you.
Peter
Click to expand...

Hi Peter, I tried to simplify my workflow so I could zone in on the problem.

I used RedCine X build 15 to grade, then exported to DNxHD175 10 bit AVID MXF files, imported those into Resolve 9.0.1. This is on a MacBook Pro with AMD Radeon HD 6750M running OS X Lion 10.7.5.

In the attached screenshots, both the image quality and the parade scope waveforms for the same frame look very different. This may be a setting issue, but wondering if this is a known issue with my config and Resolve 9.0.1. Also, what settings can possibly cause such a wide difference between RCX Build 15 and Davinci Resolve 9.0.1?

Links to the original R3D (and RMD file) are available after the screenshots.

This is most likely some goof on my end, but thanks for any insights and help!
Nikhil

RCX Images+Scopes :

rcx.png




Davinci Resolve Image + Scopes:
dvr.png



RCX EXPORT DIALOGS:
rcxexport1.png
rcxexport2.png



R3D and RMD file for this image :
http://summerray.com/screenshots/r3d.zip

Thanks!
Nikhil
 
Last edited:
Peter Chamberlain said:
Hello, we have just posted a DaVinci Resolve 9.0.1 update which includes general performance improvements, SStP 12bit codec support and also a new CinemaDNG highlight recovery option.

If you have a CinemaDNG clip that is quite over exposed, and you are using the exposure control to bring back details in the highlights, in the CameraRaw palette on the Color page you can select 'Highlight Recovery' and Resolve will act to recover as much of the overexposed image as it can.

Be sure to update to the correct CUDA version 5.0.24 if you have recently updated your Mac OS X to 10.7.5 or 10.8.2 for NVIDIA GPU based systems. For ATI card OpenCL based systems, we strongly recommend updating to 10.8.2.

thanks
Peter
Click to expand...

How do you update to CUDA 5.0.24? It's not available for MAC OSX on the Nvidia Website. So now that I updated to Resolve 9.2, it simply will not work on my computer.

This is getting to be too much. First the Mac OSX 10.8.2 updates disables all my drives so that Red Rocket doesn't work anymore, Sonnet Echo Pro is disabled to so I can't download SxS cards.

Now Resolve isn't working on OSX 10.8.2...

Where are the CUDA 5.0.24 drivers?
 
Peter Chamberlain said:
Be sure to update to the correct CUDA version 5.0.24 if you have recently updated your Mac OS X to 10.7.5 or 10.8.2 for NVIDIA GPU based systems. For ATI card OpenCL based systems, we strongly recommend updating to 10.8.2.

thanks
Peter
Click to expand...

I thought Peter works for BDM?

Anyway, I did manage to find 5.0.24 and now Resolve is working on my OSX 10.8.2.1. I just googled it since I couldn't access it through NVidia directly or at least I couldn't find it.

So frustrating.
 
You update cuda drivers from systempref cuda pane
Peter c has since recommended the latest .36 driver
This stuff changes faster than they can release documentation...

Edit. Sorry it was Dwaine who recommended .36 to another user
 
Nikhil Kamkolkar said:
Hi Peter, I tried to simplify my workflow so I could zone in on the problem.

I used RedCine X build 15 to grade, then exported to DNxHD175 10 bit AVID MXF files, imported those into Resolve 9.0.1. This is on a MacBook Pro with AMD Radeon HD 6750M running OS X Lion 10.7.5.

In the attached screenshots, both the image quality and the parade scope waveforms for the same frame look very different. This may be a setting issue, but wondering if this is a known issue with my config and Resolve 9.0.1. Also, what settings can possibly cause such a wide difference between RCX Build 15 and Davinci Resolve 9.0.1?

Links to the original R3D (and RMD file) are available after the screenshots.

This is most likely some goof on my end, but thanks for any insights and help!
Nikhil

RCX Images+Scopes :

rcx.png




Davinci Resolve Image + Scopes:
dvr.png



RCX EXPORT DIALOGS:
rcxexport1.png
rcxexport2.png



R3D and RMD file for this image :
http://summerray.com/screenshots/r3d.zip

Thanks!
Nikhil
Click to expand...


I've found that when exporting from RCX to Avid MXF or DNXHD it is necessary to check the RESTRICT SMTPE RANGE box in order for RCX scopes to match Avid scopes, or any video output from Avid going through a hardware scope. There have been a few threads about this here on reduser but they are more obscure. I'm not sure if it is related to the problems you are having but if you are finding footage MORE contrasty after the RCX export then this might help. I find it ridiculous that this is totally undocumented from RED, since A LOT of productions are exporting to Avid formats. Basically, all those DPs dailies are looking crushed out and are a betrayal of the cinematographer's intent. I have pointed out to RED that the RCX manual is inadequate especially when compared to the masterpiece that is the Davinci Resolve manual, which not only provides detailed explanations of every feature but offers REAL WORLD scenarios in which you might use them!
 
Paul Provost said:
You update cuda drivers from systempref cuda pane
Peter c has since recommended the latest .36 driver
This stuff changes faster than they can release documentation...

Edit. Sorry it was Dwaine who recommended .36 to another user
Click to expand...


Yes, I did update to 5.0.36 from my Cuda in my System Preferences... that was the problem!!!

So I googled 5.0.24 and found it hidden in Nvidia site. I updated to it and now REsolve works for me in OSX 10.8.2.1.

I'm so sick of all the work arounds and exceptions ,etc... once my system gets up and running again, I won't be doing frequent updates like I'm used to. This is just too frustrating. Each week it's something new....
 
Just started using 9.1 and I can't get the scopes to display, anybody else got the same problem.
 
You must log in or register to reply here.
Back
Top