[Cin] Adobe Premiere (2021) and HDR

[Andrew Randrianasulu]

was looking at  how exactly HDR info travels in production environment.

https://community.adobe.com/t5/premiere-pro-beta-discussions/discuss-color-management-improvements-h264-hevc-xavc-l-and-xavc-slog/m-p/12390588

=====

  Francis-Crossman
Adobe Employee Sep 17, 2021

This expands the list of color managed codecs.  H264/HEVC represents the
majority of DSLR and mirrorless prosumer cameras on the market, and XAVC-L
/ XAVC Slog are heavily used in broadcast HDR workflows.



“Color managed” means that Premiere Pro read the color tags in the file
metadata and accurately converts the file to the sequence color space. If
the color spaces of the file and sequence are the same, the Premiere Pro
passes the colors through to the sequence without conversion. Color
management is necessary for HDR production.



Codecs that are not color managed will always be interpreted as Rec709,
which worked just fine for a long time.  But with HDR becoming more and
more mainstream, proper color management is necessary.



Full list of color managed codecs

Codec

Wrapper

Color Space

New?

Apple ProRes

·      422 HQ

·      4444

·      4444 XQ

.MOV

Rec. 709

Rec. 2100 HLG

Rec. 2100 PQ

Previously supported

Sony XAVC-I (all intra)

.MXF

Rec. 709

Rec. 2100 HLG

Previously supported

Sony XAVC-L (long GOP)

.MXF

Rec. 709

Rec. 2100 HLG

NEW

H.264 / HEVC (H.264)

.MP4, .MOV

Rec. 709

Rec. 2100 HLG

Rec. 2100 PQ

NEW

=====

so in this case he talked about importing colorspace-tagged material, not
embedded icc or display side.

x264 support for XVAC-intra + HDR metadata was merged few years ago:

https://forum.doom9.org/showthread.php?p=1950549

https://forum.doom9.org/showthread.php?p=1940382

https://code.videolan.org/videolan/x264/-/merge_requests/5

I still wonder how you get those values for mastering display?

G(x,y)B(x,y)R(x,y)WP(x,y)L(max,min)

hm may be like here, vua libdisplayinfo/EDID

https://github.com/doitsujin/dxvk/blob/master/src/wsi/wsi_edid.cpp#L14

from

https://github.com/libsdl-org/SDL/issues/6587

but ofc there us dev blog saying edid can be incomplete/inaccurate:

https://planet.kde.org/xavers-blog-2024-05-10-hdr-and-color-management-in-kwin-part-3/

====

There is a fourth option though: Use the color information from the
display’s EDID. In Plasma 6.1, you can simply select this in the display
settings.

color profile settings

Note that it comes with some caveats too:

    the EDID only describes colors with the default display settings, so if
you change the “picture mode” or similar things in the display settings,
the values may not be correct anymore
    the manufacturer may not measure every panel and just put generic
values for the display model into the EDID
    the manufacturer may put completely wrong values in there (which is why
this is disabled by default)
    even when correct values are provided, ICC profiles have much more
detailed information on the display’s behavior than the EDID can contain

====

but at least this round of search shows that SDL(2.x, 3?) does have some
support for HDR now,  so may be it also an option!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20250415/df6fd7cd/attachment.htm>