Dolby Vision now possible through MP4 Mux.

[darrrkmanxxx]

@RESET_9999
For devices who can't play P7, what would be the workflow to get the best out of dynamic metadata?
exmaple:
I have one profile 7 remux and a web-dl profile 8, which are compatible in brighntess.
- Extract rpu from web-dl p8
- convert P7 to P8 with dovi_tool
- inject into converted remux
Is that correct?

[RESET_9999]

just convert the P7 rip to P8 with workflow 4-1

[darrrkmanxxx]

just convert the P7 rip to P8 with workflow 4-1

thanks, is this the same as with dovi_tool mode 2 from quietvoid?

[RESET_9999]

yes, all the workflows rely on dovi_tool.exe ... there's no other way.

[fazambuja]

Would it be possible to extract the HDR10plus of lower quality mkv and inject it into its higher quality variant?

Code: Select all

Format                                   : Matroska
Format version                           : Version 4
File size                                : 23.3 GiB
Duration                                 : 1 h 59 min
Overall bit rate                         : 28.0 Mb/s
Frame rate                               : 23.976 FPS
Movie name                               : Alien Romulus (2024)
Encoded date                             : 2024-12-05 16:14:58 UTC
Writing application                      : mkvmerge v88.0 ('All I Know') 64-bit
Writing library                          : libebml v1.4.5 + libmatroska v1.7.1 / Lavf60.3.100
Cover                                    : Yes
Attachments                              : cover.jpg
Time code of first frame                 : 01:00:00:00
Time code source                         : Matroska tags

Video
ID                                       : 1
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU, no metadata compression, HDR10 compatible / SMPTE ST 2094 App 4, [B]Version HDR10+ Profile A, HDR10+ Profile A[/B] compatible
Codec ID                                 : V_MPEGH/ISO/HEVC
Duration                                 : 1 h 59 min
Bit rate                                 : 25.7 Mb/s
Width                                    : 3 840 pixels
Height                                   : 1 608 pixels
Display aspect ratio                     : 2.39:1
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.173
Stream size                              : 21.4 GiB (92%)
Title                                    : HSaber <-|-> Z@X
Default                                  : Yes
Forced                                   : No
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : BT.2020
Mastering display luminance              : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level              : 1000 cd/m2
Maximum Frame-Average Light Level        : 400 cd/m2

Code: Select all

Format                                   : Matroska
Format version                           : Version 4
File size                                : 53.6 GiB
Duration                                 : 1 h 59 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 64.5 Mb/s
Frame rate                               : 23.976 FPS
Movie name                               : Alien: Romulus - Ultra HD™
Encoded date                             : 2024-11-26 14:39:36 UTC
Writing application                      : mkvmerge v88.0 ('All I Know') 64-bit
Writing library                          : libebml v1.4.5 + libmatroska v1.7.1
Cover                                    : Yes
Attachments                              : cover.jpg

Video
ID                                       : 1
ID in the original source medium         : 4113 (0x1011)
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : Dolby Vision, Version 1.0, Profile 7.6, dvhe.07.06, BL+EL+RPU, no metadata compression, Blu-ray compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID                                 : V_MPEGH/ISO/HEVC
Duration                                 : 1 h 59 min
Bit rate                                 : 54.9 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Bits/(Pixel*Frame)                       : 0.276
Stream size                              : 45.6 GiB (85%)
Title                                    : English
Language                                 : English
Default                                  : Yes
Forced                                   : No
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : BT.2020
Mastering display luminance              : min: 0.0001 cd/m2, max: 1000 cd/m2
Original source medium                   : Blu-ray

[RESET_9999]

Yes, measure both videos if they are the same grade.

[dkangel]

Thanks for explaining. How to interpret those? Is the madvr plot the best, because it has the most dynamics?
If I do the madvr measuremnt, I adjust cmv4.0 when I generate from madvr file with dovi_tool ,e.g.

No, madvr generated metadata (3-2) is the worst and not really suited for DV playback. Also, Madvr scene cut detection is not very good. It's quite sensitive to flashes/explosions/fast movement and can sometimes miss obvious scene cuts. The best dv metadata generation is one of the analysis tunings using Davinci Resolve. I prefer the ''balanced tuning'' which is the dovi_scripts default in workflow 3-1


Hello
in your video you said that we should choose most highlights details in resolve but now i see that you prefer balanced. So what is the best ?

[RESET_9999]

Yeah, when I did the video, I was using tuning 1.
After more tests/comparisons, I now prefer tuning 3 because it's a bit brighter without clipping. Both tunings are good though and tuning 3(balanced) is Resolve default.

[dkangel]

ok thank you

[powdeau]

Does Chroma Weight makes a big difference if it is used only in 100 nits trim?

[RESET_9999]

Does Chroma Weight makes a big difference if it is used only in 100 nits trim?

yes and it doesn't matter if it's only a 100nits trim because whatever they did in the SDR trim gets extrapolated to any brightness.
thankfully CW is not used very often.

[darrrkmanxxx]

Does Chroma Weight makes a big difference if it is used only in 100 nits trim?

yes and it doesn't matter if it's only a 100nits trim because whatever they did in the SDR trim gets extrapolated to any brightness.
thankfully CW is not used very often.

so if there are no CW trims (flat line) at 1000nits and my device has 1000nits peak brightness, will it still be tone mapped because of the 100nit trim?

[RESET_9999]

so if there are no CW trims (flat line) at 1000nits and my device has 1000nits peak brightness, will it still be tone mapped because of the 100nit trim?

If there's a blank 1000nits trim, the 100nits trim gets ignored if your target brightness is 1000+
If there's a blank 600nits trim, the 100nits trim gets ignored if your target brightness is 600+

if there's just a 100-nits trim, yes the metadata gets extrapolated to any brightness but the higher your TV target is the less effect the trims have.
if you're using LLDV, and if you use an edid of 1000+ then the trims are 100% ignored if the RPU MDL is 1000nits (tested on shield, ATV, ugoos, x800m2 x700).

@powdeau confirmed to me that the trims are not ignored in TV-LED on the LG G4 with 1000nits RPU, so the behavior is different than LLDV because that TV must have a target higher than 1000nits.
I see the same behavior with my 2000nits Hisense TV, the trims always work regardless of the RPU MDL. So the trims not working in LLDV with 1000nits edid might be another DV bug.

He also confirmed that Chroma Weight doesn't work in cmv2.9 on the G4, same as my C2 and hisense TV. So dolby cmv4.0 fixed the Chroma Weight bug in LLDV and broke it in TV-LED for cmv2.9... typical Dolby...

[powdeau]

@RESET_9999 I have tried your metadata comparison for Kill Bill 1 and Smile 2 on my G4 and I don't see any changes with Kill Bill but I do se them with Smile.
Is it because Kill Bill has almost no trims in 1000nits or because Smile is mastered for 4000 nits?

[RESET_9999]

By the look of the L2 trims and the content brightness, it sounds normal.

Smile 2 is graded at SDR level but in some shot, the trims have very strong brightening values. So you probably see no change with L1, but a brighter image with L1+L2
kill bill is a bit brighter but still only 400nits and the trims don't brighten as much as Smile 2.

And yes, the RPU also has more effect when it's 4000nits MDL.