- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi guys,
Reading the docs, I see that you don't have "poses" anymore, just Gestures.
That way, we won't have the event that the pose is not "active" anymore.
Is this the way it's going to be for the 1.0 version of the SDK?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We do support poses(such as V-sign, spread finger, etc). What kinds pose do you want? Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi David,
The perceptual sdk has 2 different things:
- poses: start event, end event
- gestures: on event
The realsense sdk has only one model: on event
Is this the way it's going to be to all gestures/poses?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, RealSense SDK combines gestures and poses together and all called gestures.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I may put my two cents in, don't you think this would result in a more restrict set of actions? I think they are different (poses and gestures).
A pose example: a game where posing a "big five" creates a "shield" as long as the "big five" is hold.
A gesture could be swinging my hand to use my sword.
I know I can reproduce the pose behavior tracking all fingers state (I'm already doing that), and I know you probably have good arguments to merge them both, but I still think that it would be more intuitive to have poses (a state) and gestures (an action) separated.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Very good question. If you look at the GestureData
struct GestureData { pxcI64 timeStamp; /// Time-stamp in which the gesture occurred pxcUID handId; /// ID of the relevant tracked hand, if relevant and known GestureStateType state; /// The state of the gesture pxcI32 frameNumber; /// The number of the frame in which the gesture occurred pxcCHAR name[MAX_NAME_SIZE]; /// Unique name of this gesture };
You can use state to track the gesture. The state can be following.
enum GestureStateType { /// Gesture started GESTURE_STATE_START=0 , GESTURE_STATE_IN_PROGRESS /// Gesture is in progress , GESTURE_STATE_END /// Gesture ended };
Hope this will answer your question. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Great!
So gestures like swipe left will have only GESTURE_STATE_START or GESTURE_STATE_END?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, and you can use those two states in your call back event.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andre,
In addition to David's comment, please note that when you enable gestures detection in the SDK, you have a flag that indicates if you want to receive only start/stop events, or get an event at every frame where the gesture is detected.
Indeed for moving gestures this doesn't make much of a difference, but for poses it can be useful
Cheers,
Dagan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks David and Dagan :)

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page