Note: Descriptions are shown in the official language in which they were submitted.
CA 02800533 2016-05-20
52785-26
NATURAL USER INPUT FOR DRIVING INTERACTIVE STORIES
BACKGROUND
[0001] In the past, computing applications such as computer games and
multimedia
applications used controllers, remotes, keyboards, mice, or the like to allow
users to
manipulate game characters or other aspects of an application. More recently,
computer
games and multimedia applications have begun employing cameras and software
gesture
recognition engines to provide a natural user interface ("NUI"). With NUI,
user gestures and
speech are detected, interpreted and used to control game characters or other
aspects of an
application.
[0002] At present, NCI systems are widely used for gaming applications.
However,
NUI systems to date have not been used as a medium for linear story telling. A
linear story is
a traditional, passive, non-interactive experience, such as for example
provided by traditional
television programs, movies and books. Linear stories have for decades been
widely embraced
by the general public. Gaming, especially with NUI systems, is relatively new
and has much
more limited acceptance to date.
SUMMARY
[0003] Disclosed herein are systems and methods for providing an
interactive story
experience which combines interactive gaming aspects into a linear story. The
linear story
may be watched by a user, start to finish, without user interaction if
desired. Alternatively, a
user may interact with the linear story to provide an interactive experience.
The user may
interact with the linear story via a NCI system, which includes a computing
environment, a
capture device for capturing user movement data and providing it to the
computing device,
and an audiovisual device for presenting the story.
[0003a] According to one aspect of the present invention, there is
provided in a system
comprising a computing environment coupled to a capture device for capturing
user motion
and an audiovisual device for displaying images and/or providing audio, a
method of
1
CA 02800533 2016-05-20
52785-26
combining interactive gaming aspects into a linear story, comprising: a)
presenting the linear
story via the audiovisual device using at least one of images and an audio
narrative, the linear
story having a default story and an altered story, the default story including
a default set of
images and/or narrative that is presented to a user if a user does not
interact with the story; b)
detecting at least one of a movement and a voice command by a user via the
capture device; c)
identifying whether the movement and/or the voice command detected in said
step b) is an
interaction with the linear story that alters the linear story to include a
story branch having at
least one of additional images and additional narrative not included in the
default set of
images and/or narrative; and d) altering the linear story to the altered story
by presenting at
least one of the additional images and additional narrative to a user via the
audiovisual device.
[0003b] According to another aspect of the present invention, there is
provided a
processor-readable storage medium for programming a processor to perform a
method of
combining interactive gaming aspects into a linear story, comprising: a)
presenting the linear
story via an audiovisual device using at least one of images and an audio
narrative, the linear
story presented as a complete story, beginning to end and including a default
set of images, in
the event no interaction by a user is perceived by a capture device monitoring
user
movements; b) detecting a movement by a user via a capture device associated
with the
audiovisual device; c) identifying whether the movement detected in said step
b) is an
interaction with the linear story requiring a modification from the linear
story to include a
story branch having additional images not included in the default set of
images; d)
determining whether the additional images may be rendered based on stored or
processed
data; e) altering the linear story by presenting the additional images to a
user via the
audiovisual device if it is determined the additional images may be rendered
in said step d);
and t) scoring a user's interaction where the interaction corresponds to
awarding or taking
away a predetermined number of points based on how the user interacts with the
story.
10003c1 According to still another aspect of the present invention,
there is provided a
system for combining interactive gaming aspects into a linear story,
comprising: an
audiovisual device for presenting at least one of images and an audio
narration; an image
capture device for capturing at least one of image and audio data from a user;
and a computing
environment coupled to the audiovisual device and image capture device, the
computing
1 a
CA 02800533 2016-05-20
52785-26
environment: a) presenting the linear story via the audiovisual device using
at least one of
images and an audio narrative, the linear story presented as a complete story,
beginning to end
and including a default set of images, in the event no interaction by a user
is perceived by the
capture device; b) detecting a movement by a user via the capture device; c)
identifying
whether the detected movement is an exploration gesture; d) branching from the
linear story
to a story branch upon identifying the movement as an exploration gesture, the
branching
including: dl) sensing a point on the audiovisual device indicated by the
user, d2) calculating
a 3-D real world vector from a portion of the user to the point on the
audiovisual device
indicated by the user, d3) translating the 3-D real world vector to a 3-D
machine space vector
having a start point at the current view perspective and an end point at the
virtual object in
3-D machine space, and d4) displaying the virtual object from a viewing
perspective at the
end point of the 3-D machine space vector.
10003d1 According to yet another aspect of the present invention, there
is provided in a
system comprising a computing environment coupled to a capture device for
capturing user
motion and an audiovisual device for displaying images and/or providing audio,
a method of
combining interactive gaming aspects into a linear story, comprising: a)
presenting the linear
story via the audiovisual device using at least an audio narrative, the audio
narrative voice by
a third party not present with the user and the third party's voice provided
as the narrative via
a speaker in a vicinity of the user; b) detecting at least one of a movement
and a voice
command by a user via the capture device; c) identifying whether the movement
and/or the
voice command detected in said step b) is an interaction with the linear story
that alters the
linear story to include a story branch having at least one of additional
images and additional
narrative not included in the default set of images and/or narrative; and d)
altering the linear
story by presenting at least one of the additional images and additional
narrative to a user via
the audiovisual device.
10003e1 According to a further aspect of the present invention, there
is provided a
method of combining interactive gaming aspects into a linear story,
comprising: a) presenting
the linear story via an audiovisual device using at least one of images and an
audio narrative,
the linear story presented as a complete story, beginning to end and including
a default set of
images, in the event no interaction by a user is perceived by a capture device
monitoring user
b
CA 02800533 2016-05-20
52785-26
movements; b) detecting a movement by a user via a capture device associated
with the
audiovisual device, wherein said step b) comprises the step of a user taking
over at least
partial control of a character displayed as part of the linear story, c)
identifying whether the
movement detected in said step b) is an interaction with the linear story
requiring a
modification from the linear story to include a story branch having additional
images not
included in the default set of images; d) determining whether the additional
images may be
rendered based on stored or processed data; and e) altering the linear story
by presenting the
additional images to a user via the audiovisual device if it is determined the
additional images
may be rendered in said step d).
[0003f] According to yet a further aspect of the present invention, there
is provided in a
system comprising a computing environment coupled to a capture device for
capturing user
motion and an audiovisual device for displaying images and/or providing audio,
a method of
combining interactive gaming aspects into a linear story, comprising: a)
presenting the linear
story via the audiovisual device using at least one of images and an audio
narrative, the linear
story having a default story and an altered story, the default story including
a default set of
images and/or narrative that is presented to a user if a user does not
interact with the story; b)
detecting at least one of a movement or a voice command by a user via the
capture device;
and c) altering the linear story to the altered story where at least one of
movement or voice
command are detected in said step b), the linear story being altered in said
step c) by
presenting at least one of the additional images and additional narrative to a
user via the
audiovisual device.
[0003g] According to still a further aspect of the present invention,
there is provided a
processor-readable storage medium for programming a processor to perform a
method of
combining interactive gaming aspects into a linear story, comprising: a)
presenting the linear
story via an audiovisual device using at least one of images and an audio
narrative, the linear
story presented as a complete story, beginning to end and including a default
set of images, in
the event no interaction by a user is perceived by a capture device monitoring
user
movements; b) detecting user interaction with the story by a user via a
capture device to alter
the linear story of the default set of images; c) altering the linear story to
a story branch by
presenting images in addition to or instead of the default set of images to a
user via the
1 c
CA 02800533 2016-05-20
52785-26
audiovisual device if user interaction is received in said step (b) to alter
the linear story of the
default set of images; and d) scoring a user's interaction where the
interaction corresponds to
awarding or taking away a predetermined number of points based on how the user
interacts
with the story.
[0003h] According to another aspect of the present invention, there is
provided a
system for combining interactive gaming aspects into a linear story,
comprising: an
audiovisual device operable to present at least one of images and an audio
narration; an image
capture device operable to capture at least one of image and audio data from a
user; and a
computing environment coupled to the audiovisual device and image capture
device, the
computing environment operable to: a) present the linear story via the
audiovisual device
using at least one of images and an audio narrative, the linear story
presented as a complete
story, beginning to end and including a default set of images, in the event no
interaction by a
user is perceived by the capture device; b) detect an exploration gesture via
the capture
device; e) branch from the linear story to a story branch upon identifying the
exploration
gesture in said step b), the branch including: el) sensing a point on the
audiovisual device
indicated by the user to be a desired viewing perspective, and c2) displaying
the virtual object
from the viewing perspective indicated in step cl).
[0004] In one embodiment, a user may alter the linear story by
performing a
predefined exploration gesture. This gesture, when detected by the capture
device and
recognized by the computing environment, brings the user into the 3-D world of
the displayed
image. In particular, the image displayed on the screen changes to create the
impression that a
user is stepping into the 3-D virtual world to allow a user to move around
within a scene, and
to explore and examine virtual objects from different perspectives in the
scene, or to peer
around virtual objects in the scene.
[0005] In one embodiment, the present system relates to a method of
combining
interactive gaming aspects into a linear story. The method includes the steps
of a) presenting
the linear story via an audiovisual device using at least one of images and an
audio narrative,
the linear story having a default set of images and/or narrative that is
id
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
presented to a user if a user does not interact with the story; b) detecting
at least one of a
movement and a voice command by a user via a capture device; c) identifying
whether the
movement and/or the voice command detected in said step b) is an interaction
with the
linear story that alters the linear story to include a story branch having at
least one of
additional images and additional narrative not included in the default set of
images and/or
narrative; and d) altering the linear story by presenting at least one of the
additional
images and additional narrative to a user via the audiovisual device.
[0006] In another embodiment, the present system relates to a computer-
readable
medium for programming a processor to perform a method of combining
interactive
gaming aspects into a linear story, including the steps of: a) presenting the
linear story via
an audiovisual device using at least one of images and an audio narrative, the
linear story
presented as a complete story, beginning to end and including a default set of
images, in
the event no interaction by a user is perceived by a capture device monitoring
user
movements; b) detecting a movement by a user via a capture device associated
with the
audiovisual device; c) identifying whether the movement detected in said step
b) is an
interaction with the linear story requiring a modification from the linear
story to include a
story branch having additional images not included in the default set of
images; d)
determining whether the additional images may be rendered based on stored or
processed
data; e) altering the linear story by presenting the additional images to a
user via the
audiovisual device if it is determined the additional images may be rendered
in said step
d); and f) scoring a user's interaction where the interaction corresponds to
awarding or
taking away a predetermined number of points based on the interaction.
[0007] In a further embodiment, the present system relates to a system for
combining
interactive gaming aspects into a linear story. The system includes an
audiovisual device
for presenting at least one of images and an audio narration; an image capture
device for
capturing at least one of image and audio data from a user; and a computing
environment
coupled to the audiovisual device and image capture device. The computing
environment
operates to a) present the linear story via the audiovisual device using at
least one of
images and an audio narrative, the linear story presented as a complete story,
beginning to
end and including a default set of images, in the event no interaction by a
user is perceived
by the capture device; b) detect a movement by a user via the capture device;
c) identify
whether the detected movement is an exploration gesture; d) branch from the
linear story
to a story branch upon identifying the movement as an exploration gesture. The
branching
includes the operations of dl) sensing a point on the audiovisual device
indicated by the
2
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
user, d2) calculating a 3-D real world vector from a portion of the user to
the point on the
audiovisual device indicated by the user, d3) translating the 3-D real world
vector to a 3-D
machine space vector having a start point at the current view perspective and
an end point
at the virtual object in 3-D machine space, and d4) displaying the virtual
object from a
viewing perspective at the end point of the 3-D machine space vector.
[0008] This Summary is provided to introduce a selection of concepts in a
simplified
form that are further described below in the Detailed Description. This
Summary is not
intended to identify key features or essential features of the claimed subject
matter, nor is
it intended to be used as an aid in determining the scope of the claimed
subject matter.
Furthermore, the claimed subject matter is not limited to implementations that
solve any or
all disadvantages noted in any part of this disclosure.
BRIEF DESCRIPTION OF THE DRAWINGS
[0009] FIGURE lA illustrates an example embodiment of a target recognition,
analysis,
and tracking system for providing an interactive story experience.
[0010] FIGURE 1B illustrates a further example embodiment of a target
recognition,
analysis, and tracking system for providing an interactive story experience.
[0011[ FIGURE 2 illustrates an example embodiment of a capture device that may
be
used in a target recognition, analysis, and tracking system.
[0012] FIGURE 3A illustrates an example embodiment of a computing environment
that
may be used to interpret one or more gestures in a target recognition,
analysis, and
tracking system.
[0013] FIGURE 3B illustrates another example embodiment of a computing
environment that may be used to interpret one or more gestures in a target
recognition,
analysis, and tracking system.
[0014] FIGURE 4 illustrates a skeletal mapping of a user that has been
generated from
the target recognition, analysis, and tracking system of Figs 1A-2.
[0015] FIGURE 5 is a high level flowchart of the operation of an embodiment of
the
present technology for providing an interactive story experience.
[0016] FIGURE 6 is a flowchart of the operation of an embodiment of the
present
technology for correlating a voice detected by the capture device with the
interactive story
experience.
3
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[0017] FIGURE 7 is a flowchart of the operation of an embodiment of the
present
technology for 3-D exploration of a virtual scene.
[0018[ FIGURE 8 is a flowchart of the operation of an embodiment of the
present
technology for a user controlling the actions of an onscreen character.
[0019] FIGURE 9 is a flowchart of the operation of an embodiment of the
present
technology for a user interacting with a scene to alter a plot of the
interactive story
experience.
[0020] FIGURE 9A is a flowchart of the operation of an alternative embodiment
of the
present technology for a user interacting with a scene to alter a plot of the
interactive story
experience where the scene is presented in pre-recorded video.
[0021] FIGURE 10 is an example of a user performing an exploration gesture to
explore
and investigate virtual objects within a displayed scene.
[0022] FIGURE 11 illustrates a branching subplot which re-converges to a
single story
outcome.
[0023] FIGURE 12 illustrates a branching plot which results in one of a
plurality of
story outcomes.
[0024] FIGURE 13 is a block diagram showing a gesture recognition engine for
recognizing gestures.
[0025] FIGURE 14 is a flowchart of the operation of the gesture recognition
engine of
Fig. 13.
DETAILED DESCRIPTION
[0026] Embodiments of the present technology will now be described with
reference to
Figs. 1A-14, which in general relate to a system and method for providing an
interactive
story experience which combines interactive gaming aspects into a linear
story. A NUI
system is provided for running an interactive story application. If run
without user
interaction, the story application provides a linear story to a user start to
finish.
Alternatively, a user may interact with the story application via the NUT
system to perform
a variety of actions.
[0027] In one embodiment, a user may alter the linear story by performing a
predefined
exploration gesture. This gesture signals to the system that the user desires
to step into
and explore the three-dimensional (3-D) virtual world displayed to the user.
Depending
on the exploration gesture performed, the displayed image changes to create
the
impression that a user is entering into the 3-D virtual world to allow a user
to move around
within a scene, and to explore and examine virtual objects from different
perspectives in
4
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
the scene. A user may also peer behind virtual objects in the scene to see the
back side of
these virtual objects or to examine more closely other objects obscured by the
foreground
objects.
[0028] While exploring within the 3-D virtual world, or by performing other
gestures or
movements, a user may alter the plot of the linear story. In such embodiments,
the story
application may branch to other subplots and possibly other story outcomes.
[0029] Referring initially to Figs. 1A-2, the hardware for implementing the
present
technology includes a target recognition, analysis, and tracking system 10
which may be
used to recognize, analyze, and/or track a human target such as the user 18.
Embodiments
of the target recognition, analysis, and tracking system 10 include a
computing
environment 12 for executing a gaming or other application, such as an
interactive story
application as explained below. The computing environment 12 may include
hardware
components and/or software components such that computing environment 12 may
be
used to execute gaming and non-gaming applications. In one embodiment,
computing
environment 12 may include a processor such as a standardized processor, a
specialized
processor, a microprocessor, or the like that may execute instructions stored
on a processor
readable storage device for performing processes described herein.
[0030] The system 10 further includes a capture device 20 for capturing image
and
audio data relating to one or more users and/or objects sensed by the capture
device. In
embodiments, the capture device 20 may be used to capture information relating
to
movements, gestures and speech of one or more users, which information is
received by
the computing environment and used to render, interact with and/or control
aspects of a
gaming or other application. Examples of the computing environment 12 and
capture
device 20 are explained in greater detail below.
[0031] Embodiments of the target recognition, analysis and tracking system 10
may be
connected to an audio/visual device 16 having a display 14. The device 16 may
for
example be a television, a monitor, a high-definition television (HDTV), or
the like that
may provide game or application visuals and/or audio to a user. For example,
the
computing environment 12 may include a video adapter such as a graphics card
and/or an
audio adapter such as a sound card that may provide audio/visual signals
associated with
the game or other application. The audio/visual device 16 may receive the
audio/visual
signals from the computing environment 12 and may then output the game or
application
visuals and/or audio associated with the audio/visual signals to the user 18.
According to
one embodiment, the audio/visual device 16 may be connected to the computing
5
- -
CA 2800533 2017-03-03
52785-26
environment 12 via, for example, an S-Video cable, a coaxial cable, an HDMI
cable, a DV1
cable, a VGA cable, a component video cable, or the like.
[0032] As shown in Figs. 1A and 1B, in an example embodiment, the
story application
executing on the computing environment 12 may present any of various story
settings.
Fig. lA shows a scene 19 including a house 21, monsters 23 and clouds 25. As
explained
below, a user may interact with the scene 19 in a variety of ways. In one
example, a user may
move clouds 25 together as shown which may alter the linear story presented by
the story
application. For example, moving the clouds together may cause it to rain.
[0033] In embodiments, the computing environment 12, the A/V device 16
and the
capture device 20 may cooperate to render an onscreen character 23 on display
14 which is at
least partially controlled by the user 18. As shown in Fig. 1B, the onscreen
character 23
mimics the movements of the user 18 in real world space in a monkey-see-monkey-
do
fashion. Thus, the user 18 may perform movements which control the movements
and actions
of the character 23 on the display 14. Moreover, a user may perform certain
movements which
are recognized by the computing environment as predefined gestures. These
predefined
gestures may cause a controlled character 23 to perform certain actions
associated in memory
with the predefined gestures. Predefined gestures may be used to initiate a
variety of other
actions as explained below.
[0034] The scene 19 of Figs. lA and 1B is one of many different scenes
which may be
generated by the story application running on computing environment 12.
Moreover, the
system 10 may further be used to interpret user 18 movements as operating
system and/or
application controls that are outside the realm of the story application
running on computing
environment 12.
[0035] Suitable examples of a system 10 and components thereof are
found in the
following co-pending patent applications: United States Patent No. 8,379,101,
entitled
"Environment And/Or Target Segmentation," filed May 29, 2009; United States
Patent
Publication No. 2011/0025689, entitled "Auto Generating a Visual
Representation," filed
July 29, 2009; United States Patent No. 8,856,691, entitled "Gesture Tool,"
filed
6
CA 2800533 2017-03-03
52785-26
May 29, 2009; United States Patent No. 8,295,546, entitled "Pose Tracking
Pipeline," filed
October 21, 2009; United States Patent No. 8,744,121, entitled "Device for
Identifying and
Tracking Multiple Humans Over Time," filed May 29, 2009; United States Patent
No. 8,564,534, entitled "Human Tracking System," filed October 7, 2009; United
States
Patent No. 7,996,793, entitled "Gesture Recognizer System Architecture," filed
April 13,
2009; United States Patent No. 8,487,938, entitled ''Standard Gestures," filed
February 23,
2009; and United States Patent No. 8,856,691, entitled "Gesture Tool," filed
May 29, 2009.
6a
=
CA 2800533 2017-03-03
=
52785-26
[0036] Fig. 2 illustrates an example embodiment of the capture device 20 that
may be
used in the target recognition, analysis, and tracking system 10. In an
example =
embodiment, the capture device 20 may be configured to capture video having a
depth
image that may include depth values via any suitable technique including, for
example,
time-of-flight, structured light, stereo image, or the like. According to one
embodiment,
the capture device 20 may organize the calculated depth information into "Z
layers," or
layers that may be perpendicular to a Z axis extending from the depth camera
along its line
of sight.
[0037] As shown in Fig. 2, the capture device 20 may include an image camera
component 22. According to an example embodiment, the image camera component
22
may be a depth camera that may capture the depth image of a scene. The depth
image
may include a two-dimensional (2-D) pixel area of the captured scene where
each pixel in
the 2-D pixel area may represent a depth value such as a length or distance
in, for
example, centimeters, Millimeters, or the like of an object in the captured
scene from the
camera,
[0038] As shown in Fig. 2, according to an example embodiment, the image
camera
component 22 may include an IR light component 24, a three-dimensional (3-D)
camera
26, and an RUB camera 28 that may be used to capture the depth image of a
scene. For
example, in time-of-flight analysis, the IR light component 24 of the capture
device 20
may emit an infrared light onto the scene and may then use sensors (not shown)
to detect
the backscattered light from the surface of one or more targets and objects in
the scene
using, for example, the 3-D camera 26 and/or the RGB camera 28.
[0039] In some embodiments, pulsed infrared light may be used such that 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 20
to a
particular location on the targets or objects in the scene. Additionally, in
other example
embodiments, the phase of the outgoing light wave may be compared to the phase
of the
incoming light wave to determine a phase shift. The phase shift may then be
used to
determine a physical distance from the capture device 20 to a particular
location on the
targets or objects.
7
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[0040] According to another example embodiment, time-of-flight analysis may be
used
to indirectly determine a physical distance from the capture device 20 to a
particular
location on the targets or objects by analyzing the intensity of the reflected
beam of light
over time via various techniques including, for example, shuttered light pulse
imaging.
[0041] In another example embodiment, the capture device 20 may use a
structured light
to capture depth information. In such an analysis, patterned light (i.e.,
light displayed as a
known pattern such as a grid pattern or a stripe pattern) may be projected
onto the scene
via, for example, the IR light component 24. Upon striking the surface of one
or more
targets or objects in the scene, the pattern may become deformed in response.
Such a
deformation of the pattern may be captured by, for example, the 3-D camera 26
and/or the
RGB camera 28 and may then be analyzed to determine a physical distance from
the
capture device 20 to a particular location on the targets or objects.
[0042] According to another embodiment, the capture device 20 may include two
or
more physically separated cameras that may view a scene from different angles,
to obtain
visual stereo data that may be resolved to generate depth information. In
another example
embodiment, the capture device 20 may use point cloud data and target
digitization
techniques to detect features of the user.
[0043] The capture device 20 may further include a microphone 30. The
microphone 30
may include a transducer or sensor that may receive and convert sound into an
electrical
signal. According to one embodiment, the microphone 30 may be used to reduce
feedback
between the capture device 20 and the computing environment 12 in the target
recognition, analysis, and tracking system 10. Additionally, the microphone 30
may be
used to receive audio signals that may also be provided by the user to control
applications
such as game applications, non-game applications, or the like that may be
executed by the
computing environment 12.
[0044] In an example embodiment, the capture device 20 may further include a
processor 32 that may be in operative communication with the image camera
component
22. The processor 32 may include a standardized processor, a specialized
processor, a
microprocessor, or the like that may execute instructions that may include
instructions for
receiving the depth image, determining whether a suitable target may be
included in the
depth image, converting the suitable target into a skeletal representation or
model of the
target, or any other suitable instruction.
8
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[0045] The capture device 20 may further include a memory component 34 that
may
store the instructions that may be executed by the processor 32, images or
frames of
images captured by the 3-D camera or RGB camera, or any other suitable
information,
images, or the like. According to an example embodiment, the memory component
34
may include random access memory (RAM), read only memory (ROM), cache, Flash
memory, a hard disk, or any other suitable storage component. As shown in Fig.
2, in one
embodiment, the memory component 34 may be a separate component in
communication
with the image camera component 22 and the processor 32. According to another
embodiment, the memory component 34 may be integrated into the processor 32
and/or
the image camera component 22.
[0046] As shown in Fig. 2, the capture device 20 may be in communication with
the
computing environment 12 via a communication link 36. The communication link
36 may
be a wired connection including, for example, a USB connection, a Firewire
connection,
an Ethernet cable connection, or the like and/or a wireless connection such as
a wireless
802.11b, g, a, or n connection. According to one embodiment, the computing
environment
12 may provide a clock to the capture device 20 that may be used to determine
when to
capture, for example, a scene via the communication link 36.
[0047] Additionally, the capture device 20 may provide the depth information
and
images captured by, for example, the 3-D camera 26 and/or the RGB camera 28,
and a
skeletal model that may be generated by the capture device 20 to the computing
environment 12 via the communication link 36. A variety of known techniques
exist for
determining whether a target or object detected by capture device 20
corresponds to a
human target. Skeletal mapping techniques may then be used to determine
various spots
on that user's skeleton, joints of the hands, wrists, elbows, knees, nose,
ankles, shoulders,
and where the pelvis meets the spine. Other techniques include transforming
the image
into a body model representation of the person and transforming the image into
a mesh
model representation of the person.
[0048] The skeletal model may then be provided to the computing environment 12
such
that the computing environment may perform a variety of actions. The computing
environment may further determine which controls to perform in an application
executing
on the computer environment based on, for example, gestures of the user that
have been
recognized from the skeletal model. For example, as shown, in Fig. 2, the
computing
environment 12 may include a gesture recognition engine 190 for determining
when the
user has performed a predefined gesture.
9
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[0049] Fig. 3A illustrates an example embodiment of a computing environment
that may
be used to interpret one or more positions and motions of a user in a target
recognition,
analysis, and tracking system. The computing environment such as the computing
environment 12 described above with respect to Figs. 1A-2 may be a multimedia
console
100, such as a gaming console. As shown in Fig. 3A, the multimedia console 100
has a
central processing unit (CPU) 101 having a level 1 cache 102, a level 2 cache
104, and a
flash ROM 106. The level 1 cache 102 and a level 2 cache 104 temporarily store
data and
hence reduce the number of memory access cycles, thereby improving processing
speed
and throughput. The CPU 101 may be provided having more than one core, and
thus,
additional level 1 and level 2 caches 102 and 104. The flash ROM 106 may store
executable code that is loaded during an initial phase of a boot process when
the
multimedia console 100 is powered ON.
[0050] A graphics processing unit (GPU) 108 and a video encoder/video codec
(coder/decoder) 114 form a video processing pipeline for high speed and high
resolution
graphics processing. Data is carried from the GPU 108 to the video
encoder/video codec
114 via a bus. The video processing pipeline outputs data to an AN
(audio/video) port
140 for transmission to a television or other display. A memory controller 110
is
connected to the GPU 108 to facilitate processor access to various types of
memory 112,
such as, but not limited to, a RAM.
[0051] The multimedia console 100 includes an I/O controller 120, a system
management controller 122, an audio processing unit 123, a network interface
controller
124, a first USB host controller 126, a second USB host controller 128 and a
front panel
I/O subassembly 130 that are preferably implemented on a module 118. The USB
controllers 126 and 128 serve as hosts for peripheral controllers 142(1)-
142(2), a wireless
adapter 148, and an external memory device 146 (e.g., flash memory, external
CD/DVD
ROM drive, removable media, etc.). The network interface 124 and/or wireless
adapter
148 provide access to a network (e.g., the Internet, home network, etc.) and
may be any of
a wide variety of various wired or wireless adapter components including an
Ethernet
card, a modem, a Bluetooth module, a cable modem, and the like.
[0052] System memory 143 is provided to store application data that is loaded
during
the boot process. A media drive 144 is provided and may comprise a DVD/CD
drive, hard
drive, or other removable media drive, etc. The media drive 144 may be
internal or
external to the multimedia console 100. Application data may be accessed via
the media
drive 144 for execution, playback, etc. by the multimedia console 100. The
media drive
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
144 is connected to the I/O controller 120 via a bus, such as a Serial ATA bus
or other
high speed connection (e.g., IEEE 1394).
[0053[ The system management controller 122 provides a variety of service
functions
related to assuring availability of the multimedia console 100. The audio
processing unit
123 and an audio codec 132 form a corresponding audio processing pipeline with
high
fidelity and stereo processing. Audio data is carried between the audio
processing unit
123 and the audio codec 132 via a communication link. The audio processing
pipeline
outputs data to the AN port 140 for reproduction by an external audio player
or device
having audio capabilities.
[0054] The front panel I/O subassembly 130 supports the functionality of the
power
button 150 and the eject button 152, as well as any LEDs (light emitting
diodes) or other
indicators exposed on the outer surface of the multimedia console 100. A
system power
supply module 136 provides power to the components of the multimedia console
100. A
fan 138 cools the circuitry within the multimedia console 100.
[0055] The CPU 101, GPU 108, memory controller 110, and various other
components
within the multimedia console 100 are interconnected via one or more buses,
including
serial and parallel buses, a memory bus, a peripheral bus, and a processor or
local bus
using any of a variety of bus architectures. By way of example, such
architectures can
include a Peripheral Component Interconnects (PCT) bus, PCT-Express bus, etc.
[0056] When the multimedia console 100 is powered ON, application data may be
loaded from the system memory 143 into memory 112 and/or caches 102, 104 and
executed on the CPU 101. The application may present a graphical user
interface that
provides a consistent user experience when navigating to different media types
available
on the multimedia console 100. In operation, applications and/or other media
contained
within the media drive 144 may be launched or played from the media drive 144
to
provide additional functionalities to the multimedia console 100.
[0057] The multimedia console 100 may be operated as a standalone system by
simply
connecting the system to a television or other display. In this standalone
mode, the
multimedia console 100 allows one or more users to interact with the system,
watch
movies, or listen to music. However, with the integration of broadband
connectivity made
available through the network interface 124 or the wireless adapter 148, the
multimedia
console 100 may further be operated as a participant in a larger network
community.
11
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[0058] When the multimedia console 100 is powered ON, a set amount of hardware
resources are reserved for system use by the multimedia console operating
system. These
resources may include a reservation of memory (e.g., 16MB), CPU and GPU cycles
(e.g.,
5%), networking bandwidth (e.g., 8 kbs), etc. Because these resources are
reserved at
system boot time, the reserved resources do not exist from the application's
view.
[0059] In particular, the memory reservation preferably is large enough to
contain the
launch kernel, concurrent system applications and drivers. The CPU reservation
is
preferably constant such that if the reserved CPU usage is not used by the
system
applications, an idle thread will consume any unused cycles.
[0060] With regard to the GPU reservation, lightweight messages generated by
the
system applications (e.g., popups) are displayed by using a GPU interrupt to
schedule code
to render popup into an overlay. The amount of memory required for an overlay
depends
on the overlay area size and the overlay preferably scales with screen
resolution. Where a
full user interface is used by the concurrent system application, it is
preferable to use a
resolution independent of the application resolution. A scaler may be used to
set this
resolution such that the need to change frequency and cause a TV resynch is
eliminated.
[0061[ After the multimedia console 100 boots and system resources are
reserved,
concurrent system applications execute to provide system functionalities. The
system
functionalities are encapsulated in a set of system applications that execute
within the
reserved system resources described above. The operating system kernel
identifies threads
that are system application threads versus gaming application threads. The
system
applications are preferably scheduled to run on the CPU 101 at predetermined
times and
intervals in order to provide a consistent system resource view to the
application. The
scheduling is to minimize cache disruption for the gaming application running
on the
console.
[0062] When a concurrent system application requires audio, audio processing
is
scheduled asynchronously to the gaming application due to time sensitivity. A
multimedia
console application manager (described below) controls the gaming application
audio
level (e.g., mute, attenuate) when system applications are active.
[0063] Input devices (e.g., controllers 142(1) and 142(2)) are shared by
gaming
applications and system applications. The input devices are not reserved
resources, but are
to be switched between system applications and the gaming application such
that each will
have a focus of the device. The application manager preferably controls the
switching of
input stream, without knowledge of the gaming application's knowledge and a
driver
12
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
maintains state information regarding focus switches. The cameras 26, 28 and
capture
device 20 may define additional input devices for the console 100.
[0064] Fig. 3B illustrates another example embodiment of a computing
environment 220
that may be the computing environment 12 shown in Figs. 1A-2 used to interpret
one or
more positions and motions in a target recognition, analysis, and tracking
system. The
computing system environment 220 is only one example of a suitable computing
environment and is not intended to suggest any limitation as to the scope of
use or
functionality of the presently disclosed subject matter. Neither should the
computing
environment 220 be interpreted as having any dependency or requirement
relating to any
one or combination of components illustrated in the exemplary operating
environment
220. In some embodiments, the various depicted computing elements may include
circuitry configured to instantiate specific aspects of the present
disclosure. For example,
the term circuitry used in the disclosure can include specialized hardware
components
configured to perform function(s) by firmware or switches. In other example
embodiments, the term circuitry can include a general purpose processing unit,
memory,
etc., configured by software instructions that embody logic operable to
perform
function(s). In example embodiments where circuitry includes a combination of
hardware
and software, an implementer may write source code embodying logic and the
source code
can be compiled into machine readable code that can be processed by the
general purpose
processing unit. Since one skilled in the art can appreciate that the state of
the art has
evolved to a point where there is little difference between hardware,
software, or a
combination of hardware/software, the selection of hardware versus software to
effectuate
specific functions is a design choice left to an implementer. More
specifically, one of skill
in the art can appreciate that a software process can be transformed into an
equivalent
hardware structure, and a hardware structure can itself be transformed into an
equivalent
software process. Thus, the selection of a hardware implementation versus a
software
implementation is one of design choice and left to the implementer.
[0065] In Fig. 3B, the computing environment 220 comprises a computer 241,
which
typically includes a variety of computer readable media. Computer readable
media can be
any available media that can be accessed by computer 241 and includes both
volatile and
nonvolatile media, removable and non-removable media. The system memory 222
includes computer storage media in the form of volatile and/or nonvolatile
memory such
as ROM 223 and RAM 260. A basic input/output system 224 (BIOS), containing the
basic routines that help to transfer information between elements within
computer 241,
13
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
such as during start-up, is typically stored in ROM 223. RAM 260 typically
contains data
and/or program modules that are immediately accessible to and/or presently
being
operated on by processing unit 259. By way of example, and not limitation,
Fig. 3B
illustrates operating system 225, application programs 226, other program
modules 227,
and program data 228. One example of application program 226 is a story
application 226
used for presenting an interactive story experience to a user as explained
herein. Fig. 3B
further includes a graphics processor unit (GPU) 229 having an associated
video memory
230 for high speed and high resolution graphics processing and storage. The
GPU 229
may be connected to the system bus 221 through a graphics interface 231.
[0066] The computer 241 may also include other removable/non-removable,
volatile/nonvolatile computer storage media. By way of example only, Fig. 3B
illustrates
a hard disk drive 238 that reads from or writes to non-removable, nonvolatile
magnetic
media, a magnetic disk drive 239 that reads from or writes to a removable,
nonvolatile
magnetic disk 254, and an optical disk drive 240 that reads from or writes to
a removable,
nonvolatile optical disk 253 such as a CD ROM or other optical media. Other
removable/non-removable, volatile/nonvolatile computer storage media that can
be used in
the exemplary operating environment include, but are not limited to, magnetic
tape
cassettes, flash memory cards, digital versatile disks, digital video tape,
solid state RAM,
solid state ROM, and the like. The hard disk drive 238 is typically connected
to the
system bus 221 through a non-removable memory interface such as interface 234,
and
magnetic disk drive 239 and optical disk drive 240 are typically connected to
the system
bus 221 by a removable memory interface, such as interface 235.
[0067] The drives and their associated computer storage media discussed above
and
illustrated in Fig. 3B, provide storage of computer readable instructions,
data structures,
program modules and other data for the computer 241. In Fig. 3B, for example,
hard disk
drive 238 is illustrated as storing operating system 258, application programs
257, other
program modules 256, and program data 255. Note that these components can
either be
the same as or different from operating system 225, application programs 226,
other
program modules 227, and program data 228. Operating system 258, application
programs 257, other program modules 256, and program data 255 are given
different
numbers here to illustrate that, at a minimum, they are different copies. A
user may enter
commands and information into the computer 241 through input devices such as a
keyboard 251 and a pointing device 252, commonly referred to as a mouse,
trackball or
touch pad. Other input devices (not shown) may include a microphone, joystick,
game
14
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
pad, satellite dish, scanner, or the like. These and other input devices are
often connected
to the processing unit 259 through a user input interface 236 that is coupled
to the system
bus, but may be connected by other interface and bus structures, such as a
parallel port,
game port or a universal serial bus (USB). The cameras 26, 28 and capture
device 20 may
define additional input devices for the console 100. A monitor 242 or other
type of
display device is also connected to the system bus 221 via an interface, such
as a video
interface 232. In addition to the monitor, computers may also include other
peripheral
output devices such as speakers 244 and printer 243, which may be connected
through an
output peripheral interface 233.
[0068] The computer 241 may operate in a networked environment using logical
connections to one or more remote computers, such as a remote computer 246.
The
remote computer 246 may be a personal computer, a server, a router, a network
PC, a peer
device or other common network node, and typically includes many or all of the
elements
described above relative to the computer 241, although only a memory storage
device 247
has been illustrated in Fig. 3B. The logical connections depicted in Fig. 3B
include a local
area network (LAN) 245 and a wide area network (WAN) 249, but may also include
other
networks. Such networking environments are commonplace in offices, enterprise-
wide
computer networks, intranets and the Internet.
[0069] When used in a LAN networking environment, the computer 241 is
connected to
the LAN 245 through a network interface or adapter 237. When used in a WAN
networking environment, the computer 241 typically includes a modem 250 or
other
means for establishing communications over the WAN 249, such as the Internet.
The
modem 250, which may be internal or external, may be connected to the system
bus 221
via the user input interface 236, or other appropriate mechanism. In a
networked
environment, program modules depicted relative to the computer 241, or
portions thereof,
may be stored in the remote memory storage device. By way of example, and not
limitation, Fig. 3B illustrates remote application programs 248 as residing on
memory
device 247. It will be appreciated that the network connections shown are
exemplary and
other means of establishing a communications link between the computers may be
used.
[0070] Fig. 4 depicts an example skeletal mapping of a user that may be
generated from
the capture device 20. In this embodiment, a variety of joints and bones are
identified:
each hand 302, each forearm 304, each elbow 306, each bicep 308, each shoulder
310,
each hip 312, each thigh 314, each knee 316, each foreleg 318, each foot 320,
the head
322, the torso 324, the top 326 and the bottom 328 of the spine, and the waist
330. Where
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
more points arc tracked, additional features may be identified, such as the
bones and joints
of the fingers or toes, or individual features of the face, such as the nose
and eyes.
[0071[ Fig. 5 is a high level flowchart of the operation of an embodiment of
the present
technology for presenting an interactive story experience via a natural user
interface. At
step 400, a user may launch the system 10 and activate computing environment
12 and
capture device 20. In step 404, the system 10 runs a story application 226. In
step 406,
the story application presents the next frame of a story to the user over
display 14.
[0072] The story may be presented graphically over display 14 and may have an
associated audio narrative. The story may be displayed in discrete, still-
image panels, i.e.,
a series of static images presented in succession as still frames on display
14. The story
may alternatively be presented in dynamic computer-graphics (CG) animation, or
as
scenes shot with a video camera with live actors. The audio narrative may be
audio
presented by the story application, by a user and/or by a third party not
present while the
story is presented, as explained below. The audio narrative may also include
dialog
between characters of a presented story. Again, this dialog between characters
may be
presented by story application, by one or more users and/or by one or more
third parties
not present while the story is presented.
[0073] In embodiments using CG animation, the story application 226 may
present a
first frame of animation generated by the GPU of the computing environment 12,
which
frame may be refreshed at the refresh rate of the capture device (for example
at 30Hz).
The frame rate may be quicker or slower than that in further embodiments. In
embodiments using static-image panels, a static image is akin to a page of a
book or
comic. The static image may be presented on the display for example for
several seconds.
In embodiments using video, the frame may be refreshed at the frame rate of
the video,
which may again be for example at 30Hz.
[0074] In embodiments, upon running the story application, a user 18 need not
interact
with the presented story. That is, the user may simply view and/or listen to
the story as it
plays from start to end. In further embodiments described below, a user may
alternatively
interact with the story presented by the story application 226.
[0075] The capture device 20 is monitoring the user as a user watches and/or
interacts
with the story application. In step 408, if the capture device 20 senses the
user leaving the
field of view, the story application may pause at step 412 until the user
reenters the field of
view. Steps 408 and 412 may be omitted in further embodiments. As indicated
above, a
user may simply sit and view and/or listen to the story presented by the story
application.
16
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
In step 416, if no user interaction is sensed, the story will simply continue
until its
completion. However, if user interaction is sensed in step 416 the system in
general
determines the interaction and performs different operations depending on the
interaction
as explained below.
[0076] In step 418, the story application may check whether the microphone
array 30 of
capture device 20 detected a voice. Techniques are known for differentiating
sounds
picked up by the microphone array 30 to determine whether one or more of the
sounds is a
human voice. Microphone array 30 may include various known filters, such as
for
example a high pass filter, to attenuate low frequency noise which may
detected by the
microphone array 30.
[0077] If a voice is detected in step 418, the system performs the steps set
forth in Fig. 6
as will now be described. In embodiments, it may be desirable to identify
whether a
particular user is the speaker or whether the voice is coming from some other
source.
Various techniques exist for associating a voice with a user within the field
of view, such
as for example prior correlation of voice characteristics to a particular
user, and acoustic
source localization techniques. These and other techniques may be used to
identify a
speaker in step 450. Step 450 may be omitted in further embodiments.
[0078] The story application may have associated narrative for narrating the
story which
may be broadcast over speakers associated with the audio/visual device 16.
However, a
narrative may alternatively be displayed in words on the screen so that they
can be read by
a user listening to the story. In one example, a child may be learning to
read, or a parent
may be reading the story to the child as the child watches the story unfold on
display 14.
As an alternative to the words appearing on the screen, a user may have a
computing
device that is paired to the computing environment 12 and participating in the
same
instance of the story application 226. In such embodiments, the words for the
narrative
may be displayed on the user's paired computing device instead of on display
14.
[0079] In further embodiments, it is envisioned that the narrative be read by
a third party
who is not then present when the story application 226 is showing the story on
system 10.
While the third party could be anyone, in embodiments, the third party may for
example
be a parent or grandparent who is not then present when the story application
is running,
but is desirous of being the voice of the narrative presented to a child
listening to and
watching the story on system 10.
17
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
[0080] In such embodiments, a third party may have pre-recorded the narrative
for the
story application and that recording may be played back as the story
application is running
to provide the narrative for the story. In this embodiment, the recording may
be played
back on an audio playback device either associated with or not associated with
the system
10. In a further embodiment, a third party may be reading the narrative for
the story
application 226 in real time as the story application runs on the system 10,
but the third
party is connected via a telephone or VOIP connection to the computing
environment 12.
[0081] In step 454, the story application determines whether the voice
perceived in step
418 correlates to a narrative for the story. Known voice analysis techniques
may be used
for this purpose, including parsing the known words of the narrative into
phonemes, doing
the same for the voice perceived by the microphone array 30, and comparing the
two
phoneme streams to find a match.
[0082] If, in step 454, the spoken voice is correlated to the narrative of the
story
application, the spoken voice may set the pace with which the story
application advances
the story. For example, where the story is presented in still image panels,
the story
application may determine in step 464 whether the last words of the narrative
associated
with a particular panel have been spoken. If not, it is not yet time to
advance to the next
panel and the flow may return to look for the next interaction as explained
below with
respect to Fig. 5. On the other hand, if the story application determines that
the last words
of the narrative associated with a particular panel have been spoken, the
story application
may advance to the next panel in step 466. The flow may return to look for the
next
interaction as explained below with respect to Fig. 5.
[0083] Where the image is video or dynamic animation, the story application
may
correlate the narrative to the spoken voice and speed up or slow down the
displayed
images to synchronize with the pace of the narrative spoken by the user or
third party.
The story application may cycle through the flowchart of Fig. 5 and may
periodically
check for a voice, check whether the voice correlates to a narrative of the
presented story,
and synchronize the presented images with the pace of the spoken narrative.
[0084] If the story application is unable to correlate a voice with a
narrative in step 454,
the application may next check in step 456 if the sound is recognized as an
audible
instruction to the story application or to the operation of system 10. If not,
the computing
environment 12 may return to Fig. 5 to look for another possible interaction
of a user with
the story application in step 422 as explained below. On the other hand, if
the voice is
recognized as instruction in step 456, the act associated with that
instruction may be
18
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
performed in step 460, and the system may then return to the flowchart of Fig.
5 to check
for the next interaction.
[0085] Returning now to Fig. 5, in step 422 the present system may look for a
specific
type of gesture, referred to herein as an "exploration gesture." In
particular, it is a feature
of the present technology to allow one type of interaction where a user, in
effect, steps into
the virtual world presented on the display 14, and explores and/or
investigates virtual
objects on the display. As one of a wide variety of examples, the story may
display a
room to a user. With no interaction by the user, the user may be shown the
room for a
period of time and then the story may move on to show other locations.
However, instead
of simply moving on, the user may perform an exploration gesture, indicating
their desire
to explore and investigate virtual objects within the room to get a closer
view and/or to see
the objects from different perspectives. In embodiments, it is also
contemplated that a
user may perform gestures and motions interpreted by the computing environment
12
which enable a user to pick up and manipulate virtual objects within a scene.
[0086] In step 422 of Fig. 5, the computing environment 12 looks for a
predefined
exploration gesture. A wide variety of movements and gestures by the user may
be set as
predefined exploration gestures in embodiments of the present technology. In
one such
embodiment described now with respect to Fig. 10, the capture device 20
captures head
and/or body movements of a user. For example, in Fig. 10, the user has bent to
the side
and craned their neck, as the user might when trying to peer around or behind
an object in
the real world. The operation of the gesture recognition engine 190 is
explained below,
but the recognition engine 190 may have a predefined rule to look for such
body
movements and, when found, interprets them as an exploration gesture. In
addition to
craning the neck and/or bending at the waist, the exploration gesture may
additionally or
alternatively include another gesture, such as for example a pointing gesture
as shown in
Fig. 10.
[0087] It is appreciated that a wide variety of other body movements may be
defined as
exploration gestures in further embodiments. In some such embodiments, the
user
movements may have a correlation in the real world to the action the user
wishes to
accomplish in the virtual world. One example is set forth above, where the
user is bent to
the side and craning their neck to signify their desire to look around or
behind an object. In
further embodiments, a user may also or alternatively walk in the direction of
the display,
indicating their desire to step into the virtual scene. In further
embodiments, an arbitrary
set of gestures may be defined which have no real world significance. However,
the
19
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
arbitrary body and/or voice gestures may be developed and recorded by the
gesture
recognition engine 190 so that, when performed, the gesture recognition engine
recognizes
them, and performs the associated action, such as stepping into a virtual
scene to look
behind an object.
[0088] Once an exploration gesture is recognized in step 422, the computing
environment 12 performs steps 490 through 538 as will now be described with
respect to
the flowchart of Fig. 7. In step 490, the computing environment 12 determines
whether
the user wishes to step into the three-dimensional virtual world showing the
display to
view a displayed scene from another position. Again, this desire, as well as
the direction
the user would like to take into the virtual scene are controlled by the user
through
predefined head, hand or other gestures. This embodiment may operate where the
scene is
presented in CG animation. Where the scene is presented in either static
panels or
recorded video, it is contemplated that CG animation may be cut into those
display models
to provide exploration of the virtual scene as explained below. In a further
embodiment,
the video may be shot in 360 , which allows some level of entry and
exploration of the
user into the video scene.
[0089[ As one example, once the exploration gesture is performed, the capture
device 20
and computing device 12 may determine a point on the display on which the user
is
focused, such as for example a point 610 in Fig. 10. This point may be
determined by
capturing where the user's eyes are pointed and/or this point may be
determined by
capturing where a user's hand is pointed. In further embodiments, a user may
also or
alternatively walk in that direction. If it is determined in step 490 that the
user wishes to
view the scene from a different position, the computer environment may define
a vector in
step 494 along which the user desires to move in the virtual world.
[0090] The vector in step 494 may be determined based on one or more real
world three-
dimensional vectors 612 from a point of reference on the user to the point of
interest 610
on the display. In Fig. 10, the vectors 612 are from the user's eyes to the
point of interest
610 and from the user's pointed hand to the point of interest 610. The point
of reference
(eyes, hand, etc.) has a known x, y and z coordinate position.
[0091] The virtual scene shown on display 14 is represented in 3-D data. That
is, the
points in a virtual scene and on virtual objects within the scene are assigned
x, y and z
values to create a 3-D virtual space referred to herein as 3-D machine space.
Given a
known position of capture device 20 to the real world in which the user is
moving, there is
a known relation between the 3-D real world space and the 3-D machine space.
As such,
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
the vectors 612 may be translated from 3-D real world space to 3-D machine
space using
known transformation matrices. The translation of real world vectors 612 to 3-
D machine
space provide the vector in step 494 along which the user is to move into the
3-D virtual
scene. As explained below, in order to create the effect of the user moving
into the virtual
scene and examining virtual objects, the perspective of the display changes to
provide a
view of different areas and objects of a scene, and from different zoomed in
or zoomed out
positions. Again, this is possible because virtual objects are not merely
defined as two-
dimensional points on the display, but rather have 3-D definitions in machine
space.
[0092] In step 498, instead of immediately repositioning the user at a desired
location,
the user's view into the virtual machine world may be changed incrementally.
The
increments at which the user's view changes may be arbitrarily set, but in
embodiments,
the view changes so as to create the impression that the user is walking into
the scene at a
normal walking pace. In step 502, the view of the scene displayed on display
14 may be
updated to the incrementally changing view of step 498. Again, transformation
matrices
are known for translating the view of the displayed scene to any perspective
of the 3-D
machine space. In step 506, the scene may be rendered from the view of the new
position
determined in step 502.
[0093] The routine may then return to step 490 to determine if the user has
arrived at the
position within the virtual scene at which they would like to investigate an
object or
whether they would like to continue to move within the virtual scene. This may
be
indicated by the user's body position and where the user is focused on the
display, or by
some other arbitrary body movement or voice gesture. If the user would like to
continue
to move within the virtual scene, steps 490 through 506 are repeated until the
user has
arrived at their desired position within the virtual scene.
[0094] If step 490 determines the user is at the desired position in the
virtual scene (i.e.,
the scene is presented on the display from the desired perspective), the flow
may branch to
step 510 to determine if a user wishes to focus more closely on an object
within the scene
at that position. Again, this desire may be indicated by one or more
predefined gestures,
either mimicking real world movements that a user would make to move to and/or
focus
on objects in the real world, or arbitrary gestures which are defined for the
purpose of
navigating and focusing on objects within the virtual world.
21
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[0095] If it is determined in step 510 that the user wishes to focus more
closely on an
object in the scene, the computing environment 12 stores the current position
(i.e., the
current view of the scene) as a reference position in step 514. As explained
below, this
reference position will be used as the view to which the system returns when
the user is
done focusing in on a particular virtual object. In step 518, the computing
environment 12
determines a vector direction from the reference position to the virtual
object. This may
be accomplished as described above by detecting in the real world the user's
head position
in x, y, z space and where the user is looking on the display, and thereafter
translating that
vector into a vector in virtual machine space.
[0096] In step 522, an intermediate incremental position along this vector may
be
determined as described above. In step 524, the perspective of the scene may
be translated
to the position determined in step 522, and in step 528, the scene may be
rendered from
the view determined in step 524. In step 532, the system may determine if a
user is
finished focusing on a particular object within the virtual scene. This may be
indicated by
any of a variety of predefined gestures. If the system does not determine that
a user is
finished with the focus view, the flow returns at step 510, and steps 510
through 528 may
be repeated to provide further and additional focus on virtual objects within
the scene. On
the other hand, if a user performs a predefined gesture in step 532 indicating
that the user
has completed their focused view, the view may be translated back in step 536
to the view
from the reference position (stored in step 514).
[0097] If the computing environment 12 is unable to discern additional
exploration
gestures in steps 490 and 510, the flow may branch to a step 538 to see if a
user performs a
predefined gesture indicating that they are done exploring the scene. If not,
the flow may
loop back to step 490 to see if a user wishes to view the scene from a
different position,
and if not, the flow moves to step 510 to determine if the user wishes to
focus on an object
within the scene at that current position. On the other hand, if some
predefined gesture is
performed indicating the user is finished with exploring within the 3-D scene
in step 538,
the flow may return to Fig. 5 to check for the next type of user interaction.
[0098] It is appreciated that steps 490 through 538 are merely one example of
how a
user may move into and around the three-dimensional virtual world provided on
a display
14 by the story application.
22
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
[0099] In embodiments of the present system, in addition to watching a story
and
exploring within a 3-D virtual world, a user may also have the option of
controlling one or
more characters within the story. This embodiment may operate where the scene
is
presented in CG animation. Where the scene is presented in either static
panels or
recorded video, it is contemplated that CG animation may be cut into those
display models
to provide character control as explained below.
[00100] In embodiments, a user 18 may perform some predefined gesture
indicating the
user's desire to control the movements and/or actions of an onscreen character
23. The
predefined gestures may for example be arbitrary gestures coupled with a user
motion for
example pointing at a given character onscreen. When such character control is
permitted
by the story application 226, the user may be registered as that character in
step 426 and
the user may thereafter control that character as described below with respect
to steps 540
through 558 of Fig. 8.
[00101] After a user is registered as controlling a character, the user may
perform certain
motions and gestures which are used to animate and affect the behavior of the
controlled
onscreen character. In step 540, the computing environment determines whether
a user
has performed a predefined, recognized gesture. If so, the computing
environment checks
at step 544 whether the onscreen character is permitted to perform the action
corresponding to the recognized gesture. In particular, in embodiments, the
user does not
have complete control over the onscreen character's action or behavior, but
rather shares
control of the onscreen character with the story application 226. In
embodiments, the user
may control a character's movement to an extent, but the application may
define
boundaries to such movements, and may limit control of other aspects of the
onscreen
character, such as for example as relating to the character's behavior and
personality.
Unfettered control of the onscreen character by a user may prevent the story
application
from moving forward, if for example the user causes the onscreen character to
perform
certain actions that were not anticipated as possible story branches
(explained below).
However, it is understood that in further embodiments, a user may be given
unfettered
control of an onscreen character.
[00102] If a character 23 is permitted to perform the gesture action in step
542 by the
story application, the character performs that action associated with the
gesture in step
544. Fig. 1B shows an example where a user is given the ability to control the
upper body
of an onscreen character 23. This particular story application may recognize a
gesture of a
user raising their arms, and having that correspond to an onscreen character,
such as for
23
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
example a monster, raising their arms in a menacing manner. Upon recognition
of such a
user gesture in step 540 of Fig. 8, the character performs the corresponding
action in step
544.
[00103] If no recognized gesture was performed in step 540, the computing
environment
next checks in step 546 whether user movement is detected by the capture
device 20. If
so, the system checks at 550 whether the onscreen characters are permitted to
move as did
the user, as set forth above. If so, the onscreen character is animated with
the user's
movement in a monkey-see-monkey-do fashion in step 552. If the computing
environment does not detect a predefined gesture in step 540 or user movement
in step
546, the computing environment may return to step 428 of Fig. 5 to detect
other user
interaction with the scene as explained below.
[00104] In step 554 the system next checks whether the user has given some
sort of
predefined gesture indicating their desire to end control of the character. If
such gesture is
detected in step 554, the user's control of the character ends and the
character is
completely controlled by the story application 226 in step 556. If the system
detects user
movement at step 546 but the character is not permitted to move in that manner
in step
550, or if the user ends control of the character at step 554, the system may
return to step
428 in Fig. 5 to look for other interaction of a user with a displayed scene.
[00105] Returning now to Fig. 5, at step 428 the computing environment 12
looks for
some interaction of the user with the displayed scene, and in particular a
user interaction
which may affect an outcome of a sub-plot of the story, or affect the overall
outcome of
the story. If such interaction is detected, the system performs steps 560
through 588 of
Fig. 9. This may occur as a result of a voice command described above with
respect to
418, an exploration gesture described above with respect to step 422, the user
controlling
an onscreen character as described above with respect to step 426, or some
other
interaction with the story.
[00106] The degree of interactivity may in part be determined by the type of
images
displayed in the story. CG animations may offer a high degree of
interactivity, while still
panels and recorded video may offer less. It is understood that CG animations
may be cut
into still panels and/or recorded video to provide greater interactivity. In
embodiments, a
user may be given the opportunity to interact with the onscreen story at
discrete points in
the story. These points may be indicated to the user by a pause in the story
or some
prompt. In further embodiments, a user may have the option to interact with
the story at
any point during the presentation of the story by application 226.
24
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[00107] Upon interaction with a displayed scene at step 428, the system
initially performs
a step 560 of determining whether the user has performed a motion or a
recognized
gesture. If so, computing environment 12 next checks in step 564 whether the
action
associated with that motion or gesture requires a branch to a different story
line. There are
a variety of known methods for determining whether a user action requires a
branch to a
different story branch, and then determining how to proceed from that story
branch. In
one example, the story application may maintain state data values for all
objects and
characters within a story. When something with respect to a scene or character
changes,
the state data for the scene or character may change accordingly. These state
data values
may be used in rendering story objects or characters, and in controlling what
happens with
those objects or characters.
[00108] In embodiments, the story application may be able to branch to a
variety of
different story lines depending on the state data values for objects and
characters, which
state data may be altered as a result of user interaction with those objects
and/or
characters. In further embodiments, a user may perform certain gestures which
do not
interact with or affect onscreen objects or characters, but nonetheless may
result in a
change in the story line. As one example, a user may choose to leave a room
displayed on
the screen before vital aspects of the story to be shown and explained with
respect to that
room have been revealed.
[00109] In step 564, the computing environment 12 determines whether the
action
associated with a user-performed gesture requires a branch to a different
story line. As
noted, this may occur with state data values for objects and characters of a
story that have
been altered by a user. In particular, the state data values have changed so
that continuing
with the story as it existed prior to the user's gesture in step 560 would be
inconsistent
with the current state data values associated with objects, characters or the
story as a
whole. If the user's gesture requires a branch to a different story line, the
computing
environment 12 may check in step 568 whether there is a known branch of the
story
consistent with the user's interaction.
[00110] If the user does not perform a motion or recognized gesture in step
560, or the
user's motion / recognized gesture does not require a branch to a different
story line in
step 564, the system may return to Fig. 5 to look for any other type of
movement or
gesture in step 432 as explained below. Moreover, if the user has performed an
action
requiring a branch to a different story line, but there is no branch
consistent with the user's
interaction known or identifiable by the story application 226, the effect of
the user's
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
gesture on the story line may be ignored in step 568 and the flow may return
to step 432 in
Fig. 5 as explained below.
[00111] Assuming a user's gesture requires a branch to a new branch story
line, and that
story line is capable of being performed by the story application, the story
application may
modify the state data associated with objects, characters and the application
as a whole,
depending on what motion or gesture the user performed. Referring to Figs. 11
and 12,
some user interactions affect a story branch varying only a sub-plot of the
story, without
affecting the overall outcome. As seen in Fig. 11, a user may perform some
interaction
620 causing the story application to branch to branch 1, branch 2, ..., branch
N, and
thereafter all the branches re-converge to continue with the original story
line. A wide
variety of such sub-plot story branches are envisioned. For example, in Fig.
1A, a user
may perform gestures moving the clouds 25 together to the point where it rains
over the
house 21. The rain may have no effect on the overall plot. It may rain for a
while, the rain
may stop and the story line may continue as it would have had it not rained.
In further
embodiments, the application story may prompt a user to answer questions or
solve
puzzles, and the story line may branch to different sub-plots depending on the
user's
answers to the prompts. The story may re-converge and continue with the
original story
line once a user has successfully answered the questions or solved the
puzzles.
[00112] On the other hand, other types of user interactions may affect a story
branch
varying the overall outcome of the story. In other words, the story will end
differently
depending on the user's interactions with the story. For example, in Fig. 11,
a user
performs an interaction 624 which causes a story branch to one of N branches
which do
not re-converge. Moreover, any one of those branches may then itself branch on
further
user interaction. For example, if user interaction 624 causes a story to
branch to branch
number 1, the user may perform another interaction 628 causing the story to
branch to
further possible outcomes. A story may have any number of sub-plot branches,
or overall
plot branches, depending on whether a story application is written to handle
many sub-plot
and overall plot branches.
[00113] In embodiments, a single user may perform interactions which cause a
story
application to perform sub-plot branches or overall plot branches. In further
embodiments, multiple users may be viewing a story. These multiple users may
be co-
located or located at different locations, using different systems 10, which
are networked
together so the various users may share the same instance of application 226
and the same
story experience. In such embodiments, the story application 226 may require
the actions
26
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
of several users acting in concert before the story line will branch to a new
sub-plot or a
new overall plot.
[00114] Returning now to Fig. 9, if the computing environment 12 has
identified a user
movement or gesture requiring a story line branch in step 564, and the story
application is
equipped to handle that new story line, the story application 226 branches to
that new
story line in step 570. The story application modifies the state data for any
objects,
characters or the application as a whole in step 572. In step 574, the story
application 226
may render graphics for a scene in accordance with the new story line and
state data, and
the story application may continue with the identified branch in step 578.
[00115] One aspect of the present system is to add game mechanics to a story
being
shown to a user. Accordingly, in addition to showing a story, story
application 226 may
further keep a user's score which may be incremented or decremented depending
on how
the user interacts with the story. In particular, certain gestures or actions
by a user may
have a predetermined story value and an associated number of points which are
to be
added to, or subtracted from, the user's overall score upon performance of the
associated
gesture. Accordingly, in step 582, the story application checks whether there
was a score
associated with the user interaction performed in step 560. If not, the flow
returns to step
432 in Fig. 5. If there is a score associated with the user's interaction, the
user's score is
adjusted accordingly in step 588, and then the flow may return to step 432 in
Fig. 5 as
described below.
[00116] The embodiment of Fig. 9 may be used in stories using static image
panels or
dynamic CG image animation. Fig. 9A shows a further embodiment for use with
recorded
video. Steps 560 through 572 may be as described above for Fig. 9. In
embodiments,
interaction with recorded video would occur at predefined points of
interaction with the
video. For recorded video stories, the story application may have a different
video clip for
each possible branch of the story. In step 590, the story application may
retrieve the
media clip appropriate to the determined branch of the story. In step 594, the
computing
environment 12 may render that clip. As an alternative or addition to pre-
recorded video
clips for different branches, CG animations may be constructed by the
computing
environment and inserted.
[00117] After a user has been shown the images from the story branch, the
story
application 226 may then go back and show the media clip for the story, had
the story not
branched to a new line in a step 596. For example, the story may relate to a
crime drama
where detectives are about to interrogate a suspect. A user may perform a
predefined
27
CA 02800533 2012-11-22
WO 2011/162974
PCT/US2011/039881
gesture indicating that they wish to interact with the story application to
interrogate the
suspect. The user may ask questions, and may perform the interrogation in
different ways
and with different attitudes. These actions may be limited in scope, for
example by a
script from which the user can select questions. Alternatively, it may be any
questions the
user wishes to ask.
[00118] The user may also ask the questions with different attitudes, some
more or less
likely to work with the suspect character being interrogated. The user may
attempt to
bully the suspect, or the user may attempt to elicit information by proceeding
with a
pleasant demeanor. The capture device 20 is capable of detecting these
different
mannerisms, and these different mannerisms may be identified by the computing
environment 12 if certain acts match defined and stored mannerism data. Once
the user
has completed the interrogation, a video clip of the detectives conducting the
interrogation
may be played. The user can see what they did better or worse than the
detectives, as far
as the amount of information he or she was able to get from the suspect in
comparison to
what the detective characters obtained in the replayed scene.
[00119] In step 600, the story line continues with the identified branch. It
may reconvene
with the original story line or it may result in a new outcome for the overall
plot. In step
604, a user's interaction may be scored. For example, if a user was able to
elicit more
information than the detective characters did in the above example, the user
may be
awarded some predefined number of points. Alternatively, if the user elicited
less
information, they may lose a predetermined number of points. The user's score
may be
adjusted accordingly and the flow may return to step 432 of Fig. 5 as
described below.
[00120] Returning to Fig. 5, it may happen that a user's gesture is not an
exploration
gesture in step 422, is not for the purpose of controlling a character in step
426, and does
not interact with a displayed scene so as to change the story line in step
428. Accordingly,
computing environment 12 checks for other such gestures in step 432. If no
other such
gesture is recognized in step 432, the story application loops back to step
406 to present
the next frame of the story and the above-described steps repeat. On the other
hand, if
some other gesture is recognized in step 432, the system checks in step 434
whether that
gesture is to end the story. If so, the story ends at step 436. Otherwise, in
step 438, the
system performs any action associated with a gesture recognized in step 432,
and then the
flow returns to step 406 to present the next frame of the story.
28
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[00121] As noted above, if a user takes no action when receiving a story, the
story may
proceed linearly per a default set of images and/or narrative or dialog. In a
further
embodiment, even where a user takes no action, elements in the linear story
may
dynamically change relative to instances of the story based on various preset
factors.
These factors may include the number of times the story has been viewed (for
example,
something new happens the 4th time through); the number of people in the
audience; and
the weather or time of day (for example, the weather in the story changes with
the seasons,
or is tied to the real world weather). The weather or time of day may be known
to the
system 10 or stored within a service to which the system 10 is networked.
Also, events in
other stories could have an impact ¨ being introduced to a character in story
B makes them
appear in story A. These features, along with the other features of the
present system
described above, make the stories more dynamic and encourage repeat viewing
and
experimentation.
[00122] Many of the interactions described above are triggered by predefined
gestures.
Fig. 13 shows a block diagram of a gesture recognition engine 190, and Fig. 14
shows a
block diagram of the operation of the gesture recognition engine 190 of Fig.
13. The
gesture recognition engine 190 receives pose information 650 in step 660. The
pose
information may include a variety of parameters relating to position and/or
motion of the
user's body parts and joints as detected in the image data.
[00123] The gesture recognition engine 190 analyzes the received pose
information 650
in step 664 to see if the pose information matches any predefined rule 658
stored within a
gestures library 654. A stored rule 658 describes when particular positions
and/or kinetic
motions indicated by the pose information 650 are to be interpreted as a
predefined
gesture. In embodiments, each gesture may have a different, unique rule or set
of rules
658. Each rule may have a number of parameters (joint position vectors,
maximum/minimum position, change in position, etc.) for one or more of the
body parts
shown in Fig. 4. A stored rule may define, for each parameter and for each
body part 302
through 330 shown in Fig. 4, a single value, a range of values, a maximum
value, a
minimum value or an indication that a parameter for that body part is not
relevant to the
determination of the gesture covered by the rule. Rules may be created by a
game author,
by a host of the gaming platform or by users themselves.
29
CA 02800533 2012-11-22
WO 2011/162974 PCT/US2011/039881
[00124] The gesture recognition engine 190 may output both an identified
gesture and a
confidence level which corresponds to the likelihood that the user's
position/movement
corresponds to that gesture. In particular, in addition to defining the
parameters required
for a gesture, a rule may further include a threshold confidence level
required before pose
information 650 is to be interpreted as a gesture. Some gestures may have more
impact as
system commands or gaming instructions, and as such, require a higher
confidence level
before a pose is interpreted as that gesture. The comparison of the pose
information
against the stored parameters for a rule results in a cumulative confidence
level as to
whether the pose information indicates a gesture.
[00125] Once a confidence level has been determined as to whether a given pose
or
motion satisfies a given gesture rule, the gesture recognition engine 190 then
determines in
step 668 whether the confidence level is above a predetermined threshold for
the rule
under consideration. The threshold confidence level may be stored in
association with the
rule under consideration. If the confidence level is below the threshold, no
gesture is
detected (step 670) and no action is taken. On the other hand, if the
confidence level is
above the threshold, the user's motion is determined to satisfy the gesture
rule under
consideration, and the gesture recognition engine 190 returns the identified
gesture in step
674. The gesture recognition engine 190 may operate by other methods in
further
embodiments.
[00126] The foregoing detailed description of the inventive system has been
presented for
purposes of illustration and description. It is not intended to be exhaustive
or to limit the
inventive system to the precise form disclosed. Many modifications and
variations are
possible in light of the above teaching. The described embodiments were chosen
in order
to best explain the principles of the inventive system and its practical
application to
thereby enable others skilled in the art to best utilize the inventive system
in various
embodiments and with various modifications as are suited to the particular use
contemplated. It is intended that the scope of the inventive system be defined
by the
claims appended hereto.
