[Config Support]: Can u rescale the camera preview in the console?

[asantaga]

Describe the problem you are having

Hi there,

I've looked for this in the docs and cant find it. Most of my cameras are either 1080p or 2k, and what Im noticing is in that when I preview the camera in the frigate ui (especially recordings) , the image is too big. Ideally it should be scaled to fit the browser window.

is there a config for this affecting only the frigate UI?

Here is an example of what i get

thank you!

Version

0.11.0 Beta 3 , but also other versions

Frigate config file

mqtt:
  host: 192.168.0.204
ui:
  use_experimental: True

detectors:
  cpu1:
    type: cpu

birdseye:
  enabled: true

cameras:
  pantilt: 
    ffmpeg:
      inputs:
        - path: rtsp://xxxx:[email protected]/live0
          roles:
            - rtmp
            - detect
            - clips
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p


    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
        - person
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 10
    motion:
      mask:
        - 1920,712,1920,0,0,0,0,750,505,632,698,625,773,716,1409,724,1400,635

    record:
      enabled: True
      retain:
        days: 10
      events:
        retain:
          default: 10




  frontroom: 
    ffmpeg:
      inputs:
        - path: rtsp://xxxxx:[email protected]:554/live0
          roles:
            - rtmp
            - detect
            - clips
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
    detect:
      width: 1920
      height: 1080
      fps: 5
    objects:
      track:
        - person
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 10
    motion:
      mask:
        - 584,531,1549,503,1552,592,1865,594,1920,576,1920,480,1920,0,569,0,563,95,570,168,576,250
    record:
      enabled: True
      retain:
        days: 10
      events:
        retain:
          default: 10


  doorbell: 
    ffmpeg:
      inputs:
        - path: rtsp://xxxxx:[email protected]/Streaming/Channels/101
          roles:
            - clips
            - record
            - detect
            - rtmp
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
      hwaccel_args:
        - -hwaccel
        - vaapi
        - -hwaccel_device
        - /dev/dri/renderD128
        - -hwaccel_output_format
        - yuv420p
#    rtmp:
#     enabled: false
    detect:
      width: 1536
      height: 1536
      fps: 5
    objects:
      track:
        - person
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 10
    motion:
      mask:
        - 1536,1102,1536,0,0,0,0,1118
    record:
      enabled: True
      retain:
        days: 10
      events:
        retain:
          default: 10

Relevant log output

n/a

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Coral version

CPU (no coral)

Any other information that may be helpful

No response

[asantaga]

Just noticed, if I shrink the Y axis then after a bit of reduction it does render correctly, as soon as the Y goes beyond a point then it scales incorrectly.

thanks

[NickM-27]

This is from the docs, should do what you're asking:

# 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

[asantaga]

Hey Nick , I tried these changes but they dont affect the "recordings" view. Also i think the UI should be reactive to the window size, even if the image is 720/1080 etc.

[NickM-27]

Hey Nick , I tried these changes but they dont affect the "recordings" view

Whoops, I misunderstood and thought you were talking about live view. Yeah that's not currently possible, I'll have to see if I can find it but there's a current feature request to change this sizing

[asantaga]

Thanks Nick, appreciate it,

[asantaga]

is this the FR you were talking about ? https://github.com/blakeblackshear/frigate/issues/1557

[NickM-27]

This is the one I had in mind https://github.com/blakeblackshear/frigate/issues/3287

[tmjpugh]

#3287 was for resize events window. I think @asantaga is having same issue as me where you must vertical scroll recording view to see full camera. At no point may top and bottom edge of camera be seen. When reviewing recordings this is especially problematic since playback controls are at bottom of camera. it is not possible to control camera when trying to see event occuring at top of camera recording.

[NickM-27]

3287 was for resize events window. I think @asantaga is having same issue as me where you must vertical scroll recording view to see full camera. At no point may top and bottom edge of camera be seen. When reviewing recordings this is especially problematic since playback controls are at bottom of camera. it is not possible to control camera when trying to see event occuring at top of camera recording.

it mentions all views in the description. Either way it does need to be addressed, likely along with other recordings view UI changes.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[asantaga]

This is still an issue, adding comment so not to mark this as stale