optical flow), although this may change in the future.
Since Futatabi is part of the Nageru source distribution, its version number
-mirrors Nageru. Thus, the first version of Futatabi is version 1.8.0,
-which is the Nageru version when it was first introduced.
+mirrors Nageru.
System requirements
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`.
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
+'''''''''''''
+
+Futatabi has limited audio support. It is recorded 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
+'''''''''''''
+
+Futatabi integrates 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, not adding WhiteBalanceEffect manually
+to the scene; see :ref:`white-balance` for an example.
+
+
Replay workflows
----------------
cue in point padding to e.g. two seconds, the cue-in point will automatically be set
two seconds ago when you cue-in, and similarly, if you set cue out point padding,
the cue-out point will be set two seconds
-into the future when you cue-out. (Cue-in and cue-out point padding were one
-joint setting before Futatabi 1.8.3.)
+into the future when you cue-out.
Instant clips
Like the previous section explained how you generally would know the *start*
of an interesting event (at least if discarding most of the candidates),
-you would be even more sure about the *end* of one. Thus, you can simply wait
+you would be even more sure about the *end* of one. Thus, you can wait
until something interesting has happened, and then click cue-in immediately
followed by cue-out. This will give you a clip of near zero length, ending
at the right point. Then, edit this clip to set the starting point as needed,
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,
-Futatabi will simply output the received JPEG frame directly to the output
+Futatabi will output the received JPEG frame directly to the output
stream, which can be a different resolution from the interpolated frames.
Also, even though Futatabi exists to make a fixed-framerate stream out of
projects / nageru-docs / blobdiff