You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been running an older version of unifi-cam-proxy since last fall. I had edited the video feed resolution and bitrates to represent the real resolution of the feeds, mainly the primary. My 4 non-unifi cameras are 4K cameras. I'm sure it is just cosmetic, but it does cause Protect to reflect them as 4K feeds and shows the right resolution in the pulldown picker. I'm sure I could go in and edit the container and change it to what I like but was thinking of a command line parameter for this.
Something like --resolution 3840,2160 1280,720 740,480 --bitrate 10240000,2048000,256000
I am not sure if Protect uses this for the "space estimation" when doing the calculations or not. I noticed in a recent build you updated stream resolutions some in base.py.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been running an older version of unifi-cam-proxy since last fall. I had edited the video feed resolution and bitrates to represent the real resolution of the feeds, mainly the primary. My 4 non-unifi cameras are 4K cameras. I'm sure it is just cosmetic, but it does cause Protect to reflect them as 4K feeds and shows the right resolution in the pulldown picker. I'm sure I could go in and edit the container and change it to what I like but was thinking of a command line parameter for this.
Something like --resolution 3840,2160 1280,720 740,480 --bitrate 10240000,2048000,256000
I am not sure if Protect uses this for the "space estimation" when doing the calculations or not. I noticed in a recent build you updated stream resolutions some in base.py.
Beta Was this translation helpful? Give feedback.
All reactions