I was using Deepstack in cpu mode for a few months but eventually got tired of the cpu fan kicking on every time a car drove by, so I simply went to the main menu AI tab and unchecked the "use AI server on IP/port" checkbox. This got rid of the fan noise. However now I seem to see dropped frames...
The General tab of all of these cameras display a substream.
Hikvision:
Main Stream 3.1MP 12.5/0.83 fps, 495 kB/s
Sub Stream 0.3MP 12.5/0.83 fps 54 kB/s
Dahua:
Main Stream 2.1 MP 20.04/1.0 fps 229 kB/s
Sub Stream 0.3 MP 20.01/1.0 fps 28.7 kB/s
I admit that I don't know why the Hik is showing...
I am trying to get accustomed to using sub-streams. Previously I had avoided using them. Why does it seem that my Dahua cameras look the same on the live-view after enabling the 640x480 substream but the Hikvision looks different? Clearly 640x480 is a 4:3 proportion, but it seems that I only see...
So there are all these specific objects like "person" and "truck" but no "generic real object" that would differentiate between something real and the false triggers due to headlights, wind and shadows?
Or a tree falls on my car? Or a motorcycle drives across my lawn? Or a bouncy house or porta-potty blows by? Or an alien spacecraft?
What if I just want to ignore wind and shadows but not everything else?
Where do I find the DS tutorial or setup? I think I have it running but with nothing to do. I mostly use triggered cameras and just hope to reduce the number of false triggers due to wind or shadows.
As I understand it on Win10-Pro you use the Group Policy Editor to prevent updates, and on WIn10-Home you use the Registry Editor. The exact procedure can be found elsewhere. What I don't understand is how 21H1 differs from 22H2.
I just replaced a 10m ethernet cable because it was clearly not good enough -- as shown by the Speedtest.net results on the laptop it was connected to.
Description of situation:
Bi is running and recording nine cameras on a dual-NIC with two subnets 192.168.0.1 and 192.168.2.1
The BI pc itself is at IP 192.168.16.10 on the motherboard port.
Nettime successfully updates and shows status = good.
On the Hikvision camera at 192.168.2.150 (static...
Nettime was successfully updating before I added the Windows Defender rule so don't know how it was able to do that. I still think the cameras are being blocked from getting NTP. Now I've added inbound and outbound "Custom" rules for UDP port 123 on the two subnet IP's. Maybe that will do it.
In Win10-Pro when I open up the "Windows Defender Firewall with Advanced Security" popup I'm not sure what the best approach is. I don't see any rule for Nettime. I guess I will try the "New Rule Wizard" and see what happens.
Oh, now I remember. I had one camera die last summer. The connector got wet and fried the camera -- or at least I have not been able to get it working again even with a new connector patched on.
I just got the SFF version from Amazon a few days ago. I guess it was a return. They labeled it "Renewed." I'm pretty sure mine doesn't have wifi. $250.