Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live view aspect ratio different than original camera stream #1466

Open
rici44 opened this issue Nov 18, 2024 · 6 comments
Open

Live view aspect ratio different than original camera stream #1466

rici44 opened this issue Nov 18, 2024 · 6 comments
Labels
question Further information is requested

Comments

@rici44
Copy link

rici44 commented Nov 18, 2024

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?

@AlexxIT AlexxIT added the question Further information is requested label Nov 18, 2024
@AlexxIT
Copy link
Owner

AlexxIT commented Nov 18, 2024

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.

@rici44
Copy link
Author

rici44 commented Nov 18, 2024

The camera is probably wrongly sending this information about the ratio. It's a fairly common situation.

Why MSE and WebRTC streams are both OK in 16:9 when using Firefox browser?

Unfortunately I don't have any cameras with these problems to fix.

What would help to solve this exact camera?

You can try to use ffmpeg source

Won't it get more resources from CM4?

@AlexxIT
Copy link
Owner

AlexxIT commented Nov 19, 2024

  • Different decoder implementations
  • Probably FFmpeg
  • Minor

@dgibbs64
Copy link

dgibbs64 commented Dec 16, 2024

I have the same issue. I just moved from rtsp stream on my tapo camera to use tapo:// protocol since tp-link released a fix for the cloud password issue JurajNyiri/HomeAssistant-Tapo-Control#551 . The recording is 16:9, but the live view is 4:3. ALso when I click to enable 2-way audio the steam goes back to 16:9. Also noticed that this is not an issue in firefox but is in Edge (Chrome)

I am using a C320WS

@AlexxIT
Copy link
Owner

AlexxIT commented Dec 16, 2024

Nothing have changed. 16:9 for WebRTC and 4:3 for MSE. Some strange video metadata from TP-Link developers.

@dgibbs64
Copy link

Yeah, im getting the impression that just using rtsp might be the best option. I think 2-way audio might be the only thing I lose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants