-
Notifications
You must be signed in to change notification settings - Fork 518
Use new libfreenect2 API #189
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
Conversation
|
+1 |
|
@xlz Sorry. Actually it compiles yes, but kinect2_bridge fails on start up now. If I go back to a previous state of libfreenect2 (21 nov), then both branches master and use-new-api work |
|
Thanks for the pull request, I will try it out next week and also check out the newest libfreenect2 then. |
libfreenect2 API no longer exports details about DepthPacketProcessor. Use Freenect2Device::setConfiguration() instead.
|
OK, the first try was not correct. It was setting configuration in This commit should be tested and good now. |
|
Great @xlz ! Seems to work like a charm :) 👍 |
|
Works for me too :) |
|
Merged! Thanks a lot for the Pull-Request and the testing. |
libfreenect2 has changed API and it breaks iai_kinect2 in the current state.
Reason of the API breakage: In the process of avoiding exposing implementation details of various depth processors and making it hard to maintain future API stability, DepthProcessor is entirely hidden from API/ABI. I provided a compatibility workaround to allow the then current iai_kinect2 to work, but the workaround broke MSVC compilation and was reverted.
Use the new libfreenect2 API here.