Login | Register 

Kinect Floor Track 099

Share your components here. First one to 100 wins!

Kinect Floor Track 099

Postby L05 » Tue Sep 19, 2017 2:54 am

I've had a few people hit me up recently about using Kinect Floor Track 088 in the newer 099. I had created an updated version back in May but had not gotten the chance to upload it to the forum, so I'm finally coming back to it now.

There are two components:

- main component that pulls in data from Kinect and returns blob tracking data and has network options for sending to a separate local or remote instance.

- secondary component that receives network data from main component.

I've also uploaded a sample video of recorded Kinect data (too big to attach):
https://www.dropbox.com/s/j9qgsz82vpgko ... tvideo.rar

screenshot_099_sm.png (149.11 KiB) Viewed 570 times


by L05
# http://L05.is
# carlosga@gmail.com

Module for tracking multiple people on a clear, flat floor space using a Kinect v2. Recommended position for the Kinect is approximately 14-15 feet (~4.5 meters) above the floor, pointed directly down, perpendicular to the floor plane. The tilt correct feature provides some correction for placement of kinect at angles.

Currently all tracking data is normalized and outputted via data_out. The number of blobs and input tracking resolution are outputted via summary_out. The tracking data itself is outputted via data_out.

I've run this module as its own instance, both locally and over a network. Data is sent to a local Touch instance via shared memory and to a networked Touch instance via IP.

This has been tested successfully on an Intel NUC i5-6260U, which makes it great for tucking into elevated spaces and extending over Cat-5e or Cat-6.

If you use this and/or improve upon it, please let me know. Feedback is encouraged!

# 099.1
# 2017.05.26
Updated so that it runs on TouchDesigner 099 and uses the new Blobtrack TOP.

Made the following feature changes:
- Input resolution selection expanded to include full, eighth, quarter, and half resolution.
- Sliders now have manual value input.
- Tilt correct slightly adjusted/improved.
- UI controls for input blur.
- Ability to send KinectMask (input matte to tracking) and KinectRGB (low-res RGB feed) over network via NDI Out.
- Basic record and playback feature for recording test files.
- Listing of local IP addresses for easy referral when doing networked setups.
- Added custom parameters to COMPs for increased modularity.
- Changed the UI COMP name from 'Left' to 'UI'.

Removed the following features:
- Tag system (not worth overhead).

- The Blobtrack TOP in 099 doesn't seem to be quite as solid as the one in 088. It takes longer to process each frame and seems to drop tracking sometimes.
- The Shared Mem Out CHOP and NDI Out TOPs only work in the Educational, Commercial, and Pro versions of TouchDesigner. Additionally, you will only be able to track up to one blob in the Non-Commercial version.
Main component that pulls in data from Kinect and returns blob tracking data.
(44.55 KiB) Downloaded 85 times
Secondary component that receives network data from main component.
(2.62 KiB) Downloaded 66 times
User avatar
Posts: 193
Joined: Thu Jan 05, 2012 2:36 pm
Location: Detroit, MI

Re: Kinect Floor Track 099

Postby chrk120 » Sun Nov 12, 2017 11:27 pm

Hey thanks for sharing. As I know, one PC only support one Kinect. Is it possible to replace the Kintct to a common IR camera, which could be multiply connected to one PC?
Posts: 16
Joined: Thu Sep 25, 2014 6:07 pm

Re: Kinect Floor Track 099

Postby L05 » Mon Nov 13, 2017 6:54 pm

This particular component is analyzing the depth image from the Kinect, so maybe something like the Stereolabs ZED camera might work (https://www.stereolabs.com). In theory this should also work with a Kinect V1, although the V2 resolution is currently hard coded into a few nodes. At its core, the component is basically taking a cross section of the depth map and running the blobtrack TOP on it; the rest is mainly UI and data handling to make it easier to use as a module within a larger system.

As I get my hands on some more sensors, I will try and test them and extend the component to make it more adaptive to different devices. I haven't had the opportunity to try any other sensors. If you do, it'd be great if you could post your findings here.
User avatar
Posts: 193
Joined: Thu Jan 05, 2012 2:36 pm
Location: Detroit, MI

Return to Shared .tox Components

Who is online

Users browsing this forum: No registered users and 3 guests