In the Futatabi example command line, add the missing port number.

[nageru-docs] / futatabi.rst

diff --git a/futatabi.rst b/futatabi.rst
index 8d9f1a02f7a1a539e7d96a9f25368fbe2f7e71b0..c2a76657a089546231094a257e51bf5dfa7e28dc 100644 (file)
--- a/futatabi.rst
+++ b/futatabi.rst
@@ -56,7 +56,7 @@ input or output. Assuming you have a recent version of Nageru (typically one
 that comes with Futatabi), it is capable of sending all of its cameras as one
 video stream (see :ref:`futatabiformat`), so you can start Futatabi with
 
-  ./futatabi http://nageru-server.example.org/multicam.mp4
+  ./futatabi http://nageru-server.example.org:9095/multicam.mp4
 
 If you do not have a running Nageru installation, see :ref:`sampledata`.
 
@@ -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,