The Exacq Mobile 3 application does not show the OSD of cameras while the device is in a different time zone.
Product
Exacq Mobile 3 application for both iPhone and Android.
Expected Results
We should be able to account for when the Device is in a different time zone than the recorder while using the Exacq Mobile 3 application to reflect the camera times, in case searching video is required.
Actual Results
The Exacq Mobile 3 application will show the cameras OSD timestamps as the time of the recorder.
Solution
If the need to search the time of an event is needed on the Exacq Mobile 3 application please keep in mind the difference between time zones.
The Onvif plugin has always time-stamped frames as they arrive at the server. With issues of network latency and camera streaming problems, this could cause video to look jittery. An option was added to provide time-stamping with camera time. Adding #timestamp=camera in the hostname would use the presentation time provided by the camera. The default will still time-stamp frames at the server.
exacqVision Server may cause incorrect frame timestamps for some cameras that are using RtspPI or AxisPI plugins.
Workaround:
None
Version Affected
20.06.4 and earlier
Resolution:
A new Override is available for RtspPI and AxisPI
The Override will prevent the server from auto adjusting timestamps and will trust verbatim what comes from camera.
The server generates and caches a timestamp offset when starting a stream, which is applied to every frame as a time correction. Normally, the camera then continues to perform NTP sync operations with the server for timestamp accuracy.
However, with a busy network, some NTP packets may fail to arrive at the camera, and in some cases the camera’s time may drift beyond a 60 second threshold, which causes server to incorrectly adjust and freeze its cached offset, which will be applied to every frame regardless whether the camera successfully NTP syncs with server.
Most noticeable in multi-sensor cameras and encoders.
If you change the time zone on a system running Enterprise System Manager (ESM), the timestamp of ESM events might not match the time that the events actually occurred.
<br>
When ESM services are started, ESM reads the timezone configured in the operating system. If the system’s time zone is then changed, you must restart the ESM services (ESMImporter, ESMWebservice, ESMDatarolloff, and ESMSendemail) to implement the change in ESM, or restart the system.
As with all third-party software not on the Product Integration section, the user assumes the risk of software incompatibility with the exacqVision software suite.
To permit antivirus software to work with exacqVision software, the following file extensions need to be exempted from scans:
.PS
.PSI
NOTE: As an alternative, you could also exclude the data drive you are using to store video.
It is also be necessary to exempt certain files if they are targeted by scans. See KB 20594.
If your antivirus protection suite has a firewall, the following must also be exempted:
exacqVision Client exacqVision Server exacqVision Web Service <br>
Additional Notes
Most systems require a restart after changing the configuration. Within some antivirus suites, settings might revert after the restart (this activity has been specifically observed with the Avast antivirus suite in the past). It is recommended that you double-check your settings after the restart to verify that your exclusions and exceptions have been saved. <br>
On an exacqVision Client workstation machine, the only exception needed is for the exacqVision Client software. <br>
Some suites, such as Kaspersky Endpoint 10, also install components on the NIC driver to monitor network traffic. It is recommended that these be disabled if you see a performance decrease or inability to connect to cameras after this component has been enabled. <br>
Best practice is not to use multiple antivirus applications on the same system as these can often conflict with each other. <br>
Timestamp issues
If you are using antivirus software and you see an incorrect timestamp in live video windows or you cannot successfully search for video in a specified time and date range, the antivirus software might be preventing the exacqVision Server from correctly identifying its own IP address. This has been known to occur when using Trend Micro OfficeScan and other antivirus software.
To resolve this issue, you must enter the IP address of the exacqVision server in the IP Camera Time Server field on the System page’s Date/Time tab.
All exacqVision video is timestamped in UTC, so there is no ambiguity as to the absolute time when the video was recorded. When exporting video, the time zone of the system on which the video was recorded is not stored. Starting with exacqVision version 3.4, two features were added to make this more transparent to the operators:
<br>
In exacqVision Client, an onscreen display shows the server time zone (in offset from UTC) along with the timestamp. If this option is not configured for the camera, the timestamp is shown in the client’s local time.
In ePlayer, the timestamp of the recorded video is shown in the time zone of the local computer on which it is playing, but the time zone offset is shown. Thus, if you watch a video on a computer set to EDT, you might see 2:00 (GMT-4:00), whereas the same video viewed on a computer in CDT would show 1:00 (GMT-5:00). The UTC timestamp is the same in both cases. Knowledge of the physical location of the recording server, which is clearly needed for evidentiary purposes, can correlate the local time of the machine on which the video is being watched to the local time of the server on which it was recorded.
