Picker RGB red value is wrong

The picker RGB red value is wrong, for example on a grey card it shows R:029 G: 128 B: 128

The picker values are still wrong in 15b2. I installed the latest Nvidia driver, that made no difference so I reverted to an earlier Desktop Video but to no avail. Can anyone please confirm this problem? Here is a screenshot.

Try adding a blur to the image first.

Gary, that makes no difference, please understand the picker worked perfectly for me in my previous versions of Resolve. Can ANYONE please let me know if it works ok for them? Just hover on a bright cloud or a white window frame, anything, please!

Gary, that makes no difference, please understand the picker worked perfectly for me in my previous versions of Resolve. Can ANYONE please let me know if it works ok for them? Just hover on a bright cloud or a white window frame, anything, please!

Hi Claire,

Here everything works well. Maybe to make a menu Workspace => reset UI Layout? (sometimes you have to do it, especially if you used the Fusion tab .... It's still a Beta version)

testchart.jpg

No problem on my system. See signature at the bottom.

color picker

picker.jpg (30.54 KiB) Viewed 1458 times

Thank you Jean and Gary! Now I know the problem is at my end, just need to track it down now...

I reset the workspace and unfortunately it made the picker problem worse. Turning on "Show picker RGB value" now causes a crash after a few moments of moving the picker. During the brief period before the crash the RGB values shown looked correct.

I have since discovered that de-selecting the Intensity Pro 4K in preferences results in the picker working perfectly, so I tried re-installing 10.9.12 Decklink again but no change.

This may not be the answer you're looking for, but the workaround I would suggest is that you change your method of working to not use the color picker. I very rarely use it and instead just use scopes and still frames to match shots. We basically come up with a "hero" shot (like a box of detergent or a dress color or whatever the client wants), then match everything to that perceptually by eye. In truth, I throw the scopes out if the shot "feels" correct on the monitor -- the scopes merely tell me when we're close enough for jazz.

I think there's often a danger of getting so overwhelmed by the trees some users start to miss the forrest. Look at the big picture and how the shots look in context, and don't worry about pixels. Great scopes will get you there -- but I'm admittedly a fan of external scopes and not the internal daVinci scopes.