You get what you pay for. 1/3" sensor is great for 720P, but a horrible choice for 4MP or 4K.
Yep, isolate your cameras from the internet because EVERY manufacturer has vulnerabilities, even top NDAA compliant AXIS had a breach a couple months back!
Keep in mind if you buy better cameras that have built in AI, then DeepStack isn't really necessary unless you specifically want to be notified of deer. But if only vehicle and people, the AI in the cameras are spot on!
It has come to my attention that certain Dahua cameras come with built in AI that distinguishes between human & cars. I was unaware of this. Well, always saw the AI word used in the reviews but never really thought about it because I thought it was a Dahua NVR integration only. I am currently...
ipcamtalk.com
Also keep in mind the focal length is more important than MP. Check out this post I created:
At the urging of several folks here, I created a thread to show the importance of focal length and how focal length can be more important than megapixels (MP). I mentioned some of this in the post regarding The Hookup’s latest video demonstrating different cameras, including one sold from a...
ipcamtalk.com
This will explain H264 versus H265 a little better.
H265 in theory provides more storage as it compresses differently, but part of that compression means it macro blocks big areas of the image that it thinks isn't moving. However, it also takes more processing power of the already small CPU in the camera and that can be problematic if someone is maxing out the camera and then it stutters.
In theory it is supposed to need 30% less storage than H264, but most of us have found it isn't that much. Mine was less than few minutes per day. And to my eye and others that I showed clips to and just said do you like video 1 or video 2 better, everyone thought the H264 provided a better image.
The left image is H264, so all the blocks are the same size corresponding to the resolution of the camera. H265 takes areas that it doesn't think has motion and makes them into bigger blocks and in doing so lessens the resolution yet increases the CPU demand to develop these larger blocks.
In theory H265 is supposed to need half the bitrate because of the macroblocking. But if there is a lot of motion in the image, then it becomes a pixelated mess. The only way to get around that is a higher bitrate. But if you need to run the same bitrate for H265 as you do H264, then the storage savings is zero. Storage is computed based on multiplying bitrate, FPS, and resolution.
In my testing I have one camera that sees a parked car in front of my house. H265 sees that the car isn't moving, so it macroblocks the whole car and surrounding area. Then the car owner walked up to the car and got in and the motion is missed because the macroblock being so large. Or if it catches it, because the bitrate is low, it is a pixelated mess during the critical capture point and by the time H265 adjusts to there is now motion, the ideal capture is missed.
In my case, the car is clear and defined in H264, but is blurry and soft edges in H265.
Digital zooming is never really good, but you stand a better chance with H264 than a large macroblocked H265. I can digital zoom on my overview camera and kinda make out the address number of the house across the street with H264, but not a chance with H265.
H265 is one of those theory things that sounds good, but reality use is much different.
As always, YMMV. But do not use Codec with BI or you may have trouble, so just stick with H264 without the H or B or + after.
