-
Notifications
You must be signed in to change notification settings - Fork 399
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
RTSP 4K to WebRTC Not Working #1391
Comments
`15:36:24.325 TRC [webrtc] remote candidate="candidate:3624146751 1 udp 1685921535 1.2.3.4 59721 typ srflx raddr 192.168.15.121 rport 59721 generation 0 ufrag 4F0x network-id 2" v=0 15:36:24.402 TRC [rtsp] client response: 15:36:24.402 TRC [streams] check prod=0 media=video, recvonly, H265 15:36:24.407 TRC [rtsp] client response: 15:36:24.407 DBG [streams] start producer url=rtsp://admin:[email protected]:554/h265Preview_01_main 15:36:24.455 TRC [rtsp] client response: |
Can go2rtc route an RTSP H265 stream to WebRTC? This camera's main stream can't product H264 at the full resolution, which I need for the FoV |
I have a bunch of Reolink cameras that are 1440p and a couple of new ones that are 4K.
The 1440p cameras I have no problem with. I use the addon in Home Assistant, and the WebRTC lovelace card. I'm able to define the sources in the .yaml config file and view the streams via the lovelace card in WebRTC.
The 4K cameras are where I have a problem. If I drop the resolution to 1440p, they come through in WebRTC no problem. However, when I bump the streams up to 4K the streams will only display in MSE, not WebRTC.
For one of the cameras the 1440p stream is fine, however with the RLC-843A if you drop the resolution instead of transcoding it just digitally crops the image! I need the FoV on this camera so cropping / dropping the resolution isn't going to work.
The text was updated successfully, but these errors were encountered: