From 1cb5dcb7dc4ddd81b29e75f517ce1464edacffd8 Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Fri, 14 Jun 2024 06:44:22 -0500 Subject: [PATCH] clarify vaapi vs qsv (#11954) --- docs/docs/configuration/hardware_acceleration.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/docs/configuration/hardware_acceleration.md b/docs/docs/configuration/hardware_acceleration.md index 6aaa1a106..4bcc7c138 100644 --- a/docs/docs/configuration/hardware_acceleration.md +++ b/docs/docs/configuration/hardware_acceleration.md @@ -11,7 +11,7 @@ It is recommended to update your configuration to enable hardware accelerated de ## Raspberry Pi 3/4 -Ensure you increase the allocated RAM for your GPU to at least 128 (`raspi-config` > Performance Options > GPU Memory). +Ensure you increase the allocated RAM for your GPU to at least 128 (`raspi-config` > Performance Options > GPU Memory). If you are using the HA addon, you may need to use the full access variant and turn off `Protection mode` for hardware acceleration. ```yaml @@ -65,7 +65,7 @@ Or map in all the `/dev/video*` devices. ### Via VAAPI -VAAPI supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VAAPI is recommended for all generations of Intel-based CPUs if QSV does not work. +VAAPI supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VAAPI is recommended for all generations of Intel-based CPUs. ```yaml ffmpeg: @@ -80,7 +80,7 @@ With some of the processors, like the J4125, the default driver `iHD` doesn't se ### Via Quicksync (>=10th Generation only) -QSV must be set specifically based on the video encoding of the stream. +If VAAPI does not work for you, you can try QSV if your processor supports it. QSV must be set specifically based on the video encoding of the stream. #### H.264 streams