deepch / RTSPtoWebRTC

RTSP to WebRTC use Pion WebRTC

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Swann NVR Cameras: "Codec Not Supported WebRTC ignore this track H265" Meaning?

darethehair opened this issue · comments

Hello! I am very new at trying to understand all the technology and terminology involved with RTSP/WebRTC/etc, but my goal is to capture and stream from our non-profit Swann 8580 NVR cameras to some Chrome browser tabs, so that we can ultimately Chromecast them to other HDMI devices -- without being connected to the NVR itself. Swann itself has mechanisms to view/control using remote browsers -- but it looks like the only ones that work this way only do so with Windows 'Internet Explorer' -- and we want to use ChromeOS with Chrome browser!

On experimentation with RTSPtoWebRTC, and using what I think are the correct RTSP stream addresses, I get the following diagnostics showing up:

thrift@penguin:~/RTSPtoWebRTC$ go run *.go
2022/10/26 15:28:34 Stream Try Connect demo1
2022/10/26 15:28:34 Server Start Awaiting Signal
[GIN] 2022/10/26 - 15:28:49 | 301 |      43.387µs |             ::1 | GET      "/"
[GIN] 2022/10/26 - 15:28:49 | 200 |     183.942µs |             ::1 | GET      "/stream/player/demo1"
[GIN] 2022/10/26 - 15:28:50 | 200 |  253.913253ms |             ::1 | GET      "/static/js/bootstrap.min.js"
[GIN] 2022/10/26 - 15:28:50 | 200 |   243.22065ms |             ::1 | GET      "/static/js/app.js?ver=2022-10-26%2015%3a28%3a49.835490671%20-0500%20CDT%20m%3d%2b15.109701536"
[GIN] 2022/10/26 - 15:28:50 | 200 |  248.613195ms |             ::1 | GET      "/static/js/adapter-latest.js"
[GIN] 2022/10/26 - 15:28:50 | 200 |   294.04285ms |             ::1 | GET      "/static/css/bootstrap.min.css"
[GIN] 2022/10/26 - 15:28:50 | 200 |  278.655306ms |             ::1 | GET      "/static/js/jquery-3.4.1.min.js"
2022/10/26 15:28:50 Codec Not Supported WebRTC ignore this track H265
[GIN] 2022/10/26 - 15:28:50 | 200 |     142.247µs |             ::1 | GET      "/stream/codec/demo1"
[GIN] 2022/10/26 - 15:28:50 | 200 |   110.59666ms |             ::1 | POST     "/stream/receiver/demo1"
2022/10/26 15:28:50 WritePacket WebRTC Codec Not Supported
[GIN] 2022/10/26 - 15:28:54 | 200 |     104.362µs |             ::1 | GET      "/stream/player/demo1"
[GIN] 2022/10/26 - 15:28:54 | 200 |     185.039µs |             ::1 | GET      "/static/js/app.js?ver=2022-10-26%2015%3a28%3a54.579286942%20-0500%20CDT%20m%3d%2b19.853497812"
2022/10/26 15:28:54 Codec Not Supported WebRTC ignore this track H265
...

Does this mean that our Swann NVR cameras are sending H265 video -- which neither WebRTC nor Chrome browser can handle? If so, any suggestions for my next steps in achieving our goals? Perhaps I could try RTSP stream '1' instead of '0' and get H264 instead of H265 (someone out there suggested this and not sure it even works that way).

Thanks!

UPDATE: Wow, talk about timing! Unless I have misunderstood, Google has just now added HEVC/H.265 support to Chrome browser! Not sure if this is both software + hardware support, or just hardware support:

https://www.neowin.net/news/chrome-107-is-landing-today-with-hevc-decoding-support-despite-pushback-from-mozilla/
https://chromestatus.com/feature/5186511939567616

Good news,Modify some of the code and Remove the restriction ,Give some time to test