Plugin - some camera cannot support plugin's event
Answered
Hi,
We use Nx Witness V5.0.0.35745.
We developed a plugin which can send analytics event (name: FaceMe Event) and object to Nx Witness.
But we found that one camera "FaceMe XNZ-6320" cannot support the event in our plugin.
Please refer to the following snapshot:
We've enable our plugin in this camera's setting page.
However, in Event Rules, we cannot find our event (FaceMe Event) in Event Types options.
When we send event and object about this camera through plugin, Nx server can receive object successfully, but cannot receive event.
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::analytics::ObjectCoordinatesTranslator(0x232d92c2158): Translating bounding box coordinates, rotation angle: 0 degrees, original bounding box: QRectF(0.400521,0.287963 0.0505208x0.110185), Device FaceMe XNZ-6320 ({fe697b87-3d58-31d1-9da0-f2d58b42a226})
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::analytics::MetadataHandler(0x232d92c2068): handleObjectMetadataPacket(): x 0.400521, y 0.287963, width 0.0505208, height 0.110185, typeId nx.faceme.track, id {905c7810-1d20-4757-a0a1-70052edb9089}
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::event::AbstractEvent(0x232f7cbeaa0): Created with type [analyticsSdkObjectDetected] for resource [nx::vms::server::plugins::HanwhaResource(0x232b7781560, E4-30-22-20-DD-07)] at [1673507869142000]us
2023-01-12 16:17:49.539 242c VERBOSE nx::vms::server::event::ExtendedRuleProcessor(0x232b5841b60): Processing event [analyticsSdkObjectDetected]
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::analytics::AnalyticsDb(0x232bae8db90): Saving packet PTS: 1673507869142000, durationUs: 33895, deviceId: {fe697b87-3d58-31d1-9da0-f2d58b42a226}, streamIndex: primary, objects: 1
x 0.400521, y 0.287963, width 0.0505208, height 0.110185, trackId {905c7810-1d20-4757-a0a1-70052edb9089}, typeId nx.faceme.track, attributes {Group: "STRANGER", Mask: "No Mask"}
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::analytics::AnalyticsDb(0x232bae8db90): Saving packet (1). 0 ms
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::analytics::db::ObjectTrackAggregator(0x232bae8dc88): Adding track {905c7810-1d20-4757-a0a1-70052edb9089}, box QRectF(0.400521,0.287963 0.0505208x0.110185), timestamp 1673507869142ms. Translated box QRect(17,9 3x4)
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::analytics::AnalyticsDb(0x232bae8db90): Saving packet (2) took 0 ms
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::VideoCamera(0x232b7abfbd0): getIFrameByTime(primary, 1673507869142000 us, channel: 0, after)
2023-01-12 16:17:49.539 2cb0 VERBOSE nx::vms::server::analytics::MetadataHandler(0x232d92c2068): handleEventMetadata(): typeId nx.faceme.alert
2023-01-12 16:17:49.539 2cb0 DEBUG nx::vms::server::analytics::MetadataHandler(0x232d92c2068): Event nx.faceme.alert is not in the list of Events supported by FaceMe XNZ-6320 ({fe697b87-3d58-31d1-9da0-f2d58b42a226})
While, other cameras do not have this issue. We can find our event (FaceMe Event) in Event Types options.
We are wondering why some camera have this issue, while some do not. What is the reason that camera FaceMe XNZ-6320 do not support our plugin's event?
Thanks.
-
Hi,
We've found that it's the camera which also supports other plugin with analytics event, such as Hikvision plugin. Then our analytics event may have this problem, disappearing from the event rule option. Plus, it happens when our plugin with V5.0.0 R12 SDK version, while V4.1.0 R9 do not have this issue.
Thanks.
0 -
Hello,
First.
Please avoid using IDs starting with "nx". These could cause conflicts. "nx" is reserved for Network Optix. Here is a quotation from the manifests.md of Metadata SDK.
For example, for a company called "My Company", an identifier for an Analytics Event type of a Line
Crossing event may look like `"myCompany.lineCrossing"`.Identifiers starting with `nx.` must not be used for the entities introduced in the Plugins
developed by parties other than Nx.Second.
V4.1.0 R9 SDK is not an official release and is not recommended for production environments. Please, avoid using it. Upgrade to the latest official patch for v4.2 or v5.0 and rebuild your plugin.
Third.
The message
Event nx.faceme.alert is not in the list of Events supported
might mean that you have declared events in the "eventType", but have not declared them in the "supportedTypes" in the manifest.
Forth.
After fixing the mistakes mentioned above, port your Plugin, Engine, DeviceAgent manifests to the sample_analytics_plugin of Metadata SDK and check if the issue still persists with sample_plugin.
If it does, please, share with us the code of modified plugin.
0
Please sign in to leave a comment.
Comments
2 comments