I requested “2017/3/16 00:00:00.500” with “TimeOrAfter”.
In spite of “2017/3/16 00:00:00.642” was recorded, It responsed “2017/3/15 23:59:59.882”.
I wanted “2017/3/16 00:00:00.642”.
Version :Xprotect 2016 R2(10.1a)
frame rate : 2FPS.
another camera is also happened.
“DbEnd” work right.
“Time” and “TimeAfter” is not try.
-------
[Request]
<?xml version="1.0" encoding="utf-8"?>cfe126ed-f6df-465f-909b-7afc157c9a8eRequestGetRecordingTime
-> 2017/3/16 00:00:00.500
[Response]
<?xml version="1.0" encoding="utf-8"?>cfe126ed-f6df-465f-909b-7afc157c9a8eResponseGetRecordingTimeOK
->2017/3/15 23:59:59.882
it was recorded data below.
1 2017/03/15 23:59:58.882
2 2017/03/15 23:59:59.382
3 2017/03/15 23:59:59.882
4 2017/03/16 00:00:00.642
5 2017/03/16 00:00:01.402
6 2017/03/16 00:00:01.902
7 2017/03/16 00:00:02.402
maybe 3~4 data was lost.
Please try using the newest release of the Mobile Server, does it make a difference?
What version is the XProtect VMS (model, year, revision)?
>Please try using the newest release of the Mobile Server, does it make a difference?
Im not try.
Is there compatibility between newest release of the Mobile Server and older recording Server?
I was curious, but you aren’t telling; what is the XProtect (Corporate/Expert/Enterprise/Professional/Express/Essential)?
Anyhow it might be less important. - The newest version of the Mobile Server is compatible with the XProtect Xxx 2016R2.
Hello,
I response your question .
It is Milestone Xprotect Professional 2016 R2.
>The newest version of the Mobile Server is compatible with the XProtect Xxx 2016R2.
thanks your nice infomation.
I investigated the behavior of “SeekType” here.
- “Time” returns the specified time or near the specified time. However, the later time is closer to the specified time but tends to return the previous time.
- “TimeOrAfter” returns time after the specified time if it does not match with “Time”. Therefore, but it may return the time in front.
- “TimeAfter” returns the time after the specified time.
- “TimeOrBefore” returns the specified time, and if there is no specified time, it returns the previous time.
- “TimeBefore” returns the time before the specified time, but it may not return the previous time if it is too close to the specified time (less than 100 ms).
Is that right behaviors?
And In this case I will try to solve it using “TimeAfter” instead of “TimeOrAfter”.
Your description should be accurate..
Do you still see the unexpected reply that you first documented now that you are using Mobile Server 2017R1?
I installed Mobile Server 2017 R1.
But, Connect command to work in the Mobile Server 2016 R2 dont work in the Mobile Server 2017 R1.
So I could not tryed “TimeOrAfter” .
it below is connect command.
<?xml version="1.0" encoding="utf-8"?>RequestConnect
Does the newly installed Mobile Server work at all? Does it work when using the web client? I suspect that something went wrong when you upgraded.
Mobile Server 2017 R1 work right.
andalso it work when using web client.
I saw sample source “DemoApp” differ 2016 R2 and 2017 R1.
And It found enabled to connect and login after changed program.
However, even when sending the command at 2017r1, the result was the same as 2016r2, and it could not be resolved.
Milestone Development will investigate deeper. A theory is that you might get the time of the key frame (start of the GOP) for a camera streaming H.264 instead of the time of the actual frame. This will be investigated.
Was there any of SeekTypes you might be able to use as a workaround?
Thank you for your investigation.
Yes. We plan to avoid this event by using the specified time change and “TimeAfter”.
