Low res video in live camera view

[rugene76]

Perhaps I'm missing something obvious, but I am not getting the high res video (2560x1920) in the live camera display for frigate. I'm using Reolink rlc-510wa cameras. Elsewhere, i.e., the home assistant feed using the lovelace card does provide the expected high res image. Captured video is also at the expected image quality.

Is this a reolink problem or is there some setting that needs to be adjusted in the frigate.yaml to get the high res live camera video?

I also use wyse cameras with the rtsp firmware and they work fine.

I'm running the latest frigate release as an addon to HA in a dedicated intel PC

Any ideas?

[NickM-27]

The live frigate view comes from the detect stream, so whatever you have as your detect stream is what will be displayed in the Frigate live UI

[rugene76]

thanks, that's good to know about the detect stream, but after changing the detect streams to rtsp://admin:[email protected]:554/h264Preview_01_main and adjusting the detect width and height, I'm still getting a low res live stream. The snapshots and captures are at the high resolution however. I tried the rtsp feed using VLC and there I do get the high res video as expected.

here's a snippet of my yaml:
reolink:
ffmpeg:
hwaccel_args:
- -hwaccel
- vaapi
- -hwaccel_device
- /dev/dri/renderD128
- -hwaccel_output_format
- yuv420p
output_args:
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
inputs:
- path: rtsp://admin:[email protected]:554/h264Preview_01_main
detect:
width: 2560
height: 1920
fps: 10

[NickM-27]

You'd also need to update your live config

# Optional: Live stream configuration for WebUI
# NOTE: Can be overridden at the camera level
live:
  # Optional: Set the height of the live stream. (default: 720)
  # This must be less than or equal to the height of the detect stream. Lower resolutions
  # reduce bandwidth required for viewing the live stream. Width is computed to match known aspect ratio.
  height: 720
  # Optional: Set the encode quality of the live stream (default: shown below)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 8

[NickM-27]

Do note that the increased resolution and fps for detect will use considerably more CPU resources

[rugene76]

the live setting was the answer. thanks so much!
Now I'll need to back down my other settings to get a reasonable balance.

I do have a coral chip installed. I'm not totally clear on the impact of using a full resolution stream vs a low res (640x480) sub stream for object detection.
It would be nice if frigate allowed the live stream to be derived from the high res stream instead of forcing it to the detect stream which, as I understand, should be low res for efficient object detection.

[NickM-27]

Now I'll need to back down my other settings to get a reasonable balance.

Do keep in mind this requirement from the live config This must be less than or equal to the height of the detect stream.

I do have a coral chip installed. I'm not totally clear on the impact of using a full resolution stream vs a low res (640x480) sub stream for object detection.

Resolution doesn't matter for the object detection itself since all regions are resized to the models input size (320x320 for the default model).

The resolution matters for motion detection (which is a lot more taxing) and then of course due to the resize I just mentioned at a certain point a higher resolution for detect is wasted since everything is downsized anyway. https://docs.frigate.video/guides/camera_setup#choosing-a-detect-resolution explains it well, you basically want the smallest resolution possible that is still able to detect everything you want to.

It would be nice if frigate allowed the live stream to be derived from the high res stream instead of forcing it to the detect stream which, as I understand, should be low res for efficient object detection.

With the way the current architecture works, the high res stream would have to be decoded to play in the frontend which would use significantly more resources.

An arch change for this is being discussed, but it is not trivial: #3753 (comment)

[digitalit]

@rugene76 i´m absolute not an expert but i´ve been told that it´s recommended to have the second stream with low resolution used in the detect and the main hi res stream to watch live.

Maybe i´m wrong but it works for me.

Have a nice day

[NickM-27]

OP is talking about the live view in frigate webUI being low res, not the RTMP Livestream

[digitalit]

@NickM-27 ok, sorry i misunderstood and i apologize.

Have a nice day

[leifnel]

I'm using go2rtp and I would like the full screen view to be the record stream, rtsp://frihost:8554/entrance_stream1.
It's okay to use the lowres detect stream when the view is not full screen, rtsp://frihost:8554/entrance_stream2