X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=futatabi.rst;h=af615963f879d7f398ca631c1a1d887ddb57b17c;hb=ca8b32618cb0182937774367aebe599dba2d815b;hp=28b0954fd08ad8bf2775a36cfb6aee6e75c747b3;hpb=7947f73369e338693c08e597762ca5ba1e7aeb80;p=nageru-docs

diff --git a/futatabi.rst b/futatabi.rst
index 28b0954..af61596 100644
--- a/futatabi.rst
+++ b/futatabi.rst
@@ -189,6 +189,28 @@ out, but it doesn't hurt to give a warning up-front. The producer might also
 be able to request replays of specific events, or ask you to save something
 for later if they can't show it right now (e.g. a foul situation that wasn't called).
 
+Audio support
+'''''''''''''
+
+Since version 1.8.5, Futatabi has limited audio support. It is recorded
+(assuming Nageru is also at version 1.8.5 or newer) and saved for all inputs,
+and played back when showing a replay, but only when the replay speed is at
+100%, or very close to it. (At other speeds, you will get silence.)
+Furthermore, there is no local audio output; the Futatabi operator will not
+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
 ----------------
 
@@ -256,9 +278,9 @@ they will certainly be watchable.
 
 There are two files:
 
- * `Trøndisk 2018, semifinal only (MJPEG, 77 GB) <https://storage.sesse.net/trondisk2018-semifinal-multicam-mjpeg.mkv>`_:
-   One of the semifinals, in MJPEG format (about 30 minutes). This can be downloaded
-   and then fed directly to Nageru as if it were a real camera stream
+ * `Trøndisk 2018, final only (MJPEG, 126 GB) <https://storage.sesse.net/trondisk2018-final-multicam-mjpeg.mkv>`_:
+   The final match, in MJPEG format (about 73 minutes). This can be downloaded
+   and then fed directly to Futatabi as if it were a real camera stream
    (remember the --slow-down-input option).
  * `Trøndisk 2018, entire tournament (H.264, 74 GB) <https://storage.sesse.net/trondisk2018-multicam-h264.mp4>`_:
    The entire first part of the tournament,
@@ -312,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,