With XProtect Pro 2018 R2, the sample behavior is different from the 2017 R3 version. When adding the MIP device, it creates another camera (Camera 17 in my case) instead of Metadata port. It was working fine with 2017.
I have a suspicion that you might have somehow used the UIVideoProvider (or CameraMetadataProvider) instead of the BoundingBoxMetadataProvider sample. This is the only way I can make your description fit, the only explanation I can thing of for your observations. Please double-check, please remove the MIP Driver based device you have now and start over making sure it is the BoundingBoxMetadataProvider sample you use.
Thanks for your answer. Here’s the screenshot, so it’s really the Bounding Box Metadata Provider.
When looking at the usage description of the sample, it is correct for 2017. But for 2018, it seems different:
/MIPSDK/Html/samples/BoundingBoxMetadataProvider.html
Here’s what I get when adding the hardware device:
I tested and I was able to see the same..
I feel a bit embarrassed, I should have given you a better answer first time, I forgot one important fact.
The fact is that Metadata in not supported in XProtect e-code!
If you have XProtect Professional or XProtect Express (without plus) then metadata and the samples that use metadata will not work.
The requirement to work with metadata is a XProtect c-code VMS: XProtect Corporate, XProtect Expert, XProtect Professional+, XProtect Express+ or XProtect Essential+.
See also - https://www.milestonesys.com/solutions/platform/product-index/
Thanks, you are right. I tried Professional+ and it works. Thanks for your support, I appreciate.