From 9d75144011840b167da7b7d91deef9f231874eb5 Mon Sep 17 00:00:00 2001 From: "Steinar H. Gunderson" Date: Sun, 12 Apr 2020 14:51:46 +0200 Subject: [PATCH] Document Futatabi white balance. --- futatabi.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/futatabi.rst b/futatabi.rst index 8d9f1a0..af61596 100644 --- a/futatabi.rst +++ b/futatabi.rst @@ -201,6 +201,16 @@ hear any audio, unless they use a video player into the Futatabi stream locally (with associated delay). All of this may change in the future. +White balance +''''''''''''' + +Since version 1.9.2, Futatabi will integrate with Nageru for white balance; +the white balance set in Nageru will be recorded, and properly applied on +playback (including fades). Note that this assumes you are using the built-in +white balance adjustment (new in 1.9.2), not adding WhiteBalanceEffect manually +to the scene; see :ref:`white-balance` for an example. + + Replay workflows ---------------- @@ -324,6 +334,10 @@ In particular: the actual RGB color space; Nageru assumes it is Rec. 709, like for capture cards, but the differences between 601 and 709 here are small. sRGB gamma is assumed throughout, like in JFIF.) + * The white balance (gray point) is stored in a minimal EXIF header, + and echoed back for original and interpolated frames. (During fades, Futatabi + applies white balance itself, and does not require gray point adjustment + from the client.) Many players may also be confused by the fact that the resolution can change from frame to frame; this is because for original (uninterpolated) frames, -- 2.39.2