Freenect(2) update thread (Linux/macOS support)

[SirLynix]

Hi,

With the upcoming 0.3 release, I splitted obs-kinect into multiple parts: common stuff like obs plugin registration, depth/infrared/faux green-screen processing, source and general device handling is part of the core but it doesn't know about Kinect devices (or even windows). Kinect v1/v2 handling is done in separate dll which are loaded by obs-kinect at startup.

This was made to add support for Kinect v1 without requiring the install of both v1 and v2 runtimes. And also to support Linux/macOS.

Obviously, Microsoft Kinect SDKs don't work on Linux/macOS, hopefully projects like libfreenect and libfreenect2 allow the use of Kinect on these systems.

Since obs-kinect device handling is done in separate libraries, it's possible to add libfreenect support kinda easily.

I tried both of these libraries on Windows (since they do have Windows support as well) for testing and it's working well!

freenect (v1):

freenect2 (v2):

However since libfreenect(2) needs raw USB commands, it requires to install a custom USB driver (like UsbDk). Hopefully this doesn't conflict with Kinect v2 (I can use libfreenect2 and Kinect SDK v2.0 without problem), but well, for Kinect v1 it's a bit more like hell. You have to replace the Kinect USB driver (using Zadig) for libfreenect to work which prevents Kinect SDK v1.8 to work, and it took me one hour to reinstall the official Kinect drivers, so yeah, I don't think I will release an obs-kinect libfreenect backend on Windows because of that (since it doesn't seem to do things you cannot do with official Kinect v1.8 runtime, except maybe for led control?).

As for Kinect v2, libfreenect2 does add more control, especially with the RGB camera color settings (things like exposure mode, white balance, gain, and such), so I think I'll support it on Windows too (even though I hope to be able to do that as well with the official SDK backend, using this).

Important note

Both libfreenect libs are really cool, but they are lacking some higher-level stuff the Kinect SDK does, like body/skeletal detection, or dedicated background removal (like Kinect SDK v1.8 does). It doesn't mean you won't be able to have background removal on Linux/macOS but it means you won't be able to use body informations for that and there's not much I can do about that. (except implementing body detecting but it requires some skill I don't have).

I will be able to compile the plugin on Linux, or even test it without problems, but I won't be able to do that with macOS. So if you have a mac and are willing to help, please let me know!

Also, as the 0.3 release is already a big one, Linux/macOS support won't be part of it (but I'll try to do it asap).

TL;DR: Linux/macOS support requires an open-source backend since official Microsoft SDKs are for Windows. There are backend for Kinect v1 and v2 but they don't do higher-level processing like body information. Things like body detection/body-based greenscreen filtering won't work on Linux/macOS because of that.

[skinlayers]

@SirLynix I can do Mac builds and testing for you. I have both a Kinect v2 and a v1.

[SirLynix]

Thanks! I have little experience with macOS compilation, I'll probably need some help!

[erdemthearch]

Hello :)
it seems that you only changed "include" and "src" files.
So how can we update the software? Which files must be copied and pasted to where?
Thanks in advance.

[SirLynix]

Hi! On which plateform are you? Premake should handle all the config for everything. Le jeu. 7 mai 2020 à 20:55, erdemthearch <notifications@github.com> a écrit :

…

Hello :) it seems that you only changed "include" and "src" files. So how can we update the software? Which files must be copied and pasted to where? Thanks in advance. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW5AXOU7UAPP7DJJIJE3F3RQL7ZPANCNFSM4MYBVH5Q> .

[erdemthearch]

W10 and Kinect v2

[SirLynix]

If you're using visual studio community 2019 all you have to do is install Kinect For Windows Runtime 2.0 and execute ’premake.exe 2019’, this will generate a solution which you can build. See readme for more info Le ven. 8 mai 2020 à 13:24, erdemthearch <notifications@github.com> a écrit :

…

W10 and Kinect v2 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW5AXLZG5UN6AXXH3GZTFLRQPTWDANCNFSM4MYBVH5Q> .

[erdemthearch]

I am really sorry but i am not a coder. I only know node based coding. I am really far away from visual studio. Is there any quick istall file or something like that? Or do you consider to make one for end users like me in future? Thanks :)

[SirLynix]

You can download the 0.2 release in the releases section of GitHub. The 0.3 binaries will be downloadable soon (I will make a release candidate for them).

As for the Kinect v2, there's not much difference between 0.2 and 0.3 for now, except for some performance improvement.

[A-Cloud-Ninja]

I've tested libfreenect on my current machine (archlinux install) and it works pretty well. Is there any reasonably straightforward way to build this with libfreenect as it currently stands? I'd be willing to go through the effort and test it on my system, this is something i've been wanting for a while now!

[SirLynix]

Hi!

From what I saw libfreenect(2) should be kinda easy to use, and Linux support is my next big task. It's just that I have a lot of work to do for other projects (and I have a relatively costly hobby called eating 😄 ) and this is not at the top of my todo list for now.

However a lot of the work that went into 0.3 (that will be 1.0 when out) was to make obs-kinect core portable, and leave Windows/Kinect SDK specific stuff in some backend code. All that to say there's not much work remaining in order to have this plugin on Linux!

[A-Cloud-Ninja]

Fantastic! If you need someone to test, please feel free to find a way to contact me haha.

[fotiDim]

I am trying to use Kinect 2 as a webcam on Mac (using Slack). Using Libfreenect2 I can get the RGB stream through their example app (Protonect) or code but there is no straightforward way to expose Kinect as a webcam to other software.

Since OBS can act a virtual webcam on Mac having this plugin working would be highly useful.

[oixtron]

Hello!
I have to agree, I would love to see a working macOS Plugin. I've been looking for a solution to use my Kinect v2 via libfreenect2 as a webcam too for quite some time now, this is by far the most promising solution. Great work so far!

[SirLynix]

Just a quick message to tell you guys I'm not forgetting about Linux and macOS, I'm just working on several things at once (a man has to eat). My next big task (and the only remaining missing feature for 1.0) is Linux and macOS support. 😄

[SirLynix]

First KinectV2 color image captured using the WIP freenect2 background!
I'm testing it on Windows for now but this backend is made for Linux and macOS users 😄

I'm also switching from premake to xmake as a build tool for its handling of dependencies, and planning to setup a CI (with nightly builds).

[SirLynix]

I managed to make the fake greenscreen work with libfreenect2. The results seems worse than with the official Windows SDK (it may be because of some options I still have to tweak).

[fotiDim]

That is cool. Personally I am happy with having greenscreen only on Windows. I only need it as a webcam on mac.

[Milliw]

Do you know if the Linux version will have the same impact on system performance than on Windows? I dropped the Kinect atm on Windows because of that.

I hope it will be less, as at least the Kinect windows service will not be there?!

Otherwise I will sell my Kinect due to lack of availability of graphics cards at normal prices atm

[SirLynix]

It depends on the Kinect model.

One of the benefit of Freenect2 (kinect for xbox one) is that it is able to exploit either the CPU or GPU to perform depth processing. I don't know if it will be faster than what the official SDK does but at least there will be more control.

I don't really know about Freenect (kinect for 360), as it's a completely different API, but I think it will be handled in a smarter way (the official Windows SDK tries to use all CPU threads at once).

As for Azure Kinect, I don't think there will be a significant difference (as it's the same SDK). Even though there maybe a difference between Windows and Linux/macOS on low-level handling.

So the real answer here is: I don't know yet, it requires some testing.

[SirLynix]

I managed to setup a CI which will build Linux plugins files (and eventually Windows and macOS) with a preliminary support for Kinect v2 (xbox one) through freenect2, and Azure Kinect support through Kinect for Azure SDK.

If you're feeling adventurous, you can download the Linux plugins files here (click on the last workflow that ran on master and download the ubuntu-latest-x64-releasedbg artifacts).

You'll still need a few other files (currently missing from this package), so you'll need to download the latest Windows nightlies to get theses files (please do it only if you know what you're doing).

This is not tested.

If you went into the troubles of trying this, please let me know if and how it worked for you (even if it didn't)!

Kinect v1 (xbox 360) and macOS users, don't worry. You'll be able to try it out soon!

[SirLynix]

I improved packaging support for Windows and Linux, which means the Linux package now has obs-kinect data (shaders and locales).

I'm wondering, what would be the best way to distribute obs-kinect on Linux? I've seen that some plugins (such as obs-websocket) build a .deb package which automatically installs the plugin files at the right place, which is something I can do, but doesn't that excludes non-debian based Linux distributions? What about them? Is obs studio even available/used on such distributions?

About mac builds, things seems easier on a technical level but would require me to pay for an Apple Developer Certificate annually. I need to think about this, and if there's another way.

[fotiDim]

I believe I can help with Apple’s developer account. I think I can add you as a member under my account.

…

On Sat 13. Feb 2021 at 12:10, Jérôme Leclercq ***@***.***> wrote: I improved packaging support for Windows and Linux, which means the Linux package now has obs-kinect data (shaders and locales). I'm wondering, what would be the best way to distribute obs-kinect on Linux? I've seen that some plugins (such as obs-websocket <https://github.com/Palakis/obs-websocket/releases/tag/4.9.0>) build a .deb package which automatically installs the plugin files at the right place, which is something I can do, but doesn't that excludes non-debian based Linux distributions? What about them? Is obs studio even available/used on such distributions? About mac builds, things seems easier on a technical level but would require me to pay for an Apple Developer Certificate annually. I need to think about this, and if there's another way. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARX7D6VHOXEJCPARYKCXPDS6ZMZJANCNFSM4MYBVH5Q> .

[Milliw]

I'm wondering, what would be the best way to distribute obs-kinect on Linux? I've seen that some plugins (such as obs-websocket) build a .deb package which automatically installs the plugin files at the right place, which is something I can do, but doesn't that excludes non-debian based Linux distributions? What about them? Is obs studio even available/used on such distributions?

Yes, if it´s a .deb package it´s only for debian based distros. AFAIK advanced users could extract that package and copy to the right places on their distro, too. IIRC I´ve done that once but not sure. I tried Solus, elementaryOS and am now with Manjaro (arch based). For all theses distros there is OBS "natively" available through their package managers.

Compiling it for one/serveral formats would limit it to these distros. Maybe at least give a manual how to install from scratch into most common distros/bases (don´t know the right term) (deb, arch). There are also distro-wide packages like flat, snap and some third I can´t remember. Though I´m not sure if this will work only together with OBS installed using this packages, too.

[SirLynix]

First image of obs-kinect on Linux!

I installed Ubuntu 20.04 and went into some troubles but finally found a way to make it work.

From what I observed, freenect2 works well, and is able to use my KinectV2 without any issue, except for the root permissions (which seems to be easy to fix, see OpenKinect/libfreenect2#870 ).

The Azure backend works too, but for some weird reason I couldn't retrieve the depth or infrared streams, probably something on my side.

The main remaining issue which remains is now a rpath one, I'll explain:
OBS-Studio loads obs-kinect which then loads its backends (obs-kinect-freenect2 for example), but this one is linked against obs-kinect and it seems Linux wants to open libobs-kinect.so back from there, except it just can't be found since libobs-kinect belongs to the plugin folder.

Setting the rpath to $origin doesn't help, as the origin here is OBS, and I can't set it to something like $origin/../../obs-plugins/64bit (which I did to test locally) because this path isn't guaranteed.

I see some solutions to fix this:

1. Find some rpath trick to retrieve libobs-kinect.so.
2. Split libobs-kinect.so in two files, set one next to obs executable and the other in obs-plugins folder (and make the backend linked to the first one, so no direct link between the plugin and its backend).
3. Use static linking.
4. Merge obs-kinect backend code into the main plugin and dynamically load backend dependencies.

I'm not sure if 1) is even possible, 3) is ugly and 4) is difficult to implement (as the libraries used are not really meant for that), so I think I'll go with 2).

Oh and I had to fix a shader on Linux, which now doesn't compile on Windows, yay.

[SirLynix]

I managed to work around theses problems and even make my Azure Kinect work on Linux (with depth-based blur!), I was just lacking Microsoft proprietary depth engine.

If the last commit compiles on the CI, it should be working for Linux users.

[A-Cloud-Ninja]

I'm wondering, what would be the best way to distribute obs-kinect on Linux? I've seen that some plugins (such as obs-websocket) build a .deb package which automatically installs the plugin files at the right place, which is something I can do, but doesn't that excludes non-debian based Linux distributions? What about them? Is obs studio even available/used on such distributions?

obs studio is available on most mainstream distros (debian, arch, gentoo probably even) and your "duty" as the developer in the typical linux packaging world is just really just tagging releases in github. Then those builds are reproducible for package maintainers in theory.

[SirLynix]

Do you know a OBS Studio plugins for Linux which does everything that should be done for this platform? The only example I've seen is obs-websocket which only provides a .deb package for Debian-based distributions.

[Milliw]

On my previous Manjaro installation I had the "NDI" plugin installed. Oh and on my laptop with Solus OS, too.
Don't know if this helps you.

[SirLynix]

Yeah obs-kinect uses the closed-source depth sensor dependency with the Azure Kinect, there's no way around this afaik.

I released a new version which should work properly this time.

[weirdal3333]

2023-01-11 11-35-39.txt

Well, it still doesn't work.

[o-kotb]

Have you installed the udev rules? https://github.com/o-kotb/flathub/tree/com.obsproject.Studio.Plugin.obs_kinect

[weirdal3333]

Yup, I am using those rules. I have a v1 kinect, but it seems like the plugin is looking for some other version of kinect.
freenect warning: Failed to get audio serial of K4W or 1473 device: **UNKNOWN**
error: [obs-kinect] [freenect] freenect error: Could not find device sibling
These are from my previous log, and seem important.
It looks like it can SEE the device, but it can't access it... Even with 777 permissions (I edited the udev rules; don't worry I put them back). This might be a freenect issue..
I used the flatpak and a fresh obs install.

Additionally, I still cannot compile the plugin on my machine with xmake. It seems to fail on one of the k4a dependencies.

install.txt

Also, the flatpak package link you commented with now returns a 403, and it's not available normally.

[SirLynix]

From your logs it seems it just fails to load the obs-freenect backend, maybe it's just a LD_LIBRARY_PATH issue?

[o-kotb]

@weirdal3333 Sorry about that, it's still not yet published on flathub. We've made some changes to the flatpak. Could you first run flatpak override --user --reset com.obsproject.Studio to reset everything and install this build.

flatpak install https://dl.flathub.org/build-repo/128539/com.obsproject.Studio.Plugin.obs_kinect.flatpakref

I'm assuming you meant you installed libfreenect(1) rules because that's for xbox 360. It should be able to access it because, by default, obs flatpak has access to all devices --device=all

Use this new build
flatpak install https://dl.flathub.org/build-repo/129469/com.obsproject.Studio.Plugin.obs_kinect.flatpakref

[weirdal3333]

I'm getting a 404 for that url...
I have the Xbox 360 version of the kinect.

[o-kotb]

Builds don't last forever on flathub's buildbot repo... I've create a flatpak bundle file that's attached here. Just extract the archive and install the bundle with flatpak install

flatpak install /path/to/obs_kinect.flatpak

obs_kinect.zip

[weirdal3333]

I am still getting this error after installing the new version. The logs are identical.
2023-01-16 07-02-15.txt
What else can I provide to get this issue resolved? I have tried this on the latest linux mint, plain debian, and manjaro to no avail.

Also, @SirLynix this isn't a normal issue on linux. It's probably something really small that we're all missing, or Something microsoft has done to make things extra-complicated. 99% of the time stuff just works and compiles for everyone without a hitch.

[o-kotb]

Can you try this build? I've built this with glfw and libjpeg-turbo. I that doesn't work I'll also try building glut as it was one of the dependencies for the examples of freenect.

obs_kinect.zip

[weirdal3333]

2023-01-16 07-53-45.txt
Same errors. I have ruled out the device being at fault with both windows and a regular freenect install.

I came across an unrelated issue; that being that freenect requires firmware for mic access on linux.
OpenKinect/libfreenect#580 (comment) <- This solves that.

Opening OBS while running any of the tests, for example the mic test, kills the kinect.

2023-01-16 08-00-11.txt

I can also hear an audible pop in my (aux jack) headphones when I do this, which is really weird.
What would happen if this plugin were recompiled with the latest release of freenect?

[o-kotb]

Yes, this is what I was looking at. I was thinking maybe it has to do with how libfreenect was compiled if it needs certain opnegl features. But I can't do much if it needs another program to upload firmware.

and a regular freenect install

Do you mean it works when you run one of the examples of freenect or when you use obs-kinect without flatpak?

[weirdal3333]

If I run the mic test, and then run obs with the plugins, the mic test stops seeing the usb, as if the whole bus were being reloaded. That could be the source of the audible pop. "USB device disappeared" and "USB audio marked dead" are the errors I'm talking about, and obs sees the device and says that it's busy.

[weirdal3333]

Oh wow, running the mic test, and then quitting it, then opening OBS makes the plugin work?! What?!
2023-01-16 08-18-09.txt

Okay, so... running the mic test while obs is open, then quitting the mic test freezes it, but then the kinect plugin starts working. This is not okay, but it works for now...........

I'd be open for a screenshare at any point if you want to see how scuffed this is on my end.

[SirLynix]

I'm sorry I can't really help you with this as your issues seem to be related with libfreenect itself (maybe try to open an issue on their side), or the way the plugin is distributed on Linux (which I think I screwed up but I don't know how to improve that).

[weirdal3333]

Could you try updating your modified version of libfreenect to the latest source of the original repo? That might fix a few things... You only changed a few things, right?

[o-kotb]

I don't think that would make much difference. The issue is still up, and I think the problem is with how the firmware is being uploaded to the kinect, but I've created a patch file with SirLynix's commits and added to the flatpak manifest to be applied while building with the latest upstream git for you to test out.

Also, I'm still learning c++ and, overall, it doesn't seem like there is much developer interest in these types of projects. So I don't think there is much to be done atm.

This is the flatpak, manifest, and the patch

[weirdal3333]

So I've been playing around with the freenect tools, and I don't think it actually needs the firmware for anything but the mic/mic array.
It just needs to be registered, and this might be specific to the kinect v1. The current obs plugin code does not successfully register the device.
After running this, the kinect light turns green and the camera starts working in obs:

[SirLynix]

I think you're misunderstanding what "registration" means in libfreenect.
See https://github.com/OpenKinect/libfreenect/blob/master/include/libfreenect.h#L104

A "registered" frame (which is what's tested in the regtest demo) is depth aligned to color (which I call color-mapped depth in this plugin), there's no kind of "device registration" required for kinect, you open the device and starts its color and depth streams with the selected mode (see https://github.com/OpenKinect/libfreenect/blob/master/examples/camtest.c#L86), which is what I do.

I think you may have some kind of power or USB issue as it seems you're not getting all data sent by the Kinect. As of why it's working once you run a libfreenect example, that's a total mystery.

Could you try updating your modified version of libfreenect to the latest source of the original repo? That might fix a few things... You only changed a few things, right?

I just added a way to apply registration later on, so I can get the color and depth frames and then map depth to color (which allows to have multiple sources showing color/depth/color-mapped depth at the same time).

I pulled the recent libfreenect changes but I don't think it will help however as the recent libfreenect changes don't seem huge.

[weirdal3333]

I've done some looking into things, and it's definitely something to do with the plugin code. Firmware does NOT need to be uploaded for the kinect's mic/video feed to work. I am getting all of the data sent by the kinect. Maybe the code to init the video feeds of the kinect isn't run when it's supposed to?

Currently the plugin is still broken.
Can you make a VM of a common, user-friendly, and up-to-date linux distro like Linux Mint/Fedora to test your flatpaks with? Windows's proprietary linux environment (WSL) is broken and generally not fully compatible with linux applications.

Installing the flatpak plugin should be all a user has to do to get it to work, after they get freenect working.

[SirLynix]

obs-kinect does not upload firmware, and I'm not sure how different should the plugin init video.

Can you make a VM of a common, user-friendly, and up-to-date linux distro like Linux Mint/Fedora to test your flatpaks with? Windows's proprietary linux environment (WSL) is broken and generally not fully compatible with linux applications.

Installing the flatpak plugin should be all a user has to do to get it to work, after they get freenect working.

I'm not a Linux user and have no idea how to make a flatpak, this is why I need help from advanced Linux users to help me with this plugin distribution.

[o-kotb]

Can you make a VM of a common, user-friendly, and up-to-date linux distro like Linux Mint/Fedora to test your flatpaks with?

All the plugin flatpak does is is extend on the OBS flatpak to add the plugin and its required dependencies (freenect, etc). The OBS flatpak would run the same regardless of the distro. And I doubt this behavior would change with native OBS (Speaking of, It’s still not published?? I’ll ask about it later)

Installing the flatpak plugin should be all a user has to do to get it to work, after they get freenect working.

You don’t need to install freenect or anything system else on your system besides the udev rules for the appropriate permissions.

I don’t know much about the original kinect, but it looks like certain models have this problem with libfreenect according to upstream reports. I’ll look into it tomorrow, but it’s hard to debug something you don’t have and can’t actively test with.

[weirdal3333]

Another problem I have is that it's currently impossible to compile the plugin on linux. Can someone fix this? The current instructions are to configure the cmake.lua file yourself, but there's no build32 or build64 folders after building libobs, and there isn't an obs-module.h file anywhere.

[SirLynix]

You can take a look at how it's setup in the CI: https://github.com/SirLynix/obs-kinect/blob/master/.github/workflows/linux-build.yml#L174

[weirdal3333]

So I've gotten the updated flatpak that o-kotb provided to reliably function.... but it's weird.
Running the freenect-tiltdemo application from the terminal and then stopping the processs before launching obs is required, otherwise the device fails to init.
Log before tiltdemo:
2023-04-20 23-35-45.txt
Log after tiltdemo
2023-04-20 23-38-54.txt

This might actually be required for the Xbox Kinect v1 now that I think about it! On an actual Xbox, when you start it up, the Kinect camera does that 'calibration' scan where it tilts it's camera all the way up and then all the way down. The green light only turns solid after that. If you interrupt it, the Xbox freaks out.
I wonder why there's so many missing packets? The usb cord isn't lossy and the power supply is stable...
Maybe the kinect is a different framerate?

[PoorPocketsMcNewHold]

Tried installing it onto my local repo obs-studio package, but it doesn't detect my KinectV1 (Xbox 360) despite working seemingly well with libfreenect (Fedora native repo package, as suggested by freenect).
I put the 64 bit .so libraries in /usr/lib64/obs-plugins/ and the rest of the plugin files in /usr/share/obs/obs-plugins/obs-kinect/
From the logs, there's nothing specific reported when adding the kinect source, and trying to refresh the kinect devices and the such.
11:46:07.430: User added source 'Kinect' (kinect_source) to scene 'Screen'
However, I saw a couple of path related issues when obs try to load the external libraries.

11:38:01.861: os_dlopen(/usr//lib64/obs-plugins/obs-kinect-azuresdk.so->/usr//lib64/obs-plugins/obs-kinect-azuresdk.so): libk4a.so.1.4: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.861: 
11:38:01.868: os_dlopen(/usr//lib64/obs-plugins/obs-kinect-azuresdk.so->/usr//lib64/obs-plugins/obs-kinect-azuresdk.so): libk4a.so.1.4: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.868: 
11:38:01.868: Module '/usr//lib64/obs-plugins/obs-kinect-azuresdk.so' not loaded
11:38:01.877: os_dlopen(/usr//lib64/obs-plugins/obs-kinect-freenect2.so->/usr//lib64/obs-plugins/obs-kinect-freenect2.so): libfreenect2.so.0.2: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.877: 
11:38:01.884: os_dlopen(/usr//lib64/obs-plugins/obs-kinect-freenect2.so->/usr//lib64/obs-plugins/obs-kinect-freenect2.so): libfreenect2.so.0.2: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.884: 
11:38:01.884: Module '/usr//lib64/obs-plugins/obs-kinect-freenect2.so' not loaded
11:38:01.946: os_dlopen(obs-kinect-azuresdk->obs-kinect-azuresdk.so): obs-kinect-azuresdk.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.946: 
11:38:01.947: os_dlopen(./obs-kinect-azuresdk->./obs-kinect-azuresdk.so): ./obs-kinect-azuresdk.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(/app/plugins/lib/obs-plugins/obs-kinect-azuresdk->/app/plugins/lib/obs-plugins/obs-kinect-azuresdk.so): /app/plugins/lib/obs-plugins/obs-kinect-azuresdk.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(obs-kinect-freenect->obs-kinect-freenect.so): obs-kinect-freenect.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(./obs-kinect-freenect->./obs-kinect-freenect.so): ./obs-kinect-freenect.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(/app/plugins/lib/obs-plugins/obs-kinect-freenect->/app/plugins/lib/obs-plugins/obs-kinect-freenect.so): /app/plugins/lib/obs-plugins/obs-kinect-freenect.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(obs-kinect-freenect2->obs-kinect-freenect2.so): obs-kinect-freenect2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(./obs-kinect-freenect2->./obs-kinect-freenect2.so): ./obs-kinect-freenect2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(/app/plugins/lib/obs-plugins/obs-kinect-freenect2->/app/plugins/lib/obs-plugins/obs-kinect-freenect2.so): /app/plugins/lib/obs-plugins/obs-kinect-freenect2.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(obs-kinect-sdk10->obs-kinect-sdk10.so): obs-kinect-sdk10.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(./obs-kinect-sdk10->./obs-kinect-sdk10.so): ./obs-kinect-sdk10.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(/app/plugins/lib/obs-plugins/obs-kinect-sdk10->/app/plugins/lib/obs-plugins/obs-kinect-sdk10.so): /app/plugins/lib/obs-plugins/obs-kinect-sdk10.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(obs-kinect-sdk20->obs-kinect-sdk20.so): obs-kinect-sdk20.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(./obs-kinect-sdk20->./obs-kinect-sdk20.so): ./obs-kinect-sdk20.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 
11:38:01.947: os_dlopen(/app/plugins/lib/obs-plugins/obs-kinect-sdk20->/app/plugins/lib/obs-plugins/obs-kinect-sdk20.so): /app/plugins/lib/obs-plugins/obs-kinect-sdk20.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
11:38:01.947: 

"Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type" is French for "Can't open the shared library: No file or folder of that type" or something along those lines. Seems obvious when it list "/usr//lib64" instead of just "/usr/lib64".

[djpiper28]

Hi there, sorry I am an OBS noob. I have the following issue on my machines (mac and arch linux), I am assuming have skipped a very obvious step, please help.

obs-kinect on  master via 🌙 v5.4.6
❯ xmake build
error: ./xmake.lua:120: attempt to index a nil value (global 'LibObs')
stack traceback:
    [./xmake.lua:120]: in main chunk

checking for platform ... macosx
checking for architecture ... arm64
checking for Xcode directory ... %s
checking for Codesign Identity of Xcode ... no
error: ./xmake.lua:120: attempt to index a nil value (global 'LibObs')
stack traceback:
    [./xmake.lua:120]: in main chunk