-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metadata broker feedback #215
Comments
Hi @paromarc , thanks for your feedback! Will send this to the team working with this API. |
Hi i will summarise the meting notes here for other that have the same questions,
|
Hey, My camera has two producers, according to vapix list producers. Since there are only topic for ASD I can only subscribe to this so the questions would be for ASD. Questions: Thanks |
Hi @Cacsjep!
|
@kevin-barudde-work thank you for your fast Response.
Thank u |
Hi @Cacsjep! The information about the data payload only including moving objects is documented in the integration guidelines, but it should be more explicitly stated in other places as well. Thank you for the feedback. The payload of consolidated metadata only includes moving items as well. Having said that, there are plans to include stationary objects in the output. May I ask you to share a bit more about the use case you are working with? Is there anything else apart from stationary objects that is missing? |
Hey @sguaqueta-work, Thanks for clarifying that this currently only tracks moving objects. It wasn’t entirely clear to me initially, so updating the documentation would definitely be helpful. It’s exciting to hear about plans to include stationary objects as well! Right now, I’m just estimating MDB and was curious why it loses tracks. Adding stationary object tracking would open up a lot of possibilities, like counting specific object classes in a scene, among other things. I believe it would be great to give developers the flexibility to choose between tracking only moving objects or including stationary ones as well. Do you have any information on when the MDB will move out of beta? Thanks a lot! |
Is there a plan in future for a radar topic to subscribe? |
Is there a plan to allow us to use MDB to detect only specific items like a face, and then be able to use a lower res larod and save resources, thus hopefully increasing it's efficacy? Because as it stands, the latest MDB is very spotty with coverage, sometimes it reports a moving face then it ignores others, you restart and you get a burst of them, then it goes away etc.. I always notice whenever "top" load starts to grow to say 2+, or when vmem goes up is when you don't see anything from the MDB which makes it very unreliable. |
Hello @rywager , We are interested in obtaining some details from the device such as the camera model, AXIS OS version, and an image of the scene to understand the environment and placement of the camera. |
Hi,
I have been playing around with the metadata broker API and wanted to report some feedback.
Starting with the API docs --> https://axiscommunications.github.io/acap-documentation/docs/api/src/api/metadata-broker/html/standard_topics.html
The payload doesn't start with the "data" property --> {
"data": {
"frame": {
"timestamp": "2023-03-08T09:00:19.320111Z",
"observations": [
but instead from the "frame" property
"frame": {
"timestamp": "2023-03-08T09:00:19.320111Z",
"observations": [
I see my P3265 fw 11.9.60 is detecting Human, Cars but also Face.
In my app I am parsing the json payload --> ** Message: 12:59:31.623: type Face: bottom 0.127300, left 0.208600, right 0.224700, top 0.098600
I have also been playing around with the 'BestShot' feature and uploading the base64 image to an S3 bucket for testing.
My P3265 is facing a display looping the same image, but the best shot seems to be inconsistent. Sometimes I get the back of my body, sometimes the front, sometimes just my face (even though my app is specifying only 'human' type and not 'face').
I am attaching a quick video showing the behavior after watching the same video twice and getting different results.
Thanks!
Marco
MetadataBroker_BestShot.mp4
The text was updated successfully, but these errors were encountered: