Support listing and exporting of recorded segments#432
Support listing and exporting of recorded segments#432jflevesque-genetec wants to merge 55 commits intodevelopmentfrom
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…e-getstate Remove GetExportRecordedSegmentsState
Include optional alias when exporting segments
|
@jflevesque-genetec @HansBusch |
|
If we're talking about span duration, and not segment duration, the only visible effect would be the We're willing to add a clarification if needed, but I'm just not sure what it should be in this case. |
kieran242
left a comment
kieran242
left a comment
There was a problem hiding this comment.
@jflevesque-genetec it was some time since I reviewed this PR and I have read all the contributions again and the full text and WSDL updates and I am happy to approve. I am aware this is in the Prototyping stage and this could change with Minor update.
Approving for now.
This comment was marked as resolved.
This comment was marked as resolved.
| The figure <xref linkend="_refSegmentExportStabilityExample" /> illustrates how a global real time clock timestamp (that doesn't reset on device reboot | ||
| or resync on NTP) could be segmented in time ranges for the target segment duration with a modulus operation. Then each boundary of these ranges are | ||
| adjusted to match the time of the next keyframe. The result is the list of segment boundaries that overlap with the original time range of the query. | ||
| Care should be taken not to return the most recent segment if it is incomplete (when more frames may be appended to it later, i.e.: it overlaps with the current time). |
There was a problem hiding this comment.
@jflevesque-genetec ,
Would be nice to clarify, the first segment case also. Even for the first segment, is it expected to find the next following Key Frame ? In this case there is a chance that some short initial duration might be missing.
There was a problem hiding this comment.
Added The results shall include segments that cover the requested time range entirely, even if they start before or end after the requested time range.
|
Rescheduling for 26.06 , since @jmelancongen confirmed that prototyping cannot be done in time for 25.12 |
8 participants
Add new APIs in the Search and Recording specification to be able to list and export recorded segments towards a cloud storage.