+1 , amazing work, just generated a profile 08.06 from an HDR10 sample, plays fine with internal Plex app: 04-2160p_23fps_dovi_p81-l_s02e01_cyan_error.tsRESET_9999 wrote: ↑Fri Oct 08, 2021 12:23 amI don't know why you're quiet about it but you should scream out loud that you updated your DV tools to generate DV metadata for ANY HDR10 MOVIE using madVR measurements lol
madvr output:
Code: Select all
Metadata:
Mastering display luminance: 0.0001/1000, gamut: 0.68 0.32, 0.15 0.06, 0.265 0.69, 0.3127 0.329
MaxCLL: 999, MaxFALL: 678 nits
Measurements:
Frames: 2160, MaxCLL 100%: 1680, 99.9%: 1545, MaxFALL: 58, AvgFALL: 9, AvgFMLL: 524 nitsCode: Select all
{
"length": 1000,
"level2": [
{
"target_nits": 1000
}
],
"level6": {
"max_display_mastering_luminance": 1000,
"min_display_mastering_luminance": 1,
"max_content_light_level": 1000,
"max_frame_average_light_level": 58
}
}Code: Select all
# run madvr madmeasure on the mkv file
# generate RPU from madmeasure bin file
dovi_tool.exe generate -j generator_madvr.json --madvr-file l_0201.bin -o RPU_from_madVR.bin
# extract hevc video and audio with mkvextract
# inject the generated RPU into stream
dovi_tool.exe inject-rpu -i video.hevc --rpu-in RPU_from_madVR.bin -o injected_output.hevc
# mux together with tsmuxer
Is this with from official apps as well (ATV+, Disney+, etc)?
That's a problem, probably never will be fixed
What do you mean about this? Does it do DoVi HDR to SDR tonemapping?
Edit: what happens with the "min_pq" L1 metadata during madmeasure2RPU generation? Will it be always 0? (I don't think that madvr's bin file has any info about it.)
Edit2: sample uploaded