From 7b8176c8f55d2a60fcb1737112278a0f83f16a12 Mon Sep 17 00:00:00 2001 From: "Steinar H. Gunderson" Date: Fri, 8 Sep 2023 00:20:42 +0200 Subject: [PATCH] Document separate streaming. --- hardware.rst | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/hardware.rst b/hardware.rst index 344744e..1ff9b64 100644 --- a/hardware.rst +++ b/hardware.rst @@ -44,7 +44,8 @@ if it is available. Currently, VA-API is the only hardware encoding method supported for encoding the digital intermediate, although Nageru might support NVIDIA's NVENC at some point in the future. In particular, this means that Intel Quick Sync Video (QSV), the hardware H.264 encoder present on all modern -Intel GPUs, is supported. +Intel GPUs, is supported. If possible, Nageru uses zerocopy from the GPU to the +VA-API buffers in order to reduce memory transfer bandwidth. QSV is more than fast enough to keep up with 720p60 in realtime without eating appreciably into the power budget, but it is not @@ -57,10 +58,12 @@ further editing or transcoding without strong generational loss.) Thus, the QSV stream is not intended for streaming to end users of the Internet; it will need to be reencoded by some external means, or you can use Nageru's x264 support to produce a user-facing stream in addition to the digital intermediate -(see :doc:`streaming`). - -If possible, Nageru uses zerocopy from the GPU to the VA-API buffers in order to -reduce memory transfer bandwidth. +(see :doc:`streaming`). You can also use x264 to produce the recording to disk +instead of Quick Sync, using the --x264-record-video flag. If you wish to have +separate flags for streaming and storing to disk (e.g., to keep a digital intermediate +on disk), and have Nageru 2.1.0 or newer, you can use the --separate-x264-disk-encode flag (and associated +--x264-separate-disk-bitrate flags etc.). Otherwise, the same stream will go +to the network and to disk. Video capture cards -- 2.39.2