Document unsynchronized HDMI/SDI output.

[nageru-docs] / futatabi.rst

diff --git a/futatabi.rst b/futatabi.rst
index c2a76657a089546231094a257e51bf5dfa7e28dc..a16d3922fb35224cd86f54435908677e9d2ad8ae 100644 (file)
--- a/futatabi.rst
+++ b/futatabi.rst
@@ -25,8 +25,7 @@ by Kroeger et al, together with about half of the algorithm from
 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
@@ -192,8 +191,7 @@ for later if they can't show it right now (e.g. a foul situation that wasn't cal
 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,
+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
@@ -204,10 +202,10 @@ hear any audio, unless they use a video player into the Futatabi stream locally
 White balance
 '''''''''''''
 
-Since version 1.9.2, Futatabi will integrate with Nageru for 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 (new in 1.9.2), not adding WhiteBalanceEffect manually
+white balance adjustment, not adding WhiteBalanceEffect manually
 to the scene; see :ref:`white-balance` for an example.
 
 
@@ -242,8 +240,7 @@ command line using *--cue-in-point-padding* and *--cue-out-point-padding*, or se
 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
@@ -251,7 +248,7 @@ 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,
@@ -341,7 +338,7 @@ In particular:
 
 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