We’ve been making great use of the zedcam plugin in the latest 2022 release. The tracking is fantastic. However it would be amazing to also get the mask for each body tracked. This is available as an output from the SDK, and is one of the few things preventing us from completely switching over from the kinect:
Is there any plan to expose this as a TOP operator? e.g. a single texture, with the pixel values set to 1 for p1, 2 for p2, etc?
thank you for the suggestion. It’s been logged as a RFE for consideration.
cheers
Markus
i would also realy like a feature like this for the zed 2i, we are trying to make our own mask from the zed sdk and some python in touchdesigner but it is proving more difficult then expected.
a “player index” function like the kinect where each player has thier own color would be super handy
The way the ZED SDK is setup, they provide a different texture for each detected object. Do you see more value in that workflow (with a way of selecting that texture), or a singular texture we’ve I’ve already merged them all together for you?
Hey Malcolm, that’s a good question, thanks for asking. My (slight) preference would be for a single texture with all human body masks merged together, but only if identifying information was embedded in the mask pixel values - e.g. the skeleton ID/player number, so that masks can be matched to body tracking data using our own code.
But overall, as long as there is a way to associate body tracking chop data with mask data, then we’re happy on our end.
Hi @malcolm , just checking in to see whether this RFE is likely to make it into a release any time soon? We’ve got a few projects this could be helpful on - I’ve been playing around with google’s mediapipe as an interim solution, but it’s a bit hacky. Thanks for your help.
We actually have it 95% done, but tracking down a crash that is occurring in some cases still.
We’ve confirmed with ZED that the crash is in their SDK, so we need to wait for SDK 4.1 to be released, then we can release this feature
hello malcom, have you been able to solve the problems with the alpha mask of the ZED camera now that SDK
4.1 has been released?
best
floyd
The crash fix we were hoping for only fixed it for object detection, not body tracking. Still working on getting one for body tracking.
@malcolm is this fixed as of the daily build posted here? I’m getting this hardware next week, just curious.
Not that we know of. The bug still exists as far as we know.
Thank you!
But also that feature isn’t exposed in any builds yet too, pending the fix.
Hello! @malcolm any news on this from the newest builds?
Hello,
The mask feature will be available in the next Experimental Release. It is also available as a separate branch based from Official available in this DropBox link
Thanks Huck! Gonna give it a try, for some reason working with zed camera on experimental builds after some time touchdesigner freezes and the only thing I can do is restarting TD i dont know why is this happening
Hello,
Is this in the newest version of Experimental 2025.30280 or 2025.30060? If you are able to reproduce this consistently can you provide me with the toe file here or you can email it to support@derivative.ca as well. Lastly what camera are you using when Touch freezes?
Thanks,
Huck
Im am using Zed 2i camera, after some minutes of working or opening touchdesigner it freezes the input from zed camera, i am using pointcloud image, so if i click reboot or turn off the camera from the Zed TOP, TD Freezes but its not generating a crash file, after reopening touchdesigner sometimes is not recognizing the camera, so i need to disconnect and reconnect the zed usb and reopen touchdesigner. I tested with two different CPUs one with a quadro A4000 and other with RTX 3080. Ill send the file via email. Thank you
Hello,
Just replying here so others can see it as well. Have you tried used the ZED viewer tool available from their website? It comes with a diagnostic tool that you can try when your camera is not responding. Another thing to note is that with devices such as these often times the cable can be a point of failure. Make sure to use the cable that came with the camera, and a USB 3.0 port.
Best,
Huck