QMPlay2 detects it automatically, but if the detection fails, try to do it manually, e.g.: export QMPLAY2_EGL_CARD_FILE_PATH=/dev/dri/card1 and run QMPlay2 from command line. In case of multiple GPUs installed in system VA-API requires to use the same device as OpenGL. If everything is working properly, you can export this variable globally. In this case you can try do it manually: export QT_XCB_GL_INTEGRATION=xcb_glx and run QMPlay2 from command line. On X11 QMPlay2 tries to detect if EGL can be used, but the detection can fail. VA-API + OpenGL uses EGL for OpenGL context creation. VideoToolBox doesn't support deinterlacing.ĬUVID + Vulkan might not work properly on RTX devices. H.264 lossless movies (CRF 0 or QP 0) might not be properly decoded via VDPAU and VA-API. VA-API on Vulkan uses its own deinterlacing filter only on Intel drivers. Their settings are available in "Settings->Video filters". VDPAU, VA-API, CUVID and DXVA2 have its own deinterlacing filters. D3D11VA and VA-API use Vulkan video output, so Vulkan features are available, but CPU filters won't work.ĭXVA2 requires "WGL_NV_DX_interop" extension. Hardware acceleration important information:ĬUVID, DXVA2, VDPAU and VA-API use OpenGL video output, so OpenGL features are available, but CPU filters won't work.ĬUVID. Move hardware accelerated decoder on decoders list to the top, Hardware acceleration is disabled by default, but you can enable it in "Settings->Playback settings": QMPlay2 supports hardware video decoding: CUVID (NVIDIA only), DXVA2 (Windows Vista and higher), D3D11VA (Vulkan, Windows 8 and higher) VDPAU/VA-API (X11 for VDPAU, Linux/BSD only) and VideoToolBox (macOS only).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |