#Frigate openvino GPU detector - nothing in debug view?

1 messages · Page 1 of 1 (latest)

fierce pagoda
#

Hi,

I updated my Frigate hardware to Beelink S12 (N100) and made some configuration changes meanwhile. Also took latest beta (0.16-beta2) in use.

I think I managed to fix my configuration so that I don't get any errors printed anymore, I have HW acceleration in use, but the possible issue is the detector.

I'm using openvino with GPU device. When I go to settings -> Debug screen I see no rectangles at all. Also GPU utilization is always at 0%.

If I change the openvino to CPU, I can see the rectangles in the debug view, but it also doubles my CPU consumption.

Having it in GPU apparently still works, because it seems to detect the motion.

Can somebody explain what is this behavior and something I need to consider?

  1. Why GPU usage is 0%?
  2. Why there are no motion rectangles in debug view?

Thanks!

image.png
#

Frigate openvino GPU detector - nothing in debug view?

#

Partly also interested, because I had one camera which was detecting the motion and one which wasn't earlier today, and I could not debug it because it shows nothing in debug view.

I was also getting OOM-kills during the day, but I don't know what it is related to.

#

Well, I do see sometimes a motion box, but it disappears quite soon.. and from intel_gpu_top I can see something happening there, so maybe everything is just fine? I will continue monitoring..

final canopy
#

I'd recommend you share the config.

fierce pagoda
#

I don't think my camera configuration is related

mqtt:
  # unrelated

tls:
  # Disable TLS for port 8971
  enabled: false

ffmpeg:
  hwaccel_args: preset-intel-qsv-h264
  output_args:
    record: preset-record-generic-audio-aac
#  input_args: preset-rtsp-restream

detectors:
  ov:
    type: openvino
    device: GPU #CPU

model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt
# 
services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
#    image: ghcr.io/blakeblackshear/frigate:stable
    image: ghcr.io/blakeblackshear/frigate:0.16.0-beta2
    shm_size: "1024mb"
    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/video11:/dev/video11 # For Raspberry Pi 4B
      - /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
      - /dev/dri/card0:/dev/dri/card0
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /home/frigate/config:/config
      - /nvr/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "5000:5000" # Internal unauthenticated access. Expose carefully.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp