I confirm subject symptom by following instructions.
- Use ‘Multi Channel Metadata Provider’ sample. Create 3 metadata channnel, register it and link to existing camera. Confirmed that bounding boxes are displayed for the target camera in SmartClient.
- Change metadata channel setting in ‘Multi Channel Metadata Provider’ from 3 to 5.
- Do “Replace Hardware” against MIP Driver and increase metadata channel from 3 to 5.
- 3 metadata driver work, bounding boxes are displayed.
- 2 metadata driver that newly added do NOT work, bounding boxes are NOT displayed.
Is this behaviour a bug?
The new metadata channels need to be defined as related for the camera definitions, and the Smart Client also has to do a re-login or refresh of its configuration
We reboot SmartClient but situation is same.
Could you let me know what kind of activities I have to do for following procedure?
> The new metadata channels need to be defined as related for the camera definitions
First of all, I am not sure the MIPSDK sample will generate metadata for more than 3 channels - I think it generates specific type of metadata for each channel.
Also, when adding new metadata channels, you need to select the relevant camera, check the ‘client’ tab and define the metadata as a related device, save, and then restart Smart Client.
We confirm ‘Multi Channel Metadata Provider’ MIPSDK sample behaviour and it works with more than 3 channels if we register multiple channel newly.
Also we follow the procedure you show “Do “Replace Hardware” and add new metadata channels, select the relevant camera, check the ‘client’ tab and define the metadata as a related device, save, and then restart Smart Client.” But newly added metadata drivers do NOT work.
I dont think I understand the setup, as the Multi Channel Metadata Provider only has 3 metadata channels, and just the first one provides bounding boxes that can be displayed by the Smart Client.
There are no way to just add more channels in the Management Client without changing the sample.
Do you have your own implementation similar to the sample?
Perhaps you could run the MetadataLiveViewer and check that metadata is in fact running in the extra streams.
We modified Multi Channel Metadata Provider sample, and it generate metadata device of 3-5 channels.
On this program, all each channel type of the meta data device are BoundingBox.
I have downloaded your sample. First I commented out so only 3 metadata channels were defined, and added it as a device,
Configured and tested that overlay is shown in Smart Client.
Then I inlcude the lines again, so 6 metadata channels were defined, and did a hardware replacement wizard.
Then I ENABLED the new metadata devices, and added them into a Metadata group.
The defined on the camera as a related metadata device, and tested that Smart Client overlay works.
All seems OK.
We tried that modified Multi Channel Metadata Provider sample program several times.
We tried it in the same way, but it succeeded several times and failed several times.
We will try this more.
It would be helpful if you had any advice.
I suggest we do a shared desktop, where you show me the issue. I can be available from 8am CET tomorrow or a day next week.
Sorry for my late response, I’m not in office almost 1 week.
Do “Increase of metadata channel” always work in your environment?
In our side, sometime work, sometime fail, not always.
I’m afraid we cannot show you failure case in shared desktop.
It worked for me the few times I tested it.
I suggest you see if it possible to identify when it works, and when not. Could be a timing thing, or because of how your program access configuration.
The sample attached previously did not contain or explain how you add more channels - I guess you could change it to work the same way as your real application via some buttons on the screen - then I can retest it with the modified sample application.
Still we couldn’t find the condition to reproduce.
Attached files are original & modified sample code we use.
I have downloaded your samples, and re-tested - and it works as it should.
I suggest that next time you see the issue, zip all the log files under the recorder and send to us. Consider to create a support case in our support system to better track the case.
OK, we’ll create support case with recording server logs when we see the problem next time.