When you first identified the need for an rtsp proxy, I thought it was brilliant and was fully onboard with the idea. You've made an incredible contribution to the community, and I apologize if I've taken any wind out of your sails. I almost deleted my comment from yesterday because it's deeply unfair to you who has put countless hours into this release and addressed nearly all of my concerns over time. The RTSP restream for the HA integration also works with just an exposed rtsp port. The only thing that needs internet access AFAIK is webrtc and that is so that it can access the ICE server. Not really sure what you are referring to? the frigate MSE live view and internal rtsp restream work without go2rtc having any exposed ports or having any access to the internet. had some stream issues but the watchdog immediately restarts when an issue occurs. Users with lower quality cameras from wyze, reolink, etc. have had no stability issues reported in the last betas or RC releases. For the most part go2rtc has been stable for users, there are some that it was not stable for which led to the necessity for a watchdog to be implemented but users running cameras with high quality streams like dahua / annke / etc. Appreciate the feedback, we had a long beta phase with thousands of downloads on each release.
0 Comments
Leave a Reply. |