[HW Accel Support]: Intel-qsv or intel-vaapi is used #16455
-
Describe the problem you are havingI just migrated from 0.14 to 0.15. Up until 0.14 Frigate used In several post it was advised to use
But when opening the "hardware info" it seems that Intel-Vaapi is used. Is this correct?
Version0.15 Frigate config fileui:
time_format: 24hour
strftime_fmt: '%d/%m/%Y %H:%M:%S'
mqtt:
enabled: false
detectors:
coral:
type: edgetpu
device: usb
database:
path: /media/frigate/frigate.db
#logger:
# default: info
# logs:
# frigate.record: debug
birdseye:
enabled: false
mode: continuous
ffmpeg:
#hwaccel_args: preset-vaapi
hwaccel_args: preset-intel-qsv-h264
#input_args: preset-rtsp-restream
output_args:
record: preset-record-generic-audio-aac
record:
enabled: true
sync_recordings: false
retain:
days: 10
mode: all
alerts:
retain:
days: 10
detections:
retain:
days: 10
go2rtc:
streams:
tuinhuiscam:
- rtsp://rtspuser:[email protected]:554/Streaming/Channels/101
tuinhuiscam_sub:
- rtsp://rtspuser:[email protected]:554/Streaming/Channels/102
deurbel:
- ffmpeg:http://192.168.1.66/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=rtspuser&password=xxxx#video=copy#audio=copy#audio=opus
deurbel_sub:
- ffmpeg:http://192.168.1.66/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=rtspuser&password=xxxx
cameras:
tuinhuiscam: # geen output_args: geen audio
enabled: true
ffmpeg:
inputs:
- path: rtsp://localhost:8554/tuinhuiscam?video&audio
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://localhost:8554/tuinhuiscam_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
enabled: true
objects:
track:
- person
motion:
mask:
- 0,0.321,0.308,0.195,0.307,0,0,0
- 1,0,1,1,0.962,1,0.858,0
- 0.811,0.439,0.845,0.44,0.845,0.15,0.811,0.149
- 0,0.323,0.077,0.291,0.082,1,0,1
zones:
tuin:
coordinates: 0.961,1,0.873,0.164,0.388,0.166,0,0.324,0,1
objects: person
inertia: 3
loitering_time: 0
review:
alerts:
required_zones: tuin
####################################################################
deurbel: # <--- this will be changed to your actual camera later
enabled: true
ffmpeg:
inputs:
- path: rtsp://localhost:8554/deurbel
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://localhost:8554/deurbel_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
enabled: true
objects:
track:
- person
- bicycle
- motorcycle
motion:
mask: 0,0,1,0,1,0.413,0,0.413
zones:
straat:
coordinates: 0,1,1,1,1,0.414,0,0.414
objects:
- person
- bicycle
- motorcycle
inertia: 3
loitering_time: 0
review:
alerts:
required_zones: straat
version: 0.15-1
camera_groups: {}docker-compose file or Docker CLI command---
# https://github.com/blakeblackshear/frigate
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "160mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
# - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- ${PATH_TO_APPDATA}/frigate/config.yml:/config/config.yml
- ${PATH_TO_MOVIES}/frigate/storage:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "password"Relevant Frigate log output--Relevant go2rtc log output--FFprobe output from your camera--Install methodDocker Compose Object DetectorCoral Network connectionWired Camera make and modelHikvision, Reolink Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
I believe this is a bug in intel_gpu_top, if the streaming cpu usage is not high then there is nothing to worry about |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your quick response. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
vainfois part ofvaapi, running hardware info does not indicate whether or not QSV is being used as QSV is built on top of vaapi