Probably too late for this request but the time to add Nuitrack support to VL has come!
We are opening the discussion to anyone interested to share their use cases, needs, ideas and experiences with this tracking API in order to make the most of the upcoming nodeset.
Even though we are still pretty much on the research stage, the main intention is to make the nodeset as similar as possible to VL.Devices.Kinect2 which is still WIP but has already laid the groundwork for Skeleton tracking.
We see there’s already been an attempt here, hope to get some input on experience by @neuston.
Please do join the discussion and bring any thoughts you have on the subject to the table.
To test the current progress just download and install the nuget package as explained here.
Stoked to hear you’re on it!
Still quite surprised it’s not appealing to more people out here.
We’ll be happy to beta test, we have a bunch of Intel / Orbbec / Kinects here to check out performance across hardware.
Probably too late indeed for our upcoming project but we’ll be looking forward to try this out!
(if dev is coming out pretty easy/fast, do hit me up though!!)
One first suggestion: I have been looking into the OFx.nuitrack addon’s .h real quick, and I think the face tracking has not been wrapped (should be easy to add, but still a bummer it’s not included in the contribution by default imho).
The feature is turned off by default in nuitrack’s config file, and it has to be polled separately and returns a JSON string. Face info is hidden under “User Instances” in the API docs, a bit hard to find at first, here is the link.
And here a blog post they made on the subject.
I think it would be great to have this supported to not look back to Kinects and Kinect nodes just for face tracking needs ;)
What do you think?
It is such a great news! But I have stopped trying Nuitrack+VL since my last post. Thus, I cannot input more. Instead, I integrate Nuitrack in vvvv by traditional c# plugin. Normally, it works (but its license checking process will block the opening of new patch windows )
tried it with:
Orbbec Astra Model:Astra
Microsoft Kinect v2
vvvv gamma 2019.1 preview 411
Overview.vl is loading and I see VL.renderwindows and VL.nodes appearing - then sudden death with Orbbec Astra, with Kinect I even see something in the renderwindows but frozen and then also sudden death - no error message appears
how can I have a look at a kind of a logFile so I can maybe tell more
Stupid me - NuitrackSDK not activated - NuiTrackTrial license is linked to one PC, after I got a new key - NuitrackSDK works and also you VLpatche Out Of the Box - as usual, looks good - after 3minutes quit but this is the TRIAL - now I have some testtime, if I should go for a PRO
Thanks for the Nuitrack lib,
I tried to run your help patches in beta 39, older rc version(38.2-4278) latest Gamma and the latest alpha as well, but somehow always failed and vvvv just chrashed.
My nuitrack is an activated pro licence and the nuitrack_sample.exe and the VL.Devices.RealSense are working fine with my Realsense D435.
Can you help me how can I fix it (tty render didn’t showed anything)?
Just a quick update, I pushed a new version of the library (0.1.17) making use of newly introduced resource operators as well as fixes to point cloud. It requires a very recent VL >= 2019.2-0300 (available through teamcity.vvvv.org)
Pushed another update (0.1.18) which fixes point cloud using a Kinect2 (or any other device which has different resolutions in color and depth or different frame rates on those). Note however that the assigned colors to the points where never tested and are probably wrong when the color and depth images don’t align. Need to have a look at that with Xenko at some point as I had no idea how to render > 50k points in different colors with Skia.