Welcome to the Orbbec SDK K4A Wrapper!
This repo is forked from Azure Kinect Sensor SDK
This branch is base on release/1.4.x, and use new impl code base on Orbbec SDK to replace the k4a implementation.
The usage of this library is same as Native K4A
This repository contains the K4A wrapper for Orbbec SDK, allowing users to develop applications using the K4A API and access Orbbec cameras. Additionally, users can replace the native K4A library in their application with this library without any code changes.
What we did?
The k4a.h is the header file of K4A API, and the source code in k4a.c is the implementation of K4A API. We have reimplemented the K4A API in ob_k4a_impl.c with Orbbec SDK, and keep the same effect as the original K4A API. Therefore, all functions called on user’s side will be redirected to the Orbbec SDK, and user can access the Orbbec camera like the K4A device.
The Wrapper enables you to get the most out of your orbbec camera. Features include:
The following document describes how to seamlessly replace the Azure Kinect camera with the Femto camera in a user’s application without any modifications. Please carefully read the following document before using the Femto Bolt camera.
Access_AKDK_Application_Software_with_Femto_Bolt.pdf
If you prefer not to compile the K4A Wrapper yourself, we recommend using our released SDK package. These released SDK packages have been tested and we highly recommend using them.
git clone https://github.com/orbbec/OrbbecSDK-K4A-Wrapper.git
git submodule update --init --recursive
main branch: The main branch is the default and primary branch,The code in this branch is stable and has been tested.
develop branch: The “develop” branch is the development branch that includes new features, but it is not stable.
others branch: The other branches are new feature branches that have not been merged into “develop” yet.
It is identical to Native K4A, please refer to: Building and Dependencies
Ninja:
cd OrbbecSDK-K4A-Wrapper
mkdir build
cd build
cmake .. -G Ninja
ninja
ninja install
cmake:
cd OrbbecSDK-K4A-Wrapper
mkdir build
cd build
cmake ../
cmake --build .
cmake --install .
install dependencs:
sudo apt update
sudo apt install -y \
pkg-config \
ninja-build \
doxygen \
clang \
gcc-multilib \
g++-multilib \
python3 \
nasm
sudo apt install -y \
libgl1-mesa-dev \
libsoundio-dev \
libvulkan-dev \
libx11-dev \
libxcursor-dev \
libxinerama-dev \
libxrandr-dev \
libusb-1.0-0-dev \
libssl-dev \
libudev-dev \
mesa-common-dev \
uuid-dev
building:
ninja:
cd OrbbecSDK-K4A-Wrapper
mkdir build && cd build
sudo cmake .. -G Ninja
sudo ninja
sudo ninja install
cmake
cd OrbbecSDK-K4A-Wrapper
mkdir build && cd build
sudo cmake ..
sudo make -j8
sudo make install
products list | firmware version | windows platform | linux platform |
---|---|---|---|
Orbbec Femto Bolt | 1.0.6/1.0.9/1.1.1 | Windows10, Windows11 | Ubuntu18.04, Ubuntu20.04, Ubuntu22.04 |
Orbbec Femto Mega | 1.1.5/1.1.7/1.2.8 | Windows10, Windows11 | Ubuntu20.04, Ubuntu22.04 |
For information on writing or running tests, please see testing.md
For Orbbec SDK K4A Wrapper feedback or to report a bug, please file a GitHub Issue. For general suggestions or ideas, visit our feedback forum.
As the Orbbec SDK K4A Wrapper directly uses the Azure Kinect Sensor SDK API, user can directly refer to the relevant examples of the Azure Kinect Sensor SDK:
In this repository: examples- each example has a readme page that describes it and the steps to set it up.
Azure-Kinect-Samples repository. There are multiple examples of how to use both Sensor and Body tracking SDKs.
The library of this branch is not support the K4A device, please use the Native K4A library to access the K4A device.
The Orbbec SDK K4A Wrapper is aim to provide the same API as the K4A, but it’s not full API for Orbbec SDK and feature for Orbbec camera. If you want to use the full feature of Orbbec camera, please use the Orbbec SDK directly.
For Linux user, there may be an issue with the initialization of DepthEngine when using Orbbec Femto Bolt due to modifications made by Microsoft in the new version of DepthEngine. This can cause failure during the start of the depth stream. The reason for this is that simultaneous use of multiple OpenGL contexts may result in conflicts. User can try to resolve it follow this: https://www.khronos.org/opengl/wiki/OpenGL_and_multithreading
For example:
// file: tools/k4aviewer/k4adevicedockcontrol.cpp
GLFWwindow *currentContext = glfwGetCurrentContext(); // store the current context
glfwMakeContextCurrent(NULL); // make current context to NULL
StartCameras(); // will initialize the DepthEngine
glfwMakeContextCurrent(currentContext); // restore the current context
# Running as Administrator using PowerShell
cd src/orbbec/OrbbecSDK/misc/scripts
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
.\obsensor_metadata_win10.ps1 -op install_all
cd src/orbbec/OrbbecSDK/misc/scripts
sudo chmod +x ./install_udev_rules.sh
./install_udev_rules.sh
# Once complete, the orbbec camera is available without being 'root'.
Complete your developer profile here to get connected with our Mixed Reality Developer Program.
Security issues and bugs should be reported privately, via email, to the administrators at <it@orbbec.com>.