The alarms list is empty if the start and end time are within a window with continuous recording

We have 2018 R2 XProtect Professional+ server, and we are using protocol integration to integrate our API with Milestone. We are using it to check for video availability.

Even though for extended periods the Image Server returns valid alarms list, in the case when start and end time are within one of the returned alarms, there is no alarm returned although it is clearly within a recorded video period.

Should I be using a center time instead, i.e. Get Max N Recorded Sequences around a Point in Time?

Thank you very much for your assistance.

The Image Server protocol was defined before XProtect had the concept of alarms, as a matter of fact the alarms on the Image Server protocol are motion detection “sequences”. You might be aware of this, but this also means that if there is continues recording with no motion detection there is no alarms.

Maybe the method you mention using “center time” will work for you instead.

Note that on the recorder command service protocol there are other forms of sequences, but these sequences data also might have the information that there is only one huge sequence spanning from start to end.

Well actually if we start the recording manually and stop it, the resulting video record would go into alarms list even though there was no motion detection.

What we have recently discovered is that “alarms” method does not output an alarm if it completely covers the interval which was requested, even though the documentation states just the opposite. And this is also the case for what is asked in this thread. See https://developer.milestonesys.com/s/question/0D53X00006ihQtaSAE/alarms-sdk-request-incorrectly-returns-an-empty-result-for-an-overlapping-interval for details.

Thank you very much, German

Thank you very much Bo.

Happy New Year!

Bo,

The center time worked for me.

Thank you very much for your assistance.