Mirrors/blakeblackshear.frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2024-11-21 19:07:46 +01:00
Code Issues Projects Releases Wiki Activity

clarify vaapi vs qsv (#11954)

Browse Source
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
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/configuration/hardware_acceleration.md
View File

@ -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