Clarification on generateEventMetadataPacket Usage and VMS Rule Integration

I'm currently working on a plugin for Hanwha Wave and need some clarity regarding the generateEventMetadataPacket function:

Invocation Context:
- Where in the plugin lifecycle or metadata pipeline is generateEventMetadataPacket typically called?
- Is it intended to be triggered during detection, post-processing, or rule evaluation?
Function Purpose:
- What exactly does generateEventMetadataPacket construct?
- Does it encapsulate event metadata for VMS rule matching, or is it purely for logging/diagnostics?
Rule Action Binding:
- Can this function be used to emit metadata that triggers a rule action configured in the camera or VMS?
- If a rule is set up in the VMS (e.g., motion detection → send notification), will a packet generated via this function be recognized and processed accordingly?

Any guidance or examples showing how this function interacts with rule logic or event pipelines would be greatly appreciated.

If possible sample code is required to capture event action from VMS

This is my function definition

Ptr<IMetadataPacket> DeviceAgent::generateEventMetadataPacket()

{

// Generate event every kTrackFrameCount'th frame.

if (m_frameIndex % kTrackFrameCount != 0)

return nullptr;

// EventMetadataPacket contains arbitrary number of EventMetadata.

const auto eventMetadataPacket = makePtr<EventMetadataPacket>();

بحث

Clarification on generateEventMetadataPacket Usage and VMS Rule Integration

تعليقات

لم تجد ما تبحث عنه؟