Default date overlays not working
Re: Default date overlays not working
When direct to disk first was introduced the time data was not included in the bvr file. The only way to get the overlay then was to re-encode the clip into a different format. Now since version 5.2.8 the time is in the bvr metadata. This gives you more control of being able to turn off the time stamp in case there is subject matter that was hidden behind the time stamp. It's really a personal choice of how you want to do it.
Re: Default date overlays not working
Oh right, now that you’ve typed this I now remember but had forgotten so thanks.Tinman wrote:When direct to disk first was introduced the time data was not included in the bvr file. The only way to get the overlay then was to re-encode the clip into a different format. Now since version 5.2.8 the time is in the bvr metadata. This gives you more control of being able to turn off the time stamp in case there is subject matter that was hidden behind the time stamp. It's really a personal choice of how you want to do it.
Re: Default date overlays not working
I have them set up in BI5 to ensure that they are all synchronised.
Originally, having cameras from various different manufacturers meant that they wouldn't all play with the same NTP server. Drift. Then I put the cameras on a separate LAN with no internet connectivity, so tried a NTP server on the BI5 pc. That didn't work well either.
Since timing between cameras becomes important when the boys in blue are checking the feeds, the obvious answer was to let BI5 add the time and date. I'm sure there was an update where it stated there was no longer much load doing it this way - and when I originally swapped it to allow BI5 to do it, the cpu load didn't change. I don't want to disable it to check
If however you are using (for example) only Dahua cameras, then the camera clock may be a good option - but in my case I would still have to run a local NTP server.
Originally, having cameras from various different manufacturers meant that they wouldn't all play with the same NTP server. Drift. Then I put the cameras on a separate LAN with no internet connectivity, so tried a NTP server on the BI5 pc. That didn't work well either.
Since timing between cameras becomes important when the boys in blue are checking the feeds, the obvious answer was to let BI5 add the time and date. I'm sure there was an update where it stated there was no longer much load doing it this way - and when I originally swapped it to allow BI5 to do it, the cpu load didn't change. I don't want to disable it to check
If however you are using (for example) only Dahua cameras, then the camera clock may be a good option - but in my case I would still have to run a local NTP server.
Forum Moderator.
Problem ? Ask and we will try to assist, but please check the Help file.
Problem ? Ask and we will try to assist, but please check the Help file.
Re: Default date overlays not working
The internal camera clock on all of my Dahua cameras drifts by what I would regard as a shocking amount especially given that it is a security cam, can’t remember exactly by how much but by the end of the week they all be a few minutes minus.
I’ve got the NTP Time Service app running on my BI PC and have all the cams set to sync using NTP every 30 mins, I think None of my cams have internet access as I use the dual NIC config to keep them off the internet.
I’ve got the NTP Time Service app running on my BI PC and have all the cams set to sync using NTP every 30 mins, I think None of my cams have internet access as I use the dual NIC config to keep them off the internet.