[HW Accel Support]: hwaccel_args: preset-rpi-64-h265 seems not to have effecto on Rpi4

[majkrzak]

Describe the problem you are having

I have been playing with setup of frigate installed as Home Assistant addon on Rpi4.
I followed the instructions of enabling the hw acceleration, by setting gpu_mem to 256 and adding hwaccel_args: preset-rpi-64-h264.

Apparently CPU usage checked in Home assistant adon panel and frigate metrics looks the same no matter if hwaccel is enabled or not. It is kinda stuck on about "20% ffmpeg" usage per camera.

No errors or warnings in logs. Despite the one about disabled acceleration when acceleration is disabled.

What can be wrong?

Version

0.14.1-f4f3cfa

Frigate config file

detectors:
  coral:
    type: edgetpu
    device: usb

ffmpeg:
  hwaccel_args: preset-rpi-64-h264

objects:
  track:
  - person
  - car
  - dog
  - cat

version: 0.14

...

docker-compose file or Docker CLI command

NA

Relevant Frigate log output

NA

Relevant go2rtc log output

NA

FFprobe output from your camera

ffprobe version 4.3.8-0+deb11u1+rpt1 Copyright (c) 2007-2024 the FFmpeg developers
  built with gcc 10 (Debian 10.2.1-6)
  configuration: --prefix=/usr --extra-version=0+deb11u1+rpt1 --toolchain=hardened --incdir=/usr/include/aarch64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-mmal --enable-neon --enable-v4l2-request --enable-libudev --enable-epoxy --enable-sand --libdir=/usr/lib/aarch64-linux-gnu --arch=arm64 --enable-pocketsphinx --enable-libdc1394 --enable-libdrm --enable-vout-drm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 51.100 / 56. 51.100
  libavcodec     58. 91.100 / 58. 91.100
  libavformat    58. 45.100 / 58. 45.100
  libavdevice    58. 10.100 / 58. 10.100
  libavfilter     7. 85.100 /  7. 85.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc    55.  7.100 / 55.  7.100
[rtsp @ 0x55d1127870] getaddrinfo(): Name or service not known
Input #0, rtsp, from 'rtsp://admin:[email protected]/media/video2':
  Metadata:
    title           : VCP IPC Realtime stream
  Duration: N/A, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: h264 (High), yuvj420p(pc, bt709, progressive), 1280x720, 5 fps, 60 tbr, 90k tbn, 10 tbc
    Stream #0:1: Audio: pcm_mulaw, 8000 Hz, 1 channels, s16, 64 kb/s
    Stream #0:2: Data: none
Unsupported codec with id 0 for input stream 2

Install method

HassOS Addon

Object Detector

Coral

Network connection

Wired

Camera make and model

internec i6

Screenshots of the Frigate UI's System metrics pages

NA

Any other information that may be helpful

No response

[NickM-27]

which addon are you using?

[majkrzak]

Frigate (Full Access)

[NickM-27]

Is protected mode off?

[majkrzak]

It seems so, the switch is on the left and huge red banner is displayed on top of the module page.

[majkrzak]

I checked, and the most load is caused by the ffmpeg process reading from the camera stream.
I see ffprobe reports yuvj420p as pixformat, but later yuv420p is required. Can the conversion here be so costly?

[majkrzak]

I tried running beta version. It claims ffmpeg is no longer in path and the 7 branch will be used. In top I see that ffmpeg reporting version 4.3 is run.

[majkrzak]

Any particular reason why to keep it such outdated? May it be reason of poor performance?

[majkrzak]

Also looks like "environment_variables" is getting ignred.

ffmpeg:
  path: "5.0"
  hwaccel_args: preset-rpi-64-h264
environment_vars:
  LIBAVFORMAT_VERSION_MAJOR: "61"

most likely TIMOUT_PARAM is getting evaluated before the code loading them.

[NickM-27]

Any particular reason why to keep it such outdated? May it be reason of poor performance?

There is a long history of issues trying to have this work with a non-rpi optimized ffmpeg #3780 #2030

[majkrzak]

Not sure if it works in my case either 😅 Same cpu usage no matter if enabled or not.

[majkrzak]

I have lunched with -standard-arm64 image version. In my case there are no additional trouble when running it. It behaves similar no matter if 5.0 or 7.0 or 4.rpi branch is running.

As the problems you mentioned are 3 years old, it may be worth considering unifying it in beta release.

But in general I would suggest using adding the "RPI" variant selecion using the same method the 5/7 is selected.

[majkrzak]

Looks like the problem is with yuvj420p to yuv420p conversion.
Disabling conversion kinda solves the issue.

ffmpeg:
  output_args:
    #detect: -threads 2 -f rawvideo -pix_fmt yuv420p
    detect: -threads 2 -f rawvideo -pix_fmt yuvj420p