Categories
Knowledge Support Support exacqVision Server

Incorrect Timestamps

Issue:

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.

The new override is #timestamp=trusted

Version Fixed:

exacqVision Server 20.09.8

Related Link:

DVR ticket ​#d21835

Categories
Knowledge Support Support Categories Products exacqVision Integrations

Camera Time Stamp Off by Years

Some cameras, particularly AXIS and Sony models, display an OSD date with an incorrect year. The time and date of the camera might be set to GMT and the Windows time is correct on the server, yet the OSD on the screen shows something like March 2, 2001.

<br>

This is usually a result of European Date Formatting (dd/mm/yy). Set the camera to USA date format (mm/dd/yy) to resolve the issue.

<br>

Camera-Time-Stamp-Off-by-Years.pdf