This test was made from a hdr10 base layer.
And it works on apple
I’ll wait for reset9999 to compare
HDR10 with madvr-generated DV is certainly better than just static HDR10. You will notice a difference, especially with bright content.rkjnsn wrote: ↑Tue May 24, 2022 11:44 pmFor movies with neither a Dolby Vision track nor HDR10+ metadata to convert, how much of a difference am I likely to notice on an LG C1 between auto-generating shot-by-shot metadata versus just playing it back with static metadata? Is it more likely to make a difference in a brighter room (so Dolby Vision IQ can do its thing) than a fully dark room?
Finally, is there any way to generate shot-by-shot metadata on Linux, or do I have to use the madMeasureHDR.exe program under Windows?
Thanks.
Manixx2020beyound wrote: ↑Tue May 24, 2022 11:57 pmI just made a profile 5 doblyvision encode (now-possible) encoded on a pc
This test was made from a hdr10 base layer.
And it works on appletv
I’ll wait for reset9999 to compare
My p5 are triggering doblyvision on the pc app. This is unbelievable
BE470269-B01B-4DDD-8390-DACFC8FC4F8D.png
Thanks, I will try tonight. Maybe you could make a mov file from the recently linked P8.4 L2 test file?Manixx2020beyound wrote: ↑Wed May 25, 2022 7:51 amHere is a p5 sample for u guys to test
This was encoded using doblyvision encoding engine & h265, RPU is a true P5 even l4 included
Source file spares & munsil m2ts untouched Mel.
Test on Apple TV’s
https://drive.google.com/file/d/14VpI6o ... p=drivesdk
Thank you. Tested on ATV 4k works perfectly via Infuse but no audio.Manixx2020beyound wrote: ↑Wed May 25, 2022 7:51 amHere is a p5 sample for u guys to test
This was encoded using doblyvision encoding engine & h265, RPU is a true P5 even l4 included
Source file spares & munsil m2ts untouched Mel.
Test on Apple TV’s
https://drive.google.com/file/d/14VpI6o ... p=drivesdk
It would heavily depend on a file.rkjnsn wrote: ↑Tue May 24, 2022 11:44 pmFor movies with neither a Dolby Vision track nor HDR10+ metadata to convert, how much of a difference am I likely to notice on an LG C1 between auto-generating shot-by-shot metadata versus just playing it back with static metadata? Is it more likely to make a difference in a brighter room (so Dolby Vision IQ can do its thing) than a fully dark room?
Also a p5 encoded from a master MxF that already has been made with Dolbyvision meta retains all the artistic intent in the conversion to p5 tested that as well.RESET_9999 wrote: ↑Wed May 25, 2022 2:29 pmExcept that it is not a true P7/P8 to P5 conversion. It is newly generated metadata and all the artistic trims are gone. Basically the same as generating DV from madvr.
In order to get the same DV, the dovi_tool would need to be able to convert RPU to XML (same structure as resolve XML). Then we could import the metadata in resolve and encode it to P5.
Will be useful to convert all my HDR10 patterns to Profile 5 though.
The encoded files aren't comparable.RESET_9999 wrote: ↑Wed May 25, 2022 11:02 pmWe discovered something else, something quite big. The DV 8.1 MP4 encoded directly from Resolve doesn't have the famous color issue bug on the Shield!!!! what the hell!!!
So it means there is something in quietvoid/yusesope/makemkv DV remuxing that the Shield doesnt like at all... Strange though that only the Shield seem to be affected.
the spears and munsill pattern is encoded with maxcll/fall 1000/400 but resolve and madvr measure it 10 000nitsquietvoid wrote: ↑Thu May 26, 2022 12:39 amThe encoded files aren't comparable.RESET_9999 wrote: ↑Wed May 25, 2022 11:02 pmWe discovered something else, something quite big. The DV 8.1 MP4 encoded directly from Resolve doesn't have the famous color issue bug on the Shield!!!! what the hell!!!
So it means there is something in quietvoid/yusesope/makemkv DV remuxing that the Shield doesnt like at all... Strange though that only the Shield seem to be affected.
Resolve: BT.2020 mastering display, 10000/256 CLL, chroma location center.
Other: DCI-P3 mastering display, 1000/400 CLL, chroma location top-left.
And in the RPU, L6 and L9 are different (Resolve matches BT.2020 primaries, dovi_tool uses DCI-P3 by default).
I doubt L11 makes a difference unless the display supports CM v4.x.
Finally, Resolve doesn't support shot based metadata, so every frame carries "scene_refresh_flag": 1.
Those should obviously be matched first before jumping to conclusions.
MakeMKV shouldn't be doing anything different, as the source isn't modified.
Also, these MP4 files are missing the proper compatibility ID for 8.1.
correct me if i am wrong but I use the first version of the mp4muxer (because the newest one doesnt work) and --dv-bl-compatible-id 1 doesnt work. ( i think it was added later)Also, these MP4 files are missing the proper compatibility ID for 8.1.
L9 needs to be matched too.RESET_9999 wrote: ↑Thu May 26, 2022 12:53 amI'll match the color primaries for the 2nd clip but i doubt it will make any difference. As for L9 i dont know.
I think the latest version of mp4muxer doesn't work only on LG TV internal player?RESET_9999 wrote: ↑Thu May 26, 2022 12:53 amcorrect me if i am wrong but I use the first version of the mp4muxer (because the newest one doesnt work) and --dv-bl-compatible-id 1 doesnt work. ( i think it was added later)