Fix wording about border colors

[nageru-docs] / gettingstarted.rst

diff --git a/gettingstarted.rst b/gettingstarted.rst
index 68edc81605f53f7e8ab53412c9d72514cf6100d4..fd6f64678965d21cc1885a707eb882993d2a215f 100644 (file)
--- a/gettingstarted.rst
+++ b/gettingstarted.rst
@@ -3,7 +3,7 @@ Getting started
 
 Welcome to Nageru! For simple use, you can jump right in and make yourself
 comfortable (at least if you have the :doc:`hardware requirements <hardware>`
 
 Welcome to Nageru! For simple use, you can jump right in and make yourself
 comfortable (at least if you have the :doc:`hardware requirements <hardware>`

-in place and have `compiled it <compile>`), but if you prefer a gentler introduction,
+in place and have `compiled it <compile>`_), but if you prefer a gentler introduction,

 this is the place.
 
 
 this is the place.
 
 


@@ -44,6 +44,14 @@ preview (using the 1–9 keys) and the right hand to choose a transition
 (using J, K or L). In addition, audio can be controlled using a MIDI controller
 if you want to; see the :doc:`audio <audio>` page for more information.
 
 (using J, K or L). In addition, audio can be controlled using a MIDI controller
 if you want to; see the :doc:`audio <audio>` page for more information.
 

+In some situations, like if you're producing sports, it can be useful to
+skip the preview step and cut directly to a source. Nageru supports this
+through **quick-cut keys**; if enabled, Q, W, E, etc. will have the same
+effect as pressing 1, 2, 3, etc. and then quickly J (for cut). Since it
+is easy to press such a key by mistake, this behavior is off by default,
+and must be enabled explicitly from the Video menu or through the
+“--quick-cut-keys” option.
+

 
 Channels
 ''''''''
 
 Channels
 ''''''''


@@ -71,8 +79,12 @@ by looking at its border. If it's got a red border, as in the leftmost
 input, it's live (either on its own, or as part of the side-by-side view).
 Similarly, if it's got a green border, as in the second input (you can
 see it if you look closely; it's a somewhat lighter shade of green),
 input, it's live (either on its own, or as part of the side-by-side view).
 Similarly, if it's got a green border, as in the second input (you can
 see it if you look closely; it's a somewhat lighter shade of green),

-it will be marked with green. On conflict, red (live) wins, since it is
-the most important piece of information.
+it is the preview. On conflict, red (live) wins, since it is the most
+important piece of information.
+
+If you have many channels, the default single-row view can make for previews
+that are somewhat small. If so, you can switch to the *video grid display*;
+see :ref:`audio-views` for more information.

 
 
 Transitions
 
 
 Transitions


@@ -123,10 +135,14 @@ The video menu contains the following elements:
     You can achieve the same effect as this option by sending
     SIGHUP to the Nageru process.
 
     You can achieve the same effect as this option by sending
     SIGHUP to the Nageru process.
 

+  * **Open frame analyzer:** See :doc:`analyzer` for more information.
+

   * **Change x264 bitrate:** See :doc:`streaming` for more information.
 
   * **Change x264 bitrate:** See :doc:`streaming` for more information.
 

-  * **HDMI/SDI output device, HDMI/SDI output resolution:** See :doc:`hdmisdi`
-    for more information.
+  * **HDMI/SDI output device, HDMI/SDI output resolution, Display time code:**
+    See :doc:`hdmisdi` for more information.
+
+  * **Enable quick-cut keys:** See above.

 
   * **Exit:** Exits Nageru, obviously.
 
 
   * **Exit:** Exits Nageru, obviously.
 


@@ -172,6 +188,16 @@ The options presented are as follows:
    cards that can handle it in hardware), but a simple option (“Scan”)
    is available to try all modes in turn until a signal is received.
 
    cards that can handle it in hardware), but a simple option (“Scan”)
    is available to try all modes in turn until a signal is received.
 

+ * **Input interpretation:** Choose how the Y'CbCr values in the input signal
+   are to be interpreted. *Auto* will choose whatever is correct (as per the
+   appropriate standards) for the current video mode, but occasionally,
+   devices will get this wrong, and you will need to change this setting
+   to get correct colors. You can use the *--input-ycbcr-interpretation=*
+   command-line option to achieve the same effect.
+
+   See :doc:`analyzer` for figuring out if you need to change this.
+   If unsure, leave it unchanged.
+

  * **Use as audio source:** See the :doc:`audio <audio>` page for more
    information. For simple audio only; unavailable in multichannel mode.
 
  * **Use as audio source:** See the :doc:`audio <audio>` page for more
    information. For simple audio only; unavailable in multichannel mode.