Kaeru is no longer experimental.

[nageru-docs] / hardware.rst

diff --git a/hardware.rst b/hardware.rst
index 5171baebad937eb69e415cf28b08572175a5d86d..e2da70916c9405cb3dc43c1e03e16491e13ad50d 100644 (file)
--- a/hardware.rst
+++ b/hardware.rst
@@ -39,7 +39,7 @@ output as a sort of “digital intermediate” that can much easier be stored to
 (for future editing or re-streaming) or sent to an encoder on another machine
 for final streaming.
 
-Although you can (since Nageru 1.5.0) use software encoding through x264 for
+Although you can use software encoding through x264 for
 the digital intermediate, it is generally preferred to use a hardware encoder
 if it is available. Currently, VA-API is the only hardware encoding method
 supported for encoding the digital intermediate, although Nageru might support
@@ -129,8 +129,9 @@ from subsampled Y'CbCr (typically 4:2:2 for inputs and 4:2:0 for outputs)
 is done transparently on the GPU. Input and output is 8-bit Y'CbCr by default,
 but be aware that 8-bit Y'CbCr, however common, cannot capture the full color
 fidelity of 8-bit RGB (not to mention 10-bit RGB). If you have spare GPU power,
-you can enable 10-bit Y'CbCr input and output with --10-bit-input and
---10-bit-output, respectively, although you should be aware that client
+you can enable 10-bit Y'CbCr input and output with --10-bit (before Nageru 2.2.0,
+you needed to use --10-bit-input and --10-bit-output as separate flags),
+although you should be aware that client
 support for 10-bit H.264 is very limited. Also, Quick Sync Video does not
 support 10-bit H.264 encoding, so in this case, the digital intermediate needs
 to be encoded in software.