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

[nageru-docs] / futatabi.rst

diff --git a/futatabi.rst b/futatabi.rst
index e8370ae4a38359fe92fe0a63bbbd56f949b897d7..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`.
 
@@ -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,11 +278,12 @@ they will certainly be watchable.
 
 There are two files:
 
- * `Trøndisk 2018, finals only (MJPEG, 77 GB) <https://storage.sesse.net/trondisk2018-finals-multicam-mjpeg.mkv>`_:
-   The final match, 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 tournament,
+ * `Trøndisk 2018, entire tournament (H.264, 74 GB) <https://storage.sesse.net/trondisk2018-multicam-h264.mp4>`_:
+   The entire first part of the tournament,
    with no cuts (about 12 hours). However, due to space and bandwidth
    constraints, it has been transcoded to H.264 (with some associated
    quality loss), and needs to be transcoded to MJPEG before Nageru can use it.
@@ -273,13 +296,10 @@ on the camera operators. In short, they should be realistic input material
 to practice with.
 
 
-Transferring data to and from Nageru
-------------------------------------
-
 .. _futatabiformat:
 
-Video format specification
-''''''''''''''''''''''''''
+Internal video format details
+-----------------------------
 
 Futatabi expects to get data in MJPEG format only; though MJPEG is old,
 it yields fairly good quality per bit for an intraframe format, supports
@@ -314,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,