Scopes and Critical Image Evaluation In Resolve 16

A very nice Insight, Joey, and nice peek into all the scope variants. Thanks!

I’m looking forward diving into the new scopes. I have been using Scopebox (driven by a mac mini) for the past 1 1/2 year and one GPU monitor. I could not live w/o HML. However, now, it looks like you configure HML in the new Resolve scopes. However, I wonder what kind of strain the new scopes will put on the GPU in a dual screen mode? Do you happen to know? I switched to a single Resolve GPU last year and felt like I got a little performance boost – at least on my old system.

Hey Scott – Yup I definitely still use scopebox also. I think external scopes are still best practice, and scopebox is the best.

But I do like the added flexibility these improvements give to Resolve. In terms of performance – I’m not sure. They seem really smooth and realtime for me, and don’t seem to load the system down at all – but i’m also running a single GUI monitor, not dual screen.

It is nice they added the ability to skip pixels if it is loading down your GPU.

Is it safe to make the switch yet? I think coming from Premiere I have a deep fear in updating my NLE but some of these new features are really making me want to update.

Scott – for me the HML vectorscope in Resolve does not replace the Scopebox version of that display. Since Resolve overlays the traces on each other, I’ve found Resolve’s implementation much too difficult to read and use the way I use the tri-scope layout in Scopebox.

RE: GPU hit – Don’t forget, you can set the scopes to Auto-mode to have them dynamically create less of a load on the GPU. Or you can set them permanently to not display at full quality – if it seems to be impacting GPU performance.

For context: Public Beta 3 has seven bug fixes that caused a crash (here are the changes in the Public Beta 3). In Public Beta 2 they had twelve bug fixes that caused a crash. IF you’re okay dealing with those possibilities (or any of the other 70 bugs listed in PB3) – then yes you can.

If not? If you don’t want to be a Beta Tester, then hold off. (and THANK YOU to Blackmagic for listing the bugs they’ve fixed! Super useful and it’s very respectful to your beta testers.)

Hi – at 7:30 you are saying the CIE diagram is useful for grading in “wide gamut or HDR formats”. Would the diagram not need to be 3 dimensional to account for luminance to be useful for grading in HDR?
Otherwise its just visualizing the gamut (which is also nice to see, but its not really that helpful for HDR in my opinion)

Thanks and best wishes

i’m mean by definition CIE is not 3D/Cube so it will never show luminance or color volume. CIE is still a great scope for HDR workflows because it’s a comparative tool for different gamuts. In a typical Dolby Vision workflow for example i will have to deliver P3D65/2020 Limited and of course the required 709 trim. CIE let’s me visualize edge gamut issues much easier than a vectorscope. in addition CIE makes it really easy to visualize gamut compression issues that are often encountered in color managed workflows.

I see, thanks for the clarification! Is there an option to highlight out of gamut/ compressed regions? Or would I just always compare by blending in a bigger space as working space?