Why metadataProviderChannel.QueueMetadata return always false

MIP
, , , ,
1

Hi,

I have a MIP driver that sends metadata (bounding boxes) using the class VideoOS.Platform.Data.MetadataProviderChannel, method QueueMetadata(…). It works perfectly in the free version of Milestone. But when I deployed the MIP driver in the Corporate Milestone version, the method QueueMetadata(…) just returns always false; therefore, I don’t see the bounding boxes in the video. I wasn’t able to find any exception in the log files (neither the event server nor the status message in the recording server). What configuration can I check? Is there any specific log for metadata?

Thanks!

Sebastian

2

The Recording Server has some debug logs located at - [C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Recording Server\Logs - Do you see anything that might explain the issue?

3

In …Logs\RecorderEngine.log I see warnings but the HardwareIds informed are not ids of the MIP Driver neither the camera for the metadata.

In …Logs\Database_.log I see only info entries

The same in …Logs\Performance.Log

The same in …Logs\SecurityTokenHandler.log

The same in …Logs\ClientCommManager.log

The same in …logs\StatusManager.log

What other logs can I check?

Due its a Corporate, do I need another configuration for metadata??

4

Does the System log in the Management Client report errors on the device?

If you test with the unmodified Bounding Box Metadata Provider sample, does it work for you?

Consider: https://developer.milestonesys.com/s/article/Can-I-have-multiple-MIP-Driver-based-devices

If you tested with the modified sample then a modified version of your own please try to remove the device in the Management Client and then add it again as new.

What XProtect product and version are you testing with? What version of the MIP SDK? (2018R3?)

5

Hi!

I tried it and it doesn’t receive any new connection.

The steps I did: run the windows app, add the mip driver in the hardware, set the relationship between camera and metadata channel in the camera client tab. It worked ok in my version of milestone, but didn’t work in the corporate.

I found this info records in the file DeviceHandling.log of the recording server:

- Metadatos 1 Starting frame group media db consumer

- Metadatos 1 Creating performance counter for device frame group media db consumer

- Metadatos 1 OnRecordingStateChanged, isRecordingRecords=True

I clear all the logs, I restarted the recording server and I found this error:

<<

2019-01-25 13:31:50.351+01:00 [ 43] WARNING - CommandHandler unhandled exception, token=ede10cd9-47f7-497e-b424-50132da8ed2f, type=VideoOS.Recorder.UpdateHardwareCommand, exception=VideoOS.IO.Drivers.DriverSetXmlException: Unable to set hardware settings (SetXmlParams failed)

en VideoOS.IO.Drivers.InteropHardwareDriver.OnSettingsChanged(SettingChangedEventData[] events)

en VideoOS.IO.Drivers.InteropHardwareDriver.ApplySavedSettings()

en VideoOS.IO.Drivers.InteropHardwareDriver.EnableSettingsUpdates()

en VideoOS.Recorder.ObjectModel.Hardware.EnableSettingsUpdates()

en VideoOS.Recorder.UpdateHardwareCommandHandler.StartHardware(UpdateHardwareCommand command, IResponseSink responseSink, ICallContextInfo callContextInfo, IHardware hardware)

en VideoOS.Recorder.UpdateHardwareCommandHandler.UpdateHardwareState(UpdateHardwareCommand command, IResponseSink responseSink, ICallContextInfo callContextInfo)

en VideoOS.Recorder.UpdateHardwareCommandHandler.Execute(CommandBase command, Object state, IResponseSink responseSink)

en VideoOS.Common.Integration.Command.ThreadPoolCommandExecutor.WorkItem(Object state)

>>

in the [C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Recording Server\Logs\RecorderEngine.log

Is it related??

6

I think it might. Do you have anything that could interfere (lock or corrupt) with the media database? Backup? Antivirus?

Besides checking this I would try to remove the device and add it as new.

Let me know if it makes a difference

7

Hi, I removed the device and added it again without success, it doesn’t still receive any connection to send metadata.

The Milestone is installed in a Windows Server 2016 Standard, do I have to have any special configuration?

Thanks in advance!

8

Does cameras work fine in your setup?

What XProtect product and version are you testing with? What version of the MIP SDK? (2018R3?)

9

Hi!

I apologize for the delay in the response.

The product is XProtect Corporate, version 2018 R3. The MIP SDK is also 2018 R3. The event server is the version 12.3a (Build 6583)

10

Does cameras work fine in your setup? I suppose they work fine and this device is the only one failing. Could there be a firewall blocking?

I will open a support case for further ideas and analysis ..

11

Hi!

The camera are ok. I think and I agree with you with the idea there is something that is blocking the communication but I don’t know what.

Thanks,

Sebastian

12

Please check have you modified or disabled the “Default Start Metadata Feed Rule”?

You need to have a rule like this

-

metadataFeedRule
metadataFeedRule567×480 88.7 KB

--

“All Metadata” could be replaced with actual devices or groups, but if no rule starts the feed on the device it explains the issue.

13

It worked!!!

Thank you very much for your time!!

Best regards,

Sebastian