Hmmm... That's an interesting solution to the time synchronization problem after neutering the cameras' ability to reach the web.The general opinion around IPCT seems to be that using the camera date/time stamp is the way to go. This reduces CPU utilization for the BI server, noticeably. To do this it is best to set up a local time server on the BI server that can be accessed by the cameras without them needing internet access. I'm using "Nettime" and it works quite well without loading the CPU like using the BI overlay does. It does require opening port 123 on the camera subnet and allowing port 123 through Windoohs firewall and/or your security software though.
I do this as well. I also use BI Tools to place temp and humidity on the video, more for info if someone remote is watching. Utilization is not a problem for me with only four cameras right now.I use blue iris exclusively. For a couple of reasons. First most of the clocks that come with cameras require some type of internet access to synchronize, and I have all of my cameras on a subnet that has no internet access to prevent them from phoning home.
Also, most of the date stamps from the camera toggle between white and black depending on the contrast and brightness of the subject behind the clock. I find that to be quite distracting, bordering on unreadable.
And, a few seconds difference in the display timestamp between cameras may not seem like much, but when you're dealing with reviewing split-second things like lightning strikes or sounds, it's nice to have everything precisely matched.
Finally, having a uniform font and a semi transparent background behind the timestamp looks quite a bit more professional and consistent than varying fonts and sizes that you get between different cameras.
I can't seem to get this to work. I followed the directions in that link you sent, the Windows Time service is running on my BI server, it is enabled, I allow both incoming and outgoing UDP port 123 in the firewall, and I set the NTP settings of my camera at the IP address of the BI server, yet it never updates the time. In my case my cameras are all 1 hour behind my server and network time. I also tried pointing the camera at my Windows Domain Controller which also has the Windows Time server running on it, but still never updates. Any ideas?You don't need third party NTP software; Windows Time service has a server built in, you just need to enable it and then open the firewall port for NTP.
At times I was pointing the cameras at my Cisco switches to sync time, now I have them syncing from the BI box, which syncs to a DC, which syncs to an NTP pool.
Anyway, as for the overlays, have the camera do that work.
I think that was the last remaining issue, thanks. Now I just have 50 more cameras to log into and tweak time settings on...Check the daylight savings time settings for the cameras.
Notwithstanding the DST settings, are they successfully picking up NTP from your server?I think that was the last remaining issue, thanks. Now I just have 50 more cameras to log into and tweak time settings on...
Yes everything is working fine now. I just enabled the Windows Time NTP server on my BI server, which is Window 10 and on my Windows domain.Notwithstanding the DST settings, are they successfully picking up NTP from your server?
I am also in the camp that lets BI apply the timestamp. As I understand direct-to-disk and the BVR format, there isn't a re-encoding being done anymore.I remember the argument about a video holding up in court (or not) depending on if the cam or BI added it. I also thought that with direct-to-disc there isn't much re-encoding if you just add the date. But I might be wrong about hat. I will look into the Windows integrated NTP again as I prefer not having another program/service running.