Normal
Suggested layoutAssuming the cameras actually throw up a trigger on it's own motion detect (detecting motion on the video stream itself is 'nontrivial' in software), I'd say that is feasible. Esp multiple OSDs. For recording: I might suggest this be implemented with a 'tour' of the inputs -- saving a few frames from each camera one after the other, -- you really don't need 30 FPS or 25 FPS for security cameras, just 3 or 4 FPS per camera -- and that'd be easily 'muxed' into a single file which in turn could be compressed.Myself, I plan to hook up a 'child cam' in my kid's room when he/she/it is born (password protected of course) to allow the remote grandparent/aunts/uncles a chance to see him/her. This would need to be decently compressed -- I don't have the bandwidth at home to actually stream a lot of data out.
Suggested layout
Assuming the cameras actually throw up a trigger on it's own motion detect (detecting motion on the video stream itself is 'nontrivial' in software), I'd say that is feasible. Esp multiple OSDs.
For recording: I might suggest this be implemented with a 'tour' of the inputs -- saving a few frames from each camera one after the other, -- you really don't need 30 FPS or 25 FPS for security cameras, just 3 or 4 FPS per camera -- and that'd be easily 'muxed' into a single file which in turn could be compressed.
Myself, I plan to hook up a 'child cam' in my kid's room when he/she/it is born (password protected of course) to allow the remote grandparent/aunts/uncles a chance to see him/her. This would need to be decently compressed -- I don't have the bandwidth at home to actually stream a lot of data out.