The timestamp provided does not match with the image timestamp when we pull the images from the Milestone image server.

We want to generate videos for a given period of time. So, we intend to pull a series of images and concatenate them into a video. The problem I am facing are listed below.

  1. Suppose I am passing the time in GOTO sequence as 27 June 2023
    

01:03:58. The GOTO method response gives me the correct timestamp in millisecond. But the images shows the timestamp as 26 June 2023 22:04:00. (Attaching two images showing that the filename matches but the response and timestamp on image does not match. We just removed the header following this issue https://developer.milestonesys.com/s/question/0D53X00007W630GSAR/image-servers-goto-endpoint-always-returns-applicationxgenericbytedataoctetstream-even-though-im-specifying-alwaysstdjpegyesalwaysstdjpeg-multipartdatanomultipartdata-and-a-transacode-element-which-resizes-the-image

)

  1. Also, I generate the first image using GOTO method and rest images using Next method. Surprisingly the prev, current and next millisecond time are same throughout. But the corresponding images have different timestamps. (Let's say we want the image from 27 June 2023 01:03:58 for the next 2 minutes. The images have timestamp which are wrong but they are changing gradually. The current, prev and next timestamps in the responses are not changing, its same as the first response.)
    

Can you explain me the reason for these two issues I am facing?

The timestamps used in the Recording Server is always UTC. I wonder if the three hours is caused by this. Please double check the clock and the time zone setup.

Generally it is very much recommended that the servers running the XProtect services is synchronized on the clock and the camera devices too, ideally using NTP.

Let me know if this helps or you still see the same.