Compare RPUs from Resolve 18.0 with implementation

quietvoid / dovi_tool

dovi_tool is a CLI tool combining multiple utilities for working with Dolby Vision.

MIT License

581 stars 57 forks source link

Compare RPUs from Resolve 18.0 with implementation #153

Closed quietvoid closed 1 year ago

quietvoid commented 2 years ago

Blackmagic Design announced that DaVinci Resolve 18.0 Beta 2 now supports Dolby Vision output to MP4 using HEVC codec.

Support for rendering Dolby Vision compatible H.265 clips.

It would be nice to compare our implementation, especially for generate with XML. Anyone welcomed to try it out.

saindriches commented 2 years ago

With some tests on 18b2:

The profile 5 output from Resolve doesn't do forward reshaping which DEE does, BL is just a normal IPTPQc2 video. Trim and L11 block is present.
The 8.1 and 8.4 output from Resolve drops trim metadata, with predefined metadata instead.
Windows platform needs a Dolby Vision license to use this feature (Don't know if it's just a bug or temporary limitation)

imhh1 commented 2 years ago

With some tests on 18b2:

@saindriches Hi, how do you deliver P5 / P8 mp4 in resolve ? I'm on 18B3 and I don't see any option to do that. thank you!

EDIT:. Ha nevermind, I just saw the requirements.

The Dolby Vision Mastering and Playback Annual License Resolve Studio 18 installed on a Dolby Vision Windows PC (see Laptops enabled with Dolby) All Intel-based Mac systems supporting Resolve Studio 18 A Windows based system supporting Resolve Studio 18 and directly connected to a Dolby Vision PC monitor

imhh1 commented 2 years ago

The main difference I'm noticing is that P8.1 mp4 from resolve has L4 metadata while the one we create from the XML file doesn't. Is L4 metadata present in the XML?

BTW it's working on a regular PC connected to an OLED without the Dolby annual License. :)

quietvoid commented 2 years ago

L4 metadata is generated by analysis of the shot, it's not stored in the XML.

saindriches commented 2 years ago

L4 metadata is generated by analysis of the shot, it's not stored in the XML.

It's generated during encoding I think, and It’s frame based PQ average / standard deviation (but will be temporal filtered). Maybe it’s good to add a feature for generate to allow using L4 from an existing RPU as an additional measurement source, just like madVR source. It can be generated without manual shot analysis when output is 8.1 or 8.4, since they are using frame based (or long play mode) analysis in Resolve, all metadata is auto generated. Shot based metadata is actually allowed for 8.4, it works since iOS15.

quietvoid commented 2 years ago

Maybe it’s good to add a feature for generate to allow using L4 from an existing RPU as an additional measurement source, just like madVR source.

I'm not sure what that means.

saindriches commented 2 years ago

I didn't say it correctly, don’t mind. I realized just use convert mode should be enough. What I thought was add a feature to combine two RPUs, picking some blocks from one, and some blocks from the other one.

quietvoid commented 1 year ago

Some documentation: https://professionalsupport.dolby.com/s/article/Dolby-Vision-Encoding-using-Blackmagic-Design-DaVinci-Resolve-Studio-AQs