"Camera Recording" rule inherit camera from generic event metadata
Answered
The client gives the user the ability to create a rule e.g. "when 'Generic Event' do 'Camera Recording'". Creating such a rule requires the user to manually select one-to-many cameras for which video should be recorded.
However, the GET /api/createEvent API allows the user to explicitly pass in one-to-many camera Ids (or "cameraRefs") in the form of "metadata".
When creating a "Do Camera Recording" rule from a generic event, we would like the optional ability to inherit the cameras at which video should be recorded from the list of "cameraRefs" passed in via the generic event. This way, we could create one blanket rule to do recording at whichever camera the generic event is associated to.
-
Austin Smith
Thanks for this, it sounds like a great improvement we can add.
We are currently working on a new rules engine, which we hope will be included in the product after the next release. New rules engine will allow "dynamic parameters".
Also -- can you describe the full scenario, why do you need multiple cameras to start recording? What is the event in the real world that triggers that? -
Hi Tagir, admittedly, our use case may be somewhat specific. We have developed an integration between the VMS platform and some 3rd party systems. 3rd party systems output events, we receive them, and then send those events as generic events & bookmarks to VMS for specific cameras, depending on configuration of the particular event. We simply want to ensure there is always recorded video for the events we are sending.
-
Yea, thx for the clarification!
for specific cameras, depending on configuration of the particular event
I was just trying to figure out why would someone want to record multiple cameras for one event. But I can assume that it is several cameras pointed in the same area. And when some event appears from that area, we want it to be recorded from different angles.
-
Correct. Though that is all configurable on our side. There may be multiple cameras for a given event, or there may be just one. Either way, we will send the "generic event" with the required "cameraRefs" (could be one-to-many), and we simply want to be able to create a rule that says "record video" for whichever camera or cameras are passed in with the generic event.
Please sign in to leave a comment.
Comments
4 comments