Is test pattern RPU.p8.1.L1.L2_cmv29.mp4 meant to include cmv4, what is the reason ? It would not display in DoVi nor respond to any RPU changes (fallback to HDR10). Only by removing the cmv4 frames that it worked on ATV21/22 -> Infuse 7.5/Auto -> LG E7. Thanks.
dovi_tool info -s -i RPU.p8.1.L1.L2_cmv29.bin
Parsing RPU file...
Infuse will not play DV file with cmv4 in it since cmv4 seems to have over saturation problem on Mac. https://community.firecore.com/t/dolby- ... /19713/351
But looks fine on iOS devices and Atv, no idea what's going on here.
Thanks @sw5163 , my main question is about the reason to include some cmv4 metadata in that test pattern labelled with cmv29. Is it to check a device DoVi’s implementation’s for handling of both metadata versions ?
The test pattern does not play as DoVi nor respond to the changes in RPU metadata. Infuse plays it as HDR and it is possible and likely the presence of cmv4 causes problems for the P8 to P5 « processing ».
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
Thanks - if @RESET_9999 wants to update his test pattern repo, here's the corresponding one without cmv4 using dovi_tool/MP4Box: RPU.p8.1.L1.L2_cmv29-ONLY.mp4
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
Thanks - if @RESET_9999 wants to update his test pattern repo, here's the corresponding one without cmv4 using dovi_tool/MP4Box: RPU.p8.1.L1.L2_cmv29-ONLY.mp4
In case you aren't aware yet, @RESET_9999, DGDemux since build 65 (Feb 15) has renamed its outputs from *.265 to *.hevc. Current version of DoVi_Scripts (1.7.7) would fail with "The system cannot find the file specified" when looking for the demuxed BL and EL, because of lines like:
sorry for this OT Q, is there a reliable method to check a DoVi BL video colour range (full vs limited) ?
I have found few methods online that analyze the BL using ffprobe lavfi.signalstats.[YMIN,YMAX] where results may conflict with the metadata in either video container headers (ffprobe pc/tv) and/or RPU info. (or the info is unclear based on my limited understanding)
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
sorry for this OT Q, is there a reliable method to check a DoVi BL video colour range (full vs limited) ?
I have found few methods online that analyze the BL using ffprobe lavfi.signalstats.[YMIN,YMAX] where results may conflict with the metadata in either video container headers (ffprobe pc/tv) and/or RPU info. (or the info is unclear based on my limited understanding)
I don't understand what you're trying to do.
The RPU levels are always full range.
The only time the BL is full range is if it's profile 5.
…
The only time the BL is full range is if it's profile 5.
My question was how can the range be checked for a Dovi P5 BL or another profile aside from inspecting metadata? Sorry if it was unclear.
Aside from RPU metadata full range flag, is there a tool or some means that can confirm that the video stream/contents are indeed full range for a P5? I shared above the ffprobe technique. Thanks.
[Oppo UDP-203, ATV 4K] —> Anthem MRX-720 —> LG OLED65E7P
…
The only time the BL is full range is if it's profile 5.
My question was how can the range be checked for a Dovi P5 BL or another profile aside from inspecting metadata? Sorry if it was unclear.
Aside from RPU metadata full range flag, is there a tool or some means that can confirm that the video stream/contents are indeed full range for a P5? I shared above the ffprobe technique. Thanks.
Not reliably by looking at MediaInfo or FFprobe because some aren't flagged as full range.
So analysing frames should work I guess.