Systems such as computer games and multimedia applications have evolved to the point where the systems are able to utilize user movement and verbal communication as inputs to the system. Such natural systems may be geared toward multiple users, where it is compelling to distinguish individuals from one another. Techniques exist to allow a game or application to identify users within the field of view through a variety of mechanisms, including a three-dimensional depth camera capable of sensing user traits such as size, facial features, clothing color, etc. Voice recognition techniques also exist to identify perceived user voices through a variety of mechanisms including a microphone array. These two techniques have not conventionally been used in tandem. It would be compelling to automatically match user voices with bodies without involving a deliberate setup on the part of the users. For example, it may happen that a person's identity is ambiguous using imaging techniques alone or audio techniques alone. This is especially true in lower cost consumer systems. In addition to helping to disambiguate users, such a correlation of audio and visual identity can be used to bolster the user experience within the game or application.
Described herein is a system and method for correlating a voice to user in a multi-user application. The system includes an image camera component capable of providing a depth image of one or more users in a field of view of the image camera component. The system further includes a microphone array capable of receiving audio within range of the microphone array. The microphone array is further capable of localizing a source of a voice to within a first tolerance. Embodiments further include a computing environment in communication with both the image capture component and microphone array and capable of distinguishing between different users in the field of view to a second tolerance. In embodiments, the first and second tolerances may at times prevent correlation of a voice to a user after an initial sampling of data from the image camera and data from the microphone array. However, the computing environment further performs additional samplings of data from the image camera and data from the microphone array. These additional samplings allow the correlation of the voice with the user or the additional samplings reducing a likelihood that the voice is correlated to the user.
Embodiments of the present technology will now be described with reference to
Where the image and audio systems are able to unambiguously determine that a given voice belongs to a given user body in the field of view, that voice-body correlation is stored. However, it may happen that the system is not able to establish a single unambiguous correlation after an image and audio sampling. Instead, the system identifies one or more candidate users to whom a sampled voice may belong. In this instance, the present system may employ a variety of factors to determine whether a voice is associated with a body above a predetermined threshold confidence level (“TCL”). If so, although not unambiguous, that voice-body association may be returned and stored for use in future samplings. The future samplings will either reinforce the association, or show that the association remains ambiguous, in which case the association may be removed.
Referring initially to
As shown in
Although not critical to the present technology, the users A-D may perform gestures which are recognized by a software engine running on computing environment 12, so that a user's avatar performs some action upon recognition of a gesture by that user. While four users are shown in the example of
Additional details relating to cameras which may form part of capture device 20 are set forth in copending patent application Ser. No. 12/474,655 filed on May 29, 2009, entitled “GESTURE TOOL,” and copending patent application Ser. No. 12/391,150 filed on Feb. 23, 2009, entitled “STANDARD GESTURES,” each of which applications is incorporated herein by reference in its entirety. However, in general, as shown in
As shown in
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 either embodiment, the image camera component 22 is able to determine the orientation of the people within the field of view relative to each other, and is able to calculate the angle of each person in the field of view relative to the capture device 20.
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. For example, the capture device 20 may capture depth information of a capture area that may include a human target. The depth image may then be analyzed to determine whether the depth image includes a human target and/or non-human targets. Portions of the depth image may be flood filled and compared to a pattern to determine whether the target may be a human target. If one or more of the targets in the depth image includes a human target, the human target may be scanned.
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. The skeletal model may then be provided to the computing environment 12 such that the computing environment may track the skeletal model and render an avatar associated with the skeletal model.
The capture device 20 may further include a microphone array 32 including two more microphones 30. The array of microphones perform at least two functions. The microphones 30 receive audio signals that may also be provided by one or more of users A-D to control their avatars A′-D′, affect other game or system metrics, or control other applications that may be executed by the computing environment 12. A second function of the microphone array 32 is to facilitate identification of users as explained below.
In the embodiment shown, there are two microphones 30, but it is understood that the microphone array may have more than two microphones in further embodiments. The microphones may be aligned in a common vertical plane (i.e., at the same height) for embodiments where it may not be critical to resolve relative position along a vertical axis. However, it is further understood that the present technology may employ two to four or more cameras lying along different vertical lines and horizontal lines. In such embodiments, the microphone array would be able to employ acoustic localization techniques along both vertical and horizontal planes to pinpoint the location of one or more voices in three-dimensional space.
The microphones 30 in the array may be positioned near to each other as shown in the figures, such as for example one foot apart. It is understood that in further embodiments, the microphones may be spaced closer together, or farther apart, for example at corners of a wall to which the capture device 20 is adjacent.
The microphones 30 in the array may be synchronized with each other, and each may include a transducer or sensor that may receive and convert sound into an electrical signal. Techniques are known for differentiating sounds picked up by the microphones to determine whether one or more of the sounds is a human voice. Microphones 30 may include various known filters, such as a high pass filter, to attenuate low frequency noise which may be detected by the microphones 30.
Within given tolerances, the array 32 is also able to determine the orientation of the perceived voices relative to each other, and is able to calculate the angle of each voice source relative to the microphone array using acoustic localization techniques. Various acoustic localization techniques are known. One embodiment may employ a time difference of arrivals (TDOA) technique having a first step of determining a set of TDOAs among different microphone pairs. That is, for each of a set of microphone pairs, the relative time difference between the arrival of the acoustic source signal at each of the microphones in the pair is determined. For example, the TDOA for two microphones i and j measuring the location, s, of an acoustic source may be determined by:
TDOAi,j=(|s−mi|−|s−mj|)/c
where mi is the position of the ith microphone, mi is the position of the jth microphone and c is the speed of light.
TDOA techniques further include a second step of using the determined TDOA data and the microphone array geometry to estimate the location of the acoustic source. This second step may be performed by a variety of known methods including for example the maximum likelihood method, the triangulation method, the spherical intersection method, and the spherical interpolation method.
The TDOA method is one of a number of known methods which may be employed to locate the source of a perceived voice. Others include steered beamformer-based techniques and high-resolution spectral estimation-based techniques. Further details relating to microphone systems for acoustic localization may be found for example in U.S. Pat. No. 6,826,284, entitled “Method and Apparatus for Passive Acoustic Source Localization for Video Camera Steering Applications,” and in a published paper by H. Wang and P. Chu, “Voice Source Localization for Automatic Camera Pointing System In Videoconferencing,” in Proc. IEEE Int. Conf. Acoustics, Speech, and Signal Processing (ICASSP), Munich, Germany, April 1997, pp. 187-190. The above patent and paper are hereby incorporated by reference herein in their entirety. Where a technique allows acoustic source localization to a given tolerance using a single microphone, microphone array 32 may include one or more microphones.
In an example embodiment, the capture device 20 may further include a processor 33 that may be in operative communication with the image camera component 22 and microphone array 32. The processor 33 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. The processor 33 may also perform the above described operations relating to acoustic localization.
The capture device 20 may further include a memory component 34 that may store the instructions that may be executed by the processor 33, images or frames of images captured by the 3-D camera or RGB camera, audio data from microphones 30 or any other suitable information 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
As shown in
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 A/V (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.
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.
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 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).
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 A/V port 140 for reproduction by an external audio player or device having audio capabilities.
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.
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 (PCI) bus, PCI-Express bus, etc.
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.
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.
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., 16 MB), 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.
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.
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.
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.
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.
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 applications such that each will have a focus of the device. The application manager preferably controls the switching of the input stream, without knowledge of the gaming application's knowledge and a driver maintains state information regarding focus switches. The cameras 26, 28 and capture device 20 may define additional input devices for the console 100.
In
The computer 241 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
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
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,
Methods for identifying users based on a correlation between perceived image data relating to a user and perceived voice data will now be described with reference to the flowcharts of
In step 302, the present system enrolls voices detected within range of the microphone array 32. There will be instances where the present system is able to unambiguously associate a voice with a particular body. For example, the microphone array 32 may be able to localize the source of a voice to a tolerance including a particular angle or range of angles with respect to the image capture device 20, and the image camera component 22 determines that there is only one user at that angle or range of angles. In such an instance, the present system is able to unambiguously correlate the detected person with the detected voice. Further details relating to steps 302 and 306 are set forth below with respect to the flowchart of
On the other hand, it may happen that the system is not able to establish a single unambiguous correlation after an image and audio sampling, but rather identifies one or more candidate users to whom the voice may possibly belong. For example, there may be two users having a physical appearance that is too close to distinguish between using image recognition techniques of the present system. Alternatively or additionally, the microphone array may only be able to determine that a voice comes from an area in the field of view having more than one person. This may be true for example where consumer-grade hardware is used to capture the image and audio data.
In this instance, the present system may employ a variety of factors to build a confidence level score indicative of a confidence level with which the voice is associated with a given user. Even though not unambiguous, the factors may result in a score above a threshold confidence level. If so, that voice-body association above the threshold confidence level is stored for use in future samplings. The future samplings may reinforce the association, for example where the future samplings eliminate other users to whom the voice may belong to. Alternatively, the future samples may show that the association remains ambiguous, in which case the association may be removed.
Even after a voice is correlated to a body, embodiments of the present technology may repeatedly re-evaluate and reaffirm confidence levels of the voice-body correlations (step 312). The processes of evaluating, disambiguating and reaffirming confidence levels is described hereinafter with respect to the flowcharts of
The flowchart of
Accordingly, in step 320, the present system scans a video frame for human users within the field of view, such as for example one or more users A-D. As indicated above, current technologies allow for human bodies to be discerned from other objects which may be within the field of view. In step 322, the present system determines whether a body has been found within the field of view. If not, the system looks as to whether there are more objects to scan in the field of view in step 326. Assuming there are, the system returns to step 320 to scan for more bodies. On the other hand, if a body is found in step 322, the present system checks in step 330 whether that body was present in a prior frame. The system may look at a variety of factors in making this determination, including a match of skeletal reference points or other physical characteristics between a body in a current frame and previous frame, and whether the position of the body in the current frame could have moved there from the position detected in the prior frame given the frame rate. Once it is determined that a found body was present in a prior frame in step 330, the system returns to step 320 to scan for more bodies.
On the other hand, if step 330 determines that a found body was not found in a prior frame, the system checks in step 334 whether the found body matches a body that has already been enrolled. In particular, the system compares the information describing a body in the current frame with information from memory regarding bodies that have previously been identified and enrolled. If the body from the current frame was not previously enrolled, the system stores the body signature (i.e., skeletal features and/or other physical characteristics) in memory in step 338. After storing the body signature, the system marks the matching body as being identified in step 344, and then returns to step 320 to scan for more bodies.
On the other hand, if it is determined in step 334 that the found body does match a known body, the system checks in step 340 whether the found body matches only one known body. In particular, the found body may have skeletal features which are sufficiently close to the skeletal features of previously identified and stored bodies. If the system determines in step 340 that the found body matches only one known body, the found body is marked as matching the known body in step 344 and the system returns to step 320 to scan for more bodies. Alternatively, if it is determined in step 340 that the found body matches more than one known body, the found body is marked as associated with an ambiguity in step 346, and the system returns to step 320 to scan the frame for more bodies.
After the system has determined that there are no further objects to scan in the frame in step 326, the system updates the body positions for the current frame in step 350 and enrolls and stores all body matches in step 354. Step 354 also stores ambiguities in body identity which were found.
As indicated above, acoustic technologies are able to filter out and discern human voices from the variety of sounds and background noises which may be picked up by the microphone array. Concurrently with searching for and enrolling bodies as described above with respect to the flowchart of
The process of enrolling voices begins with a step 360 of determining whether a discerned voice can be correlated with a visible body. Step 360 is described in greater detail below with reference to the flowchart of
On the other hand, if the voice does come within the field of view, the system determines in step 366 whether there is a body at the estimated source of the voice. If not, the system determines that the voice is not correlated with a visible body in step 364. On the other hand, if there is a body detected at the estimated source of the voice, the system next checks in step 368 whether there is more than one body within the range of possible sources of the voice. If there are, the system cannot correlate the voice with a visible body in step 364. On the other hand, if the system passes all the checks in steps 363, 366 and 368, the system is able to unambiguously correlate a voice with one visible body in step 370.
Returning to the flowchart of
In embodiments, where an utterance is not eligible for enrollment in step 372, the present system may prompt one or more users in the field of view to speak and perform some physical act in step 373. The physical act may for example be to stand in the field of view but apart from other users. In this way, in addition to receiving voice data, the system is able to positively identify and enroll the speaker as the one performing the requested act. These physical acts may be part of the game or application metric or outside of the game or application metric. Step 373 may be omitted in further embodiments. Where omitted, the user will experience less intrusion due to enrollment, but completion of enrollment may be subject to the chance actions of users.
On the other hand, if it is determined in step 360 that the voice is correlated with a visible body, the system next checks in step 374 whether the identified visible body is continuous from the previous enrollment utterance. In other words, if the system correlates the voice with a visible body in step 360, the system checks in step 374 whether that body from the previous frame could have moved continuously to the position of the body identified in step 360 in the current frame. If it is determined in step 374 that the body with which the voice was associated in the previous frame could not be the body with which the voice is associated in the current frame, the system treats the prior correlation as being incorrect. In such an event, the system begins a new enrollment process for the voice in step 376 with the body identified in step 360. In step 378 the utterance is then added to the enrollment.
In step 380, the system checks whether enrollment is complete. That is, the system checks whether sufficient phonetic data has been collected to allow the system to unambiguously identify a given voice as distinguished from other voices. If not, the utterance is not sufficient for enrollment, but in embodiments, it may be stored in step 381 for use together with future utterances to establish enrollment once the necessary diversity of phonetic data has been collected. If on the other hand, the system determines that enrollment is complete in step 380, the system saves the enrolled voice in step 382 and associates and stores the enrolled voice with a known body in step 384. The system then returns the known voice correlated to the known body.
In embodiments, where enrollment is not complete in step 380, the present system may prompt one or more users in the field of view to speak in step 383. This action by the system may be masked as part of the game or application metric, or it may be outside of the game or application metric. Where step 383 is performed, it may prompt a particular enrolled user to speak certain phonetically rich words and/or sounds so that, once spoken, the system is able to enroll the user's voice with the user's known body for later utterances. Step 383 may be omitted, in which case a failure to enroll in step 380 may result in the return of an unknown voice as described above.
The operation of the present technology as described above with respect to
In general, the microphone array 32 listens for uttered voices, and upon detecting a voice utterance, it performs the steps 386-432 described below with respect to
In step 386, the system checks whether an utterance is a voice that is enrolled. If not, the system goes to step 360 as described above with respect to
In step 386, if it is determined that the voice is enrolled, the system checks in step 388 whether the voice has a prior match with a known body. If not, the system determines whether there is a spatial match between the voice and a body within the field of view as described hereinafter with respect to step 416 in
If it is determined in step 390 that the body previously matched to the voice is not visible and step 394 confirms no match of the voice to a body that is then visible, the prior association in step 398 is maintained and the system returns a known voice with a known body. On the other hand, if step 390 determines that the body previously matched to the voice is visible, the system next checks in step 400 whether the spatial match between the voice and the known body is a good match, i.e., the spatial match is unambiguous. Step 400 may for example be performed as described above in
The present system keeps track of whether a given voice-body association remains ambiguous in a number of different samplings. If, after examining a voice-body association in a number of different samplings, the system cannot unambiguously determine that the voice is in fact associated with that body by the process of elimination, the system may treat the association as being too ambiguous to maintain, and it removes that association. Accordingly, in step 404, the present system tallies how many times a given voice-body association was found to be ambiguous. In step 406, the system determines whether the tally in step 404 exceeds some ambiguity threshold. If so, the previously identified association is removed in step 410, and the system returns a known voice but not associated with a known body. If the tally in step 406 does not exceed the ambiguity threshold, the system maintains the association in step 408 and returns a known voice-body association. In embodiments, the ambiguity threshold may for example be between 3 and 6. Thus, if the threshold is set at 5 for example, if the system cannot rule out an ambiguity of an association between a given voice and a body after 5 samplings, the system would remove that association. The ambiguity threshold may be lower than 3 and higher than 6 in further embodiments.
Described above is what the system does if a spatial match in step 400 is ambiguous. However, if it is determined in step 400 that the spatial match is unambiguous, the system next determines in step 414 whether the body matched to the voice was previously considered ambiguous. If so, the system updates the association to remove the ambiguity as explained below with reference to step 430 in
As described above, step 390 and those following are performed if it is determined in step 388 that a voice has a prior association with a known body. However, if it is determined in step 388 that the enrolled voice does not have a prior match with a known body, the present system performs step 416 in
Alternatively, although not unambiguous, the step 416 may identify one or more users which could possibly be associated with the voice. In order to make this determination, the present system may employ a variety of factors which can be applied to arrive at a scored confidence level. In general, if a voice can be associated to a body above a threshold confidence level upon consideration of the factors, that voice-body association is stored and returned. In embodiments, the factors which may contribute to a score may include one or more of the following.
One factor may be how close the estimated position of the voice source is to the known body. Where the body is at the exact location estimated by the acoustic localization technique, this factor would yield a higher score than an instance where the body was spaced from the estimated position of the voice. Another factor forming part of the score may be how many bodies are in the field of view. The more bodies there are, the less confidence there will be in the correlation of the voice to any one of those bodies. Conversely, if the only person in the field of view is the person with whom the voice was previously associated, this would result in a score tending to indicate a good spatial match between the correlated voice and body.
Another factor contributing to the score is the number of voices which are being heard. This factor may detract from or add to the score. For example, if there are many voices such that there is too much noise to accurately determine the source of the voice being considered, this would tend to lower the score of the association of that voice to the identified body. On the other hand, if the voices heard in addition to the voice under consideration have previously been associated with other users and those users are within the field of view, this factor may add to the score measuring the association between the voice under consideration and the previously identified body.
In addition to the number of people within the field of view, the closeness of the people to the estimated source of the voice is another factor affecting the score. If two or more people are near to the estimated source, this will tend to lower the score, whereas a situation where there are multiple people in the field of view, but only the previously matched person is near the estimated source, this will tend to bolster the score.
Another factor contributing to the score is whether the source of the voice is estimated to be centered within the field of view, as opposed to near the edges. When a voice is estimated to be near the edge of the field of view, the voice could be from the previously matched person within the field of view, or from a person outside of the field of view. Thus, a spatial match between a person and a voice estimated to be at the center of the field of view will result in a higher score than one at the edge of the field of view. Those of skill in the art will appreciate additional factors which may be used to arrive at a score indicative of whether there is a correlation between a voice and a body.
Different embodiments may use one or more of the above-described factors in reaching a scored confidence level. Other factors may be used in addition to or instead of one or more of the above-described factors. In embodiments, the factors that are used may be weighted and quantized so that, upon consideration of the factors used with respect to a particular voice-body pair, a numerical score may be obtained. A threshold confidence level may be arbitrarily selected above which the score is said to be significant and enough to store an association between the voice with a body.
After an unambiguous identification or a scored confidence level is reached in step 416, the system updates evidence (scores) for any associations made in step 420. In step 424, the system checks whether a match was found that was either unambiguous or otherwise attained a score which exceeds the threshold confidence level. If not, the system returns that there are no known bodies were found to match the known voice. On the other hand, if it is determined in step 424 that one or more bodies were found to match the voice above the threshold confidence level, those associations are recorded in step 428, and the system returns that the known voice was associated with at least one known body. As indicated, the steps of
As described above with respect to
Even after the system has determined that a voice is unambiguously associated with a user, the present system allows for a possible error in that association. In particular, it may be possible that that same voice is unambiguously associated with another user in memory, or that user is unambiguously associated with another voice in memory. Thus, step 432 determines whether the ambiguity is resolved. If so, the system returns a known voice with a known body. If it is not, the system returns a known voice, but without an associated known body. The steps of
Using the above-described system, voices may be correlated with bodies in a gaming, multimedia or other multi-user application. While systems may exist which are capable of unambiguously correlating a voice to a body in a single sampling, these systems require costly, precision systems which are not feasible in most gaming, multimedia or other consumer-based application. However, unlike conventional systems, the present system is able to make reliable voice-body correlations where the equipment used is unable to determine such correlations in a single sampling. Moreover, systems are known which start with enrolled users. That is, the set of users have known, enrolled body signatures and/or known, enrolled voices. Conventional systems do not make voice-body correlations starting with users having unknown body signatures and unknown voices. The present technology allows such correlations to be made.
While the present disclosure has been described in connection with the preferred aspects, as illustrated in the various figures, it is understood that other similar aspects may be used or modifications and additions may be made to the described aspects for performing the same function of the present disclosure without deviating therefrom. Therefore, the present disclosure should not be limited to any single aspect, but rather construed in breadth and scope in accordance with the appended claims. For example, the various procedures described herein may be implemented with hardware or software, or a combination of both. Thus, the methods and apparatus of the disclosed embodiments, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium. When the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus configured for practicing the disclosed embodiments. In addition to the specific implementations explicitly set forth herein, other aspects and implementations will be apparent to those skilled in the art from consideration of the specification disclosed herein. It is intended that the specification and illustrated implementations be considered as examples only.
Number | Name | Date | Kind |
---|---|---|---|
4627620 | Yang | Dec 1986 | A |
4630910 | Ross et al. | Dec 1986 | A |
4645458 | Williams | Feb 1987 | A |
4695953 | Blair et al. | Sep 1987 | A |
4702475 | Elstein et al. | Oct 1987 | A |
4711543 | Blair et al. | Dec 1987 | A |
4751642 | Silva et al. | Jun 1988 | A |
4796997 | Svetkoff et al. | Jan 1989 | A |
4809065 | Harris et al. | Feb 1989 | A |
4817950 | Goo | Apr 1989 | A |
4843568 | Krueger et al. | Jun 1989 | A |
4893183 | Nayar | Jan 1990 | A |
4901362 | Terzian | Feb 1990 | A |
4925189 | Braeunig | May 1990 | A |
5101444 | Wilson et al. | Mar 1992 | A |
5148154 | MacKay et al. | Sep 1992 | A |
5184295 | Mann | Feb 1993 | A |
5229754 | Aoki et al. | Jul 1993 | A |
5229756 | Kosugi et al. | Jul 1993 | A |
5239463 | Blair et al. | Aug 1993 | A |
5239464 | Blair et al. | Aug 1993 | A |
5288078 | Capper et al. | Feb 1994 | A |
5295491 | Gevins | Mar 1994 | A |
5320538 | Baum | Jun 1994 | A |
5347306 | Nitta | Sep 1994 | A |
5385519 | Hsu et al. | Jan 1995 | A |
5405152 | Katanics et al. | Apr 1995 | A |
5417210 | Funda et al. | May 1995 | A |
5423554 | Davis | Jun 1995 | A |
5454043 | Freeman | Sep 1995 | A |
5469740 | French et al. | Nov 1995 | A |
5495576 | Ritchey | Feb 1996 | A |
5516105 | Eisenbrey et al. | May 1996 | A |
5524637 | Erickson et al. | Jun 1996 | A |
5534917 | MacDougall | Jul 1996 | A |
5563988 | Maes et al. | Oct 1996 | A |
5577981 | Jarvik | Nov 1996 | A |
5580249 | Jacobsen et al. | Dec 1996 | A |
5594469 | Freeman et al. | Jan 1997 | A |
5597309 | Riess | Jan 1997 | A |
5616078 | Oh | Apr 1997 | A |
5617312 | Iura et al. | Apr 1997 | A |
5638300 | Johnson | Jun 1997 | A |
5641288 | Zaenglein | Jun 1997 | A |
5682196 | Freeman | Oct 1997 | A |
5682229 | Wangler | Oct 1997 | A |
5690582 | Ulrich et al. | Nov 1997 | A |
5703367 | Hashimoto et al. | Dec 1997 | A |
5704837 | Iwasaki et al. | Jan 1998 | A |
5715834 | Bergamasco et al. | Feb 1998 | A |
5761329 | Chen et al. | Jun 1998 | A |
5764779 | Haranishi | Jun 1998 | A |
5875108 | Hoffberg et al. | Feb 1999 | A |
5877803 | Wee et al. | Mar 1999 | A |
5913727 | Ahdoot | Jun 1999 | A |
5933125 | Fernie | Aug 1999 | A |
5980256 | Carmein | Nov 1999 | A |
5989157 | Walton | Nov 1999 | A |
5995649 | Marugame | Nov 1999 | A |
6005548 | Latypov et al. | Dec 1999 | A |
6009210 | Kang | Dec 1999 | A |
6054991 | Crane et al. | Apr 2000 | A |
6066075 | Poulton | May 2000 | A |
6072494 | Nguyen | Jun 2000 | A |
6073489 | French et al. | Jun 2000 | A |
6077201 | Cheng et al. | Jun 2000 | A |
6098458 | French et al. | Aug 2000 | A |
6100896 | Strohecker et al. | Aug 2000 | A |
6101289 | Kellner | Aug 2000 | A |
6128003 | Smith et al. | Oct 2000 | A |
6130677 | Kunz | Oct 2000 | A |
6141463 | Covell et al. | Oct 2000 | A |
6147678 | Kumar et al. | Nov 2000 | A |
6152856 | Studor et al. | Nov 2000 | A |
6159100 | Smith | Dec 2000 | A |
6173066 | Peurach et al. | Jan 2001 | B1 |
6181343 | Lyons | Jan 2001 | B1 |
6188777 | Darrell et al. | Feb 2001 | B1 |
6215890 | Matsuo et al. | Apr 2001 | B1 |
6215898 | Woodfill et al. | Apr 2001 | B1 |
6226396 | Marugame | May 2001 | B1 |
6229913 | Nayar et al. | May 2001 | B1 |
6256033 | Nguyen | Jul 2001 | B1 |
6256400 | Takata et al. | Jul 2001 | B1 |
6283860 | Lyons et al. | Sep 2001 | B1 |
6289112 | Jain et al. | Sep 2001 | B1 |
6299308 | Voronka et al. | Oct 2001 | B1 |
6308565 | French et al. | Oct 2001 | B1 |
6316934 | Amorai-Moriya et al. | Nov 2001 | B1 |
6363160 | Bradski et al. | Mar 2002 | B1 |
6384819 | Hunter | May 2002 | B1 |
6411744 | Edwards | Jun 2002 | B1 |
6430997 | French et al. | Aug 2002 | B1 |
6476834 | Doval et al. | Nov 2002 | B1 |
6496598 | Harman | Dec 2002 | B1 |
6503195 | Keller et al. | Jan 2003 | B1 |
6539931 | Trajkovic et al. | Apr 2003 | B2 |
6570555 | Prevost et al. | May 2003 | B1 |
6633294 | Rosenthal et al. | Oct 2003 | B1 |
6640202 | Dietz et al. | Oct 2003 | B1 |
6661918 | Gordon et al. | Dec 2003 | B1 |
6674877 | Jojic et al. | Jan 2004 | B1 |
6681031 | Cohen et al. | Jan 2004 | B2 |
6714665 | Hanna et al. | Mar 2004 | B1 |
6731799 | Sun et al. | May 2004 | B1 |
6738066 | Nguyen | May 2004 | B1 |
6765726 | French et al. | Jul 2004 | B2 |
6788809 | Grzeszczuk et al. | Sep 2004 | B1 |
6801637 | Voronka et al. | Oct 2004 | B2 |
6873723 | Aucsmith et al. | Mar 2005 | B1 |
6876496 | French et al. | Apr 2005 | B2 |
6937742 | Roberts et al. | Aug 2005 | B2 |
6941274 | Ramachandran et al. | Sep 2005 | B1 |
6950534 | Cohen et al. | Sep 2005 | B2 |
7003134 | Covell et al. | Feb 2006 | B1 |
7036094 | Cohen et al. | Apr 2006 | B1 |
7038855 | French et al. | May 2006 | B2 |
7039676 | Day et al. | May 2006 | B1 |
7042440 | Pryor et al. | May 2006 | B2 |
7050606 | Paul et al. | May 2006 | B2 |
7058204 | Hildreth et al. | Jun 2006 | B2 |
7060957 | Lange et al. | Jun 2006 | B2 |
7113918 | Ahmad et al. | Sep 2006 | B1 |
7121946 | Paul et al. | Oct 2006 | B2 |
7130446 | Rui et al. | Oct 2006 | B2 |
7170492 | Bell | Jan 2007 | B2 |
7184048 | Hunter | Feb 2007 | B2 |
7202898 | Braun et al. | Apr 2007 | B1 |
7222078 | Abelow | May 2007 | B2 |
7227526 | Hildreth et al. | Jun 2007 | B2 |
7259747 | Bell | Aug 2007 | B2 |
7308112 | Fujimura et al. | Dec 2007 | B2 |
7317836 | Fujimura et al. | Jan 2008 | B2 |
7348963 | Bell | Mar 2008 | B2 |
7359121 | French et al. | Apr 2008 | B2 |
7367887 | Watabe et al. | May 2008 | B2 |
7379563 | Shamaie | May 2008 | B2 |
7379566 | Hildreth | May 2008 | B2 |
7389591 | Jaiswal et al. | Jun 2008 | B2 |
7412077 | Li et al. | Aug 2008 | B2 |
7421093 | Hildreth et al. | Sep 2008 | B2 |
7430312 | Gu | Sep 2008 | B2 |
7436496 | Kawahito | Oct 2008 | B2 |
7450736 | Yang et al. | Nov 2008 | B2 |
7452275 | Kuraishi | Nov 2008 | B2 |
7460690 | Cohen et al. | Dec 2008 | B2 |
7489812 | Fox et al. | Feb 2009 | B2 |
7492367 | Mahajan et al. | Feb 2009 | B2 |
7536032 | Bell | May 2009 | B2 |
7555142 | Hildreth et al. | Jun 2009 | B2 |
7560701 | Oggier et al. | Jul 2009 | B2 |
7570805 | Gu | Aug 2009 | B2 |
7574020 | Shamaie | Aug 2009 | B2 |
7576727 | Bell | Aug 2009 | B2 |
7590262 | Fujimura et al. | Sep 2009 | B2 |
7593552 | Higaki et al. | Sep 2009 | B2 |
7598942 | Underkoffler et al. | Oct 2009 | B2 |
7607509 | Schmiz et al. | Oct 2009 | B2 |
7620202 | Fujimura et al. | Nov 2009 | B2 |
7627139 | Marks et al. | Dec 2009 | B2 |
7668340 | Cohen et al. | Feb 2010 | B2 |
7680298 | Roberts et al. | Mar 2010 | B2 |
7683954 | Ichikawa et al. | Mar 2010 | B2 |
7684592 | Paul et al. | Mar 2010 | B2 |
7701439 | Hillis et al. | Apr 2010 | B2 |
7702130 | Im et al. | Apr 2010 | B2 |
7704135 | Harrison, Jr. | Apr 2010 | B2 |
7710391 | Bell et al. | May 2010 | B2 |
7729530 | Antonov et al. | Jun 2010 | B2 |
7746345 | Hunter | Jun 2010 | B2 |
7760182 | Ahmad et al. | Jul 2010 | B2 |
7801726 | Ariu | Sep 2010 | B2 |
7809167 | Bell | Oct 2010 | B2 |
7834846 | Bell | Nov 2010 | B1 |
7852262 | Namineni et al. | Dec 2010 | B2 |
RE42256 | Edwards | Mar 2011 | E |
7898522 | Hildreth et al. | Mar 2011 | B2 |
8035612 | Bell et al. | Oct 2011 | B2 |
8035614 | Bell et al. | Oct 2011 | B2 |
8035624 | Bell et al. | Oct 2011 | B2 |
8072470 | Marks | Dec 2011 | B2 |
8155394 | Allegra et al. | Apr 2012 | B2 |
20030200217 | Ackerman | Oct 2003 | A1 |
20040261097 | Hanks | Dec 2004 | A1 |
20060075422 | Choi et al. | Apr 2006 | A1 |
20080026838 | Dunstan et al. | Jan 2008 | A1 |
20080152191 | Fujimura et al. | Jun 2008 | A1 |
20080252596 | Bell et al. | Oct 2008 | A1 |
20090077504 | Bell et al. | Mar 2009 | A1 |
20090141933 | Wagg | Jun 2009 | A1 |
20090215533 | Zalewski et al. | Aug 2009 | A1 |
20090221368 | Yen et al. | Sep 2009 | A1 |
20100093435 | Glaser et al. | Apr 2010 | A1 |
Number | Date | Country |
---|---|---|
101254344 | Jun 2010 | CN |
0583061 | Feb 1994 | EP |
08044490 | Feb 1996 | JP |
9310708 | Jun 1993 | WO |
9717598 | May 1997 | WO |
9944698 | Sep 1999 | WO |
WO2009059065 | May 2009 | WO |
Number | Date | Country | |
---|---|---|---|
20110182481 A1 | Jul 2011 | US |