Event integration inquiry

Hello, thanks for your support. We would like to display more details for events generated from Hanwha Vision cameras. Currently, the SmartClient event monitor tab only shows the name of an event (such as ‘Object detection’), but we want to display the specific class, such as people/face/vehicle, and similarly for other types of events.

We heard that on the Hanwha Vision side, we can make this possible using the MIP SDK. Can you provide a sample project for reference?

If we succeed to show details for events from Hanwha Vision cameras using MIP sdk, how would the events already saved and shown in the event monitor panel be handled? I think they should be deleted; otherwise, a single event will be saved duplicated in both its original form (showing only the event name) and a detailed display form.

Milestone XProtect and the MIP SDK offer events that can be very rich on data; Analytics Events, if we are comparing to camera events you can include the data.

Let me start by linking some documentation and samples.

https://doc.developer.milestonesys.com/html/index.html?base=gettingstarted/intro_events.html&tree=tree_4.html

https://doc.developer.milestonesys.com/html/index.html?base=samples/protocolsamples/triggeranalyticseventxml/readme.html&tree=tree_4.html

Hello Bo,

If an object detection event from a camera is processed by Milestone XProtect VMS Device Pack, processing here means the event data is saved in the form of a camera event. At the same time, if I create the analytics event as you suggested to add additional information for the same object detection event, is it unavoidable that a single event from a camera will be saved as two different events?

If so, is it possible to change the way of the saved form at the stage of Device Pack? Or do you have a common use case for this case?

The Device Pack and regular camera drivers does not offer camera events that carry extra data. I guess this is by design, perhaps it is due to a very old design or there are other good reasons for the design, I cannot say.

If a camera event is offered by the camera, and the user configures it, you cannot through code delete it again, “recorded” events cannot be removed and will only be removed once their retention (configurable) period is over. Same behavior goes for Analytics Events.

I have an idea that having two events, a camera event and an analytics event, will not be an issue. I do not think it will cause confusion and each event can have its use in different scenarios.