- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Posted on 10/31/21 at 10:28 pm to CarRamrod
There are a lot of parts to a camera system. Obviously the video streams, but also the ONVIF event stream that the cameras put out, possibly secondary motion or object detection, then of course the video streams must be recorded and the events indexed to the right position in the video files (I haven't figured this part out yet), then we have timeline generation and playback and all the user facing stuff and notifications and on and on. I just want to break all of it down into standalone components that can be stacked together as needed and across multiple systems. For example I want to build a Pi camera that handles object detection and storage onboard, and also re-streams the video and ONVIF events for a second system to process. I'd also like a Pi-based cluster NVR system that can grow with your needs rather than the typical big jumps from an 8 to 16 to 32 camera NVR. And if I'm going that far just make the cameras themselves the NVR cluster.
Anyway, I'm going to use Go for this project and I've found a couple libraries for ONVIF and RTSP already. It's pretty easy to scan the network for ONVIF cameras, probe each camera for its RTSP stream url, and start recording video. So I already have a really basic NVR. Next I will look into subscribing to the ONVIF event stream and figure out how to store them and generate a timeline. Maybe I will post the code after that.
Popular
Back to top
Follow TigerDroppings for LSU Football News