christiancurtis

I'm using the dp.kinect2 for an interactive installation. I've read thought the attributes info here (

https://github.com/diablodale/dp.kinect2/wiki/Attributes)

 but can't find what I'm looking for. I'm wondering if any of you who have experience with this object could confirm if this is not possible, or I'm just missing something.

The main thing is, is there a way of setting a threshold for tracking the skeletons? What I'd like to do is only pick up skeletons that are within about 2 meters of the camera. This way, I can mark off the floor with a mat that says "Stand Here to Play" and any spectators behind them will not be picked up.

I have written the patch so that it is a 2 player experience, and only when the players cross a certain threshold do they start affecting the audio/visual content. The problem is that there could be 2 players standing up close trying to play, but the kinect could be locked onto a third person standing behind them, say 3 meters from the kinect, which will stop one of them from being tracked. This could lead to confusion and people thinking it's broken or buggy, which I really don't want.

The other thing is, and this isn't all that important. Is it possible to select which joints you would like to track? All I actually need is hands, neck and waist. Just thought this would stop a lot of unneeded messages being processed...

I'd be extremely grateful if anyone could let me know if these things are possible with the dp.kinect2 object.

I'm using the dp.kinect2 for an interactive installation. I've read thought the attributes info here (https://github.com/diablodale/dp.kinect2/wiki/Attributes) but can't find what I'm looking for. I'm wondering if any of you who have experience with this object could confirm if this is not possible, or I'm just missing something.

dp-kinect2-threshold-for-tracked-skeletons

I don't think this is possible inside the external, but it's definitely doable with Max.

The easiest way would be to filter the joint messages based on their Z values:

For your second issue, again, you can't tell dp.kinect2 which messages to output, but that can be easily managed with some routing:

I don't think this is possible inside the external, but it's definitely doable with Max.
The easiest way would be to filter the joint messages based on their Z values:

For your second issue, again, you can't tell dp.kinect2 which messages to output, but that can be easily managed with some routing:


The Kinectv2 drivers will track up to 6 humans. It is impossible to control or limit this in the drivers. Microsoft's algorithm uses several factors to choose which 6 humans in a large group to track.

The filtering for only two players will need to be done by your patch/application. The location of a human can be found with the USER message.

https://github.com/diablodale/dp.kinect2/wiki/Message-based-Data#user-location

After you know what user's you want to track, then you can filter the skeleton joints. The numeric id's are the same and you can use built-in max objects like (route) to get the joints for your two players.

https://github.com/diablodale/dp.kinect2/wiki/Message-based-Data#skeleton-joints

- you will need to handle state changes (new players, players that leave, new players that come within 2 meters, etc.)

- what happens when there are 3 people all within two meters? What are your rules for choosing only two players?

- It is possible for a person's hand to be within 2 meters yet all other joints to be outside 2 meters. Therefore, I recommend using the USER message to choose which two players you want and then only act on the joints matching matching numeric ID's

There are many possibilities. First is for you to make choices on your rules, player interaction, etc. After that, the specific implementation in a patch with objects will likely be clear. (route) is not the only way. :-) Here is a crude approach to use (coll) to always find the closest human and output the related skeleton joints.

The filtering for only two players will need to be done by your patch/application. The location of a human can be found with the USER message.
https://github.com/diablodale/dp.kinect2/wiki/Message-based-Data#user-location

After you know what user's you want to track, then you can filter the skeleton joints. The numeric id's are the same and you can use built-in max objects like (route) to get the joints for your two players.
https://github.com/diablodale/dp.kinect2/wiki/Message-based-Data#skeleton-joints

Some things to keep in mind
- you will need to handle state changes (new players, players that leave, new players that come within 2 meters, etc.)
- what happens when there are 3 people all within two meters? What are your rules for choosing only two players?
- It is possible for a person's hand to be within 2 meters yet all other joints to be outside 2 meters. Therefore, I recommend using the USER message to choose which two players you want and then only act on the joints matching matching numeric ID's

There are many possibilities. First is for you to make choices on your rules, player interaction, etc. After that, the specific implementation in a patch with objects will likely be clear. (route) is not the only way. :-) Here is a crude approach to use (coll) to always find the closest human and output the related skeleton joints.


My understanding was that although the Kinect would track up to 6 people. It would only give the skeleton info for 2 of those. Did I get that wrong?

This is how I've programmed the skeleton ID selection. If the Kinect sends info for more than 2 skeletons at a time then I'll need to rethink it though. I've just copied this bit to keep it simple, but basically after this comes the 1 and 2 player logic.

If one player then track that players left and right hands.

If 2 players then track only the closest hand of each player.

If one player then track that players left and right hands.
If 2 players then track only the closest hand of each player.


Kinect v1 and dp.kinect provide up to 2 skeletons simultaneously

Kinect v2 and dp.kinect2 provide up to 6 skeletons simultaneously

Kinect v1 and dp.kinect provide up to 2 skeletons simultaneously
Kinect v2 and dp.kinect2 provide up to 6 skeletons simultaneously


Ah, that's great. I only just switched to the Kinect v2 in the last couple of weeks.

I've just spoken to someone else who has some experience working with the Kinect sdk. He says it should be possible to set a "far plane" beyond which no skeletons will be tracked. Is that the case?

Microsoft does not provide that functionality. The Kinectv2 and dp.kinect2 will automatically track up to 6 full skeletons within 4m range.

You need to implement the filtering yourself. It is not hard. On this thread are already two methods with patch examples.

Microsoft does not provide that functionality. The Kinectv2 and dp.kinect2 will automatically track up to 6 full skeletons within 4m range.
You need to implement the filtering yourself. It is not hard. On this thread are already two methods with patch examples.


Thanks for you help on this guys. This is what what I end up doing to get a list of users from closest to furthest from the Kinectv2. In case it's of use to anyone else.

dp.kinect2 - threshold for tracked skeletons