Document the change of --10-bit flags in 2.2.0.

[nageru-docs] / hdmisdi.rst

diff --git a/hdmisdi.rst b/hdmisdi.rst
index 064fe85aef8c90cbc6ddf75ec846c31b6d1b14d6..e04b8b720bcb96c51dd2fe2e2befbd606b98705b 100644 (file)
--- a/hdmisdi.rst
+++ b/hdmisdi.rst
@@ -8,14 +8,14 @@ the stream on another PC, but for many uses, the end-to-end latency is
 too high, and you might not want to involve a full extra PC just for this
 anyway.
 
-Thus, since 1.5.0, Nageru supports using a spare output card for HDMI/SDI
+Thus, Nageru supports using a spare output card for HDMI/SDI
 output, turning it into a simple, reasonably low-latency audio/video switcher.
 
 
 Setting up HDMI/SDI output
 --------------------------
 
-Turning on HDMI/SDI output is simple; just right-click on the live view and
+To turn on HDMI/SDI output, right-click on the live view and
 select the output card. (Equivalently, you can access the same functionality
 from the *Video* menu in the regular menu bar, or you can give the
 *--output-card=* parameter on the command line.) Currently, this is supported
@@ -164,12 +164,14 @@ Audio and video queue lengths do not need to match exactly; the two streams
 and for HDMI/SDI output.
 
 
+.. _measuring-latency:
+
 Measuring latency
 .................
 
 In order to optimize latency, it can be useful to measure it, but for most
 people, it's hard to measure delays precisely enough to distinguish reliably
-between e.g. 70 and 80 milliseconds by eye alone. Nageru gives you some simple
+between e.g. 70 and 80 milliseconds by eye alone. Nageru gives you some
 tools that will help.
 
 The most direct is the flag *--print-video-latency*. This samples, for every
@@ -194,13 +196,21 @@ lowest and highest will be printed. Do note that the measurement is still done
 over a single *output* frame; it is *not* a measurement over the last 100
 output frames, even though the statistics are only printed every 100th.
 
+For more precise measurements, you can use Prometheus metrics to get percentiles
+for all of these points, which will measure over all frames (over a one-minute
+window). This yields more precise information than sampling every 100 frames,
+but setting up Prometheus and a graphic tool is a bit more work, and usually not
+worth it for simple measurement. For more information, see :doc:`monitoring`.
+
 Another trick that can be useful in some situations is *looping* your signal,
 ie., connecting your output back into your input. This allows you to measure
 delays that don't happen within Nageru itself, like any external converters,
 delays in the input driver, etc.. (It can also act as a sanity check to make
 sure your A/V chain passes the signal through without quality degradation,
 if you first set up a static picture as a signal and then switch to the loop
-input to verify that the signal stays stable without color shifts e.g. [#]_)
+input to verify that the signal stays stable without color e.g. shifts [#]_.
+See the section on :doc:`the frame analyzer <analyzer>` for other ways of
+debugging signal integrity.)
 
 For this, the *timecode output* is useful; you can turn it on from the Video
 menu, or through the command-line flag *--timecode-stream*. (You can also