Femto Mega is 2-3 frames (66-100ms) behind the Azure Kinect

Technical Support & Q&A
1

Please watch this test: https://youtu.be/eyY6ERpyxEA

66-100ms may not sound like much, but it’s absolutely critical in interactive applications, and this is on top of the Azure Kinect’s latency, which I haven’t measured, but I expect to be at least 60ms.

Does anyone have proposals for how to lower this latency? Does some of it arise from the one-device depth processing? In that case, the Femto Bolt might score better.

I am pretty confident about the computer, switch and cables I’ve used for the test. But let me know if you think there is anything may improve the situation.

Orbbec Femto Mega
Firmware: 1.3.1
SDK 2.2.5

Azure Kinect
Firmware: 1.6.79 (Depth)
SDK: 1.4.1

Computer
CPU: AMD Ryzen 7 9800X3D
GPU: RTX 5090
MOBO: MSI MPG X870E Carbon

Switch
QNAP QSW-M2106R-2S2T

Cables
RJ45: CAT7 S/FTP
USB: The cable included in the box

1 Like
2

I did another test using the k4a wrapper and also comparing the Femto Bolt. The Bolt turns out to have the same latency as the Azure Kinect.

1 Like
3

Hi,
Did you find a solution for this issue ?
It seems I have the exact same conclusion also from my side

4

I returned my unboxed Femto Mega sensors, put the one I tested with for sale, and got a bunch of Femto Bolts instead. It sucks not to have POE, but in my use case latency is more critical.

1 Like