Frigate/HW Acceleration/Proxmox Help

I hope someone can help here as I just don’t understand how to get this to work lol

Running Proxmox, HAOS on a VM and a single container running Alpine Linux which has Frigate in a docker container

Using 2 cameras on Frigate, one is H264 so working great, other is H265 so not so great so having issues with it. Can get it into Frigate no problem but its CPU intensive causing my little NUC equivalent (running a Ryzen 5560u) to be using too much CPU getting warm n loud etc. This is because its H265 so having to use:

      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v libx264 -an
        rtmp: -c:v libx264 -an -f flv

I want to use hardware acceleration to bring the CPU overhead down and make this a more bearable situation but I can’t seem to work it out, also using the current method is quite laggy and the camera is around 10 seconds or so behind my other h264 one

I believe this is correct for my CPU:

hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p

But just getting the green screen, Frigate log (camera is called driveway):

[2023-01-16 01:06:19] frigate.video                  ERROR   : driveway: Unable to read frames from ffmpeg process.
[2023-01-16 01:06:19] frigate.video                  ERROR   : driveway: ffmpeg process is not running. exiting capture thread...
[2023-01-16 01:06:37] watchdog.driveway              ERROR   : Ffmpeg process crashed unexpectedly for driveway.
[2023-01-16 01:06:37] watchdog.driveway              ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2023-01-16 01:06:37] ffmpeg.driveway.detect         ERROR   : Guessed Channel Layout for Input Stream #0.1 : mono
[2023-01-16 01:06:37] ffmpeg.driveway.detect         ERROR   : [AVHWDeviceContext @ 0x55ee06388880] No VA display found for device /dev/dri/renderD128.
[2023-01-16 01:06:37] ffmpeg.driveway.detect         ERROR   : Device creation failed: -22.
[2023-01-16 01:06:37] ffmpeg.driveway.detect         ERROR   : [hevc @ 0x55ee0638fbc0] No device available for decoder: device type vaapi needed for codec hevc.
[2023-01-16 01:06:37] ffmpeg.driveway.detect         ERROR   : Device setup failed for decoder on input stream #0:0 : Invalid argument

Running VAINFO on the same alpine linux container gives me this:

Trying display: wayland
error: XDG_RUNTIME_DIR not set in the environment.
Trying display: x11
error: can't connect to X server!
Trying display: drm
error: failed to initialize display

I am a real linux noob but really would like to get this working so hope someone here that’s much smarter than me can help point me in the right direction…

Beta version of frigate use go2rtc and may work better with h.265

Why are you using libx264 for recordings? There is absolutely no need to transcode to h264 for recordings as long as you use a browser that supports h265 playback.

also yes, as @tmjpugh mentioned we use go2rtc for restreaming in 0.12 (currently in beta) which supports h265 also unlike RTMP

No idea, I just followed others instructions and recommendations on what should be set for h265. Would be grateful for any tips.

I’ve actually found out in the meantime that I can change the cameras feed to h264 so have done that for now, long term will h265 and the beta be a better idea?