@robmc I noticed that using the Orbbec Femto Mega in Color along with Player Index mode with a Kinectselect TOP doesn’t work. Or it hangs for at least 5 seconds at a time. Is this a known bug?
@robmc could you also send me this experimental build as well? Would love to test it out!
Here’s my email coleemery9@gmail.com
Currently in the same situation as @rishabhrajan and need to send color data via ethernet for a big tour that begins in a couple weeks.
Hi!, We’ve got two Femto Mega (fw 1.3.1) over Ethernet: big lag with Azure Kinect TOP, fine with Orbbec TOP. Could you share the SDK/early build to tech@chsk.net ? Thanks!
Sorry for the delay. The newer Orbbec SDKs use a third party library that conflicts with one we were already using and it took some significant effort to get them working alongside each other.
Because of that, the Orbbec update didn’t quite make it into the public experimental we released yesterday, but it is in there now. We updated to version 1.10.16 of the Orbbec SDK since that is the most recent version that still supports the Kinect and has a MacOS version.
I don’t have a newer camera here to double check this build, but you guys are welcome to download it and give it a try. We’d be interested in hearing any feedback you have on it:
1 Like
Thanks for this.
So it’s not working for me but I’m not sure if this is a TouchDesigner issue. The Orbbec viewer also doesn’t see the camera over network. I reached out to orbbec directly but they never responded. So I gave up on the idea of running this camera over a network for now.
@robmc So I finally got a response from support and now can use the Femto Mega over ethernet. The Orbbec Viewer sees the camera. The Orbbec TOP sees the camera but the Kinect Azure does not. This is the same in the ‘official’ latest experimental build as well as the one you have shared here.
Are you using the auto-detection over the network or specifying an IP?
The Kinect Azure will only work with the auto-detection system since it doesn’t have a way of specifying an IP address. The auto-detection only works with newer firmware and requires a configuration file to enable it. If you enable the TOUCH_TEXT_CONSOLE environment variable, you should see if it is auto-detecting the camera in the console window. There is info about the config file setup here: K4A Access Femto Mega Network Mode - ORBBEC - Leading Provider of Robotics and AI Vision
Did you get a response from Orbbec’s team? Curious if you were able to get any guidance about rolling back firmware. We recently purchased 2x more Femto Megas that were on 1.3.1 but were unable to roll back the firmware via Linux. I pinged Orbbec as well but didn’t get a reply in almost a month now.
So I did get a response from Orbbec. The Femto Mega requires a specific value for its IP address. Once I figured that out it was working fine. The only issue then was the Kinect CHOP wasn’t seeing it. Rob above mentioned how to get the Femto to work with the Kinect CHOP a post above but it was getting a bit too above my head so I gave up on that.
For now, if I just use the Orbbec CHOP, it works great over Ethernet.
FYI if you want to try Experimental builds, the Orbbec SDK was updated in Experimental build 2025.31310 and now supports cameras running firmware 1.3.1+
Fantastic, great work you guys!
Hi everyone,
We’ve moved from experimental to official releases. The official builds now support 1.10.16 Orbbec SDK as well, allowing for Femto Mega firmware 1.3.0+. Official builds also include some other fixes and changes like supporting an RGB color stream when connected via Ethernet in the Orbbec TOP. We’ll continue to develop for official releases going forward.
You can get the latest official here: Download | Derivative
1 Like