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 setup Frigate v14 in privileged container on Raspberry Pi CM4 module and connected Tapo C120 camera as tapo source. Frigate automatically choose MSE/WebRTC streams which are provided by go2rtc v1.9.2.
If MSE stream is chosen then live view aspect ratio is different than original camera stream. Camera has stream aspect ratio 16:9 but go2rt v1.9.2 provide MSE stream in aspect ratio 4:3.
If WebRTC stream is chosen then live aspect ratio is the same as the original camera stream 16:9.
I tested standalone go2rtc v1.9.7 with the same config of the same camera and results are the same (MSE 4:3, WebRTC 16:9).
Is it possible to setup correct aspect ratio in MSE stream ? Is go2rtc doing something with original stream when providing MSE stream?
The text was updated successfully, but these errors were encountered:
The camera is probably wrongly sending this information about the ratio. It's a fairly common situation.
Unfortunately I don't have any cameras with these problems to fix.
You can try to use ffmpeg source.
I setup Frigate v14 in privileged container on Raspberry Pi CM4 module and connected Tapo C120 camera as tapo source. Frigate automatically choose MSE/WebRTC streams which are provided by go2rtc v1.9.2.
If MSE stream is chosen then live view aspect ratio is different than original camera stream. Camera has stream aspect ratio 16:9 but go2rt v1.9.2 provide MSE stream in aspect ratio 4:3.
If WebRTC stream is chosen then live aspect ratio is the same as the original camera stream 16:9.
I tested standalone go2rtc v1.9.7 with the same config of the same camera and results are the same (MSE 4:3, WebRTC 16:9).
Is it possible to setup correct aspect ratio in MSE stream ?
Is go2rtc doing something with original stream when providing MSE stream?
The text was updated successfully, but these errors were encountered: