[HW Accel Support]: iGPU UHD 630 ffmpeg errors when not using v5

[mattenz]

Describe the problem you are having

I have an Intel i7 10700K with a UHD 630 iGPU. If I have hwaccel config set to "preset-intel-qsv-h264" I get continuous ffmpeg errors for one camera (Reolink POE Doorbell):

info  | 2025-09-14 17:19:58 | watchdog.doorbell      | doorbell exceeded fps limit. Exiting ffmpeg...
info  | 2025-09-14 17:19:58 | watchdog.doorbell      | Waiting for ffmpeg to exit gracefully...
error | 2025-09-14 17:19:59 | frigate.video          | doorbell: Unable to read frames from ffmpeg process.
error | 2025-09-14 17:19:59 | frigate.video          | doorbell: ffmpeg process is not running. exiting capture thread...
error | 2025-09-14 17:19:59 | watchdog.doorbell      | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: VA-API version 1.22.0
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: Found init function __vaDriverInit_1_22
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: va_openDriver() returns 0
info  | 2025-09-14 17:19:59 | watchdog.doorbell      | Restarting ffmpeg...

I only get it with this camera tho. I also have a Unifi G3 Flex which does not generate those errors on QSV.

If I switch the Doorbell to Vaapi I get a different set of errors, but far less frequently, like maybe once every few hours:

error | 2025-09-15 15:36:42 | frigate.video          | doorbell: Unable to read frames from ffmpeg process.
error | 2025-09-15 15:36:42 | frigate.video          | doorbell: ffmpeg process is not running. exiting capture thread...
error | 2025-09-15 15:36:42 | watchdog.doorbell      | Ffmpeg process crashed unexpectedly for doorbell.
error | 2025-09-15 15:36:42 | watchdog.doorbell      | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [AVHWFramesContext @ 0x723628066b40] Failed to sync surface 0xd: 1 (operation failed).
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [hwdownload @ 0x723638003980] Failed to download frame: -5.
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [vf#0:0 @ 0x569b958bfdc0] Error while filtering: Input/output error
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [vf#0:0 @ 0x569b958bfdc0] Task finished with error code: -5 (Input/output error)
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [vf#0:0 @ 0x569b958bfdc0] Terminating thread with return code -5 (Input/output error)
info  | 2025-09-15 15:36:42 | watchdog.doorbell      | Restarting ffmpeg...

If I switch ffmpeg back to V5 and use Vaapi, I get no errors. I have Frigate running in a Proxmox LXC Ubuntu container.

I have experimented with switching the Doorbell between RSTP and HTTP and having both options in QSV and Vaapi but it doesn't seem to make any difference.

Version

0.16.1-e664cb2

Frigate config file

detectors:
  ov_0:
    type: openvino
    device: GPU
model:
  path: plus://92ad50d0e21741d1a00e4a376cd34671
  # width: 320
  # height: 320
  # model_type: yolonas
  # input_tensor: nchw
  # input_pixel_format: bgr
  # labelmap_path: /labelmap.txt
tls:
  enabled: false
database:
  path: /config/frigate.db
mqtt:
  host: homeassistant.fortress.local
  topic_prefix: frigate
  user: '{FRIGATE_MQTT_USER}'
  password: '{FRIGATE_MQTT_PASSWORD}'
  client_id: frigate
go2rtc:
  webrtc:
    listen: 192.168.0.106:8555
    candidates:
      - 202.124.101.177:8555
  streams:
    driveway:
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.11:554/s0
      - ffmpeg:driveway#audio=opus
    driveway_sub:
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.11:554/s1
    # bedroom:
    # - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.0.61:554/s0
    doorbell:
      #- "ffmpeg:http://1.1.1.12/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=<username>&password=<password>#video=copy#audio=copy#audio=opus"
      #- rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.12:554/h264Preview_01_sub
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.12:554/h264Preview_01_main
      - ffmpeg:driveway#audio=opus
    doorbell_sub:
      - "ffmpeg:http://1.1.1.12/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=<username>&password=<password>"
      #- ffmpeg:rtmp://1.1.1.12/bcs/channel0_ext.bcs?channel=0&stream=2&user=<username>&password=<password>
    # doorbell_tts:
    #   - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.12:554/h264Preview_01_main
    #   - ffmpeg:doorbell_tts#audio=opus#audio=copy
  homekit:
    driveway:
      name: Driveway
      pin: 12345678
      device_id: driveway
      pairings:
        - client_id=E98E192A-1464-44BE-A282-9E043B37E506&client_public=05889beeabeb4bbb1cf663617ae642904503bab1cbac7f6711d32b527a3aa87b&permissions=1
        - client_id=87B7423B-A66A-485F-8CDA-E33B4B8C8C1B&client_public=311d1d78f6bd8eb02beb65aa80fce81cf96b300c6cf7defa2f4c67560b1a1cca&permissions=1
  
    doorbell:
      name: Doorbell
      pin: 12345678
      device_id: doorbell
      pairings:
        - client_id=E98E192A-1464-44BE-A282-9E043B37E506&client_public=05889beeabeb4bbb1cf663617ae642904503bab1cbac7f6711d32b527a3aa87b&permissions=1
        - client_id=87B7423B-A66A-485F-8CDA-E33B4B8C8C1B&client_public=311d1d78f6bd8eb02beb65aa80fce81cf96b300c6cf7defa2f4c67560b1a1cca&permissions=1
ffmpeg:
  # path: "5.0"
  #hwaccel_args: preset-vaapi
  hwaccel_args: preset-intel-qsv-h264
objects:
  track:
    - person
    - dog
    - car
    - cat
    - rabbit
    - nzpost
    - face
    - package
    - license_plate
  filters:
    car:
      min_score: 0.8
cameras:
  driveway:
    webui_url: 1.1.1.11
    ffmpeg:
      output_args:
        record: preset-record-ubiquiti
      inputs:
        - path: rtsp://127.0.0.1:8554/driveway
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
        # - path: rtsp://127.0.0.1:8554/driveway_sub
        #   input_args: preset-rtsp-restream
        #   roles:
        #     - detect
    detect:
      width: 1280
      height: 720
      fps: 5
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 5
    zones:
      driveway_zone:
        coordinates: 
          0.001,0.999,0.001,0.071,0.084,0.035,0.221,0.033,0.263,0.072,0.383,0.074,0.388,0.079,0.56,0.072,0.764,0.128,0.739,0.334,0.413,0.192,0.18,0.455,0.094,0.999
        objects:
          - person
          - face
          - dog
          - car
          - license_plate
          - cat
          - rabbit
          - nzpost
        filters:
          person:
            min_area: 5100
        inertia: 3
        loitering_time: 0
      carpark_zone:
        coordinates: 
          0.414,0.193,0.737,0.332,0.782,0.017,1,0.049,1,1,0.095,0.999,0.18,0.454
        loitering_time: 3
        objects:
          - car
          - cat
          - dog
          - license_plate
          - face
          - person
          - rabbit
          - nzpost
        filters:
          person:
            min_area: 20000
          cat:
            max_area: 2000
            min_score: 0.8
          car:
            min_area: 80000
        inertia: 3
    record:
      enabled: true
      retain:
        days: 7
      alerts:
        retain:
          days: 7
      detections:
        retain:
          days: 7
    review:
      alerts:
        required_zones:
          - driveway_zone
          - carpark_zone
      detections:
        required_zones:
          - driveway_zone
          - carpark_zone
    motion:
      mask: 0,0.03,0.187,0.031,0.187,0,0.001,0
      threshold: 40
      contour_area: 20
      improve_contrast: true
  doorbell:
    webui_url: http://1.1.1.12/
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell?video=copy&audio=aac
          input_args: preset-rtsp-restream
          hwaccel_args: preset-vaapi
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_sub?video=copy
          input_args: preset-rtsp-restream
          hwaccel_args: preset-vaapi
          roles:
            - detect
    objects:
      track:
        - face
        - person
        - dog
        - cat
      filters:
        person:
          min_score: 0.89
    zones:
      frontdoor_zone:
        coordinates: 
          1,1,0,1,0,0.731,0.239,0.637,0.251,0.649,0.284,0.57,0.269,0,1,0
        objects:
          - person
          - face
          - dog
          - cat
        filters:
          person:
            min_score: 0.89
        inertia: 3
        loitering_time: 0
    detect:
      width: 896
      height: 672
      fps: 10
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 7
    record:
      enabled: true
      retain:
        days: 7
      alerts:
        retain:
          days: 5
      detections:
        retain:
          days: 5
    lpr:
      enabled: false
    motion:
      mask: 0.008,0.017,0.012,0.052,0.478,0.059,0.482,0.016
version: 0.16-0
detect:
  enabled: true
semantic_search:
  enabled: false
  model_size: small
face_recognition:
  enabled: true
  model_size: large
lpr:
  enabled: true
  #device: GPU
  known_plates:
    Shark:
      - <plate>
    Model 3:
      - <plate>
classification:
  bird:
    enabled: false

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    cap_add:
      - CAP_PERFMON    
    shm_size: "134mb" # update for your cameras based on calculation above
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /root/frigate/config/:/config/
      - /opt/frigate/media:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    network_mode: "host"

Relevant Frigate log output

info  | 2025-09-14 17:19:58 | watchdog.doorbell      | doorbell exceeded fps limit. Exiting ffmpeg...
info  | 2025-09-14 17:19:58 | watchdog.doorbell      | Waiting for ffmpeg to exit gracefully...
error | 2025-09-14 17:19:59 | frigate.video          | doorbell: Unable to read frames from ffmpeg process.
error | 2025-09-14 17:19:59 | frigate.video          | doorbell: ffmpeg process is not running. exiting capture thread...
error | 2025-09-14 17:19:59 | watchdog.doorbell      | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: VA-API version 1.22.0
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: Found init function __vaDriverInit_1_22
error | 2025-09-14 17:19:59 | ffmpeg.doorbell.detect | libva info: va_openDriver() returns 0
info  | 2025-09-14 17:19:59 | watchdog.doorbell      | Restarting ffmpeg...

error | 2025-09-15 15:36:42 | frigate.video          | doorbell: Unable to read frames from ffmpeg process.
error | 2025-09-15 15:36:42 | frigate.video          | doorbell: ffmpeg process is not running. exiting capture thread...
error | 2025-09-15 15:36:42 | watchdog.doorbell      | Ffmpeg process crashed unexpectedly for doorbell.
error | 2025-09-15 15:36:42 | watchdog.doorbell      | The following ffmpeg logs include the last 100 lines prior to exit.
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [AVHWFramesContext @ 0x723628066b40] Failed to sync surface 0xd: 1 (operation failed).
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [hwdownload @ 0x723638003980] Failed to download frame: -5.
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [vf#0:0 @ 0x569b958bfdc0] Error while filtering: Input/output error
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [vf#0:0 @ 0x569b958bfdc0] Task finished with error code: -5 (Input/output error)
error | 2025-09-15 15:36:42 | ffmpeg.doorbell.detect | [vf#0:0 @ 0x569b958bfdc0] Terminating thread with return code -5 (Input/output error)
info  | 2025-09-15 15:36:42 | watchdog.doorbell      | Restarting ffmpeg...

Relevant go2rtc log output

github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error="read tcp 192.168.0.50:54036->1.1.1.12:554: read: connection reset by peer" url=rtsp://<username>:<password>@1.1.1.12:554/h2

FFprobe output from your camera

Metadata:
    |RtmpSampleAccess: true
    displayWidth    : 896
    displayHeight   : 672
  Duration: 00:00:00.00, start: 54536.219000, bitrate: N/A
  Stream #0:0: Video: h264 (High), yuv420p(progressive), 896x672, 20 fps, 20 tbr, 1k tbn
  Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp

  Metadata:
    title           : Session streamed by "preview"
    comment         : reolink rtsp stream
  Duration: N/A, start: 0.000688, bitrate: N/A
  Stream #0:0: Video: h264 (High), yuv420p(progressive), 2560x1920, 20 fps, 40 tbr, 90k tbn
  Stream #0:1: Audio: aac (LC), 16000 Hz, mono, fltp

Install method

Docker Compose

Object Detector

OpenVino

Network connection

Wired

Camera make and model

Reolink Doobell POE

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

Your config uses both VAAPI and QSV hardware acceleration for your Intel UHD 630 iGPU, which is supported in Frigate, but certain hardware/driver combinations can behave differently per camera or stream(1). For Intel CPUs gen8-gen12 (which includes your i7-10700K), both preset-vaapi and preset-intel-qsv-h264 are supported options(1). You may need to experiment to find which preset is most stable for your camera streams.

• For QSV (preset-intel-qsv-h264), this is correct for your CPU generation(1).
• For VAAPI, the recommended preset is preset-vaapi if QSV is unstable(1).
• If you have stability issues with one camera (like your Reolink Doorbell), but not others, it suggests the stream specifics (resolution, encoding, etc.) may interact poorly with a specific hardware pipeline(1).
• You can set stream-specific hwaccel_args in the camera config to use VAAPI for the doorbell and QSV for others(2).

Example for stream-specific hardware acceleration:

cameras:
  doorbell:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell?video=copy&audio=aac
          input_args: preset-rtsp-restream
          hwaccel_args: preset-vaapi
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_sub?video=copy
          input_args: preset-rtsp-restream
          hwaccel_args: preset-vaapi
          roles:
            - detect

You can do the same per input for other cameras, using preset-intel-qsv-h264(2).

If you see fewer errors with VAAPI, it's reasonable to run the doorbell on VAAPI and your other cameras on QSV. You may also want to check your Proxmox LXC GPU passthrough configuration to ensure full access to /dev/dri devices(1).

If you find that using FFmpeg v5 eliminates errors, you can set the FFmpeg version globally or per camera:

ffmpeg:
  path: "5.0"

or per camera:

cameras:
  doorbell:
    ffmpeg:
      path: "5.0"

(2)

If you continue to see issues, review your container privileges and ensure you are passing through the correct /dev/dri devices(1). You might also want to try running the container in privileged mode and experimenting with the LIBVA_DRIVER_NAME environment variable set to iHD (or i965 for older CPUs)(1).

For more details, see:

• Video Decoding
• Full Reference Config

📚 Sources:

1. Video Decoding
2. Full Reference Config

---

Have another question? Just tag @inkeep.

[hawkeye217]

In addition to the AI's response, I'd suggest a few things:

1. You probably should be using the recommended Reolink config for your doorbell.
2. You are not specifying the correct stream name for transcoding to opus audio for your doorbell. You currently have:

    doorbell:
      #- "ffmpeg:http://1.1.1.12/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=<username>&password=<password>#video=copy#audio=copy#audio=opus"
      #- rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.12:554/h264Preview_01_sub
      - rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@1.1.1.12:554/h264Preview_01_main
      - ffmpeg:driveway#audio=opus

You should be providing doorbell as the stream name for opus audio, driveway. The transcoding line needs to be ffmpeg:doorbell#audio=opus.

[mattenz]

Based on the log file and these lines "ffmpeg.doorbell.detect", is it correct to assume that the issue is with the detect feed?

[hawkeye217]

Yes

[mattenz]

Interesting...that feed is using the recommended Reolink settings. Is there any downside to just using ffmpeg v5 for that feed rather than the default version?

[hawkeye217]

No downside. If it works better for you with ffmpeg 5, just stick with that!

[mattenz]

Huh, not sure how I had missed that audio line. Somehow it's been working all this time like that!

I have experimented with the recommended reolink config options (they're currently commented out in the config) but in the past I had found when using the HTTP stream that as the day went on the audio would become more and more out of sync. In regards to this issue though, it didn't stop the ffmpeg errors that I'm seeing.

[hawkeye217]

The line matters mostly for two-way audio - if you haven't been using that, you likely wouldn't notice any issues.