<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пт, 2 июн. 2023 г., 23:22 Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com">randrianasulu@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">ср, 31 мая 2023 г., 23:53 Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com" rel="noreferrer noreferrer" target="_blank">randrianasulu@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><a href="https://aur.archlinux.org/packages/vapoursynth-plugin-awsmfunc-git" rel="noreferrer noreferrer noreferrer" target="_blank">https://aur.archlinux.org/packages/vapoursynth-plugin-awsmfunc-git</a><div dir="auto"><br></div><div dir="auto">literally ...</div><div dir="auto"><br></div><div dir="auto">For that? For x265 HDR param calculations, of course! :)</div></div></blockquote></div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Unfortunately, on just dualcore notebook cpu this script works extremely slowly (0.13 fps?) but apparently it works!</div><div dir="auto"><br></div><div dir="auto"><a href="https://www.linux.org.ru/forum/multimedia/17247063?lastmod=1685951506829">https://www.linux.org.ru/forum/multimedia/17247063?lastmod=1685951506829</a><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">There is another discussion on Magic Lantern forums, some users tried DVR as way to generate x265's parameters, either static or dynamic, but on their monitors dynamic hdr10+ was not really different ...</div><div dir="auto"><br></div><div dir="auto"><a href="https://www.magiclantern.fm/forum/index.php?topic=26428.0" rel="noreferrer noreferrer" target="_blank">https://www.magiclantern.fm/forum/index.php?topic=26428.0</a><br></div><div dir="auto"><br></div><div dir="auto">====</div><div dir="auto"><div dir="auto">
<div>
<h4>
<a href="https://www.magiclantern.fm/forum/index.php?action=profile;u=87548" target="_blank" rel="noreferrer">vastunghia</a>
</h4>
<ul></ul>
</div>
<div>
<div>
<div>
<div>« <strong>Reply #16 on:</strong> April 27, 2022, 01:15:21 PM »</div>
<div></div>
</div>
</div>
<div>
<div><div><div><a href="https://www.magiclantern.fm/forum/index.php?topic=26428.msg238612#msg238612" target="_blank" rel="noreferrer">Quote from: timbytheriver on April 21, 2022, 01:13:39 PM</a></div></div><blockquote>Btw, did you ever get to actually see the effect of your HDR10+ metadata on your display? <img src="https://www.magiclantern.fm/forum/Smileys/aaron/cheesy.gif" alt=":D"><br></blockquote><div><div></div></div><br>I prepared 4 versions of the same clip, namely<br><ul style="list-style-type:decimal"><li><strong>PQ10</strong>, i.e. PQ transfer characteristics and BT.2020 color space (no metadata at all!)</li><li><strong>HDR10</strong>, namely (1) + static HDR10 metadata (mastering display color primaries + min and max luminance + MaxCLL + MaxFALL)</li><li><strong>HDR10+ Profile A</strong>, namely (2) + dynamic metadata consisting of luminance distribution parameters</li><li><strong>HDR10+ Profile B</strong>, namely (3) + dynamic metadata consisting of Bezier curve parameters</li></ul>The clip included some very bright scenes, some more balanced scenes, as well as some very dark scenes with a few bright spots.<br><br>To
assess the four versions of the clip, I photographed the TV screen from
a long distance in a dark room, of course taking Raw pictures and
baking them with exactly the same (somewhat neutral) settings in ACR.<br><br>The results:<br><ul><li>version
1 is slightly darker in all cases (this somewhat surprised me as I
expected on the contrary that no metadata could lead to oversaturated /
clipped highlights)</li><li>versions 3 and 4 look apparently identical
(no surprise), but they seem to roll highlights (as well as shadows)
slightly differently from 2, in a non-trivial way (in most, but not all
cases, increasing contrast slightly)</li></ul>So yes, in the end I could
find some differences with my TV -- but very subtle, in many cases
visible more by comparing the sample pictures histogram rather than
really perceivable with the naked eye.<br><br><em>Sergio</em></div><div dir="auto"><em><br></em></div><div dir="auto"><em>==== end of quote ====</em></div>
</div></div></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Still, I guess having those python functions cloned locally might be good idea!</div><div dir="auto"><br></div><div dir="auto">Also, note they used hdr metadata output in DVR, this is reason why I looked into mpv's incomplete (in this regard) HDR support ...</div><div dir="auto"><br></div><div dir="auto">Also note they used hdr10+ capable TV so, even if you do not have monitor, may be going to friend with BIIIG TV will help in some ways!</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote></div></div></div>
</blockquote></div></div></div>