Update hardware_acceleration.md - Intel wording changes and addition of drm hwaccel in Raspberry Pi section. #6413
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Just an update with some of my personal experiences using Frigate with a Raspberry Pi 4 and an Intel Celeron N5100 system.
✅ Deploy Preview for frigate-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
LaurenceGough
changed the title
NickM-27
requested changes
May 6, 2023
Comment on lines
+17
to
+18
| ##### H.264 and H.265 support | ||
| **NOTICE**: Raspberry Pi 3 does not support hardware acceleration of H.265. H.265 can use a large amount of compute resources on the Raspberry Pi 3 and 4, in some cases it might be better to use H.264 streams. |
There was a problem hiding this comment.
Suggested change
| ##### H.264 and H.265 support | |
| **NOTICE**: Raspberry Pi 3 does not support hardware acceleration of H.265. H.265 can use a large amount of compute resources on the Raspberry Pi 3 and 4, in some cases it might be better to use H.264 streams. | |
| :::note | |
| Raspberry Pi 3 does not support hardware acceleration of H.265. | |
| H.265 can use a large amount of compute resources on the Raspberry Pi 3 and 4, in some cases it might be better to use H.264 streams. | |
| ::: | |
|
|
||
| ### Intel-based CPUs | ||
|
|
||
| #### Via VAAPI | ||
| #### Via VA-API |
There was a problem hiding this comment.
Suggested change
| #### Via VA-API | |
| #### Via VAAPI |
Comment on lines
+19
to
+22
| ```yaml | ||
| ffmpeg: | ||
| hwaccel_args: -hwaccel drm | ||
| ``` |
There was a problem hiding this comment.
Suggested change
| ```yaml | |
| ffmpeg: | |
| hwaccel_args: -hwaccel drm | |
| ``` |
There was a problem hiding this comment.
We don't do raw args in the docs anymore, only presets.
|
|
||
| ```yaml | ||
| ffmpeg: | ||
| hwaccel_args: preset-vaapi | ||
| ``` | ||
|
|
||
| **NOTICE**: With some of the processors, like the J4125, the default driver `iHD` doesn't seem to work correctly for hardware acceleration. You may need to change the driver to `i965` by adding the following environment variable `LIBVA_DRIVER_NAME=i965` to your docker-compose file or [in the frigate.yml for HA OS users](advanced.md#environment_vars). | ||
| **NOTICE**: With some of the processors, like the J4125, the default driver `iHD` doesn't seem to work correctly for hardware acceleration. You may need to change the driver to `i965` by adding the following environment variable `LIBVA_DRIVER_NAME=i965` to your docker-compose file or [in the frigate.yml for HA OS users](advanced.md#environment_vars). You can use ```ls /dev/dri``` to check available drivers. |
There was a problem hiding this comment.
Suggested change
| **NOTICE**: With some of the processors, like the J4125, the default driver `iHD` doesn't seem to work correctly for hardware acceleration. You may need to change the driver to `i965` by adding the following environment variable `LIBVA_DRIVER_NAME=i965` to your docker-compose file or [in the frigate.yml for HA OS users](advanced.md#environment_vars). You can use ```ls /dev/dri``` to check available drivers. | |
| **NOTICE**: With some of the processors, like the J4125, the default driver `iHD` doesn't seem to work correctly for hardware acceleration. You may need to change the driver to `i965` by adding the following environment variable `LIBVA_DRIVER_NAME=i965` to your docker-compose file or [in the frigate.yml for HA OS users](advanced.md#environment_vars). You can use `ls /dev/dri` to check available drivers. |
|
|
||
| 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. | ||
| VA-API (Open Source Video Acceleration API) supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VA-API is recommended for all generations of Intel CPUs. Dedicated Quick Sync Video hardware for hardware-accelerated video encoding and decoding is supported with VA-API where available. |
There was a problem hiding this comment.
Suggested change
| VA-API (Open Source Video Acceleration API) supports automatic profile selection so it will work automatically with both H.264 and H.265 streams. VA-API is recommended for all generations of Intel CPUs. Dedicated Quick Sync Video hardware for hardware-accelerated video encoding and decoding is supported with VA-API where available. | |
| 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 CPUs. Dedicated Quick Sync Video hardware for hardware-accelerated video encoding and decoding is supported with VAAPI where available. |
|
@LaurenceGough Please accept the commit suggestions or update the PR to address my changes if you don't like what I suggested |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just an update with some of my personal experiences using Frigate with a Raspberry Pi 4 and an Intel Celeron N5100 system.