WO2011071808A2 - Poursuite visuelle d'une cible - Google Patents

Poursuite visuelle d'une cible Download PDF

Info

Publication number
WO2011071808A2
WO2011071808A2 PCT/US2010/059072 US2010059072W WO2011071808A2 WO 2011071808 A2 WO2011071808 A2 WO 2011071808A2 US 2010059072 W US2010059072 W US 2010059072W WO 2011071808 A2 WO2011071808 A2 WO 2011071808A2
Authority
WO
WIPO (PCT)
Prior art keywords
pixel
model
synthesized
force
observed
Prior art date
Application number
PCT/US2010/059072
Other languages
English (en)
Other versions
WO2011071808A3 (fr
Inventor
Ryan M. Geiss
Original Assignee
Microsoft Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corporation filed Critical Microsoft Corporation
Priority to CN201080055361.6A priority Critical patent/CN102648484B/zh
Publication of WO2011071808A2 publication Critical patent/WO2011071808A2/fr
Publication of WO2011071808A3 publication Critical patent/WO2011071808A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V40/00—Recognition of biometric, human-related or animal-related patterns in image or video data
    • G06V40/10—Human or animal bodies, e.g. vehicle occupants or pedestrians; Body parts, e.g. hands
    • G06V40/103—Static body considered as a whole, e.g. static pedestrian or occupant recognition
    • A—HUMAN NECESSITIES
    • A63—SPORTS; GAMES; AMUSEMENTS
    • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
    • A63F2300/00—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game
    • A63F2300/10—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game characterized by input arrangements for converting player-generated signals into game device control signals
    • A63F2300/1087—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game characterized by input arrangements for converting player-generated signals into game device control signals comprising photodetecting means, e.g. a camera
    • A63F2300/1093—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game characterized by input arrangements for converting player-generated signals into game device control signals comprising photodetecting means, e.g. a camera using visible light
    • A—HUMAN NECESSITIES
    • A63—SPORTS; GAMES; AMUSEMENTS
    • A63F—CARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
    • A63F2300/00—Features of games using an electronically generated display having two or more dimensions, e.g. on a television screen, showing representations related to the game
    • A63F2300/60—Methods for processing data by generating or executing the game program
    • A63F2300/66—Methods for processing data by generating or executing the game program for rendering three dimensional images
    • A63F2300/6607—Methods for processing data by generating or executing the game program for rendering three dimensional images for animating game characters, e.g. skeleton kinematics

Definitions

  • One disclosed embodiment includes representing a human target with a machine-readable model configured for adjustment into a plurality of different poses and receiving an observed depth image of the human target from a source. The observed depth image is compared to the model. A refine-z force vector is then applied to one or more force-receiving locations of the model to move a portion of the model towards a corresponding portion of the observed depth image if that portion of the model is Z-shifted from that corresponding portion of the observed depth image.
  • FIG. 1A shows an embodiment of an exemplary target recognition, analysis, and tracking system tracking a game player playing a boxing game.
  • FIG. IB shows the game player of FIG. 1A throwing a punch that is tracked and interpreted as a game control that causes a player avatar to throw a punch in game space.
  • FIG. 2 schematically shows a computing system in accordance with an embodiment of the present disclosure.
  • FIG. 3 shows an exemplary body model used to represent a human target.
  • FIG. 4 shows a substantially frontal view of an exemplary skeletal model used to represent a human target.
  • FIG. 5 shows a skewed view of an exemplary skeletal model used to represent a human target.
  • FIG. 6 shows an exemplary mesh model used to represent a human target.
  • FIG. 7 shows a flow diagram of an example method of visually tracking a target.
  • FIG. 8 shows an exemplary observed depth image.
  • FIG. 9 shows an exemplary synthesized depth image.
  • FIG. 10 schematically shows some of the pixels making up a synthesized depth image.
  • FIG. 11A schematically shows the application of a force to a force-receiving location of a model.
  • FIG. 11B schematically shows a result of applying the force to the force-receiving location of the model of FIG. 11A.
  • FIG. 12A shows a player avatar rendered from the model of FIG.
  • FIG. 12B shows a player avatar rendered from the model of FIG.
  • FIG. 13 schematically shows comparing a synthesized depth image to a corresponding observed depth image.
  • FIG. 14 schematically shows identifying regions of mismatched synthesized pixels of the comparison of FIG. 13.
  • FIG. 15 schematically shows another comparison of a synthesized depth image and a corresponding observed depth image, wherein regions of mismatched pixels correspond to various pixel cases.
  • FIG. 16 schematically shows an example embodiment of a pull pixel case.
  • FIG. 17 schematically shows an example embodiment of a push pixel case.
  • FIG. 18 shows a table detailing example relationships between various pixel cases and skeletal model joints.
  • FIG. 19 illustrates application of constraints to a model representing a target.
  • FIG. 20 illustrates another application of constraints to a model representing a target.
  • FIG. 21 illustrates yet another application of constraints to a model representing a target.
  • the present disclosure is directed to target recognition, analysis, and tracking.
  • the use of a depth camera or other source for acquiring depth information for one or more targets is disclosed.
  • Such depth information may then be used to efficiently and accurately model and track the one or more targets, as described in detail below.
  • the target recognition, analysis, and tracking described herein provides a robust platform in which one or more targets can be consistently tracked at a relatively fast frame rate, even when the target(s) move into poses that have been considered difficult to analyze using other approaches (e.g., when two or more targets partially overlap and/or occlude one another! when a portion of a target self-occludes another portion of the same target, when a target changes its topographical appearance (e.g., a human touching his or her head), etc.).
  • FIG. 1A shows a nonlimiting example of a target recognition, analysis, and tracking system 10.
  • FIG. 1A shows a computer gaming system 12 that may be used to play a variety of different games, play one or more different media types, and/or control or manipulate non-game applications.
  • FIG. 1A also shows a display 14 in the form of a high-definition television, or HDTV 16, which may be used to present game visuals to game players, such as game player 18.
  • FIG. 1A shows a capture device in the form of a depth camera 20, which may be used to visually monitor one or more game players, such as game player 18.
  • the example shown in FIG. 1A is nonlimiting. As described below with reference to FIG. 2, a variety of different types of target recognition, analysis, and tracking systems may be used without departing from the scope of this disclosure.
  • a target recognition, analysis, and tracking system may be used to recognize, analyze, and/or track one or more targets, such as game player 18.
  • FIG. 1A shows a scenario in which game player 18 is tracked using depth camera 20 so that the movements of game player 18 may be interpreted by gaming system 12 as controls that can be used to affect the game being executed by gaming system 12. In other words, game player 18 may use his movements to control the game. The movements of game player 18 may be interpreted as virtually any type of game control.
  • FIG. 1A shows game player
  • FIG. IB shows HDTV 16 visually presenting player avatar 24 throwing a punch that strikes boxing opponent 22 responsive to game player 18 throwing a punch in physical space.
  • Other movements by game player 18 may be interpreted as other controls, such as controls to bob, weave, shuffle, block, jab, or throw a variety of different power punches.
  • some movements may be interpreted into controls that serve purposes other than controlling player avatar 24. For example, the player may use movements to end, pause, or save a game, select a level, view high scores, communicate with a friend, etc.
  • a target may include a human and an object.
  • a player of an electronic game may be holding an object, such that the motions of the player and the object are utilized to adjust and/or control parameters of the electronic game.
  • the motion of a player holding a racket may be tracked and utilized for controlling an on-screen racket in an electronic sports game.
  • the motion of a player holding an object may be tracked and utilized for controlling an on-screen weapon in an electronic combat game.
  • Target recognition, analysis, and tracking systems may be used to interpret target movements as operating system and/or application controls that are outside the realm of gaming.
  • the illustrated boxing scenario is provided as an example, but is not meant to be limiting in any way. To the contrary, the illustrated scenario is intended to demonstrate a general concept, which may be applied to a variety of different applications without departing from the scope of this disclosure.
  • FIGs. 1A and IB show a nonlimiting example in the form of gaming system 12, HDTV 16, and depth camera 20.
  • FIG. 2 schematically shows a computing system 40 that may perform one or more of the target recognition, tracking, and analysis methods and processes described herein.
  • Computing system 40 may take a variety of different forms, including, but not limited to, gaming consoles, personal computing gaming systems, military tracking and/or targeting systems, and character acquisition systems offering green- screen or motion-capture functionality, among others.
  • Computing system 40 may include a logic subsystem 42, a data- holding subsystem 44, a display subsystem 46, and/or a capture device 48.
  • the computing system may optionally include components not shown in FIG. 2, and/or some components shown in FIG. 2 may be peripheral components that are not integrated into the computing system.
  • Logic subsystem 42 may include one or more physical devices configured to execute one or more instructions.
  • the logic subsystem may be configured to execute one or more instructions that are part of one or more programs, routines, objects, components, data structures, or other logical constructs. Such instructions may be implemented to perform a task, implement a data type, transform the state of one or more devices, or otherwise arrive at a desired result.
  • the logic subsystem may include one or more processors that are configured to execute software instructions. Additionally or alternatively, the logic subsystem may include one or more hardware or firmware logic machines configured to execute hardware or firmware instructions.
  • the logic subsystem may optionally include individual components that are distributed throughout two or more devices, which may be remotely located in some embodiments.
  • Data-holding subsystem 44 may include one or more physical devices configured to hold data and/or instructions executable by the logic subsystem to implement the herein described methods and processes. When such methods and processes are implemented, the state of data-holding subsystem 44 may be transformed (e.g., to hold different data).
  • Data-holding subsystem 44 may include removable media and/or built-in devices.
  • Data- holding subsystem 44 may include optical memory devices, semiconductor memory devices (e.g., RAM, EEPROM, flash, etc.), and/or magnetic memory devices, among others.
  • Data-holding subsystem 44 may include devices with one or more of the following characteristics : volatile, nonvolatile, dynamic, static, read/write, read-only, random access, sequential access, location addressable, file addressable, and content addressable.
  • logic subsystem 42 and data-holding subsystem 44 may be integrated into one or more common devices, such as an application specific integrated circuit or a system on a chip.
  • FIG. 2 also shows an aspect of the data-holding subsystem in the form of computer-readable removable media 50, which may be used to store and/or transfer data and/or instructions executable to implement the herein described methods and processes.
  • Display subsystem 46 may be used to present a visual representation of data held by data-holding subsystem 44. As the herein described methods and processes change the data held by the data-holding subsystem, and thus transform the state of the data-holding subsystem, the state of display subsystem 46 may likewise be transformed to visually represent changes in the underlying data. As a nonlimiting example, the target recognition, tracking, and analysis described herein may be reflected via display subsystem 46 in the form of a game character that changes poses in game space responsive to the movements of a game player in physical space. Display subsystem 46 may include one or more display devices utilizing virtually any type of technology. Such display devices may be combined with logic subsystem 42 and/or data-holding subsystem 44 in a shared enclosure, or such display devices may be peripheral display devices, as shown in FIGs. 1A and IB.
  • Computing system 40 further includes a capture device 48 configured to obtain depth images of one or more targets.
  • Capture device 48 may be configured to capture video with depth information via any suitable technique (e.g., time-of-flight, structured light, stereo image, etc.).
  • capture device 48 may include a depth camera, a video camera, stereo cameras, and/or other suitable capture devices.
  • the capture device 48 may emit infrared light to the target and may then use sensors to detect the backscattered light from the surface of the target.
  • pulsed infrared light may be used, wherein the time between an outgoing light pulse and a corresponding incoming light pulse may be measured and used to determine a physical distance from the capture device to a particular location on the target.
  • the phase of the outgoing light wave may be compared to the phase of the incoming light wave to determine a phase shift, and the phase shift may be used to determine a physical distance from the capture device to a particular location on the target.
  • time-of-flight analysis may be used to indirectly determine a physical distance from the capture device to a particular location on the target by analyzing the intensity of the reflected beam of light over time, via a technique such as shuttered light pulse imaging.
  • structured light analysis may be utilized by capture device 48 to capture depth information.
  • patterned light i.e., light displayed as a known pattern such as grid pattern or a stripe pattern
  • the pattern may become deformed in response, and this deformation of the pattern may be studied to determine a physical distance from the capture device to a particular location on the target.
  • the capture device may include two or more physically separated cameras that view a target from different angles, to obtain visual stereo data.
  • the visual stereo data may be resolved to generate a depth image.
  • capture device 48 may utilize other technologies to measure and/or calculate depth values. Additionally, capture device 48 may organize the calculated depth information into "Z layers," i.e., layers perpendicular to a Z axis extending from the depth camera along its line of sight to the viewer.
  • two or more different cameras may be incorporated into an integrated capture device.
  • a depth camera and a video camera e.g., RGB video camera
  • two or more separate capture devices may be cooperatively used.
  • a depth camera and a separate video camera may be used.
  • a video camera it may be used to provide target tracking data, confirmation data for error correction of target tracking, image capture, face recognition, high-precision tracking of fingers (or other small features), light sensing, and/or other functions.
  • a capture device may include one or more onboard processing units configured to perform one or more target analysis and/or tracking functions.
  • a capture device may include firmware to facilitate updating such onboard processing logic.
  • Computing system 40 may optionally include one or more input devices, such as controller 52 and controller 54.
  • Input devices may be used to control operation of the computing system.
  • input devices such as controller 52 and/or controller 54 can be used to control aspects of a game not controlled via the target recognition, tracking, and analysis methods and procedures described herein.
  • input devices such as controller 52 and/or controller 54 may include one or more of accelerometers, gyroscopes, infrared target/sensor systems, etc., which may be used to measure movement of the controllers in physical space.
  • the computing system may optionally include and/or utilize input gloves, keyboards, mice, track pads, trackballs, touch screens, buttons, switches, dials, and/or other input devices.
  • target recognition, tracking, and analysis may be used to control or augment aspects of a game, or other application, conventionally controlled by an input device, such as a game controller.
  • the target tracking described herein can be used as a complete replacement to other forms of user input, while in other embodiments such target tracking can be used to complement one or more other forms of user input.
  • Computing system 40 may be configured to perform the target tracking methods described herein. However, it should be understood that computing system 40 is provided as a nonlimiting example of a device that may perform such target tracking. Other devices are within the scope of this disclosure.
  • Computing system 40 may be configured to represent each target with a model.
  • information derived from such a model can be compared to information obtained from a capture device, such as a depth camera, so that the fundamental proportions or shape of the model, as well as its current pose, can be adjusted to more accurately represent the modeled target.
  • the model may be represented by one or more polygonal meshes, by a set of mathematical primitives, and/or via other suitable machine representations of the modeled target.
  • FIG. 3 shows a nonlimiting visual representation of an example body model 70.
  • Body model 70 is a machine representation of a modeled target (e.g., game player 18 from FIGs. 1A and IB).
  • the body model may include one or more data structures that include a set of variables that collectively define the modeled target in the language of a game or other application/operating system.
  • a model of a target can be variously configured without departing from the scope of this disclosure.
  • a model e.g., a machine- readable model
  • Each body part may be characterized as a mathematical primitive, examples of which include, but are not limited to, spheres, anisotropically- scaled spheres, cylinders, anisotropic cylinders, smooth cylinders, boxes, beveled boxes, prisms, and the like.
  • the target may be represented by a model including a plurality of portions, each portion associated with a part index corresponding to a part of the target.
  • the part index may be a body-part index corresponding to a part of the human target.
  • body model 70 of FIG. 3 includes body parts bpl through bpl4, each of which represents a different portion of the modeled target.
  • Each body part is a three-dimensional shape.
  • bp3 is a rectangular prism that represents the left hand of a modeled target
  • bp 5 is an octagonal prism that represents the left upper-arm of the modeled target.
  • Body model 70 is exemplary in that a body model may contain any number of body parts, each of which may be any machine-understandable representation of the corresponding part of the modeled target.
  • a model including two or more body parts may also include one or more joints. Each joint may allow one or more body parts to move relative to one or more other body parts.
  • a model representing a human target may include a plurality of rigid and/or deformable body parts, wherein some body parts may represent a corresponding anatomical body part of the human target.
  • each body part of the model may comprise one or more structural members (i.e., "bones"), with joints located at the intersection of adjacent bones. It is to be understood that some bones may correspond to anatomical bones in a human target and/or some bones may not have corresponding anatomical bones in the human target.
  • a human target may be modeled as a skeleton including a plurality of skeletal points, each skeletal point having a three- dimensional location in world space.
  • the various skeletal points may correspond to actual joints of a human target, terminal ends of a human target's extremities, and/or points without a direct anatomical link to the human target.
  • Each skeletal point has at least three degrees of freedom (e.g., world space x, y, z).
  • the skeleton can be fully defined by 3 x ⁇ values, where ⁇ is equal to the total number of skeletal points included in the skeleton.
  • a skeleton with 33 skeletal points can be defined by 99 values, for example.
  • some skeletal points may account for axial roll angles.
  • the bones and joints may collectively make up a skeletal model, which may be a constituent element of the model.
  • the skeletal model may include one or more skeletal members for each body part and a joint between adjacent skeletal members.
  • Exemplary skeletal model 80 and exemplary skeletal model 82 are shown in FIGs. 4 and 5, respectively.
  • FIG. 4 shows a skeletal model 80 as viewed from the front, with joints jl through j33.
  • FIG. 5 shows a skeletal model 82 as viewed from a skewed view, also with joints jl through j33.
  • Skeletal model 82 further includes roll joints j34 through j47, where each roll joint may be utilized to track axial roll angles.
  • an axial roll angle may be used to define a rotational orientation of a limb relative to its parent limb and/or the torso.
  • roll joint j40 may be used to indicate the direction the associated wrist is pointing (e.g., palm facing up).
  • joints can receive forces and adjust the skeletal model, as described below, roll joints may instead be constructed and utilized to track axial roll angles.
  • an axial roll angle may be determined. For example, if examining a lower leg, the orientation of the lower leg relative to the associated upper leg and hips may be examined in order to determine an axial roll angle.
  • some models may include a skeleton and/or body parts that serve as a machine representation of a modeled target.
  • a model may alternatively or additionally include a wireframe mesh, which may include hierarchies of rigid polygonal meshes, one or more deformable meshes, or any combination of the two.
  • FIG. 6 shows a model 90 including a plurality of triangles (e.g., triangle 92) arranged in a mesh that defines the shape of the body model. Such a mesh may include bending limits at each polygonal edge.
  • the number of triangles, and/or other polygons, that collectively constitute the mesh can be selected to achieve a desired balance between quality and computational expense. More triangles may provide higher quality and/or more accurate models, while fewer triangles may be less computationally demanding.
  • a body model including a polygonal mesh need not include a skeleton, although it may in some embodiments.
  • the above described body part models, skeletal models, and polygonal meshes are nonlimiting example types of models that may be used as machine representations of a modeled target.
  • Other models are also within the scope of this disclosure.
  • some models may include patches, non-uniform rational B-splines, subdivision surfaces, or other high-order surfaces.
  • a model may also include surface textures and/or other information to more accurately represent clothing, hair, and/or other aspects of a modeled target.
  • a model may optionally include information pertaining to a current pose, one or more past poses, and/or model physics. It is to be understood that any model that can be posed and then rasterized to (or otherwise rendered to or expressed by) a synthesized depth image, is compatible with the herein described target recognition, analysis, and tracking.
  • a model serves as a representation of a target, such as game player 18 in FIGs. 1A and IB.
  • information from a capture device such as depth camera 20 in FIGs. 1A and IB, can be used to adjust a pose and/or the fundamental size/shape of the model so that it more accurately represents the target.
  • one or more forces may be applied to one or more force-receiving aspects of the model to adjust the model into a pose that more closely corresponds to the pose of the target in physical space.
  • the force may be applied to a joint, a centroid of a body part, a vertex of a triangle, or any other suitable force-receiving aspect of the model.
  • two or more different calculations may be used when determining the direction and/or magnitude of the force.
  • differences between an observed image of the target, as retrieved by a capture device, and a rasterized (i.e., synthesized) image of the model may be used to determine the forces that are applied to the model in order to adjust the body into a different pose.
  • FIG. 7 shows a flow diagram of an example method 100 of tracking a target using a model (e.g., body model 70 of FIG. 3).
  • the target may be a human, and the human may be one of two or more targets being tracked.
  • method 100 may be executed by a computing system (e.g., gaming system 12 shown in FIG. 1 and/or computing system 40 shown in FIG. 2) to track one or more players interacting with an electronic game being played on the computing system.
  • a computing system e.g., gaming system 12 shown in FIG. 1 and/or computing system 40 shown in FIG. 2
  • tracking of the players allows physical movements of those players to act as a real-time user interface that adjusts and/or controls parameters of the electronic game.
  • the tracked motions of a player may be used to move an on-screen character or avatar in an electronic role-playing game.
  • the tracked motions of a player may be used to control an on-screen vehicle in an electronic racing game.
  • the tracked motions of a player may be used to control the building or organization of objects in a virtual environment.
  • method 100 includes receiving an observed depth image of the target from a source.
  • the source may be a depth camera configured to obtain depth information about the target via a suitable technique such as time-of-flight analysis, structured light analysis, stereo vision analysis, or other suitable techniques.
  • the observed depth image may include a plurality of observed pixels, where each observed pixel has an observed depth value.
  • the observed depth value includes depth information of the target as viewed from the source. Knowing the depth camera's horizontal and vertical field of view, as well as the depth value for a pixel and the pixel address of that pixel, the world space position of a surface imaged by that pixel can be determined. For convenience, the world space position of a surface imaged by the pixel may be referred to as the world space position of the pixel.
  • FIG. 8 shows a visual representation of an exemplary observed depth image 140.
  • observed depth image 140 captures an exemplary observed pose of a person (e.g., game player 18) standing with his arms raised.
  • method 100 may optionally include downsampling the observed depth image to a lower processing resolution. Downsampling to a lower processing resolution may allow the observed depth image to be more easily utilized and/or more quickly processed with less computing overhead.
  • method 100 may optionally include removing non-player background elements from the observed depth image. Removing such background elements may include separating various regions of the observed depth image into background regions and regions occupied by the image of the target. Background regions can be removed from the image or identified so that they can be ignored during one or more subsequent processing steps. Virtually any background removal technique may be used, and information from tracking (and from the previous frame) can optionally be used to assist and improve the quality of background-removal.
  • method 100 may optionally include removing and/or smoothing one or more high-variance and/or noisy depth values from the observed depth image.
  • Such high-variance and/or noisy depth values in the observed depth image may result from a number of different sources, such as random and/or systematic errors occurring during the image capturing process, defects and/or aberrations resulting from the capture device, etc. Since such high-variance and/or noisy depth values may be artifacts of the image capturing process, including these values in any future analysis of the image may skew results and/or slow calculations. Thus, removal of such values may provide better data integrity for future calculations.
  • Other depth values may also be filtered.
  • the accuracy of growth operations described below with reference to step 118 may be enhanced by selectively removing pixels satisfying one or more removal criteria. For instance, if a depth value is halfway between a hand and the torso that the hand is occluding, removing this pixel can prevent growth operations from spilling from one body part onto another during subsequent processing steps.
  • method 100 may optionally include filling in and/or reconstructing portions of missing and/or removed depth information. Such backfilling may be accomplished by averaging nearest neighbors, filtering, and/or any other suitable method.
  • method 100 may include obtaining a model (e.g., body model 70 of FIG. 3).
  • the model may include a skeleton comprising a plurality of skeletal points, one or more polygonal meshes, one or more mathematical primitives, one or more high- order surfaces, and/or other features used to provide a machine representation of the target.
  • the model may exist as an instance of one or more data structures existing on a computing system.
  • the model may be a posed model obtained from a previous time step (i.e., frame). For example, if method 100 is performed continuously, a posed model resulting from a previous iteration of method 100, corresponding to a previous time step, may be obtained. In this way, the model may be adjusted from one frame to the next based on the observed depth image for the current frame and the model from the previous frame. In some cases, the previous frame's model may be projected by a momentum calculation to yield an estimated model for comparison to the current observed depth image. This may be done without looking up a model from a database or otherwise starting from scratch every frame. Instead, incremental changes may be made to the model in successive frames.
  • a pose may be determined by one or more algorithms, which can analyze a depth image and identify, at a coarse level, where the target(s) of interest (e.g., human(s)) are located and/or the pose of such target(s). Algorithms can be used to select a pose during an initial iteration or whenever it is believed that the algorithm can select a pose more accurate than the pose calculated during a previous time step.
  • the target(s) of interest e.g., human(s)
  • Algorithms can be used to select a pose during an initial iteration or whenever it is believed that the algorithm can select a pose more accurate than the pose calculated during a previous time step.
  • the model may be obtained from a database and/or other program.
  • a model may not be available during a first iteration of method 100, in which case the model may be obtained from a database including one or more models. In such
  • model from the database may be chosen using a searching algorithm designed to select a model exhibiting a pose similar to that of the target. Even if a model from a previous time step is available, a model from a database may be used. For example, a model from a database may be used after a certain number of frames, if the target has changed poses by more than a predetermined threshold, and/or according to other criteria.
  • the model, or portions thereof may be synthesized.
  • the target's body core torso, midsection, and hips
  • that model may be originally constructed using the contents of an observed depth image, where the outline of the target in the image (i.e., the silhouette) may be used to shape the mesh in the X and Y dimensions.
  • the observed depth value(s) in that area of the observed depth image may be used to "mold" the mesh in the XY direction, as well as in the Z direction, of the model to more favorably represent the target's body shape.
  • Method 100 may further include representing any clothing appearing on the target using a suitable approach.
  • a suitable approach may include adding to the model auxiliary geometry in the form of primitives or polygonal meshes, and optionally adjusting the auxiliary geometry based on poses to reflect gravity, cloth simulation, etc.
  • Such an approach may facilitate molding the models into more realistic representations of the targets.
  • method 100 may optionally comprise applying a momentum algorithm to the model. Because the momentum of various parts of a target may predict change in an image sequence, such an algorithm may assist in obtaining the pose of the model.
  • the momentum algorithm may use a trajectory of each of the joints or vertices of a model over a fixed number of a plurality of previous frames to assist in obtaining the model.
  • knowledge that different portions of a target can move a limited distance in a time frame can be used as a constraint in obtaining a model.
  • a constraint may be used to rule out certain poses when a prior frame is known.
  • method 100 may also include rasterizing the model into a synthesized depth image. Rasterization allows the model described by mathematical primitives, polygonal meshes, or other objects to be converted into a synthesized depth image described by a plurality of pixels.
  • Rasterizing may be carried out using one or more different techniques and/or algorithms.
  • rasterizing the model may include projecting a representation of the model onto a two-dimensional plane.
  • rasterizing may include projecting and rasterizing the collection of body-part shapes onto a two-dimensional plane. For each pixel in the two dimensional plane onto which the model is projected, various different types of information may be stored.
  • FIG. 9 shows a visual representation 150 of an exemplary synthesized depth image corresponding to body model 70 of FIG. 3.
  • FIG. 10 shows a pixel matrix 160 of a portion of the same synthesized depth image.
  • each synthesized pixel in the synthesized depth image may include a synthesized depth value.
  • the synthesized depth value for a given synthesized pixel may be the depth value from the corresponding part of the model that is represented by that synthesized pixel, as determined during rasterization. In other words, if a portion of a forearm body part (e.g., forearm body part bp4 of FIG.
  • a corresponding synthesized pixel (e.g., synthesized pixel 162 of FIG. 10) may be given a synthesized depth value (e.g., synthesized depth value 164 of FIG. 10) equal to the depth value of that portion of the forearm body part.
  • synthesized pixel 162 has a synthesized depth value of 382 cm.
  • a neighboring hand body part e.g., hand body part bp3 of FIG. 3
  • a corresponding synthesized pixel (e.g., synthesized pixel 166 of FIG.
  • synthesized depth value 168 of FIG. 10 may be given a synthesized depth value (e.g., synthesized depth value 168 of FIG. 10) equal to the depth value of that portion of the hand body part.
  • synthesized pixel 166 has a synthesized depth value of 383 cm.
  • the corresponding observed depth value is the depth value observed by the depth camera at the same pixel address. It is to be understood that the above is provided as an example. Synthesized depth values may be saved in any unit of measurement or as a dimensionless number.
  • each synthesized pixel in the synthesized depth image may include an original body-part index determined during rasterization. Such an original body-part index may indicate to which of the body parts of the model that pixel corresponds.
  • synthesized pixel 162 has an original body-part index of bp4
  • synthesized pixel 166 has an original body-part index of bp3.
  • the original body-part index of a synthesized pixel may be nil if the synthesized pixel does not correspond to a body part of the target (e.g., if the synthesized pixel is a background pixel).
  • synthesized pixels that do not correspond to a body part may be given a different type of index.
  • a body-part index may be a discrete value or a probability distribution indicating the likelihood that a pixel belongs to two or more different body parts.
  • each synthesized pixel in the synthesized depth image may include an original player index determined during rasterization, where the original player index corresponds to the target. For example, if there are two targets, synthesized pixels corresponding to the first target will have a first player index and synthesized pixels corresponding to the second target will have a second player index.
  • the pixel matrix 160 corresponds to only one target, therefore synthesized pixel 162 has an original player index of PI, and synthesized pixel 166 has an original player index of PI.
  • Other types of indexing systems may be used without departing from the scope of this disclosure.
  • each synthesized pixel in the synthesized depth image may include a pixel address.
  • the pixel address may define the position of a pixel relative to other pixels.
  • synthesized pixel 162 has a pixel address of [5,7]
  • synthesized pixel 166 has a pixel address of [4,8] . It is to be understood that other addressing schemes may be used without departing from the scope of this disclosure.
  • each synthesized pixel may optionally include other types of information, some of which may be obtained after rasterization.
  • each synthesized pixel may include an updated body-part index, which may be determined as part of a snap operation performed during rasterization, as described below.
  • Each synthesized pixel may include an updated player index, which may be determined as part of a snap operation performed during rasterization.
  • Each synthesized pixel may include an updated body-part index, which may be obtained as part of a grow/fix operation, as described below.
  • Each synthesized pixel may include an updated player index, which may be obtained as part of a grow/fix operation, as described above.
  • Each synthesized pixel may include an updated synthesized depth value, which may be obtained as part of the snap operation.
  • pixel information provided above are not limiting.
  • Various different types of information may be stored as part of each pixel.
  • Such information may include information obtained from the depth image, information obtained from rasterizing the machine-readable model, and/or information derived from one or more processing operations (e.g., snap operation, grow operation, etc.).
  • processing operations e.g., snap operation, grow operation, etc.
  • Such information can be stored as part of a common data structure, or the different types of information may be stored in different data structures that can be mapped to particular pixel locations (e.g., via a pixel address).
  • player indices and/or body-part indices obtained as part of a snap operation during rasterization may be stored in a rasterization map and/or a snap map
  • player indices and/or body-part indices obtained as part of a grow/fix operation after rasterization may be stored in a grow map, as described below.
  • Nonlimiting examples of other types of pixel information that may be assigned to each pixel include, but are not limited to, joint indices, bone indices, vertex indices, triangle indices, centroid indices, and the like.
  • observed pixels may be used to represent observed information obtained from a depth camera or other source.
  • data may be used to represent information that is rasterized, derived, calculated, or otherwise synthesized.
  • observed data e.g., an observed depth value
  • synthesized data e.g., a synthesized depth value
  • method 100 of FIG. 7 may optionally include snapping and/or growing the body-part indices and/or player indices.
  • the synthesized depth image may be augmented so that the body-part index and/or player index of some pixels are changed in an attempt to more closely correspond to the modeled target.
  • indices derived from the snap operation or the indices derived from the grow operation, it is to be understood that any one or more of these indices may be used, as well as other indices obtained from other suitable methods of estimating the player and/or body part to which that pixel belongs.
  • Buffers and/or body-part/player index maps may be constructed.
  • a first version of such a buffer/map may be constructed by performing a Z-test in which a forward-most surface closest to the viewer (e.g., depth camera) at each pixel is selected and a body-part index and/or player index associated with that surface is written to the corresponding pixel.
  • This map may be referred to as the rasterization map or the original synthesized depth map, and this map may include the original body-part index for each pixel.
  • a second version of such a buffer/map may be constructed by performing a Z-test in which a surface of the model that is closest to an observed depth value at that pixel is selected and a body-part index and/or player index associated with that surface is written to the corresponding pixel.
  • This may be referred to as the snap map, and this map may include the snap body-part index for each pixel.
  • Such tests may be constrained so as to reject a Z- distance between a synthesized depth value and an observed depth value that is beyond a predetermined threshold.
  • two or more Z-buffers and/or two or more body-part/player index maps may be maintained, thus allowing two or more of the above described tests to be carried out.
  • a third version of a buffer/map may be constructed by growing and/or correcting a body-part/player index map. This may be referred to as a grow map.
  • the values may be grown over any "unknown" values within a predetermined Z- distance, so that a space being occupied by the target, but not yet occupied by the body model, may be filled with proper body-part/player indices.
  • Such an approach may further include overtaking a known value if a more favorable match is identified.
  • the grow map may begin with a pass over synthesized pixels of the snap map to detect pixels having neighboring pixels with a different body- part/player index. These may be considered “edge" pixels, i.e., frontiers along which values may optionally be propagated.
  • growing the pixel values may include growing into either "unknown” or "known” pixels.
  • the body-part/player index value for example, in one scenario, may have been zero before, but may now have a non-zero neighboring pixel.
  • the four direct neighboring pixels may be examined, and the neighboring pixel having an observed depth value more closely resembling that of the pixel of interest may be selected and assigned to the pixel of interest.
  • a pixel with a known nonzero body-part/player index value may be overtaken, if one of its neighboring pixels has a depth value written during rasterization that more closely matches the observed depth value of the pixel of interest than that of the synthesized depth value for that pixel.
  • updating a body-part/player index value of a synthesized pixel may include adding its neighboring four pixels to a queue of pixels to be revisited on a subsequent pass. As such, values may continue to be propagated along the frontiers without doing an entire pass over all the pixels.
  • different NxN blocks of pixels e.g., 16x16 blocks of pixels
  • occupied by a target of interest can be tracked so that other blocks that are not occupied by a target of interest can be ignored.
  • Such an optimization may be applied at any point during the target analysis after rasterization in various forms.
  • grow operations may take a variety of different forms. For example, various flood-fills may first be performed to identify regions of like values, and then it can be decided which regions belong to which body parts. Furthermore, the number of pixels that any body-part/player index object (e.g., left forearm body part bp4 of FIG. 3) can grow may be limited based on how many pixels such an object is expected to occupy (e.g., given its shape, distance and angle) vs. how many pixels in the snap map were assigned that body-part/player index. Additionally, the aforementioned approaches may include adding advantages or disadvantages, for certain poses, to bias the growth for certain body parts so that the growth may be correct.
  • any body-part/player index object e.g., left forearm body part bp4 of FIG. 3
  • the aforementioned approaches may include adding advantages or disadvantages, for certain poses, to bias the growth for certain body parts so that the growth may be correct.
  • a progressive snap adjustment can be made to the snap map if it is determined that a distribution of pixels from a body part is grouped at one depth, and another distribution of pixels from the same body part is grouped at another depth, such that a gap exists between these two distributions. For example, an arm waving in front of a torso, and near to that torso, may "spill into” the torso. Such a case may yield a group of torso pixels with a body-part index indicating that they are arm pixels, when in fact they should be torso pixels. By examining the distribution of synthesized depth values in the lower arm, it may be determined that some of the arm pixels may be grouped at one depth, and the rest may be grouped at another depth.
  • the gap between these two groups of depth values indicates a jump between arm pixels and what should be torso pixels.
  • the spillover may then be remedied by assigning torso body-part indices to the spillover pixels.
  • a progressive snap adjustment can be helpful in an arm-over-background-object case.
  • a histogram can be used to identify a gap in the observed depth of the pixels of interest (i.e., pixels thought to belong to the arm). Based on such a gap, one or more groups of pixels can be identified as properly belonging to an arm and/or other group(s) can be rejected as background pixels.
  • the histogram can be based on a variety of metrics, such as absolute depth; depth error (synthesized depth— observed depth), etc.
  • the progressive snap adjustment may be performed in ⁇ line during rasterization, prior to any grow operations.
  • method 100 of FIG. 7 may optionally include creating a height map from the observed depth image, the synthesized depth image, and the body-part/player index maps at the three stages of processing described above.
  • the gradient of such a height map, and/or a blurred version of such a height map may be utilized when determining the directions of adjustments that are to be made to the model, as described hereafter.
  • the height map is merely an optimization, however! alternatively or additionally, a search in all directions may be performed to identify nearest joints where adjustments may be applied and/or the direction in which such adjustments are to be made.
  • a height map it may be created before, after, or in parallel to the pixel class determinations described below.
  • the height map When used, the height map is designed to set the player's actual body at a low elevation and the background elements at a high elevation.
  • a watershed- style technique can then be used to trace "downhill” in the height map, to find the nearest point on the player from the background, or vice versa (i.e., seek "uphill” in the height map to find the nearest background pixel to a given player pixel).
  • the synthesized depth image and the observed depth image may not be identical, and thus the synthesized depth image can use adjustments and or modifications so that it more closely matches an observed depth image and can thus more accurately represent the target. It is to be understood that adjustments can be made to the synthesized depth image by first making adjustments to the model (e.g., change the pose of the model), and then synthesizing the adjusted model into a new version of the synthesized depth image.
  • adjustments can be made to the synthesized depth image by first making adjustments to the model (e.g., change the pose of the model), and then synthesizing the adjusted model into a new version of the synthesized depth image.
  • a number of different approaches may be taken to modify a synthesized depth image.
  • two or more different models may be obtained and rasterized to yield two or more synthesized depth images.
  • Each synthesized depth image may then be compared to the observed depth image by a predetermined set of comparison metrics.
  • the synthesized depth image demonstrating a closest match to the observed depth image may be selected, and this process may be optionally repeated in order to improve the model.
  • this process can be particularly useful for refining the body model to match the player's body type and/or dimensions.
  • the two or more synthesized depth images may be blended via interpolation or extrapolation to yield a blended synthesized depth image.
  • two or more synthesized depth images may be blended in such a way that the blending techniques and parameters vary across the blended synthesized depth image.
  • the pose selected in the blended synthesized depth image could be a mixture resembling the pose used to create the first synthesized depth image in the first region, and the pose used to create the second synthesized depth image in the second region.
  • the synthesized depth image may be compared to the observed depth image.
  • Each synthesized pixel of the synthesized depth image may be classified based on the results of the comparison. Such classification may be referred to as determining the pixel case for each pixel.
  • the model used to create the synthesized depth image e.g., body model 70 of FIG. 3 may be systematically adjusted in accordance with the determined pixel cases.
  • one or more pixel cases may be selected for each synthesized pixel based on a comparison to a corresponding pixel of the observed image having a same pixel address as the synthesized pixel.
  • the comparison may be based on one or more factors, which include, but are not limited to - the difference between an observed depth value and a synthesized depth value for that synthesized pixel; the difference between the original body-part index, the (snap) body-part index, and/or the (grow) body/part index for that synthesized pixel; and/or the difference between the original player index, the (snap) player index, and/or the (grow) player index for that synthesized pixel.
  • the pixel case may be selected from a set of defined pixel cases, as described in more detail with reference to 124-136 of FIG. 7.
  • FIG. 13 shows an example of a synthesized depth image (e.g., synthesized depth image 150 of FIG. 9) analytically compared with a corresponding observed depth image (e.g., observed depth image 140 of FIG. 8), for determining pixel mismatches and thus identifying pixel cases.
  • Synthesized pixels of synthesized depth image 150 corresponding to the model are represented in FIG. 13 by a synthesized silhouette 200 depicted in solid line
  • the observed pixels of observed depth image 140 corresponding to the target are represented in FIG. 13 by an observed silhouette 202 depicted in dashed line.
  • an observed silhouette 202 depicted in dashed line may be an analytical comparison of information corresponding to each pixel address such as depicted at FIG. 10.
  • each synthesized pixel may be associated with a pixel case.
  • a pixel case may be selected from a set of defined pixel cases such as a refine-z pixel case, a magnetism pixel case, a push pixel case, a pull pixel case, a self-occluding push and/or pull pixel case, etc.
  • FIG. 14 shows example regions of synthesized pixels of synthesized silhouette 200 having pixel mismatches (e.g., depth value of observed depth image different than depth value of synthesized image by more than a threshold amount), indicated in diagonal-line shading such as shown at 204.
  • pixel mismatches e.g., depth value of observed depth image different than depth value of synthesized image by more than a threshold amount
  • the model represented in the synthesized depth image may be adjusted so that the model better represents the target.
  • FIG. 15 shows another example comparison 206 of a synthesized depth image and a corresponding observed depth image, wherein different pixel cases have been selected for different regions of synthesized pixels.
  • Region 208 includes one or more portions of the model that are shifted forward or backward in a depth direction (i.e., Z-shifted) from a corresponding portion or portions of the observed depth image.
  • region 208 may correspond to pixels having a refine-z pixel case.
  • the regions identified by diagonal shading, such as example region 210 indicate portions of the model shifted away from a silhouette of the human target in the observed depth image.
  • region 210 may correspond to pixels having a push pixel case.
  • regions identified by horizontal shading such as example region 212
  • region 212 may correspond to pixels having a pull pixel case.
  • regions identified by cross-hatch shading such as example region 214, indicate portions of the model such as arms and/or hands that correspond to pixels having a magnetism pixel case.
  • a pixel case may be selected from a set of defined pixel cases such as a refine-z pixel case, a magnetism pixel case, a push pixel case, a pull pixel case, a self-occluding push and/or pull pixel case, etc.
  • the synthesized pixels of the model having these pixel mismatches may then be corrected by adjusting the model to more closely match the observed image.
  • Such adjustments may be made, for example, by applying forces to the model to reposition the model into a different pose that more closely matches the observed image.
  • forces may be applied via force vectors having a magnitude and a direction, which may be applied to a force-receiving location of the model, as indicated at 141, 142 and 144 of FIG. 7.
  • the computation and application of each force vector may be based on the pixel case.
  • Such a force vector may be derived from a single pixel address or from a group of two or more related pixel addresses (e.g., neighboring pixel addresses with matching values— body-part indices, player indices, etc.). Examples of the pixel cases and associated force vectors are discussed hereafter in more detail.
  • determining a pixel case may include selecting a refine-z pixel case.
  • the refine-z pixel case may be selected when the observed depth value of an observed pixel (or in a region of observed pixels) of the observed depth image does not match the synthesized depth value(s) in the synthesized depth image, but is close enough to likely belong to the same object in both images, and the body-part indices match (or, in some cases, correspond to neighboring body parts or regions).
  • a refine-z pixel case may be selected for a synthesized pixel if a difference between an observed depth value and a synthesized depth value for that synthesized pixel is within a predetermined range and, optionally, if that synthesized pixel's (grow) body part index corresponds to a body part that has not been designated for receiving magnetism forces.
  • a synthesized pixel of interest may be classified with a refine-z pixel case if the synthesized depth value does not match the observed depth value, and an absolute difference between the synthesized depth value and the observed depth value is less than a predetermined threshold.
  • the refine-z pixel case corresponds to a computed force vector that may exert a force on the model to move the model into the correct position.
  • a refine-z force vector may be applied to one or more force-receiving locations of the model to move a portion of the model towards a corresponding portion of the observed depth image (e.g., in a direction along the Z axis and perpendicular to an image plane).
  • the computed force vector may be applied along the Z axis perpendicular to the image plane, along a vector normal to an aspect of the model (e.g., face of the corresponding body part), and/or along a vector normal to nearby observed pixels.
  • the computed force vector may be applied to a combination of a vector normal to the face of the corresponding body part and a vector normal to nearby observed pixels.
  • a combination may be an average, a weighted average, a linear interpolation, etc.
  • the magnitude of the force vector is based on the difference in the observed and synthesized depth values, with greater differences corresponding to larger forces.
  • the force vector may increase in proportion to the absolute difference between the synthesized depth value and the observed depth value.
  • the force-receiving location to which the force is applied can be selected to be the nearest qualifying force-receiving location to the pixel of interest (e.g., nearest torso joint), or the force can be distributed among a weighted blend of the nearest qualifying force-receiving locations.
  • the nearest qualifying force-receiving location may be chosen, however, in some cases, the application of biases can be helpful. For example, if a pixel lies halfway down the upper leg, and it has been established that the hip joint is less mobile (or agile) than the knee, it may be helpful to bias the joint forces for mid-leg pixels to act on the knee rather than the hip. Additional examples of biases are described hereafter.
  • the nearest qualifying force-receiving location for a refine-z pixel case may be determined by comparing a distance between the synthesized pixel of interest and each qualifying force-receiving location.
  • the nearest qualifying force-receiving location may be determined, for example, by comparing a distance between the synthesized pixel of interest and each qualifying force-receiving location on a body part that is associated with a body-part index of the synthesized pixel of interest.
  • the force vector may be one of a plurality of force vectors applied to a weighted blend of nearest qualifying force-receiving locations.
  • the force vector may be biased, for example, towards relatively more mobile qualifying force-receiving locations. For example, application of the force vector may be biased to a less-than-nearest qualifying force-receiving location that is more mobile than the nearest qualifying force-receiving location.
  • the determination of which force-receiving location is nearest to the pixel of interest can be found by a brute-force search, with or without the biases mentioned above.
  • the set of force-receiving locations searched may be limited to only those on or near the body part that is associated with the body-part index of this pixel.
  • BSP binary space partitioning
  • Each region on the body, or each body part corresponding to a body-part index, may be given its own BSP tree. If so, the biases can be applied differently for each body part, which further enables wise selection of the proper force-receiving locations.
  • determining a pixel case may include selecting a magnetism pixel case.
  • the magnetism pixel case may be utilized when the synthesized pixel being examined, in the grow map, corresponds to a predetermined subset of the body parts (e.g., the arms, or bp3, bp4, bp5, bp7, bp8, and bp9 of FIG. 3). While the arms are provided as an example, other body parts, such as the legs or the entire body, may optionally be associated with the magnetism pixel case in some scenarios. Likewise, in some scenarios, the arms may not be associated with the magnetism pixel case.
  • the pixels marked for the magnetism case may be grouped into regions, each region being associated with a specific body part (such as, in this example, upper left arm, lower left arm, left hand, and so on).
  • a grow operation such as described above may be completed prior to the processing of magnetism pixels.
  • each pixel may be "tagged" with the body part of the target which most likely corresponds to that pixel.
  • one or more pixels may be tagged with the wrong body part (i.e., mis-tagged) during the grow operation.
  • a motion predictor may not be capable of completing a prediction, and as a result, fast-moving hand pixels may not be added into the snap map, whereas slower upper-arm pixels near the shoulder may still be added to the snap map.
  • limb pixels further from the shoulder may have relatively more error in the assignment of body-part indices.
  • lower-arm pixels may grow down into the hand area during the grow operation.
  • upper-arm pixels added to the snap map may be grown down into the lower-arm and the hand areas.
  • pixels corresponding to the hand of the human target may be labeled as "lower-arm” or all the arm pixels may be labeled “upper-arm.” Therefore, it may be useful to discard this information when processing magnetism, described in more detail as follows.
  • the grow operation may incorrectly identify which part of the limb the pixels belong to, the original body-part assigned to the pixels identifying the limb itself tends to be of higher confidence.
  • a lower arm pixel may be incorrectly associated with an upper arm, the fact that the pixel corresponds to some part of the arm is still correct.
  • the subset classification assigned during the grow operation may be dropped.
  • magnetism pixels may be grouped into broader classes (i.e. "pools"), such as "left arm,” “right arm” and “other.” The pixels in the left arm and right arm pools may then be marked as belonging to the magnetism pixel case.
  • the above is a nonlimiting example, and other methods of identifying arm pixels or other pixels belonging to agile body parts may be used.
  • the pixel's location may be converted from a screen-space location, having an X, Y pixel position and a depth value, to a world-space location having coordinates identifying the location in a three-dimensional space. It can be appreciated that this is just one embodiment for processing pixels. In other embodiments, the pixel's screen-space location may not be converted to a world- space location.
  • the pixel may be projected onto the "bones" that make up the arm of the model and are represented as line segments.
  • the pixel may be projected onto a current, best-guess version of the bone.
  • This best-guess version of the bone may come from the previous frame's final pose, with or without momentum! or it may be updated with any adjustments made during the current frame (e.g., run refine-z pixel case to adjust bone, and then use adjusted bone for magnetism pixels).
  • joints may be progressively updated at any point during the processing of a frame, and the updated joints may be used for subsequent processing in the current or subsequent frames.
  • the arm may comprise three bone segments, namely an upper arm bone, a lower arm bone, and a hand.
  • a point on the finite line segment that is closest to the pixel may be analytically determined. In some embodiments, this may include comparing pixels against three-dimensional joint positions that are pulled forward in the Z-direction by the estimated radius of the limb at that joint, so that the comparison is of two surface values rather than of a surface value and an internal value.
  • the pixel may then be assigned to that closest line segment. In some embodiments, the pixel may be assigned to a different line segment if it is determined that the closest line segment may be incorrect.
  • a pixel that is sufficiently far from the shoulder may have the closest line segment overridden to be the lower-arm bone.
  • the pixel's location may be added to the "near" and "far" centroids of that bone, described in more detail as follows.
  • centroids of the pixels belonging to the region may be computed. These centroids can be either orthodox (all contributing pixels are weighted equally), or biased, where some pixels carry more weight than others. For example, for the upper arm, three centroids may be tracked: l) an unbiased centroid, 2) a "near" centroid, whose contributing pixels are weighted more heavily when they are closer to the shoulder! and 3) a "far" centroid, whose contributing pixels are weighted more heavily when closer to the elbow. These weightings may be linear (e.g., 2X) or nonlinear (e.g., x 2 ) or follow any curve.
  • centroids are computed, a variety of options are available (and can be chosen dynamically) for computing the position and orientation of the body part of interest, even if some are partially occluded. For example, when trying to determine the new position for the elbow, if the centroid in that area is sufficiently visible (if the sum of the weights of the contributing pixels exceeds a predetermined threshold), then the centroid itself marks the elbow (estimate #l). However, if the elbow area is not visible (perhaps because it is occluded by some other object or body part), the elbow location can still often be determined, as described in the following nonlimiting example.
  • a selection of one of the three potential estimates can be made, or a blend between the three potential estimates may be made, giving priority (or higher weight) to the estimates that have higher visibility, confidence, pixel counts, or any number of other metrics.
  • a single magnetism force vector may be applied to the model at the location of the elbow! however, it may be more heavily weighted (when accumulated with the pixel force vectors resulting from other pixel cases, but acting on this same force-receiving location), to represent the fact that many pixels were used to construct it.
  • the computed magnetism force vector may move the model so that the corresponding model more favorably matches the target shown in the observed image.
  • a model without defined joints or body parts may be adjusted using only the magnetism pixel case.
  • determining a pixel case may include selecting a push pixel case and/or a pull pixel case. These pixel cases may be invoked at the silhouette, where the synthesized and observed depth values may be severely mismatched at the same pixel address. It is noted that the pull pixel case and the push pixel case can also be used when the original player index does not match the (grow) player index.
  • the determination of push vs. pull is as follows. If the synthesized depth image contains a depth value that is greater than (farther than) the depth value in the observed depth image at that same pixel address, for example by more than a threshold amount, then the model can be pulled toward the true silhouette seen in the grown image.
  • the model may be pulled in an XY plane towards the silhouette of the target in the observed depth image.
  • pull force vectors applied to one or more force-receiving locations of the model may be used to "pull" the model.
  • FIG. 16 illustrates an example of such a pull pixel case, and is described in more detail as follows.
  • FIG. 16 schematically illustrates an example observed depth image 220 compared with an example synthesized depth image 222, as indicated at 224.
  • the pixel addresses of synthesized depth image 222 correspond to those of observed depth image 220.
  • FIG. 16 depicts an exaggerated example where observed depth image 220 and synthesized depth image 222 are clearly mismatched.
  • the two images may only be mismatched by a relatively small amount and mismatches as severe as that illustrated may be difficult to resolve.
  • Observed depth image 220 includes an image of an observed human target (i.e., game player), namely, player image 226, wherein the player image 226 has a silhouette, namely player silhouette 228, such that pixels inside player silhouette 228 are pixels of the player image 226 and pixels outside of player silhouette 228 are pixels of the observed background 230.
  • synthesized depth image 222 includes a model 232 representing the observed game player, wherein the model 232 has a silhouette, namely model silhouette 234, such that pixels inside model silhouette 234 are pixels of the model 232 and pixels outside of model silhouette 234 are pixels of the synthesized background 236.
  • synthesized depth image 222 Upon comparing synthesized depth image 222 with observed depth image 220, it becomes more apparent that a mismatch exists, such that pixels at a same pixel address correspond to different parts of each depth image.
  • an example pixel is selected for discussion, namely synthesized pixel of interest 238.
  • synthesized pixel of interest 238 corresponds to synthesized background 236 of synthesized depth image 222.
  • a same pixel address in the corresponding observed depth image corresponds to an observed pixel 240 associated with the player image 226.
  • synthesized pixel of interest 238 has a greater depth value than that of the corresponding observed pixel 240 since the background is at greater depth (i.e., farther from the depth camera) than the game player.
  • model 232 may be pulled toward the synthesized pixel of interest 238 (i.e., toward player silhouette 228) as indicated by arrow 240.
  • the model can be pushed out of the space that the player no longer occupies (and toward the real silhouette in the grown image).
  • the model may be pushed in an XY plane towards the silhouette of the human target in the observed depth image.
  • push force vectors applied to one or more force-receiving locations of the model may be used to "push" the model.
  • FIG. 17 illustrates an example of such a push pixel case, and is described in more detail as follows.
  • FIG. 17 schematically illustrates a comparison similar to that shown in FIG. 16, namely a comparison of synthesized depth image 222 and observed depth image 220.
  • a different synthesized pixel of interest is examined, namely synthesized pixel of interest 250.
  • Synthesized pixel of interest 250 corresponds to model 232 of synthesized depth image 222, whereas at a same pixel address in the corresponding observed depth image 220, observed pixel 252 is associated with observed background 230.
  • synthesized pixel of interest 250 has a lesser depth value than that of the corresponding observed pixel 252 since the model is at a lesser depth (i.e. closer to the depth camera) than the background.
  • model 222 may be pushed away from the synthesized pixel of interest 250 (i.e. toward player silhouette 228) as indicated by arrow 254.
  • a two- or three- dimensional computed force vector may be exerted on the model to correct the silhouette mismatch, either pushing or pulling parts of the body model into a position that more accurately matches the position of the target in the observed depth image.
  • the direction of such pushing and/or pulling is often predominantly in the XY plane, although a Z component can be added to the force in some scenarios. Accordingly, in some cases the push force vectors and/or the pull force vectors may be three-dimensional vectors including Z- components.
  • a pull force vector may be applied to a force-receiving location of model 232 to pull model 232 toward the player silhouette 228 in the observed depth image.
  • a magnitude of the pull force vector may be proportional to a pull-offset distance with which a portion of the observed depth image is shifted away from the silhouette of the model.
  • a pull-offset distance Dl may be defined as a distance between the synthesized pixel of interest (e.g., pixel 238) and a nearest qualifying pixel of model silhouette 234.
  • the magnitude of the pull force vector, D2 may be a function of the pull-offset distance Dl, as described in more detail hereafter.
  • a direction of the pull force vector may be parallel to a vector extending from the nearest qualifying pixel on model silhouette 234 to the synthesized pixel of interest 238.
  • a push force vector may be applied to a force-receiving location of model 232 to push model 232 towards the player silhouette 228 in the observed depth image 220.
  • a magnitude of the push force vector may be proportional to a push-offset distance with which a portion of the model is shifted away from the player silhouette 228.
  • a push-offset distance Dl may be defined as a distance between the synthesized pixel of interest, (e.g., pixel 250), and a nearest qualifying pixel of player silhouette 228.
  • the magnitude of the push force vector, D2 may be a function of the push-offset distance Dl as described in more detail hereafter.
  • a direction of the push force vector may be parallel to a vector extending from the synthesized pixel of interest 250 to the nearest qualifying pixel on the player silhouette 228.
  • the nearest qualifying point on either the player silhouette in the synthesized depth image (i.e., model silhouette) (for a pull case), or on the player silhouette in the observed depth image (for a push case) may first be found. This point can be found, for each source pixel (or for each group of source pixels), by performing a brute-force, exhaustive 2D search for the nearest point (on the desired silhouette) that meets the following criteria.
  • the closest pixel with a player index in the original map (at the seek position) that matches the player index in the grown map (at the source pixel or region) is found.
  • the closest pixel with a player index in the grown map (at the seek position) that matches the player index in the original map (at the source pixel or region) is found.
  • a nearest qualifying pixel on the model silhouette 234 and/or a nearest qualifying pixel on the player silhouette 228 may be found using a one dimensional search along the gradient of the blurred height map. Further, the nearest qualifying pixel on the model silhouette 234 may be found by testing model silhouette pixels near the silhouette pixel found using the one dimensional search. Likewise, the nearest qualifying pixel on the player silhouette 228 may be found by testing player silhouette pixels near the silhouette pixel found using the one dimensional search.
  • Other basic optimizations for this seek operation include skipping pixels, using interval halving, or using a slope-based approach; re ⁇ sampling the gradient, at intervals, as the seek progresses! as well as checking nearby for better/closer matches (not directly along the gradient) once the stopping criteria are met.
  • Some search strategies may choose the nearest qualifying pixel from a subset of candidate pixels satisfying one or more selection criteria, such as pixels having a certain body-part index.
  • D2 (Dl - 0.5 pixels) * 2.
  • Dl may either a pull- offset distance or a push-offset distance.
  • D2 may be a magnitude of a pull force vector or a push force vector, respectively.
  • the pull-offset distance and/or a push-offset distance may be found using the one dimensional search along the gradient of the blurred height map as described above.
  • each pixel in this gap may perform a small "seek" and produce a force vector.
  • the pixels near the real silhouette may seek by only 1 pixel to reach the silhouette, so the force magnitude at those pixels will be (l -
  • the final force vector for each source pixel, may then be constructed with a direction and a magnitude (i.e., length).
  • a direction is determined by the vector from the silhouette pixel to the source pixel! for push pixels, it is the opposite vector.
  • the length of this force vector is D2.
  • the force may be applied to a best- qualifying (e.g., nearest) force-receiving location (or distributed between several), and these forces can be averaged, at each force-receiving location, to produce the proper localized movements of the body model.
  • the force-receiving location may be a joint of the model.
  • determining a pixel case may include selecting a self-occluding push and/or pull pixel case.
  • a body part may be moving in the foreground relative to a background or another target
  • the self-occluding push and pull pixel cases consider the scenarios where the body part is in front of another body part of the same target (e.g., one leg in front of another, arm in front of torso, etc.).
  • these cases may be identified when the pixel's (snap) player index matches its corresponding (grow) player index , but when the (snap) body-part index does not match its corresponding (grow) body-part index.
  • the seek direction may be derived in several ways. As nonlimiting examples, a brute-force 2D search may be performed; a second set of "occlusion" height maps may be tailored for this case so that a gradient can guide a ID search; or the direction may be set toward the nearest point on the nearest skeletal member. Details for these two cases are otherwise similar to the standard pull and push cases.
  • Push, pull, self- occluding push, and/or self-occluding pull pixel cases may be selected for a synthesized pixel if that synthesized pixel's (grow) body part index corresponds to a body part that has not been designated for receiving magnetism forces.
  • a single pixel may be responsible for one or more pixel cases.
  • a pixel may be responsible for both a self- occluding push pixel force and a refine-z pixel force, where the self-occluding push pixel force is applied to a force-receiving location on the occluding body part and the refine-z pixel force is applied to a force-receiving location on the body part being occluded.
  • determining a pixel case may include selecting no pixel case for a synthesized pixel. Oftentimes a force vector will not need to be calculated for all synthesized pixels of the synthesized depth image. For example, synthesized pixels that are farther away from the body model shown in the synthesized depth image, and observed pixels that are farther away from the target shown in the observed depth image (i.e., background pixels), may not influence any force-receiving locations or body parts. A pixel case need not be determined for such pixels, although it can be in some scenarios.
  • a difference between an observed depth value and a synthesized depth value for that synthesized pixel may be below a predetermined threshold value (e.g., the model already matches the observed image).
  • a pixel case need not be determined for such pixels, although it can be in some scenarios.
  • method 100 of FIG. 7 includes, for each synthesized pixel for which a pixel case has been determined, computing a force vector based on the pixel case selected for that synthesized pixel.
  • each pixel case corresponds to a different algorithm and/or methodology for selecting the magnitude, direction, and/or force-receiving location of a force vector.
  • a force vector (magnitude and direction) may be calculated for each synthesized pixel based on the determined pixel case and, depending on the type of model, the computed force vector can be applied to a nearest qualifying joint, a centroid of a body part, a point on a body part, a vertex of a triangle, or another predetermined force-receiving location of the model used to generate the synthesized depth image.
  • the force attributed to a given pixel can be distributed between two or more force-receiving locations on the model.
  • the force vectors may be computed and/or accumulated in any coordinate space, such as world space, screen space (pre-Z-divide), projection space (post-Z-divide), model space, and the like.
  • a magnitude of the push and/or pull force vector may be proportional to a push-offset distance and/or pull-offset distance, respectively.
  • a magnitude of the refine-z force vector may be based on the absolute difference between the synthesized depth value and the observed depth value, such that the refine-z force vector increases in proportion to that absolute difference.
  • the force vector may depend on a synthesized pixel's proximity to a bone segment, as well as the centroids of the corresponding limb.
  • method 100 includes mapping each computed force vector to one or more force-receiving locations of the model.
  • Mapping may include mapping a computed force vector to a "best-matching" force-receiving location.
  • the selection of a best-matching force-receiving location of the model is dependent on the pixel case selected for the corresponding pixel.
  • the best- matching force-receiving location may be the nearest joint, vertex, or centroid, for example.
  • moments i.e., rotational forces
  • a single pixel may be responsible for two or more different force vectors.
  • a pixel may be identified as a limb pixel occluding the torso after the snap operation, but the same pixel may then be identified as a torso pixel after the grow operation (i.e., the limb has moved from that pixel address).
  • the pixel may be responsible for a push force to the limb to push the limb out of the way and a refine-z force to the torso to move the torso to the proper depth.
  • two or more pixel forces may result from a single pixel if the pixel lies between two or more joints. For example, a mid-calf pixel may move both the ankle and the knee.
  • combinations of the original player index, snap player index, grow player index, original body-part index, snap body-part index, grow body-part index, synthesized depth value, snap depth value, observed depth value, and/or other observed or synthesized data for a given pixel address may be used to determine one or more pixel cases for that pixel address.
  • FIG. 18 shows a table detailing an example relationship between the pixel cases described above and the joints illustrated in skeletal model 82 of FIG. 5 to which the force vectors may be mapped.
  • Pixel cases 1-7 are abbreviated in the table as follows ⁇ 1-Pull (regular), 2-Pull (occlusion), 3-Push (regular), 4-Push (occlusion), 5-Refine-Z, 6-Magnetic Pull, and 7-Occlusion (no action).
  • a "Yes" entry in the "Receives Forces?” column indicates that the joint of that row may receive forces from a force vector.
  • An "X" entry in a pixel cases column denotes that the joint of that row may receive a force from a force vector corresponding to the pixel case of that column.
  • the table is provided as an example. It is not to be considered limiting. Other relationships between models and pixel cases may be established without departing from the scope of this disclosure.
  • translations may result from forces with similar directions acting on the force-receiving locations of a model
  • rotations may result from forces of different directions acting on the force-receiving locations of a model.
  • some of the components of the force vectors may be used to deform the model within its deformation limits, and the remaining components of the force vectors may be used to translate and/or rotate the model.
  • force vectors may be mapped to the best- matching rigid or deformable object, sub-object, and/or set of polygons of an object. Accordingly, some of the force vectors may be used to deform the model, and the remaining components of the force vectors may be used to perform rigid translation of the model. Such a technique may result in a "broken" model (e.g., an arm could be severed from the body). As discussed in more detail below, a rectification step may then be used to transform translations into rotations and/or apply constraints in order to connect body parts back together along a low-energy path.
  • 142 of method 100 includes mapping more than one force vector. For example, a first synthesized pixel having a body-part index corresponding to an arm of the human target may have been classified with a first pixel case, and a second synthesized pixel having a body-part index corresponding to a torso of the human target may have been classified with a second pixel case.
  • first force vector for the first synthesized pixel may be computed in accordance with the first pixel case
  • a second force vector for the second synthesized pixel may be computed in accordance with the second pixel case.
  • the first force vector may be mapped to a first force-receiving location of the model, where the first force-receiving location corresponds to the arm of the human target.
  • the second force vector may be mapped to a second force- receiving location of the model, where the second force-receiving location corresponds to the torso of the human target.
  • FIGs. 11A and 11B show a very simplified example of applying force vectors to a model - in the illustrated example, a skeletal model 180.
  • a skeletal model 180 For the sake of simplicity, only two force vectors are shown in the illustrated example.
  • Each such force vector may be the result of the summation of two or more different force vectors resulting from the pixel case determinations and force vector calculations of two or more different pixels.
  • a model will be adjusted by many different force vectors, each of which is the sum of many different force vectors resulting from the pixel case determinations and force vector calculations of many different pixels.
  • FIG. 11A shows a skeletal model 180, where force vector 182 is to be applied to joint jl8 (i.e., an elbow) and force vector 184 is to be applied to joint j20 (i.e., a wrist), for the purpose of straightening one arm of skeletal model 180 to more closely match an observed depth image.
  • FIG. 11B shows skeletal model 180 after the forces are applied.
  • FIG. 11B illustrates how the applied forces adjust the pose of the model.
  • the lengths of the skeletal members may be preserved.
  • the position of joint j2 remains at the shoulder of the skeletal model, as expected for the case of a human straightening their arm.
  • the skeletal model remains intact after the forces have been applied. Maintaining the integrity of the skeletal model when applying forces results from one or more constraints being applied, as discussed in more detail hereafter. A variety of different constraints can be enforced to maintain the integrity of different possible model types.
  • method 100 of FIG. 7 optionally includes rectifying the model to a pose satisfying one or more constraints.
  • the computed force vectors may then be applied to the model. If performed without constraint, this may "break” the model, stretching it out of proportion and/or moving body parts into invalid configurations for the actual body of the target. Iterations of various functions may then be used to "relax" the new model position into a "nearby" legal configuration.
  • constraints may be gently and/or gradually applied to the pose, in order to limit the set of poses to those that are physically expressible by one or more actual bodies of one or more targets. In other embodiments, such a rectifying step may be done in a non-iterative manner.
  • the constraints may include one or more of : skeletal member length constraints, joint angle constraints, polygon edge angle constraints, and collision tests, as described hereafter.
  • skeletal member i.e., bone
  • Force vectors that can be detected i.e., force vectors at locations where joints and/or body parts are visible and not occluded
  • the propagated forces may "settle in" once all of the skeletal members are of acceptable lengths.
  • one or more of the skeletal member lengths are allowed to be variable within a predetermined range.
  • the length of skeletal members making up the sides of the torso may be variable to simulate a deformable midsection.
  • the length of skeletal members making up the upper-arm may be variable to simulate a complex shoulder socket.
  • a skeletal model may additionally or alternatively be constrained by computing a length of each skeletal member based on the target, such that these lengths may be used as constraints during rectification.
  • the desired bone lengths are known from the body model; and the difference between the current bone lengths (i.e., distances between new joint positions) and the desired bone lengths can be assessed.
  • the model can be adjusted to decrease any error between desired lengths and current lengths. Priority may be given to certain joints and/or bones that are deemed more important, as well as joints or body parts that are currently more visible than others. Also, high-magnitude changes may be given priority over low-magnitude changes.
  • FIG. 19 illustrates application of one or more constraints to a model representing the target.
  • application of the constraints may be analytical, and may include, for example, modifying pixel data such as that illustrated in FIG. 10.
  • application of a force vector to model 260 may result in a "broken" model.
  • the target may reposition itself to have an arm raised overhead.
  • a force vector may be applied to one or more force- receiving locations of the arm to mimic the motion of the target. However, doing so could potentially result in "breaking" the arm, such as depicted at 262, and/or changing the proportions of the arm, such as shown at 264.
  • constraints may be applied to ensure that adjustments to the model are physically appropriate.
  • a constraint may be applied, such as shown at 266, to ensure that the forearm and upper arm remain attached at the elbow.
  • a bone-length constraint may be applied to the forearm, such as shown at 268, to ensure that the forearm remains approximately the same length.
  • the constraints such as shown at 270, the model maintains its physical integrity.
  • Joint visibility and/or confidence may be separately tracked in the X, Y, and Z dimensions to allow more accurate application of bone length constraints. For example, if a bone connects the chest to the left shoulder, and the chest joint's Z position is high-confidence (i.e., many refine-z pixels correspond to the joint) and the shoulder's Y-position is high-confidence (many push/pull pixels correspond to the joint), then any error in the bone length may be corrected while partially or fully limiting movement of the shoulder in the Y direction or the chest in the Z direction.
  • joint positions prior to rectification may be compared to joint positions after rectification. If it is determined that a consistent set of adjustments is being made to the skeletal model in every frame, method 100 may use this information to perform a "progressive refinement" on the skeletal and/or body model. For example, by comparing joint positions before and after rectification it may be determined that in each frame the shoulders are being pushed wider apart during rectification. Such a consistent adjustment suggests that the shoulders of the skeletal model are smaller than that of the target being represented, and consequently, the shoulder width is being adjusted each frame during rectification to correct for this. In such a case, a progressive refinement, such as increasing the shoulder width of the skeletal model, may be made to correct the skeletal and/or body model to better match the target.
  • certain limbs and body parts may be limited in their range of motion relative to an adjacent body part. Additionally, this range of motion may change based on the orientation of adjacent body parts.
  • applying joint angle constraints may allow limb segments to be constrained to possible configurations, given the orientation of parent limbs and/or body parts.
  • the lower leg can be configured to bend backwards (at the knee), but not forwards. If illegal angles are detected, the offending body part(s) and/or their parents (or, in the case of a mesh model, the offending triangles and their neighbors) are adjusted to keep the pose within a range of predetermined possibilities, thus helping avoid the case where the model collapses into a pose that is deemed to be unacceptable.
  • FIG. 20 illustrates an example of a model 280 having one or more joint angle constraints applied to rectify an incorrect joint angle shown at 282, to be a within an acceptable range of motion such as shown at 284.
  • the pose may be recognized as backwards, i.e., what is being tracked as the chest is really the player's back; the left hand is really the right hand; and so on. When such an impossible angle is clearly visible (and sufficiently egregious), this can be interpreted to mean that the pose has been mapped backwards onto the player's body, and the pose can be flipped to accurately model the target.
  • Collision tests may be applied to prevent the model from interpenetrating itself.
  • collision tests may prevent any part of the forearms/hands from penetrating the torso, or prevent the forearms/hands from penetrating each other. In other examples, collision tests may prevent a leg from penetrating the other leg.
  • collision tests may be applied to models of two or more players to prevent similar scenarios from occurring between models. It is to be understood that this can be accomplished through many different representations of the model geometry — e.g., polygonal hulls may be used for the core body, and parametric capsules (rounded cylinders, which may have different radii at opposing ends) for the limb segments. In some embodiments, collision tests may be applied to a body model and/or a skeletal model.
  • collision tests may be applied to certain polygons of a mesh model.
  • FIG. 21 shows a model 290 wherein the hand and forearm of model 290 has interpenetrated the torso, as depicted at 292. Upon application of collision tests, such interpenetration can be detected and corrected, such as shown at 294.
  • Collision tests may be applied in any suitable manner.
  • One approach examines collisions of one "volumetric line segment" vs. another, where a volumetric line segment may be a line segment with a radius that extends out in 3-D.
  • An example of such a collision test may be examining a forearm vs. another forearm.
  • the volumetric line segment may have a different radius at each end of the segment.
  • Another approach examines collisions of a volumetric line segment vs. a posed polygonal object.
  • An example of such a collision test may be examining a forearm vs. a torso.
  • the posed polygonal object may be a deformed polygonal object.
  • knowledge that different portions of a target can move a limited distance in a time frame can be used as a constraint.
  • a constraint may be used to rule out certain poses resulting from application of forces to pixel-receiving locations of the model.
  • the process can loop back to begin a new rasterization of the model into a new synthesized depth image, which may then be compared to the observed depth image so that further adjustments can be made to the model. In this way, the model can be progressively adjusted to more closely represent the modeled target.
  • method 100 of FIG. 7 optionally includes changing the visual appearance of an on-screen character (e.g., player avatar 190 of FIG. 12A) responsive to changes to the model, such as changes shown in FIG. 11B.
  • an on-screen character e.g., player avatar 190 of FIG. 12A
  • a user playing an electronic game on a gaming console e.g., gaming system 12 of FIGs. 1A and IB
  • a body model e.g., body model 70 of FIG. 3
  • a skeletal model e.g., skeletal model 180 of FIG. 11A
  • the gaming console may track this motion, then in response to the tracked motion, adjust the model 180 as depicted in FIG 11B.
  • the gaming console may also apply one or more constraints, as described above.
  • the gaming console may display the adjusted player avatar 192, as shown in FIG. 12B. This is also shown by way of example in FIG. 1A, in which player avatar 24 is shown punching boxing opponent 22 responsive to game player 18 throwing a punch in real space.
  • visual target recognition can be performed for purposes other than changing the visual appearance of an on-screen character or avatar.
  • the visual appearance of an on-screen character or avatar need not be changed in all embodiments.
  • target tracking can be used for virtually limitless different purposes, many of which do not result in the changing of an on-screen character.
  • the target tracking and/or the pose of the model, as adjusted, can be used as a parameter to affect virtually any element of an application, such as a game.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Theoretical Computer Science (AREA)
  • Processing Or Creating Images (AREA)
  • Image Analysis (AREA)

Abstract

Un procédé de poursuite visuelle d'une cible consiste à représenter une cible humaine par un modèle lisible par machine pouvant être ajusté en une pluralité de poses différentes, et à recevoir d'une source une image de profondeur observée de la cible humaine. L'image de profondeur observée est comparée au modèle. Un vecteur de force affiné en z est ensuite appliqué en un ou plusieurs emplacements du modèle recevant la force pour déplacer une partie du modèle vers une partie correspondante de l'image de profondeur observée si cette partie du modèle est décalée en z par rapport à la partie correspondante de l'image de profondeur observée.
PCT/US2010/059072 2009-12-07 2010-12-06 Poursuite visuelle d'une cible WO2011071808A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201080055361.6A CN102648484B (zh) 2009-12-07 2010-12-06 虚拟目标跟踪

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/632,587 US8577084B2 (en) 2009-01-30 2009-12-07 Visual target tracking
US12/632,587 2009-12-07

Publications (2)

Publication Number Publication Date
WO2011071808A2 true WO2011071808A2 (fr) 2011-06-16
WO2011071808A3 WO2011071808A3 (fr) 2011-10-27

Family

ID=44146125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/059072 WO2011071808A2 (fr) 2009-12-07 2010-12-06 Poursuite visuelle d'une cible

Country Status (3)

Country Link
US (1) US8577084B2 (fr)
CN (1) CN102648484B (fr)
WO (1) WO2011071808A2 (fr)

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101640039B1 (ko) * 2009-09-22 2016-07-18 삼성전자주식회사 영상 처리 장치 및 방법
US8564534B2 (en) 2009-10-07 2013-10-22 Microsoft Corporation Human tracking system
US8867820B2 (en) 2009-10-07 2014-10-21 Microsoft Corporation Systems and methods for removing a background of an image
US7961910B2 (en) * 2009-10-07 2011-06-14 Microsoft Corporation Systems and methods for tracking a model
US8963829B2 (en) 2009-10-07 2015-02-24 Microsoft Corporation Methods and systems for determining and tracking extremities of a target
US8994790B2 (en) * 2010-02-25 2015-03-31 The Board Of Trustees Of The Leland Stanford Junior University Motion capture with low input data constraints
US8611670B2 (en) * 2010-02-25 2013-12-17 The Board Of Trustees Of The Leland Stanford Junior University Intelligent part identification for use with scene characterization or motion capture
RU2534892C2 (ru) * 2010-04-08 2014-12-10 Самсунг Электроникс Ко., Лтд. Устройство и способ для захвата безмаркерных движений человека
US8259994B1 (en) * 2010-09-14 2012-09-04 Google Inc. Using image and laser constraints to obtain consistent and improved pose estimates in vehicle pose databases
TWI419082B (zh) * 2010-12-20 2013-12-11 Ind Tech Res Inst 偵測視訊序列中的移動物體影像的方法以及影像處理系統
CN102074018B (zh) * 2010-12-22 2013-03-20 Tcl集团股份有限公司 一种基于深度信息的轮廓跟踪方法
US9011293B2 (en) 2011-01-26 2015-04-21 Flow-Motion Research And Development Ltd. Method and system for monitoring and feed-backing on execution of physical exercise routines
JP2012160039A (ja) * 2011-02-01 2012-08-23 Fujifilm Corp 画像処理装置、立体画像印刷システム、画像処理方法およびプログラム
US8942917B2 (en) 2011-02-14 2015-01-27 Microsoft Corporation Change invariant scene recognition by an agent
US9449241B2 (en) * 2011-02-23 2016-09-20 The Johns Hopkins University System and method for detecting and tracking a curvilinear object in a three-dimensional space
US9924907B2 (en) 2011-09-30 2018-03-27 Google Technology Holdings LLC Method and system for identifying location of a touched body part
US9628843B2 (en) * 2011-11-21 2017-04-18 Microsoft Technology Licensing, Llc Methods for controlling electronic devices using gestures
US9557819B2 (en) 2011-11-23 2017-01-31 Intel Corporation Gesture input with multiple views, displays and physics
KR101908284B1 (ko) * 2012-01-13 2018-10-16 삼성전자주식회사 신체 연결 관계 분석 장치 및 방법
US9053382B2 (en) * 2012-03-22 2015-06-09 Digital Media Professionals Inc. Robust image based edge detection
US9170648B2 (en) * 2012-04-03 2015-10-27 The Boeing Company System and method for virtual engineering
US20140267611A1 (en) * 2013-03-14 2014-09-18 Microsoft Corporation Runtime engine for analyzing user motion in 3d images
US9177410B2 (en) * 2013-08-09 2015-11-03 Ayla Mandel System and method for creating avatars or animated sequences using human body features extracted from a still image
WO2015038138A1 (fr) * 2013-09-13 2015-03-19 Intel Corporation Mesure de concentration de l'attention fondée sur des données de mouvement pour faciliter un traitement d'image
US9436277B2 (en) * 2014-04-21 2016-09-06 Xerox Corporation System and method for producing computer control signals from breath attributes
CN104539934A (zh) * 2015-01-05 2015-04-22 京东方科技集团股份有限公司 图像采集装置和图像处理方法、系统
US11511156B2 (en) 2016-03-12 2022-11-29 Arie Shavit Training system and methods for designing, monitoring and providing feedback of training
CN105844705B (zh) * 2016-03-29 2018-11-09 联想(北京)有限公司 一种三维虚拟对象模型生成方法及电子设备
WO2019026598A1 (fr) * 2017-07-31 2019-02-07 ソニー株式会社 Dispositif de traitement d'image, procédé de traitement d'image, programme, et système de communication à distance
US10366510B1 (en) * 2017-10-04 2019-07-30 Octi Systems and methods for determining location and orientation of a body
US10937240B2 (en) 2018-01-04 2021-03-02 Intel Corporation Augmented reality bindings of physical objects and virtual objects
CN112957726B (zh) * 2021-02-01 2024-05-03 北京海天维景科技有限公司 一种虚拟运动场景的交互控制方法和装置
WO2022266333A1 (fr) * 2021-06-16 2022-12-22 The Meta Game, Inc. Système et procédé d'extraction de données physiques et de données de mouvement à partir d'environnements virtuels

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050099547A (ko) * 2003-02-11 2005-10-13 가부시키가이샤 소니 컴퓨터 엔터테인먼트 실시간 모션 캡처를 위한 방법 및 장치
US20070298882A1 (en) * 2003-09-15 2007-12-27 Sony Computer Entertainment Inc. Methods and systems for enabling direction detection when interfacing with a computer program
US20090221374A1 (en) * 2007-11-28 2009-09-03 Ailive Inc. Method and system for controlling movements of objects in a videogame

Family Cites Families (213)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4288078A (en) * 1979-11-20 1981-09-08 Lugo Julio I Game apparatus
US4695953A (en) 1983-08-25 1987-09-22 Blair Preston E TV animation interactively controlled by the viewer
US4630910A (en) 1984-02-16 1986-12-23 Robotic Vision Systems, Inc. Method of measuring in three-dimensions at high speed
US4627620A (en) 1984-12-26 1986-12-09 Yang John P Electronic athlete trainer for improving skills in reflex, speed and accuracy
US4645458A (en) 1985-04-15 1987-02-24 Harald Phillip Athletic evaluation and training apparatus
US4702475A (en) 1985-08-16 1987-10-27 Innovating Training Products, Inc. Sports technique and reaction training system
US4843568A (en) 1986-04-11 1989-06-27 Krueger Myron W Real time perception of and response to the actions of an unencumbered participant/user
US4711543A (en) 1986-04-14 1987-12-08 Blair Preston E TV animation interactively controlled by the viewer
US4796997A (en) 1986-05-27 1989-01-10 Synthetic Vision Systems, Inc. Method and system for high-speed, 3-D imaging of an object at a vision station
US5184295A (en) 1986-05-30 1993-02-02 Mann Ralph V System and method for teaching physical skills
US4751642A (en) 1986-08-29 1988-06-14 Silva John M Interactive sports simulation system with physiological sensing and psychological conditioning
US4809065A (en) 1986-12-01 1989-02-28 Kabushiki Kaisha Toshiba Interactive system and related method for displaying data to produce a three-dimensional image of an object
US4817950A (en) 1987-05-08 1989-04-04 Goo Paul E Video game control unit and attitude sensor
US5239463A (en) 1988-08-04 1993-08-24 Blair Preston E Method and apparatus for player interaction with animated characters and objects
US5239464A (en) 1988-08-04 1993-08-24 Blair Preston E Interactive video system providing repeated switching of multiple tracks of actions sequences
US4901362A (en) 1988-08-08 1990-02-13 Raytheon Company Method of recognizing patterns
US4893183A (en) 1988-08-11 1990-01-09 Carnegie-Mellon University Robotic vision system
JPH02199526A (ja) 1988-10-14 1990-08-07 David G Capper 制御インターフェース装置
US4925189A (en) 1989-01-13 1990-05-15 Braeunig Thomas F Body-mounted video game exercise device
US5229756A (en) 1989-02-07 1993-07-20 Yamaha Corporation Image control apparatus
US5469740A (en) 1989-07-14 1995-11-28 Impulse Technology, Inc. Interactive video testing and training system
JPH03103822U (fr) 1990-02-13 1991-10-29
US5101444A (en) 1990-05-18 1992-03-31 Panacea, Inc. Method and apparatus for high speed object location
US5148154A (en) 1990-12-04 1992-09-15 Sony Corporation Of America Multi-dimensional user interface
US5534917A (en) 1991-05-09 1996-07-09 Very Vivid, Inc. Video image based control system
JP3182876B2 (ja) 1991-05-24 2001-07-03 ソニー株式会社 画像信号処理方法とその装置
US5417210A (en) 1992-05-27 1995-05-23 International Business Machines Corporation System and method for augmentation of endoscopic surgery
US5295491A (en) 1991-09-26 1994-03-22 Sam Technology, Inc. Non-invasive human neurocognitive performance capability testing method and system
US6054991A (en) 1991-12-02 2000-04-25 Texas Instruments Incorporated Method of modeling player position and movement in a virtual reality system
WO1993010708A1 (fr) 1991-12-03 1993-06-10 French Sportech Corporation Systeme pour tester et entrainer les capacites physiques d'un sujet utilisant la video et du type interactif
US5875108A (en) 1991-12-23 1999-02-23 Hoffberg; Steven M. Ergonomic man-machine interface incorporating adaptive pattern recognition based control system
JPH07325934A (ja) 1992-07-10 1995-12-12 Walt Disney Co:The 仮想世界に向上したグラフィックスを提供する方法および装置
US5999908A (en) 1992-08-06 1999-12-07 Abelow; Daniel H. Customer-based product design module
US7098891B1 (en) 1992-09-18 2006-08-29 Pryor Timothy R Method for providing human input to a computer
US5320538A (en) 1992-09-23 1994-06-14 Hughes Training, Inc. Interactive aircraft training system and method
IT1257294B (it) 1992-11-20 1996-01-12 Dispositivo atto a rilevare la configurazione di un'unita' fisiologicadistale,da utilizzarsi in particolare come interfaccia avanzata per macchine e calcolatori.
US5495576A (en) 1993-01-11 1996-02-27 Ritchey; Kurtis J. Panoramic image based virtual reality/telepresence audio-visual system and method
US5690582A (en) 1993-02-02 1997-11-25 Tectrix Fitness Equipment, Inc. Interactive exercise apparatus
JP2799126B2 (ja) 1993-03-26 1998-09-17 株式会社ナムコ ビデオゲーム装置及びゲーム用入力装置
US5405152A (en) 1993-06-08 1995-04-11 The Walt Disney Company Method and apparatus for an interactive video game with physical feedback
US5454043A (en) 1993-07-30 1995-09-26 Mitsubishi Electric Research Laboratories, Inc. Dynamic and static hand gesture recognition through low-level image analysis
US5423554A (en) 1993-09-24 1995-06-13 Metamedia Ventures, Inc. Virtual reality game method and apparatus
US5980256A (en) 1993-10-29 1999-11-09 Carmein; David E. E. Virtual reality system with enhanced sensory apparatus
JP3419050B2 (ja) 1993-11-19 2003-06-23 株式会社日立製作所 入力装置
US5347306A (en) 1993-12-17 1994-09-13 Mitsubishi Electric Research Laboratories, Inc. Animated electronic meeting place
JP2552427B2 (ja) 1993-12-28 1996-11-13 コナミ株式会社 テレビ遊戯システム
US5577981A (en) 1994-01-19 1996-11-26 Jarvik; Robert Virtual reality exercise machine and computer controlled video system
US5580249A (en) 1994-02-14 1996-12-03 Sarcos Group Apparatus for simulating mobility of a human
US5597309A (en) 1994-03-28 1997-01-28 Riess; Thomas Method and apparatus for treatment of gait problems associated with parkinson's disease
US5385519A (en) 1994-04-19 1995-01-31 Hsu; Chi-Hsueh Running machine
US5524637A (en) 1994-06-29 1996-06-11 Erickson; Jon W. Interactive system for measuring physiological exertion
US5563988A (en) 1994-08-01 1996-10-08 Massachusetts Institute Of Technology Method and system for facilitating wireless, full-body, real-time user interaction with a digitally represented visual environment
US6714665B1 (en) 1994-09-02 2004-03-30 Sarnoff Corporation Fully automated iris recognition system utilizing wide and narrow fields of view
US5516105A (en) 1994-10-06 1996-05-14 Exergame, Inc. Acceleration activated joystick
US5638300A (en) 1994-12-05 1997-06-10 Johnson; Lee E. Golf swing analysis system
JPH08161292A (ja) 1994-12-09 1996-06-21 Matsushita Electric Ind Co Ltd 混雑度検知方法およびそのシステム
US5594469A (en) 1995-02-21 1997-01-14 Mitsubishi Electric Information Technology Center America Inc. Hand gesture machine control system
US5682229A (en) 1995-04-14 1997-10-28 Schwartz Electro-Optics, Inc. Laser range camera
US5913727A (en) 1995-06-02 1999-06-22 Ahdoot; Ned Interactive movement and contact simulation game
JP3481631B2 (ja) 1995-06-07 2003-12-22 ザ トラスティース オブ コロンビア ユニヴァーシティー イン ザ シティー オブ ニューヨーク 能動型照明及びデフォーカスに起因する画像中の相対的なぼけを用いる物体の３次元形状を決定する装置及び方法
US5682196A (en) 1995-06-22 1997-10-28 Actv, Inc. Three-dimensional (3D) video presentation system providing interactive 3D presentation with personalized audio responses for multiple viewers
US5702323A (en) 1995-07-26 1997-12-30 Poulton; Craig K. Electronic exercise enhancer
US5889524A (en) 1995-09-11 1999-03-30 University Of Washington Reconstruction of three-dimensional objects using labeled piecewise smooth subdivision surfaces
US6098458A (en) 1995-11-06 2000-08-08 Impulse Technology, Ltd. Testing and training system for assessing movement and agility skills without a confining field
US6073489A (en) 1995-11-06 2000-06-13 French; Barry J. Testing and training system for assessing the ability of a player to complete a task
US6308565B1 (en) 1995-11-06 2001-10-30 Impulse Technology Ltd. System and method for tracking and assessing movement skills in multidimensional space
US6430997B1 (en) 1995-11-06 2002-08-13 Trazer Technologies, Inc. System and method for tracking and assessing movement skills in multidimensional space
US6176782B1 (en) 1997-12-22 2001-01-23 Philips Electronics North America Corp. Motion-based command generation technology
US5933125A (en) 1995-11-27 1999-08-03 Cae Electronics, Ltd. Method and apparatus for reducing instability in the display of a virtual environment
US5641288A (en) 1996-01-11 1997-06-24 Zaenglein, Jr.; William G. Shooting simulating process and training device using a virtual reality display screen
CA2253626A1 (fr) 1996-05-08 1997-11-13 Real Vision Corporation Simulation en temps reel utilisant une detection de position
US6173066B1 (en) 1996-05-21 2001-01-09 Cybernet Systems Corporation Pose determination and tracking by matching 3D objects to a 2D sensor
AU2978397A (en) * 1996-06-05 1998-01-05 Sega Enterprises, Ltd. Image processor for games
US5989157A (en) 1996-08-06 1999-11-23 Walton; Charles A. Exercising system with electronic inertial game playing
CN1168057C (zh) 1996-08-14 2004-09-22 挪拉赫梅特·挪利斯拉莫维奇·拉都包夫 追踪并显示使用者在空间的位置与取向的方法,向使用者展示虚拟环境的方法以及实现这些方法的系统
JP3064928B2 (ja) 1996-09-20 2000-07-12 日本電気株式会社 被写体抽出方式
EP0849697B1 (fr) 1996-12-20 2003-02-12 Hitachi Europe Limited Procédé et système de reconnaissance de gestes de la main
US6009210A (en) 1997-03-05 1999-12-28 Digital Equipment Corporation Hands-free interface to a virtual reality environment using head tracking
US6100896A (en) 1997-03-24 2000-08-08 Mitsubishi Electric Information Technology Center America, Inc. System for designing graphical multi-participant environments
US5877803A (en) 1997-04-07 1999-03-02 Tritech Mircoelectronics International, Ltd. 3-D image detector
US6215898B1 (en) 1997-04-15 2001-04-10 Interval Research Corporation Data processing system and method
JP3077745B2 (ja) 1997-07-31 2000-08-14 日本電気株式会社 データ処理方法および装置、情報記憶媒体
US6188777B1 (en) 1997-08-01 2001-02-13 Interval Research Corporation Method and apparatus for personnel detection and tracking
US6720949B1 (en) 1997-08-22 2004-04-13 Timothy R. Pryor Man machine interfaces and applications
US6289112B1 (en) 1997-08-22 2001-09-11 International Business Machines Corporation System and method for determining block direction in fingerprint images
AUPO894497A0 (en) 1997-09-02 1997-09-25 Xenotech Research Pty Ltd Image processing method and apparatus
EP0905644A3 (fr) 1997-09-26 2004-02-25 Matsushita Electric Industrial Co., Ltd. Dispositif de reconnaissance de gestes de la main
US6141463A (en) 1997-10-10 2000-10-31 Electric Planet Interactive Method and system for estimating jointed-figure configurations
US6072494A (en) 1997-10-15 2000-06-06 Electric Planet, Inc. Method and apparatus for real-time gesture recognition
US6130677A (en) 1997-10-15 2000-10-10 Electric Planet, Inc. Interactive computer vision system
US6101289A (en) 1997-10-15 2000-08-08 Electric Planet, Inc. Method and apparatus for unencumbered capture of an object
US6411744B1 (en) 1997-10-15 2002-06-25 Electric Planet, Inc. Method and apparatus for performing a clean background subtraction
WO1999019840A1 (fr) 1997-10-15 1999-04-22 Electric Planet, Inc. Systeme et procede pour produire un personnage anime
US6181343B1 (en) 1997-12-23 2001-01-30 Philips Electronics North America Corp. System and method for permitting three-dimensional navigation through a virtual reality environment using camera-based gesture inputs
US6159100A (en) 1998-04-23 2000-12-12 Smith; Michael D. Virtual reality game
US6077201A (en) 1998-06-12 2000-06-20 Cheng; Chau-Yang Exercise bicycle
US7036094B1 (en) 1998-08-10 2006-04-25 Cybernet Systems Corporation Behavior recognition system
US20010008561A1 (en) 1999-08-10 2001-07-19 Paul George V. Real-time object tracking system
US6681031B2 (en) 1998-08-10 2004-01-20 Cybernet Systems Corporation Gesture-controlled interfaces for self-service machines and other applications
US6950534B2 (en) 1998-08-10 2005-09-27 Cybernet Systems Corporation Gesture-controlled interfaces for self-service machines and other applications
US7121946B2 (en) 1998-08-10 2006-10-17 Cybernet Systems Corporation Real-time head tracking system for computer games and other applications
US6801637B2 (en) 1999-08-10 2004-10-05 Cybernet Systems Corporation Optical body tracker
IL126284A (en) 1998-09-17 2002-12-01 Netmor Ltd System and method for three dimensional positioning and tracking
DE69936620T2 (de) 1998-09-28 2008-05-21 Matsushita Electric Industrial Co., Ltd., Kadoma Verfahren und Vorrichtung zum Segmentieren von Handgebärden
AU1930700A (en) 1998-12-04 2000-06-26 Interval Research Corporation Background estimation and segmentation based on range and color
US6147678A (en) 1998-12-09 2000-11-14 Lucent Technologies Inc. Video hand image-three-dimensional computer interface with multiple degrees of freedom
AU1574899A (en) 1998-12-16 2000-07-03 3Dv Systems Ltd. Self gating photosurface
US6570555B1 (en) 1998-12-30 2003-05-27 Fuji Xerox Co., Ltd. Method and apparatus for embodied conversational characters with multimodal input/output in an interface device
US6363160B1 (en) 1999-01-22 2002-03-26 Intel Corporation Interface using pattern recognition and tracking
US7003134B1 (en) 1999-03-08 2006-02-21 Vulcan Patents Llc Three dimensional object pose estimation which employs dense depth information
US6299308B1 (en) 1999-04-02 2001-10-09 Cybernet Systems Corporation Low-cost non-imaging eye tracker system for computer control
US6503195B1 (en) 1999-05-24 2003-01-07 University Of North Carolina At Chapel Hill Methods and systems for real-time structured light depth extraction and endoscope using real-time structured light depth extraction
US6476834B1 (en) 1999-05-28 2002-11-05 International Business Machines Corporation Dynamic creation of selectable items on surfaces
US6873723B1 (en) 1999-06-30 2005-03-29 Intel Corporation Segmenting three-dimensional video images using stereo
US6738066B1 (en) 1999-07-30 2004-05-18 Electric Plant, Inc. System, method and article of manufacture for detecting collisions between video images generated by a camera and an object depicted on a display
US7113918B1 (en) 1999-08-01 2006-09-26 Electric Planet, Inc. Method for video enabled electronic commerce
US7050606B2 (en) 1999-08-10 2006-05-23 Cybernet Systems Corporation Tracking and gesture recognition system particularly suited to vehicular control applications
US6674877B1 (en) 2000-02-03 2004-01-06 Microsoft Corporation System and method for visually tracking occluded objects in real time
US6663491B2 (en) 2000-02-18 2003-12-16 Namco Ltd. Game apparatus, storage medium and computer program that adjust tempo of sound
US6633294B1 (en) 2000-03-09 2003-10-14 Seth Rosenthal Method and apparatus for using captured high density motion for animation
EP1152261A1 (fr) 2000-04-28 2001-11-07 CSEM Centre Suisse d'Electronique et de Microtechnique SA Dispositif et procédé de détection avec résolution spatiale et démodulation d'ondes électromagnétiques modulées
US6640202B1 (en) 2000-05-25 2003-10-28 International Business Machines Corporation Elastic sensor mesh system for 3-dimensional measurement, mapping and kinematics applications
US6731799B1 (en) 2000-06-01 2004-05-04 University Of Washington Object segmentation with background extraction and moving boundary techniques
US6788809B1 (en) 2000-06-30 2004-09-07 Intel Corporation System and method for gesture recognition in three dimensions using stereo imaging and color vision
US20020024517A1 (en) * 2000-07-14 2002-02-28 Komatsu Ltd. Apparatus and method for three-dimensional image production and presenting real objects in virtual three-dimensional space
JP2002058045A (ja) 2000-08-08 2002-02-22 Komatsu Ltd 現実の物体をバーチャル３次元空間に登場させるためのシステム及び方法
US7227526B2 (en) 2000-07-24 2007-06-05 Gesturetek, Inc. Video-based image control system
US7058204B2 (en) 2000-10-03 2006-06-06 Gesturetek, Inc. Multiple camera control system
US7039676B1 (en) 2000-10-31 2006-05-02 International Business Machines Corporation Using video image analysis to automatically transmit gestures over a network in a chat or instant messaging session
US6567536B2 (en) 2001-02-16 2003-05-20 Golftec Enterprises Llc Method and system for physical motion analysis
US7116330B2 (en) 2001-02-28 2006-10-03 Intel Corporation Approximating motion using a three-dimensional model
FR2822573B1 (fr) * 2001-03-21 2003-06-20 France Telecom Procede et systeme de reconstruction a distance d'une surface
US6539931B2 (en) 2001-04-16 2003-04-01 Koninklijke Philips Electronics N.V. Ball throwing assistant
US7363199B2 (en) 2001-04-25 2008-04-22 Telekinesys Research Limited Method and apparatus for simulating soft object movement
US20020164067A1 (en) 2001-05-02 2002-11-07 Synapix Nearest neighbor edge selection from feature tracking
US7259747B2 (en) 2001-06-05 2007-08-21 Reactrix Systems, Inc. Interactive video display system
US8035612B2 (en) 2002-05-28 2011-10-11 Intellectual Ventures Holding 67 Llc Self-contained interactive video display system
JP3420221B2 (ja) 2001-06-29 2003-06-23 株式会社コナミコンピュータエンタテインメント東京 ゲーム装置及びプログラム
US7274800B2 (en) 2001-07-18 2007-09-25 Intel Corporation Dynamic gesture recognition from stereo sequences
US6937742B2 (en) 2001-09-28 2005-08-30 Bellsouth Intellectual Property Corporation Gesture activated home appliance
US6990639B2 (en) 2002-02-07 2006-01-24 Microsoft Corporation System and process for controlling electronic components in a ubiquitous computing environment using multimodal integration
EP1497160B2 (fr) 2002-04-19 2010-07-21 IEE INTERNATIONAL ELECTRONICS & ENGINEERING S.A. Dispositif de securite pour vehicule
US7170492B2 (en) 2002-05-28 2007-01-30 Reactrix Systems, Inc. Interactive video display system
US7348963B2 (en) 2002-05-28 2008-03-25 Reactrix Systems, Inc. Interactive video display system
US7710391B2 (en) 2002-05-28 2010-05-04 Matthew Bell Processing an image utilizing a spatially varying pattern
US7489812B2 (en) 2002-06-07 2009-02-10 Dynamic Digital Depth Research Pty Ltd. Conversion and encoding techniques
JP3760347B2 (ja) 2002-07-30 2006-03-29 株式会社光栄 プログラム、記録媒体、ゲームキャラクタ描画方法及びゲーム装置
US6919892B1 (en) * 2002-08-14 2005-07-19 Avaworks, Incorporated Photo realistic talking head creation system and method
US7576727B2 (en) 2002-12-13 2009-08-18 Matthew Bell Interactive directed light/sound system
JP4235729B2 (ja) 2003-02-03 2009-03-11 国立大学法人静岡大学 距離画像センサ
US7257237B1 (en) 2003-03-07 2007-08-14 Sandia Corporation Real time markerless motion tracking using linked kinematic chains
US8745541B2 (en) 2003-03-25 2014-06-03 Microsoft Corporation Architecture for controlling a computer using hand gestures
EP1477924B1 (fr) 2003-03-31 2007-05-02 HONDA MOTOR CO., Ltd. Appareil, procédé et logiciel de reconnaissance des gestes
JP4355341B2 (ja) 2003-05-29 2009-10-28 本田技研工業株式会社 深度データを用いたビジュアルトラッキング
US8072470B2 (en) 2003-05-29 2011-12-06 Sony Computer Entertainment Inc. System and method for providing a real-time three-dimensional interactive environment
EP1631937B1 (fr) 2003-06-12 2018-03-28 Honda Motor Co., Ltd. Estimation d'orientation de cible au moyen de la detection de profondeur
US7263209B2 (en) 2003-06-13 2007-08-28 Sarnoff Corporation Vehicular vision system
US7068815B2 (en) * 2003-06-13 2006-06-27 Sarnoff Corporation Method and apparatus for ground detection and removal in vision systems
WO2005041579A2 (fr) 2003-10-24 2005-05-06 Reactrix Systems, Inc. Procede et systeme pour traiter des informations d'image capturee dans un systeme d'affichage video interactif
US20050215319A1 (en) 2004-03-23 2005-09-29 Harmonix Music Systems, Inc. Method and apparatus for controlling a three-dimensional character in a three-dimensional gaming environment
JP4708422B2 (ja) 2004-04-15 2011-06-22 ジェスチャー テック，インコーポレイテッド 両手動作の追跡
US7308112B2 (en) 2004-05-14 2007-12-11 Honda Motor Co., Ltd. Sign based human-machine interaction
US7704135B2 (en) 2004-08-23 2010-04-27 Harrison Jr Shelton E Integrated game system, method, and device
US20060055706A1 (en) 2004-09-15 2006-03-16 Perlman Stephen G Apparatus and method for capturing the motion of a performer
KR20060070280A (ko) 2004-12-20 2006-06-23 한국전자통신연구원 손 제스처 인식을 이용한 사용자 인터페이스 장치 및 그방법
EP1849123A2 (fr) 2005-01-07 2007-10-31 GestureTek, Inc. Capteur d'inclinaison base sur un flux optique
WO2006074310A2 (fr) 2005-01-07 2006-07-13 Gesturetek, Inc. Creation d'images tridimensionnelles d'objets par illumination au moyen de motifs infrarouges
CN102831387B (zh) 2005-01-07 2016-12-14 高通股份有限公司 检测和跟踪图像中的物体
US7598942B2 (en) 2005-02-08 2009-10-06 Oblong Industries, Inc. System and method for gesture based control system
US7492367B2 (en) 2005-03-10 2009-02-17 Motus Corporation Apparatus, system and method for interpreting and reproducing physical motion
WO2006099597A2 (fr) 2005-03-17 2006-09-21 Honda Motor Co., Ltd. Estimation de pose reposant sur l'analyse de points critiques
RU2007146172A (ru) 2005-05-17 2009-06-27 Гестуретэк, Инк. (Us) Вывод сигнала, чувствительный к ориентации
ATE412882T1 (de) 2005-08-12 2008-11-15 Mesa Imaging Ag Hochempfindliches, schnelles pixel für anwendung in einem bildsensor
US20080026838A1 (en) 2005-08-22 2008-01-31 Dunstan James E Multi-player non-role-playing virtual world games: method for two-way interaction between participants and multi-player virtual world games
US8050461B2 (en) 2005-10-11 2011-11-01 Primesense Ltd. Depth-varying light fields for three dimensional sensing
JP2009514106A (ja) 2005-10-26 2009-04-02 株式会社ソニー・コンピュータエンタテインメント コンピュータプログラムとインタフェースするためのシステムおよび方法
US7450736B2 (en) 2005-10-28 2008-11-11 Honda Motor Co., Ltd. Monocular tracking of 3D human motion with a coordinated mixture of factor analyzers
US7536030B2 (en) 2005-11-30 2009-05-19 Microsoft Corporation Real-time Bayesian 3D pose tracking
US20070159455A1 (en) 2006-01-06 2007-07-12 Ronmee Industrial Corporation Image-sensing game-controlling device
WO2007130693A2 (fr) 2006-05-07 2007-11-15 Sony Computer Entertainment Inc. Procédés et systèmes de traitement d'un échange d'effets en temps réel lors de communications vidéo
US7864181B1 (en) * 2006-06-08 2011-01-04 Pixar Shape friction: shape preservation of simulated objects in computer animation
US7864180B1 (en) * 2006-06-09 2011-01-04 Pixar Methods and apparatus for auto-scaling properties of simulated objects
US7852338B1 (en) * 2006-06-08 2010-12-14 Pixar Velocity drag: shape preservation of simulated objects in computer animation
US7907750B2 (en) 2006-06-12 2011-03-15 Honeywell International Inc. System and method for autonomous object tracking
US7701439B2 (en) 2006-07-13 2010-04-20 Northrop Grumman Corporation Gesture recognition simulation system and method
US8411149B2 (en) 2006-08-03 2013-04-02 Alterface S.A. Method and device for identifying and extracting images of multiple users, and for recognizing user gestures
TWI321297B (en) 2006-09-29 2010-03-01 Ind Tech Res Inst A method for corresponding, evolving and tracking feature points in three-dimensional space
JP5395323B2 (ja) 2006-09-29 2014-01-22 ブレインビジョン株式会社 固体撮像素子
US8023726B2 (en) * 2006-11-10 2011-09-20 University Of Maryland Method and system for markerless motion capture using multiple cameras
JP4677046B2 (ja) 2006-12-06 2011-04-27 本田技研工業株式会社 多次元ブースト回帰を経た外観及び動作を使用する高速人間姿勢推定
US8351646B2 (en) 2006-12-21 2013-01-08 Honda Motor Co., Ltd. Human pose estimation and tracking using label assignment
US7412077B2 (en) 2006-12-29 2008-08-12 Motorola, Inc. Apparatus and methods for head pose estimation and head gesture detection
US7971156B2 (en) 2007-01-12 2011-06-28 International Business Machines Corporation Controlling resource access based on user gesturing in a 3D captured image stream of the user
CN101681438A (zh) 2007-03-02 2010-03-24 有机运动公司 跟踪三维对象的系统和方法
US7729530B2 (en) 2007-03-03 2010-06-01 Sergey Antonov Method and apparatus for 3-D data input to a personal computer with a multimedia oriented operating system
US7872653B2 (en) 2007-06-18 2011-01-18 Microsoft Corporation Mesh puppetry
US7965866B2 (en) 2007-07-03 2011-06-21 Shoppertrak Rct Corporation System and process for detecting, tracking and counting human objects of interest
US8726194B2 (en) 2007-07-27 2014-05-13 Qualcomm Incorporated Item selection using enhanced control
US7852262B2 (en) 2007-08-16 2010-12-14 Cybernet Systems Corporation Wireless mobile indoor/outdoor tracking system
US7970176B2 (en) 2007-10-02 2011-06-28 Omek Interactive, Inc. Method and system for gesture classification
US20090221368A1 (en) 2007-11-28 2009-09-03 Ailive Inc., Method and system for creating a shared game space for a networked game
GB2455316B (en) 2007-12-04 2012-08-15 Sony Corp Image processing apparatus and method
US7925081B2 (en) 2007-12-12 2011-04-12 Fuji Xerox Co., Ltd. Systems and methods for human body pose estimation
US8159458B2 (en) 2007-12-13 2012-04-17 Apple Inc. Motion tracking user interface
US9098766B2 (en) 2007-12-21 2015-08-04 Honda Motor Co., Ltd. Controlled human pose estimation from depth image streams
US8696458B2 (en) 2008-02-15 2014-04-15 Thales Visionix, Inc. Motion tracking system and method using camera and non-camera sensors
US9772689B2 (en) 2008-03-04 2017-09-26 Qualcomm Incorporated Enhanced gesture-based image manipulation
US8075942B1 (en) 2008-03-21 2011-12-13 Nanoport Technologies Microengineered optical filters that closely match predefined transmission curves and systems and methods of manufacture
US20090280901A1 (en) 2008-05-09 2009-11-12 Dell Products, Lp Game controller device and methods thereof
CN201254344Y (zh) 2008-08-20 2009-06-10 中国农业科学院草原研究所 植物标本及种子存贮器
EP2343685B1 (fr) 2008-10-01 2020-07-29 Sony Interactive Entertainment Inc. Dispositif de traitement d'informations, procédé de traitement d'informations, programme et support de mémorisation d'informations
EP2209091B1 (fr) 2009-01-16 2012-08-08 Honda Research Institute Europe GmbH Système et procédé pour la détection de mouvement d'objets basée sur la déformation 3D multiple et véhicule équipé d'un tel système
US7996793B2 (en) 2009-01-30 2011-08-09 Microsoft Corporation Gesture recognizer system architecture

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050099547A (ko) * 2003-02-11 2005-10-13 가부시키가이샤 소니 컴퓨터 엔터테인먼트 실시간 모션 캡처를 위한 방법 및 장치
US20070298882A1 (en) * 2003-09-15 2007-12-27 Sony Computer Entertainment Inc. Methods and systems for enabling direction detection when interfacing with a computer program
US20090221374A1 (en) * 2007-11-28 2009-09-03 Ailive Inc. Method and system for controlling movements of objects in a videogame

Also Published As

Publication number Publication date
US20100195869A1 (en) 2010-08-05
WO2011071808A3 (fr) 2011-10-27
CN102648484A (zh) 2012-08-22
US8577084B2 (en) 2013-11-05
CN102648484B (zh) 2014-08-13

Similar Documents

Publication Publication Date Title
US9842405B2 (en) Visual target tracking
US8577084B2 (en) Visual target tracking
US8565476B2 (en) Visual target tracking
US8682028B2 (en) Visual target tracking
CA2748557C (fr) Suivi de cible visuelle
US8577085B2 (en) Visual target tracking
US7974443B2 (en) Visual target tracking using model fitting and exemplar
US8565477B2 (en) Visual target tracking
US9465980B2 (en) Pose tracking pipeline

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080055361.6

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10836473

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10836473

Country of ref document: EP

Kind code of ref document: A2