From: Steinar H. Gunderson Date: Thu, 7 Sep 2023 22:13:04 +0000 (+0200) Subject: We have had autodetect of EGL etc. for a while now. X-Git-Url: https://git.sesse.net/?a=commitdiff_plain;ds=inline;h=afb4ae5e8db801be9283aa5ad5ca518ce6985780;p=nageru-docs We have had autodetect of EGL etc. for a while now. --- diff --git a/hardware.rst b/hardware.rst index e2da709..272330f 100644 --- a/hardware.rst +++ b/hardware.rst @@ -60,18 +60,8 @@ 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`). -By default, Nageru uses zerocopy from the GPU to the VA-API buffers in order to -reduce memory transfer bandwidth, but this depends on EGL support (as opposed to -the older GLX standard), and also that the GPU you are rendering to also -supports VA-API. NVIDIA's proprietary drivers do not support either. Unfortunately, -this is somewhat cumbersome to automatically detect before it's too late to do anything -about it (Qt has already initialized using EGL), so on NVIDIA -systems, Nageru will exit with an error message asking you to set *--va-display* -to your Intel GPU manually. Simply follow the instructions printed to the terminal -to select what looks like your Intel GPU, and Nageru will fall back to using GLX -and transferring the memory data between the two GPUs via the CPU. (Some BIOSes -automatically disable the Intel GPU if you have a discrete GPU installed; you -will need to reenable it to get access to QSV, or Nageru can't run.) +If possible, Nageru uses zerocopy from the GPU to the VA-API buffers in order to +reduce memory transfer bandwidth. Video capture cards