clarify vaapi vs qsv (#11954)

This commit is contained in:
Blake Blackshear 2024-06-14 06:44:22 -05:00 committed by GitHub
parent 2535519830
commit 1cb5dcb7dc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -11,7 +11,7 @@ It is recommended to update your configuration to enable hardware accelerated de
## Raspberry Pi 3/4 ## 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. 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 ```yaml
@ -65,7 +65,7 @@ Or map in all the `/dev/video*` devices.
### Via VAAPI ### 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 ```yaml
ffmpeg: 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) ### 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 #### H.264 streams