Dynamic player selection for audio signal processing

Description

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, to methods, systems, products, features, services, and other elements directed to media playback or some aspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loud setting were limited until in 2003, when SONOS, Inc. filed for one of its first patent applications, entitled “Method for Synchronizing Audio Playback between Multiple Networked Devices,” and began offering a media playback system for sale in 2005. The Sonos Wireless HiFi System enables people to experience music from many sources via one or more networked playback devices. Through a software control application installed on a smartphone, tablet, or computer, one can play audio in any room that has a networked playback device. Additionally, using the control device, for example, different songs can be streamed to each room with a playback device, rooms can be grouped together for synchronous playback, or the same song can be heard in all rooms synchronously.

Given the ever growing interest in digital media, there continues to be a need to develop consumer-accessible technologies to further enhance the listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:

FIG. 1 shows an example playback system configuration in which certain embodiments may be practiced;

FIG. 2 shows a functional block diagram of an example playback device;

FIG. 3 shows a functional block diagram of an example control device;

FIG. 4 shows an example control device interface;

FIG. 5 shows an example network configuration in which certain embodiments may be practiced;

FIG. 6 shows a functional block diagram of an example network microphone device;

FIG. 7 shows an example environment in which certain embodiments may be practiced;

FIG. 8 shows an example flow diagram associated with distributing processing across devices in a media playback system;

FIG. 9 shows a more detailed example flow diagram associated with distributing processing across devices in the media playback system; and

FIG. 10 shows example tables for managing signal measures of audio signals and spare computational power of devices in the media playback system.

The drawings are for the purpose of illustrating example embodiments, but it is understood that the embodiments are not limited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION
I. Overview

A media playback system may include one or more playback devices, network microphone devices, controller devices, and/or computing devices. The playback device, network microphone device, controller device, and computing device may collectively coordinate play back of audio content such as music tracks.

The playback device, the controller device, and the network microphone device may be in an environment such as a living room in a home. A microphone array of one or more of these devices may receive an audio signal. The audio signal may include a sonic input and noise. The sonic input may be a voice input such as a request to perform an action associated with the media playback system, e.g., “play audio” or “stop playing audio”. The sonic input may take the form of any other voice input as well. The noise may be any type of audio other than the sonic input. For example, the noise could include white noise or impulse noise. Alternatively, the “noise” could be audio content played by a playback device in the media playback system such as music.

It may be desirable to recover the sonic input from the audio signal. Embodiments described herein are directed to distributing, across devices in the media playback system, processing associated with improving a signal measure (e.g., signal to noise ratio) of the audio signal received by a device in the media playback system prior to the recovery of the sonic input. The processing is distributed to reduce degradation in performance of a particular device in the media playback system while the signal to noise ratio is improved. Improving the signal to noise ratio results in attenuating noise in the audio signal. The improved audio signal may then be passed to the computing device such as a server which is arranged to recover the sonic input. If the sonic input is a voice input, the server may interpret the voice input to determine the action associated with the voice input such as “play music on a playback device” or to “turn off the playback device”. The server may then cause the media playback system to perform the action.

As one example, an echo cancellation method may be used to improve the signal to noise ratio of the audio signal received by a device in the media playback system. The echo cancellation method seeks to remove echoes in the received audio signal. As another example, a beamforming method may be used to improve the signal to noise ratio of the audio signal received by a device in the media playback system. The beamforming method may determine characteristics of an audio signal received in certain direction such as whether the sonic input of the audio signal originates from the certain direction. In another example, one or more playback devices in the media playback system may be playing audio content in the background as the sonic input is received. The media playback system may have knowledge of this audio content, e.g., the spectral content of the audio content. The knowledge of the audio playing in the background may be used to improve the signal to noise ratio of the audio signal.

The methods described above are examples of various methods of improving the signal to noise ratio which can be applied separately or together to the audio signal to improve the signal to noise ratio. In this regard, a device may apply one or more of the algorithms described above, i.e., a first set of audio processing algorithms, to improve the signal to noise ratio of an audio signal that is received by the device. In embodiments, one or more of the received audio signal and the improved audio signal may also be stored on the playback device, controller device, or computing device as audio files.

In addition to improving the signal to noise ratio of the audio signal, a signal measure, such as the signal to noise ratio, for the audio signal as improved by one of the example algorithms described above may be calculated. The signal to noise ratio may be a ratio of the improved audio signal to the received audio signal. For example, the received audio signal and the improved audio signal may be represented as impulse responses. The impulse response of the improved audio signal may be divided by the received audio signal to calculate the signal to noise ratio.

A signal to noise ratio may be associated with each microphone array. For example, the echo cancellation algorithm provides an improved audio signal based on the audio signal received by the microphone array. The signal to noise ratio is based on this improved audio signal. Further, this signal to noise ratio may be also be associated with the device of the microphone array.

Alternatively, a plurality of signal to noise ratios may be associated with the microphone array. Each direction of a plurality of directions processed by a beamforming algorithm may have an associated signal to noise ratio. For example, the audio signal may be processed at directions of 20 degree angular intervals around the microphone array. Each 20 degree angular interval (18 intervals in total over 360 degrees) may have an associated impulse response of the received audio signal, impulse response of the improved audio signal, and signal to noise ratio.

The signal to noise ratios may be stored in a table. The table may also store an indication of the device/microphone array associated with a signal to noise ratio. In the case of beamforming, the table may also store an indication of a direction associated with the signal to noise ratio. The table may also be sorted such that the first entry in the table may identify the highest signal to noise ratio for the audio signal and the last entry may identify the lowest signal to noise ratio for the audio signal.

The respective processors of devices in the media playback system may have spare computational power. The spare computational power may be that computational power beyond what may be necessary to perform certain functions of the device. For example, the playback device may use computational power to play back audio but all the computational power may not be needed to play back the audio. The remaining computational power may be considered spare and could be used for further processing of the audio signal such as improving the signal to noise ratio of the audio signal received by a device.

Each device may indicate its spare computational power to a given device, such as a playback device, controller device, or server in the media playback system. For example, the spare computational power may be indicated by a state variable of the media playback system. This state variable may be periodically updated and made available to the devices in the media playback system. In some examples, the state variable may take the form of a flag which indicates that that playback device has a spare computational power. Further, various types of flags may be set depending on an amount of spare computational power available. Based on the state variable, the given device in the media playback system may obtain the spare computational power for each device and generate a table that identifies for each device its spare processing power. The spare computational power of each device in the media playback device may be organized in a table. Further, the table may be ordered based on availability of processing power. For example, the first entry in the table may be the device with a highest spare processing power and the last entry may identify the device with a lowest spare processing power. Other arrangements are also possible.

Then, processing tasks are assigned to the devices based on its spare computational power as defined by the table and computational power required by a processing task. The processing tasks may be defined by a second set of audio processing algorithms which includes the echo cancellation method, beamforming method, and/or subtraction of known signal method, among other. Each of these methods may have a higher resolution as compared to the first set of audio processing algorithms. The higher resolution processing may result in a further improvement of the signal to noise ratio of the audio signal as compared the first set of audio processing algorithms applied by the device when the audio signal was received.

The given device may assign impulse responses of one or more of the audio signals received by the device based on the spare computational power of a device and signal to noise ratios of the impulse responses. The impulse responses processed by each device based on the second set of audio processing algorithms result in an improved audio signal with a higher signal to noise ratio than what was previously determined with the first set of audio processing algorithms. Further, by using available spare computational power, performance of the media playback device is not degraded as a result of the additional processing.

The improved audio signal may also be weighted. The weighing may be based on a confidence level. The improved audio signals may then be combined. The combined signal may result in cancellation of any noise in the improved audio signal processed by the second set of audio processing algorithms. This combined audio signal may be then passed to a computing device such as a server for further processing.

Moving on from the above illustration, in one example embodiment, a network device may comprise a network interface; a processor comprising instructions, which when executed, cause the processor to: receive a set of signal measures, wherein each signal measure in the set of signal measures corresponds to a respective audio signal received by a device in a media playback system which is processed based on a first set of audio processing algorithms; identify a plurality of signal measures in the set of signal measures; cause, via the network interface, audio signals corresponding to the identified plurality of signal measures to be processed by one or more devices in the media playback system so as to improve a signal measure of each of the audio signals, wherein the audio signals are processed based on a second set of audio processing algorithms; and combine the processed audio signals into a combined audio signal. An algorithm of the second set of audio processing algorithms may process the audio signals based on content played by a playback device of the media playback system. Causing the audio signals corresponding to the identified plurality of signal measures to be processed by one or more devices in the media playback system may comprise receiving an indication of spare computational power from the one or more devices, identifying which devices have a spare computational power above a threshold amount, and causing the audio signals corresponding to the identified plurality of signal measures to be processed by the identified devices. A resolution of the first set of audio processing algorithms may be lower than a resolution of the second set of audio processing algorithms. The network device may further comprise instructions for causing the processor to send, via the network connection, the combined audio signal to a server. The first set of audio processing algorithms and the second set of audio processing algorithms may comprise one or more of an echo cancellation algorithm and a beamforming algorithm. Combining the processed audio signals into a combined audio signal may comprise weighting one or more of the processed audio signals. The audio signals may be impulse responses. A signal measure of the combined processed audio signals may be higher than any of the audio signals with improved signal measures. The identified plurality of signal measures in the set of signal measures may be those with signal to noise ratios above a threshold amount.

In another example embodiment, a method may comprise: receiving a set of signal measures, wherein each signal measure in the set of signal measures corresponds to a respective audio signal received by a device in a media playback system which is processed based on a first set of audio processing algorithms; identifying a plurality of signal measures in the set of signal measures; causing audio signals corresponding to the identified plurality of signal measures to be processed by one or more devices in the media playback system to improve a signal measure of each of the audio signals, wherein the audio signals are processed based on a second set of audio processing algorithms; and combining the processed audio signals into a combined audio signal. Causing the audio signals corresponding to the identified plurality of signal measures to be processed by one or more devices in the media playback system may comprise receiving an indication of spare computational power from each device in the media playback system, identifying which devices have a spare computational power above a threshold amount, and causing the audio signals corresponding to the identified plurality of signal measures to be processed by the identified devices. Combining the audio signals with improved signal measures into a combined audio signal may comprise weighting one or more of the processed audio signals. The method may further comprise sending the combined audio signal to a server. The first set of audio processing algorithms and the second set of audio processing algorithms may comprise one or more of an echo cancellation algorithm and a beamforming algorithm. The identified plurality of signal measures in the set of signal measures may be those with signal to noise ratios above a threshold amount.

In yet another example embodiment, a computer readable storage medium may include instructions for execution by a processor, the instructions, when executed, cause the processor to implement a method comprising: receiving a set of signal measures, wherein each signal measure in the set of signal measures corresponds to a respective audio signal received by a device in a media playback system which is processed based on a first set of audio processing algorithms; identifying a plurality of signal measures in the set of signal measures; causing audio signals corresponding to the identified plurality of signal measures to be processed by one or more devices in the media playback system to improve a signal measure of each of the audio signals, wherein the audio signals are processed based on a second set of audio processing algorithms; and combining the processed audio signals into a combined audio signal. Causing the audio signals corresponding to the identified plurality of signal measures to be processed by one or more devices in the media playback system may comprise receiving an indication of spare computational power from the one or more devices, identifying which devices have a spare computational power above a threshold amount, and causing the audio signals corresponding to the identified plurality of signal measures to be processed by the identified devices. Combining the processed audio signals into a combined audio signal may comprise weighting one or more of the processed audio signals.

II. Example Operating Environment

FIG. 1 shows an example configuration of a media playback system 100 in which one or more embodiments disclosed herein may be practiced or implemented. The media playback system 100 as shown is associated with an example home environment having several rooms and spaces, such as for example, a master bedroom, an office, a dining room, and a living room. As shown in the example of FIG. 1, the media playback system 100 includes playback devices 102-124, control devices 126 and 128, and a wired or wireless network router 130.

Further discussions relating to the different components of the example media playback system 100 and how the different components may interact to provide a user with a media experience may be found in the following sections. While discussions herein may generally refer to the example media playback system 100, technologies described herein are not limited to applications within, among other things, the home environment as shown in FIG. 1. For instance, the technologies described herein may be useful in environments where multi-zone audio may be desired, such as, for example, a commercial setting like a restaurant, mall or airport, a vehicle like a sports utility vehicle (SUV), bus or car, a ship or boat, an airplane, and so on.

a. Example Playback Devices

FIG. 2 shows a functional block diagram of an example playback device 200 that may be configured to be one or more of the playback devices 102-124 of the media playback system 100 of FIG. 1. The playback device 200 may include a processor 202, software components 204, memory 206, audio processing components 208, audio amplifier(s) 210, speaker(s) 212, a network interface 214 including wireless interface(s) 216 and wired interface(s) 218, and microphone(s) 220. In one case, the playback device 200 may not include the speaker(s) 212, but rather a speaker interface for connecting the playback device 200 to external speakers. In another case, the playback device 200 may include neither the speaker(s) 212 nor the audio amplifier(s) 210, but rather an audio interface for connecting the playback device 200 to an external audio amplifier or audio-visual receiver.

In one example, the processor 202 may be a clock-driven computing component configured to process input data according to instructions stored in the memory 206. The memory 206 may be a tangible computer-readable medium configured to store instructions executable by the processor 202. For instance, the memory 206 may be data storage that can be loaded with one or more of the software components 204 executable by the processor 202 to achieve certain functions. In one example, the functions may involve the playback device 200 retrieving audio data from an audio source or another playback device. In another example, the functions may involve the playback device 200 sending audio data to another device or playback device on a network. In yet another example, the functions may involve pairing of the playback device 200 with one or more playback devices to create a multi-channel audio environment.

Certain functions may involve the playback device 200 synchronizing playback of audio content with one or more other playback devices. During synchronous playback, a listener will preferably not be able to perceive time-delay differences between playback of the audio content by the playback device 200 and the one or more other playback devices. U.S. Pat. No. 8,234,395 entitled, “System and method for synchronizing operations among a plurality of independently clocked digital data processing devices,” which is hereby incorporated by reference, provides in more detail some examples for audio playback synchronization among playback devices.

The memory 206 may further be configured to store data associated with the playback device 200, such as one or more zones and/or zone groups the playback device 200 is a part of, audio sources accessible by the playback device 200, or a playback queue that the playback device 200 (or some other playback device) may be associated with. The data may be stored as one or more state variables that are periodically updated and used to describe the state of the playback device 200. The memory 206 may also include the data associated with the state of the other devices of the media system, and shared from time to time among the devices so that one or more of the devices have the most recent data associated with the system. Other embodiments are also possible.

The audio processing components 208 may include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor (DSP), and so on. In one embodiment, one or more of the audio processing components 208 may be a subcomponent of the processor 202. In one example, audio content may be processed and/or intentionally altered by the audio processing components 208 to produce audio signals. The produced audio signals may then be provided to the audio amplifier(s) 210 for amplification and playback through speaker(s) 212. Particularly, the audio amplifier(s) 210 may include devices configured to amplify audio signals to a level for driving one or more of the speakers 212. The speaker(s) 212 may include an individual transducer (e.g., a “driver”) or a complete speaker system involving an enclosure with one or more drivers. A particular driver of the speaker(s) 212 may include, for example, a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and/or a tweeter (e.g., for high frequencies). In some cases, each transducer in the one or more speakers 212 may be driven by an individual corresponding audio amplifier of the audio amplifier(s) 210. In addition to producing analog signals for playback by the playback device 200, the audio processing components 208 may be configured to process audio content to be sent to one or more other playback devices for playback.

Audio content to be processed and/or played back by the playback device 200 may be received from an external source, such as via an audio line-in input connection (e.g., an auto-detecting 3.5 mm audio line-in connection) or the network interface 214.

The network interface 214 may be configured to facilitate a data flow between the playback device 200 and one or more other devices on a data network. As such, the playback device 200 may be configured to receive audio content over the data network from one or more other playback devices in communication with the playback device 200, network devices within a local area network, or audio content sources over a wide area network such as the Internet. In one example, the audio content and other signals transmitted and received by the playback device 200 may be transmitted in the form of digital packet data containing an Internet Protocol (IP)-based source address and IP-based destination addresses. In such a case, the network interface 214 may be configured to parse the digital packet data such that the data destined for the playback device 200 is properly received and processed by the playback device 200.

As shown, the network interface 214 may include wireless interface(s) 216 and wired interface(s) 218. The wireless interface(s) 216 may provide network interface functions for the playback device 200 to wirelessly communicate with other devices (e.g., other playback device(s), speaker(s), receiver(s), network device(s), control device(s) within a data network the playback device 200 is associated with) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The wired interface(s) 218 may provide network interface functions for the playback device 200 to communicate over a wired connection with other devices in accordance with a communication protocol (e.g., IEEE 802.3). While the network interface 214 shown in FIG. 2 includes both wireless interface(s) 216 and wired interface(s) 218, the network interface 214 may in some embodiments include only wireless interface(s) or only wired interface(s).

The microphone(s) 220 may be arranged to detect sound in the environment of the playback device 200. For instance, the microphone(s) may be mounted on an exterior wall of a housing of the playback device. The microphone(s) may be any type of microphone now known or later developed such as a condenser microphone, electret condenser microphone, or a dynamic microphone. The microphone(s) may be sensitive to a portion of the frequency range of the speaker(s) 220. One or more of the speaker(s) 220 may operate in reverse as the microphone(s) 220. In some aspects, the playback device 200 might not have microphone(s) 220.

In one example, the playback device 200 and one other playback device may be paired to play two separate audio components of audio content. For instance, playback device 200 may be configured to play a left channel audio component, while the other playback device may be configured to play a right channel audio component, thereby producing or enhancing a stereo effect of the audio content. The paired playback devices (also referred to as “bonded playback devices”) may further play audio content in synchrony with other playback devices.

In another example, the playback device 200 may be sonically consolidated with one or more other playback devices to form a single, consolidated playback device. A consolidated playback device may be configured to process and reproduce sound differently than an unconsolidated playback device or playback devices that are paired, because a consolidated playback device may have additional speaker drivers through which audio content may be rendered. For instance, if the playback device 200 is a playback device designed to render low frequency range audio content (i.e. a subwoofer), the playback device 200 may be consolidated with a playback device designed to render full frequency range audio content. In such a case, the full frequency range playback device, when consolidated with the low frequency playback device 200, may be configured to render only the mid and high frequency components of audio content, while the low frequency range playback device 200 renders the low frequency component of the audio content. The consolidated playback device may further be paired with a single playback device or yet another consolidated playback device.

By way of illustration, SONOS, Inc. presently offers (or has offered) for sale certain playback devices including a “PLAY:1,” “PLAY:3,” “PLAY:5,” “PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future playback devices may additionally or alternatively be used to implement the playback devices of example embodiments disclosed herein. Additionally, it is understood that a playback device is not limited to the example illustrated in FIG. 2 or to the SONOS product offerings. For example, a playback device may include a wired or wireless headphone. In another example, a playback device may include or interact with a docking station for personal mobile media playback devices. In yet another example, a playback device may be integral to another device or component such as a television, a lighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Zone Configurations

Referring back to the media playback system 100 of FIG. 1, the environment may have one or more playback zones, each with one or more playback devices. The media playback system 100 may be established with one or more playback zones, after which one or more zones may be added, or removed to arrive at the example configuration shown in FIG. 1. Each zone may be given a name according to a different room or space such as an office, bathroom, master bedroom, bedroom, kitchen, dining room, living room, and/or balcony. In one case, a single playback zone may include multiple rooms or spaces. In another case, a single room or space may include multiple playback zones.

As shown in FIG. 1, the balcony, dining room, kitchen, bathroom, office, and bedroom zones each have one playback device, while the living room and master bedroom zones each have multiple playback devices. In the living room zone, playback devices 104, 106, 108, and 110 may be configured to play audio content in synchrony as individual playback devices, as one or more bonded playback devices, as one or more consolidated playback devices, or any combination thereof. Similarly, in the case of the master bedroom, playback devices 122 and 124 may be configured to play audio content in synchrony as individual playback devices, as a bonded playback device, or as a consolidated playback device.

In one example, one or more playback zones in the environment of FIG. 1 may each be playing different audio content. For instance, the user may be grilling in the balcony zone and listening to hip hop music being played by the playback device 102 while another user may be preparing food in the kitchen zone and listening to classical music being played by the playback device 114. In another example, a playback zone may play the same audio content in synchrony with another playback zone. For instance, the user may be in the office zone where the playback device 118 is playing the same rock music that is being playing by playback device 102 in the balcony zone. In such a case, playback devices 102 and 118 may be playing the rock music in synchrony such that the user may seamlessly (or at least substantially seamlessly) enjoy the audio content that is being played out-loud while moving between different playback zones. Synchronization among playback zones may be achieved in a manner similar to that of synchronization among playback devices, as described in previously referenced U.S. Pat. No. 8,234,395.

As suggested above, the zone configurations of the media playback system 100 may be dynamically modified, and in some embodiments, the media playback system 100 supports numerous configurations. For instance, if a user physically moves one or more playback devices to or from a zone, the media playback system 100 may be reconfigured to accommodate the change(s). For instance, if the user physically moves the playback device 102 from the balcony zone to the office zone, the office zone may now include both the playback device 118 and the playback device 102. The playback device 102 may be paired or grouped with the office zone and/or renamed if so desired via a control device such as the control devices 126 and 128. On the other hand, if the one or more playback devices are moved to a particular area in the home environment that is not already a playback zone, a new playback zone may be created for the particular area.

Further, different playback zones of the media playback system 100 may be dynamically combined into zone groups or split up into individual playback zones. For instance, the dining room zone and the kitchen zone 114 may be combined into a zone group for a dinner party such that playback devices 112 and 114 may render audio content in synchrony. On the other hand, the living room zone may be split into a television zone including playback device 104, and a listening zone including playback devices 106, 108, and 110, if the user wishes to listen to music in the living room space while another user wishes to watch television.

c. Example Control Devices

FIG. 3 shows a functional block diagram of an example control device 300 that may be configured to be one or both of the control devices 126 and 128 of the media playback system 100. As shown, the control device 300 may include a processor 302, memory 304, a network interface 306, a user interface 308, microphone(s) 310, and software components 312. In one example, the control device 300 may be a dedicated controller for the media playback system 100. In another example, the control device 300 may be a network device on which media playback system controller application software may be installed, such as for example, an iPhone™, iPad™ or any other smart phone, tablet or network device (e.g., a networked computer such as a PC or Mac™).

The processor 302 may be configured to perform functions relevant to facilitating user access, control, and configuration of the media playback system 100. The memory 304 may be data storage that can be loaded with one or more of the software components executable by the processor 302 to perform those functions. The memory 304 may also be configured to store the media playback system controller application software and other data associated with the media playback system 100 and the user.

In one example, the network interface 306 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on). The network interface 306 may provide a means for the control device 300 to communicate with other devices in the media playback system 100. In one example, data and information (e.g., such as a state variable) may be communicated between control device 300 and other devices via the network interface 306. For instance, playback zone and zone group configurations in the media playback system 100 may be received by the control device 300 from a playback device or another network device, or transmitted by the control device 300 to another playback device or network device via the network interface 306. In some cases, the other network device may be another control device.

Playback device control commands such as volume control and audio playback control may also be communicated from the control device 300 to a playback device via the network interface 306. As suggested above, changes to configurations of the media playback system 100 may also be performed by a user using the control device 300. The configuration changes may include adding/removing one or more playback devices to/from a zone, adding/removing one or more zones to/from a zone group, forming a bonded or consolidated player, separating one or more playback devices from a bonded or consolidated player, among others. Accordingly, the control device 300 may sometimes be referred to as a controller, whether the control device 300 is a dedicated controller or a network device on which media playback system controller application software is installed.

Control device 300 may include microphone(s) 310. Microphone(s) 310 may be arranged to detect sound in the environment of the control device 300. Microphone(s) 310 may be any type of microphone now known or later developed such as a condenser microphone, electret condenser microphone, or a dynamic microphone. The microphone(s) may be sensitive to a portion of a frequency range. Two or more microphones 310 may be arranged to capture location information of an audio source (e.g., voice, audible sound) and/or to assist in filtering background noise.

The user interface 308 of the control device 300 may be configured to facilitate user access and control of the media playback system 100, by providing a controller interface such as the controller interface 400 shown in FIG. 4. The controller interface 400 includes a playback control region 410, a playback zone region 420, a playback status region 430, a playback queue region 440, and an audio content sources region 450. The user interface 400 as shown is just one example of a user interface that may be provided on a network device such as the control device 300 of FIG. 3 (and/or the control devices 126 and 128 of FIG. 1) and accessed by users to control a media playback system such as the media playback system 100. Other user interfaces of varying formats, styles, and interactive sequences may alternatively be implemented on one or more network devices to provide comparable control access to a media playback system.

The playback control region 410 may include selectable (e.g., by way of touch or by using a cursor) icons to cause playback devices in a selected playback zone or zone group to play or pause, fast forward, rewind, skip to next, skip to previous, enter/exit shuffle mode, enter/exit repeat mode, enter/exit cross fade mode. The playback control region 410 may also include selectable icons to modify equalization settings, and playback volume, among other possibilities.

The playback zone region 420 may include representations of playback zones within the media playback system 100. In some embodiments, the graphical representations of playback zones may be selectable to bring up additional selectable icons to manage or configure the playback zones in the media playback system, such as a creation of bonded zones, creation of zone groups, separation of zone groups, and renaming of zone groups, among other possibilities.

For example, as shown, a “group” icon may be provided within each of the graphical representations of playback zones. The “group” icon provided within a graphical representation of a particular zone may be selectable to bring up options to select one or more other zones in the media playback system to be grouped with the particular zone. Once grouped, playback devices in the zones that have been grouped with the particular zone will be configured to play audio content in synchrony with the playback device(s) in the particular zone. Analogously, a “group” icon may be provided within a graphical representation of a zone group. In this case, the “group” icon may be selectable to bring up options to deselect one or more zones in the zone group to be removed from the zone group. Other interactions and implementations for grouping and ungrouping zones via a user interface such as the user interface 400 are also possible. The representations of playback zones in the playback zone region 420 may be dynamically updated as playback zone or zone group configurations are modified.

The playback status region 430 may include graphical representations of audio content that is presently being played, previously played, or scheduled to play next in the selected playback zone or zone group. The selected playback zone or zone group may be visually distinguished on the user interface, such as within the playback zone region 420 and/or the playback status region 430. The graphical representations may include track title, artist name, album name, album year, track length, and other relevant information that may be useful for the user to know when controlling the media playback system via the user interface 400.

The playback queue region 440 may include graphical representations of audio content in a playback queue associated with the selected playback zone or zone group. In some embodiments, each playback zone or zone group may be associated with a playback queue containing information corresponding to zero or more audio items for playback by the playback zone or zone group. For instance, each audio item in the playback queue may comprise a uniform resource identifier (URI), a uniform resource locator (URL) or some other identifier that may be used by a playback device in the playback zone or zone group to find and/or retrieve the audio item from a local audio content source or a networked audio content source, possibly for playback by the playback device.

In one example, a playlist may be added to a playback queue, in which case information corresponding to each audio item in the playlist may be added to the playback queue. In another example, audio items in a playback queue may be saved as a playlist. In a further example, a playback queue may be empty, or populated but “not in use” when the playback zone or zone group is playing continuously streaming audio content, such as Internet radio that may continue to play until otherwise stopped, rather than discrete audio items that have playback durations. In an alternative embodiment, a playback queue can include Internet radio and/or other streaming audio content items and be “in use” when the playback zone or zone group is playing those items. Other examples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,” playback queues associated with the affected playback zones or zone groups may be cleared or re-associated. For example, if a first playback zone including a first playback queue is grouped with a second playback zone including a second playback queue, the established zone group may have an associated playback queue that is initially empty, that contains audio items from the first playback queue (such as if the second playback zone was added to the first playback zone), that contains audio items from the second playback queue (such as if the first playback zone was added to the second playback zone), or a combination of audio items from both the first and second playback queues. Subsequently, if the established zone group is ungrouped, the resulting first playback zone may be re-associated with the previous first playback queue, or be associated with a new playback queue that is empty or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Similarly, the resulting second playback zone may be re-associated with the previous second playback queue, or be associated with a new playback queue that is empty, or contains audio items from the playback queue associated with the established zone group before the established zone group was ungrouped. Other examples are also possible.

Referring back to the user interface 400 of FIG. 4, the graphical representations of audio content in the playback queue region 440 may include track titles, artist names, track lengths, and other relevant information associated with the audio content in the playback queue. In one example, graphical representations of audio content may be selectable to bring up additional selectable icons to manage and/or manipulate the playback queue and/or audio content represented in the playback queue. For instance, a represented audio content may be removed from the playback queue, moved to a different position within the playback queue, or selected to be played immediately, or after any currently playing audio content, among other possibilities. A playback queue associated with a playback zone or zone group may be stored in a memory on one or more playback devices in the playback zone or zone group, on a playback device that is not in the playback zone or zone group, and/or some other designated device.

The audio content sources region 450 may include graphical representations of selectable audio content sources from which audio content may be retrieved and played by the selected playback zone or zone group. Discussions pertaining to audio content sources may be found in the following section.

d. Example Audio Content Sources

As indicated previously, one or more playback devices in a zone or zone group may be configured to retrieve for playback audio content (e.g. according to a corresponding URI or URL for the audio content) from a variety of available audio content sources. In one example, audio content may be retrieved by a playback device directly from a corresponding audio content source (e.g., a line-in connection). In another example, audio content may be provided to a playback device over a network via one or more other playback devices or network devices.

Example audio content sources may include a memory of one or more playback devices in a media playback system such as the media playback system 100 of FIG. 1, local music libraries on one or more network devices (such as a control device, a network-enabled personal computer, or a networked-attached storage (NAS), for example), streaming audio services providing audio content via the Internet (e.g., the cloud), or audio sources connected to the media playback system via a line-in input connection on a playback device or network devise, among other possibilities.

In some embodiments, audio content sources may be regularly added or removed from a media playback system such as the media playback system 100 of FIG. 1. In one example, an indexing of audio items may be performed whenever one or more audio content sources are added, removed or updated. Indexing of audio items may involve scanning for identifiable audio items in all folders/directory shared over a network accessible by playback devices in the media playback system, and generating or updating an audio content database containing metadata (e.g., title, artist, album, track length, among others) and other associated information, such as a URI or URL for each identifiable audio item found. Other examples for managing and maintaining audio content sources may also be possible.

The above discussions relating to playback devices, controller devices, playback zone configurations, and media content sources provide only some examples of operating environments within which functions and methods described below may be implemented. Other operating environments and configurations of media playback systems, playback devices, and network devices not explicitly described herein may also be applicable and suitable for implementation of the functions and methods.

e. Example Plurality of Networked Devices

FIG. 5 shows an example plurality of devices 500 that may be configured to provide an audio playback experience based on voice control. One having ordinary skill in the art will appreciate that the devices shown in FIG. 5 are for illustrative purposes only, and variations including different and/or additional devices may be possible. As shown, the plurality of devices 500 includes computing devices 504, 506, and 508; network microphone devices (NMDs) 512, 514, and 516; playback devices (PBDs) 532, 534, 536, and 538; and a controller device (CR) 522.

Each of the plurality of devices 500 may be network-capable devices that can establish communication with one or more other devices in the plurality of devices according to one or more network protocols, such as NFC, Bluetooth, Ethernet, and IEEE 802.11, among other examples, over one or more types of networks, such as wide area networks (WAN), local area networks (LAN), and personal area networks (PAN), among other possibilities.

As shown, the computing devices 504, 506, and 508 may be part of a cloud network 502. The cloud network 502 may include additional computing devices. In one example, the computing devices 504, 506, and 508 may be different servers. In another example, two or more of the computing devices 504, 506, and 508 may be modules of a single server. Analogously, each of the computing device 504, 506, and 508 may include one or more modules or servers. For ease of illustration purposes herein, each of the computing devices 504, 506, and 508 may be configured to perform particular functions within the cloud network 502. For instance, computing device 508 may be a source of audio content for a streaming music service.

As shown, the computing device 504 may be configured to interface with NMDs 512, 514, and 516 via communication path 542. NMDs 512, 514, and 516 may be components of one or more “Smart Home” systems. In one case, NMDs 512, 514, and 516 may be physically distributed throughout a household, similar to the distribution of devices shown in FIG. 1. In another case, two or more of the NMDs 512, 514, and 516 may be physically positioned within relative close proximity of one another. Communication path 542 may comprise one or more types of networks, such as a WAN including the Internet, LAN, and/or PAN, among other possibilities.

In one example, one or more of the NMDs 512, 514, and 516 may be devices configured primarily for audio detection. In another example, one or more of the NMDs 512, 514, and 516 may be components of devices having various primary utilities. For instance, as discussed above in connection to FIGS. 2 and 3, one or more of NMDs 512, 514, and 516 may be the microphone(s) 220 of playback device 200 or the microphone(s) 310 of network device 300. Further, in some cases, one or more of NMDs 512, 514, and 516 may be the playback device 200 or network device 300. In an example, one or more of NMDs 512, 514, and/or 516 may include multiple microphones arranged in a microphone array.

As shown, the computing device 506 may be configured to interface with CR 522 and PBDs 532, 534, 536, and 538 via communication path 544. In one example, CR 522 may be a network device such as the network device 200 of FIG. 2. Accordingly, CR 522 may be configured to provide the controller interface 400 of FIG. 4. Similarly, PBDs 532, 534, 536, and 538 may be playback devices such as the playback device 300 of FIG. 3. As such, PBDs 532, 534, 536, and 538 may be physically distributed throughout a household as shown in FIG. 1. For illustration purposes, PBDs 536 and 538 may be part of a bonded zone 530, while PBDs 532 and 534 may be part of their own respective zones. As described above, the PBDs 532, 534, 536, and 538 may be dynamically bonded, grouped, unbonded, and ungrouped. Communication path 544 may comprise one or more types of networks, such as a WAN including the Internet, LAN, and/or PAN, among other possibilities.

In one example, as with NMDs 512, 514, and 516, CR 522 and PBDs 532, 534, 536, and 538 may also be components of one or more “Smart Home” systems. In one case, PBDs 532, 534, 536, and 538 may be distributed throughout the same household as the NMDs 512, 514, and 516. Further, as suggested above, one or more of PBDs 532, 534, 536, and 538 may be one or more of NMDs 512, 514, and 516.

The NMDs 512, 514, and 516 may be part of a local area network, and the communication path 542 may include an access point that links the local area network of the NMDs 512, 514, and 516 to the computing device 504 over a WAN (communication path not shown). Likewise, each of the NMDs 512, 514, and 516 may communicate with each other via such an access point.

Similarly, CR 522 and PBDs 532, 534, 536, and 538 may be part of a local area network and/or a local playback network as discussed in previous sections, and the communication path 544 may include an access point that links the local area network and/or local playback network of CR 522 and PBDs 532, 534, 536, and 538 to the computing device 506 over a WAN. As such, each of the CR 522 and PBDs 532, 534, 536, and 538 may also communicate with each over such an access point.

In one example, communication paths 542 and 544 may comprise the same access point. In an example, each of the NMDs 512, 514, and 516, CR 522, and PBDs 532, 534, 536, and 538 may access the cloud network 502 via the same access point for a household.

As shown in FIG. 5, each of the NMDs 512, 514, and 516, CR 522, and PBDs 532, 534, 536, and 538 may also directly communicate with one or more of the other devices via communication means 546. Communication means 546 as described herein may involve one or more forms of communication between the devices, according to one or more network protocols, over one or more types of networks, and/or may involve communication via one or more other network devices. For instance, communication means 546 may include one or more of for example, Bluetooth™ (IEEE 802.15), NFC, Wireless direct, and/or Proprietary wireless, among other possibilities.

In one example, CR 522 may communicate with NMD 512 over Bluetooth™, and communicate with PBD 534 over another local area network. In another example, NMD 514 may communicate with CR 522 over another local area network, and communicate with PBD 536 over Bluetooth. In a further example, each of the PBDs 532, 534, 536, and 538 may communicate with each other according to a spanning tree protocol over a local playback network, while each communicating with CR 522 over a local area network, different from the local playback network. Other examples are also possible.

In some cases, communication means between the NMDs 512, 514, and 516, CR 522, and PBDs 532, 534, 536, and 538 may change depending on types of communication between the devices, network conditions, and/or latency demands. For instance, communication means 546 may be used when NMD 516 is first introduced to the household with the PBDs 532, 534, 536, and 538. In one case, the NMD 516 may transmit identification information corresponding to the NMD 516 to PBD 538 via NFC, and PBD 538 may in response, transmit local area network information to NMD 516 via NFC (or some other form of communication). However, once NMD 516 has been configured within the household, communication means between NMD 516 and PBD 538 may change. For instance, NMD 516 may subsequently communicate with PBD 538 via communication path 542, the cloud network 502, and communication path 544. In another example, the NMDs and PBDs may never communicate via local communications means 546. In a further example, the NMDs and PBDs may communicate primarily via local communications means 546. Other examples are also possible.

In an illustrative example, NMDs 512, 514, and 516 may be configured to receive voice inputs to control PBDs 532, 534, 536, and 538. The available control commands may include any media playback system controls previously discussed, such as playback volume control, playback transport controls, music source selection, and grouping, among other possibilities. In one instance, NMD 512 may receive a voice input to control one or more of the PBDs 532, 534, 536, and 538. In response to receiving the voice input, NMD 512 may transmit via communication path 542, the voice input to computing device 504 for processing. In one example, the computing device 504 may convert the voice input to an equivalent text command, and parse the text command to identify a command. Computing device 504 may then subsequently transmit the text command to the computing device 506. In another example, the computing device 504 may convert the voice input to an equivalent text command, and then subsequently transmit the text command to the computing device 506. The computing device 506 may then parse the text command to identify one or more playback commands.

For instance, if the text command is “Play ‘Track 1’ by ‘Artist 1’ from ‘Streaming Service 1’ in ‘Zone 1’,” The computing device 506 may identify (i) a URL for “Track 1” by “Artist 1” available from “Streaming Service 1,” and (ii) at least one playback device in “Zone 1.” In this example, the URL for “Track 1” by “Artist 1” from “Streaming Service 1” may be a URL pointing to computing device 508, and “Zone 1” may be the bonded zone 530. As such, upon identifying the URL and one or both of PBDs 536 and 538, the computing device 506 may transmit via communication path 544 to one or both of PBDs 536 and 538, the identified URL for playback. One or both of PBDs 536 and 538 may responsively retrieve audio content from the computing device 508 according to the received URL, and begin playing “Track 1” by “Artist 1” from “Streaming Service 1.”

One having ordinary skill in the art will appreciate that the above is just one illustrative example, and that other implementations are also possible. In one case, operations performed by one or more of the plurality of devices 500, as described above, may be performed by one or more other devices in the plurality of device 500. For instance, the conversion from voice input to the text command may be alternatively, partially, or wholly performed by another device or devices, such as NMD 512, computing device 506, PBD 536, and/or PBD 538. Analogously, the identification of the URL may be alternatively, partially, or wholly performed by another device or devices, such as NMD 512, computing device 504, PBD 536, and/or PBD 538.

f. Example Network Microphone Device

FIG. 6 shows a function block diagram of an example network microphone device 600 that may be configured to be one or more of NMDs 512, 514, and 516 of FIG. 5. As shown, the network microphone device 600 includes a processor 602, memory 604, a microphone array 606, a network interface 608, a user interface 610, software components 612, and speaker(s) 614. One having ordinary skill in the art will appreciate that other network microphone device configurations and arrangements are also possible. For instance, network microphone devices may alternatively exclude the speaker(s) 614 or have a single microphone instead of microphone array 606.

The processor 602 may include one or more processors and/or controllers, which may take the form of a general or special-purpose processor or controller. For instance, the processing unit 602 may include microprocessors, microcontrollers, application-specific integrated circuits, digital signal processors, and the like. The memory 604 may be data storage that can be loaded with one or more of the software components executable by the processor 602 to perform those functions. Accordingly, memory 604 may comprise one or more non-transitory computer-readable storage mediums, examples of which may include volatile storage mediums such as random access memory, registers, cache, etc. and non-volatile storage mediums such as read-only memory, a hard-disk drive, a solid-state drive, flash memory, and/or an optical-storage device, among other possibilities.

The microphone array 606 may be a plurality of microphones arranged to detect sound in the environment of the network microphone device 600. Microphone array 606 may include any type of microphone now known or later developed such as a condenser microphone, electret condenser microphone, or a dynamic microphone, among other possibilities. In one example, the microphone array may be arranged to detect audio from one or more directions relative to the network microphone device. The microphone array 606 may be sensitive to a portion of a frequency range. In one example, a first subset of the microphone array 606 may be sensitive to a first frequency range, while a second subset of the microphone array may be sensitive to a second frequency range. The microphone array 606 may further be arranged to capture location information of an audio source (e.g., voice, audible sound) and/or to assist in filtering background noise. Notably, in some embodiments the microphone array may consist of only a single microphone, rather than a plurality of microphones.

The network interface 608 may be configured to facilitate wireless and/or wired communication between various network devices, such as, in reference to FIG. 5, CR 522, PBDs 532-538, computing device 504-508 in cloud network 502, and other network microphone devices, among other possibilities. As such, network interface 608 may take any suitable form for carrying out these functions, examples of which may include an Ethernet interface, a serial bus interface (e.g., FireWire, USB 2.0, etc.), a chipset and antenna adapted to facilitate wireless communication, and/or any other interface that provides for wired and/or wireless communication. In one example, the network interface 608 may be based on an industry standard (e.g., infrared, radio, wired standards including IEEE 802.3, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.15, 4G mobile communication standard, and so on).

The user interface 610 of the network microphone device 600 may be configured to facilitate user interactions with the network microphone device. In one example, the user interface 608 may include one or more of physical buttons, graphical interfaces provided on touch sensitive screen(s) and/or surface(s), among other possibilities, for a user to directly provide input to the network microphone device 600. The user interface 610 may further include one or more of lights and the speaker(s) 614 to provide visual and/or audio feedback to a user. In one example, the network microphone device 600 may further be configured to playback audio content via the speaker(s) 614.

III. Example Systems

The playback device, the controller device, and the network microphone device may be in an environment such as a living room in a home. The microphone array of one or more of these devices may receive an audio signal. The audio signal may include an indication of a sonic input and noise. The sonic input may be a voice input such as a request to perform an action associated with the media playback system, e.g., “play audio” or “stop playing audio”. The sonic input may take the form of any other voice input as well. The noise could include white noise or impulse noise. Alternatively, the “noise” could be audio content played by a playback device in the media playback system.

It may be desirable to recover the sonic input from the audio signal that is received via the microphone array of a device. Examples described herein are directed to distributing, across devices in the media playback system, processing associated with improving a signal measure (e.g., signal to noise ratio) of the audio signal received by a device in the media playback system prior to the recovery of the sonic input. The processing is distributed to reduce degradation in performance of a particular device in the media playback system while the signal to noise ratio is improved. Improving the signal to noise ratio results in attenuating noise in the audio signal. The improved audio signal may then be passed to a computing device such as a server which is arranged to recover the sonic input. If the sonic input is a voice input, the server may further interpret from voice input the action associated with the voice input such as “play music on a playback device” or to “turn off the playback device”. The server may then cause the media playback system to perform the action.

FIG. 7 illustrates an example environment 700 where audio signals may be present. The example environment may be a room of a home, such as a living room or bedroom, which has a media playback system for playing audio content. The media playback system may include one or more playback devices 702, network microphone devices 704, controller devices 706, and/or computing devices (not shown). The playback device 702 may have one or more microphones (e.g., microphone arrays) for receiving an audio signal, one or more speakers for playing back audio content, and a processor for playing back the audio content. The network microphone device 704 may have one or more microphones (e.g., microphone arrays) for receiving the audio signal and a processor for transmitting the received audio signal to the computing device. The controller device 706 may have one or more microphones (e.g., microphone arrays) for receiving an audio signal and a processor for controlling the one or more playback devices in the media playback system. The computing device may be a server which is arranged with a processor to perform various processing associated with the media playback system. The processing may include processing of the audio signal sent by the network microphone device 704. The computing device may be located remote to devices in the environment 700 such as in a cloud network. The computing device may also source audio content to the one or more playback devices for playback.

The example environment 700 may also have an audio source 710. The audio source 710 may provide a sonic input. For example, the audio source 710 may be a user of the media playback system who speaks in the environment. In this case, the audio source may be a voice input. The sonic input produced by the audio source 710 may be directed in one or more directions. In one example, the sonic input may be generally directed toward a device in the media playback system. In another example, sonic input may be directed away from the device in the media playback system. In yet another example, the sonic input may be directed uniformly in all directions throughout the environment. In this regard, one or more of the microphone arrays of the playback device 702, NMD 704, and/or controller device 706 may receive an audio signal that includes an indication of the sonic input.

The audio signal received by the microphone array may also receive any noise present in the environment. The noise may be audio that is received by the device aside from the sonic input. For example, the noise may include an attenuated version of the sonic input, and echoes of the sonic input, as a result of the sonic input traveling through the environment, bouncing off walls and objects in the environment before reaching a microphone array. The “noise” could also be any audio content being played back by a playback device such as music.

A signal to noise ratio is a signal measure indicative of a comparison of a desired signal in the audio signal to the noise in the audio signal. The desired signal may be the sonic input in the audio signal and the noise may be audio other than the sonic input in the audio signal. The audio signal may have a relatively high signal to noise ratio if the device which receives the audio signal is in a same direction as the sonic input. For example, the NMD 704 in the upper left corner of the environment 700 may receive an audio signal with a high signal to noise ratio because the audio source 710 is outputting a sonic input in the direction of the NMD 704. On the other hand, the audio signal may have a relatively low signal to noise ratio if the device which receives the audio signal is not in a same direction as the audio source 710. For example, the NMD 704 in the lower right corner of the environment 700 may receive an audio signal with a low signal to noise ratio because the audio source 710 is not outputting a sonic input in the direction of the NMD 704. The microphone array of the NMD 704 may still receive the sonic input, but indirectly, for example, as a result of the sonic input bouncing off walls of the environment, objects in the environment such as furniture, or the ceiling in the environment and reaching the microphone array.

In one example, the signal to noise ratio can be improved using echo cancellation. The microphone array may receive multiple versions of the audio signal having different phases and magnitudes depending on the path that the audio signal took to reach the microphone array. For example, the audio signal may bounce off objects in an environment, such as furniture, walls, and the ceiling, before being received by the microphone array. The microphone array may receive multiple versions of the audio signal, i.e., echoes, and the multiple versions may arrive at the microphone array at different times depending on how long the audio signal takes to travel from the source to the microphone array.

Echo cancellation seeks to remove such “echoes” in the received audio signal. The audio signal that is received by the microphone array may be represented as a plurality of impulse responses. Each impulse response may be associated with a microphone of the microphone array. The impulse responses may be time aligned based on a distance between microphones associated with a respective impulse response and combined into a single signal, e.g., a combined impulse response. Then, the combined impulse response may be divided into windows of time. For example, an impulse response of 1000 ms may be divided into overlapping and/or non-overlapping windows of impulse responses of 100 ms for processing. The size of the windows of time may determine the improvement of the signal to noise ratio, e.g., a larger window results in a better signal to noise ratio. The echoes may be removed in each window of time through an adaptive filtering process. Further, the combined impulse responses could be compared to echo characteristics of various sonic inputs. For example, the computing device may have a database of echo characteristics for the various sonic inputs. These echo characteristics may have been determined during a calibration process of the microphone array and/or stored in a database on the computing device. The comparison may result in determining a likelihood that a signal in the combined impulse response is a sonic input. The likelihood determination facilitates isolating the sonic input from echoes in the audio signal to improve the signal to noise ratio of the audio signal.

As another example, the signal to noise ratio can be improved using beamforming. In a polar domain, the audio signal may be present in a range of 0 to 360 degrees around the microphone array, albeit at different magnitudes and phases depending on how the sonic input travels from the audio source 710 to a microphone array. The microphone array may be arranged to capture the audio signals in an angular range of the 360 degrees. For example, NMD 704 in the upper left corner of the environment 700 is shown at 712 to capture audio in a 100 degree angular range. The audio signal received over a certain angular range, may be divided into angular intervals 714. For example, in the polar domain, the audio signal may be received at over a 100 degree angular range which is divided into five 20 degree angular intervals. Applying beamforming over a larger angular range and/or a smaller angular interval may result in an improved signal to noise ratio.

The audio signal received in an angular interval may have certain characteristics. The characteristics of the audio signal may be compared to known characteristics when a sonic input originates in that direction. These known characteristics may have been determined during a calibration process of the microphone array and/or stored in a database on the computing device. For example, an impulse response of the audio signal may be compared to a known impulse response when sonic input originated from a particular direction. This comparison may provide a likelihood that the sonic input of the audio signal originates in that particular direction. The direction of the sonic input may then be used by the beamforming algorithm to improve the signal to noise ratio of the audio signal.

If a playback device in the media playback system is playing audio at the same time that the microphone array receives the audio signal, then yet another algorithm (herein referred to as “subtraction of known signal method” and variants) may be used to improve the signal to noise ratio of the audio signal. The audio playing in the background is known to the media playback system. It may be stored in an audio file or streaming from a server. This known audio can be subtracted from the received audio signal to improve the signal to noise ratio of the audio signal. For example, the audio playing in the background and the audio signal may be represented as impulse responses of a certain duration. The impulse response of the audio playing in the background may be subtracted from the received audio signal so as to attenuate the audio that is being played from the audio signal and improve the signal to noise ratio of the audio signal.

The signal to noise ratio may be further improved based on one or more of a microphone response of the microphone array, a playback device response, and a room response. The microphone array may have a response indicative of its audio sensitivity versus frequency. The playback device may have a response indicative its audio output versus frequency. The room response may be indicative of acoustic characteristics of the room as described in U.S. patent application Ser. No. 14/481,511, entitled “Playback Device Calibration”, the contents of which is herein incorporated by reference in its entirety. The microphone array response, the playback device response, and a room response may be used to improve the signal to noise ratio. For example, an inverse of the microphone array response, an inverse of the playback device response, and an inverse of the room response may be applied to the audio signal received by the microphone array prior to subtracting the impulse response of the audio being played back to improve the signal to noise ratio of the audio signal. The responses may also be used to improve the signal measures determined by the other algorithms as well.

The methods described above are examples of various methods of improving the signal to noise ratio. One or several algorithms may be applied or combined to improve the signal to noise ratio of the audio signal. An arrangement among a playback device playing audio, a microphone array, and an audio source may determine the type of audio improvement algorithm that is applied and the order in which it is applied. For example, if the playback device plays audio content and the audio source produces sonic input in a same direction toward the microphone array, then the subtraction of the known audio method may be applied to improve the signal to noise ratio. Beamforming may not be effective because the audio source and playback device are facing in the same direction and the beamforming would not be able to isolate the sonic input in view of the audio being played back by the playback device in the same direction. Then, echo cancellation method may be applied to cancel out any echoes associated with reverberation in the environment. As another example, the microphone array may be in between the playback device and the audio source. If the audio source produces sonic input in a direction of the playback device and the playback device plays audio in the direction of the audio source, then the beamforming may be applied first if the microphone array is facing in the same direction as the audio source. Then, an echo cancellation may be used to cancel echoes. Other arrangements are also possible in accordance with the disclosed embodiments and the arrangement of the media playback system in the environment.

The audio signal, as processed by one or more signal to noise improvement methods may be referred to herein as an improved audio signal. In embodiments, the audio signal received by the microphone array and the improved audio signal may be stored on the playback device, controller device, or computing device as an audio file. The audio signal may be a digital file representing a spectral response or temporal response. The spectral response may be an indication of how the audio signal captured by the microphone array and the improved audio signal varies with frequency. A power spectral density is an example representation of the spectral response. The temporal response may be an indication of how the audio signal and the improved audio signal changes within the room. The change may be characterized as a reverberation, delay, decay, or phase change of the audio signal. Additionally, or alternatively, the audio signal and improved audio signal may be represented as a set of impulse responses or bi-quad filter coefficients representative of the audio signal, among others.

In the case of the audio signal being represented as impulse responses, the signal to noise ratio of the improved audio signal may be calculated by dividing the impulse response of the improved audio signal with the received audio signal. As yet another example, the beamforming method may define a probability density function which indicates a likelihood that the sonic input the audio signal originates in a particular direction. An integral of the probability density function may be indicative of a signal to noise ratio of the improved audio signal. Still alternatively, the signal to noise ratio may be based on determining for the probability density function those directions where a first derivative of the likelihood is maximized, and integrating those regions to calculate the signal to noise ratio for the improved audio signal. Other arrangements are also possible for calculating a signal to noise ratio.

At least one signal to noise ratio or a plurality of signal to noise ratios may be associated with a microphone array. For example, the echo cancellation algorithm provides an improved audio signal based on the audio signal received by the microphone array. The signal to noise ratio of this improved audio signal may be calculated and associated with the microphone array. As another example, beamforming may be performed in a plurality of directions to improve an audio signal received in a particular direction. The signal to noise ratio of this improved audio signal with respect to direction may be calculated and associated with the microphone array. For example, the audio signal may be processed at directions of 20 degree angular intervals around the microphone array. Each 20 degree angular interval may have associated impulse response of the received audio signal, impulse response of the improved audio signal, and signal to noise ratio.

FIGS. 8 and 9 present respective embodiments that can be implemented within the disclosed operating environment. Methods and the other process disclosed herein may include one or more operations, functions, or actions. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

In addition, for the methods and other processes and methods disclosed herein, the flowchart shows functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, each block in the figures may represent circuitry that is wired to perform the specific logical functions in the process.

FIG. 8 is a flow chart 800 of functions associated with distributed processing to improving a signal measure, e.g., signal to noise ratio, of an audio signal received by a plurality of devices in a media playback system. In one example, the disclosed functions may be coordinated and at least partially performed by a playback device, such as one of the one or more playback devices in the media playback system. In another example, the disclosed functions may be coordinated and at least partially performed by a computing device. In yet another example, the functions may be coordinated and at least partially performed by a controller device. In another example, the disclosed functions may be coordinated and at least partially performed by a NMD. Other arrangements are also possible.

Referring to FIG. 8, at 802, a set of signal measures corresponding to audio signals processed based on first set of audio processing algorithms may be received. At 804, a plurality of signal measures in the set of signal measures may be identified. Then, at 806, the audio signals corresponding to the identified plurality of signal measures may be processed by one or more devices in the media playback system based on a second set of audio processing algorithms. Additionally, the audio signals may be processed based on spare computational power of a device of the one or more devices. At 808, the processed audio signals may be combined to produce a combined audio signal. The combined audio signal may have an improved signal measure such as a signal to noise ratio as compared to the audio signals processed at 802 and at 806. This improved signal measure allows for improved recovery of a sonic input of the audio signal so that, for instance, in the case that the sonic input is a voice input, a server arranged with voice processing capabilities may be able to interpret the voice input and perform a function associated with the voice input.

The functions of the example process shown in FIG. 8 will now be described in more detail.

Starting at 802, a set of signal measures corresponding to audio signals processed based on a first set of audio processing algorithms may be received. The playback device, controller device, and/or NMD of the media playback system may each receive one or more audio signals. A first set of audio processing algorithms may be applied to an audio signal received by a device to improve a signal to noise ratio of the audio signal. The first set of audio algorithms may be the echo cancellation method, beamforming method and/or subtraction of known signal method for a particular resolution. For example, the first set of audio processing algorithms may process impulse responses in a certain window size, e.g., 100 ms, or a certain angular interval of an angular range, e.g., 20 degrees over a 100 degree range. In some embodiments, the window sand/or angular interval size that is processed may be limited by available processing power of the playback device, controller device, NMD, or computing device that processes the audio signal. As a result of the processing, one or more signal measures may be associated with each device. The signal measure may be a signal to noise ratio also determined by the playback device, controller device, NMD, or computing device the processed audio signal. The one or more signal measures from each device in the media playback system may define a set of signal measures. For example, the set of signal measures may include the signal to noise ratio associated with a microphone array of a device or the signal to noise ratio associated with receiving an audio signal in a certain direction.

At 804, a plurality of signal measures in the set of signal measures may be identified. For example, the plurality of signal measures may be those signal measures, e.g., signal to noise ratio, which are the highest and/or those signal measures which are the lowest.

Then, at 806, the audio signals corresponding to the identified plurality of signal measures may be processed by one or more devices in the media playback system so as to improve a signal measure of each of the audio signals. The audio signals may be processed based on a second set of audio processing algorithms.

The audio signal may be processed based on the second set of audio processing algorithms to improve a signal to noise ratio. The second set of audio processing algorithms may be one or more of the echo cancellation algorithm, beamforming algorithm, or known signal subtraction algorithm, for instance, performed with a higher resolution. The higher resolution may be, for example, processing impulse responses in a larger window size, e.g., 200 ms vs. 100 ms as compared to the first set of audio processing algorithms, a smaller angular interval, e.g., 5 degree intervals vs. 20 degree intervals as compared to the first set of audio processing algorithms, or a larger angular range, e.g., a 200 degree range vs. a 100 degree range as compared to the first set of audio processing algorithms.

The devices in the media playback system have one or more processors. The one or more processors may have a maximum computational power. The maximum computational power is the power available to perform functions associated with device. In the case of the controller device, the maximum computational power may be characterized as available clock cycles to process and playback the audio signal control the playback devices. In the case of the server, the maximum computational power may be characterized as available clock cycles to source audio content to the playback devices. In the case of the playback device, the maximum computational power may be characterized as available clock cycles to play back audio content. The spare computational power may be that computational power beyond what may be needed to perform functions of the device, such as to play back the audio in the case of a playback device or control playback devices in the case of a controller device.

The higher resolution processing requires more computational power than the first set of audio processing algorithms. In this regard, the audio signals may be processed in a distributed manner across one or more devices in the media playback system based on the spare computational power available of a device to improve the signal to noise ratio beyond that of the first set of audio processing algorithms. By using the spare computational power, performance of the media playback system does not degrade with the additional processing associated with improving the signal to noise ratio of the audio signal. The audio signals may be distributed based on other criteria as well such as a speed of a processor of a device.

At 808, the processed audio signals may be combined into a combined audio signal. In some embodiments, the combined audio signal may be provided to the server to recover the sonic input of the audio signal.

FIG. 9 is a flow chart 900 of functions that describes in more detail the functions recited in FIG. 8 that may be performed in the distributed processing described in FIG. 8. In embodiments, these functions may be performed by the computing device but could be performed by a playback device, controller, and/or NMD.

At 902, the signal measures corresponding to the audio signals processed by devices in the media playback system may be received. For example, the playback device, NMD, and controller device may apply an audio processing algorithms to the audio signal or audio signals that are received by the device. The audio processing algorithm that is applied may be based on a first set of audio processing algorithms. In one example, the computing device may have a network interface and communication links that communicatively couple the computing device to the playback device, NMD, and controller device to receive the signal measure or signal measures that is determined by each device. In another example, the computing device instead of the device which receives the audio signal may receive the audio signal from a device, apply the audio processing algorithms and/or determine a signal measure. Other arrangements are also possible.

At 904, the signal measures may be stored in memory. The computing device may receive for each signal measure an indication of the microphone array of the device associated with the signal measure, an indication of the device associated with the signal measure, and/or an indication of a direction associated with the signal measure. The signal measures stored in memory may be further associated with one or more of these indications.

FIG. 10 illustrates various examples of storing the signal measures in memory. In embodiments, the signal measures may be stored in the form a table. If each device in the media playback system has one microphone array, the signal measures may be stored in table 1002 which identifies the signal to noise ratio for each device/microphone array. The table 1002 may be a two-dimensional matrix with each row having a signal to noise ratio and each column identifying the device/microphone array. If a device in the media playback system has one or more microphone arrays, then the signal measures may be stored in a table 1004 which identifies the signal to noise ratio for each microphone array on each device. The table 1004 may be a two-dimensional matrix with each row identifying the signal to noise ratios for each microphone array. If the signal to noise ratio is directional, e.g., determined by a beamforming algorithm, then the signal measure may be stored in a table 1006, e.g., two-dimensional matrix, which identifies the signal to ratio for a particular direction. The table could also have a third dimension which identifies the particular device or microphone array associated with the signal to noise ratio for a direction and/or microphone array, rather than included in one of the two dimensions of the table. The table may take other forms as well depending on the arrangement of the devices in the media playback system and based on the processing algorithms used to determine the signal to noise ratio.

The table may also be sorted such that the first entry in the table may identify the highest signal measure, e.g., signal to noise ratio, for the audio signal received by a microphone array and the last entry may identify the lowest signal measure, e.g., signal to noise ratio, for the audio signal received by a microphone array. In the case of the example tables 1002-1006 of FIG. 10, SNR A may represent a highest signal to noise measure and SNR F may represent a lowest signal to noise measure. The table, and for this matter how the signal measures are stored in memory, may take other forms as well depending on the arrangement of the devices in the media playback system and based on the processing algorithms used to determine the signal measure. For example, the table may also be sorted based on the signal to noise ratios meeting a threshold level.

At 906, the computing device may determine the spare computational power of the devices in the media playback system. Each device may indicate its spare computational power to a given device, such as a playback device, controller device, or server. In one example, the media playback may define a state variable indicative of an amount of spare computational power associated with a device. This state variable may be periodically updated and made available to the devices in the media playback system. In some embodiments, the state variable may take the form of a flag which indicates that it has a spare computational power.

Various types of flags may be set depending on an amount of spare computational power available. The flag may take the form of one or more bits that are set on the device or some other device to indicate that the device has spare computational power. For instance, “000” may indicate that the playback device has 50K clock cycles of computational power and “111” may indicate that the playback device has 1000K clock cycles of computational power. Based on the state variable, a given device, e.g., computing device, in the media playback system may obtain the spare computational power for each device and generate a table that identifies for each device its spare processing power. For example, the given device may read the bits associated with the flag to determine the spare computational power associated with a particular device in the media playback system.

At 908, an indication of the spare computational power of the devices may be stored in memory. The spare computational power may be further associated with the indication of the device that has the spare computational power.

FIG. 10 illustrates an example of storing the computational power in memory. The computational power may be stored in the form a table 1008. The table 1008 may identify a spare computational power and a device in the media playback system having the spare computational power. Further, the table may be ordered such that a first entry in the table identifies a device with a highest spare computational power in the media playback system and a last entry in the table identifies a device with a lowest spare computational power in the media playback system. In this regard, table 1008 indicates that device 5 has the highest spare computational power of 8 units and device 1 has the lowest spare computational power of 2 units. The units may represent a certain amount of available clock cycles for a processor. The table may store indications other than spare computational power as well so long as spare computational power may be determined from the stored indication.

At 910, processing tasks are assigned to the devices identified in the table determined at 908 so as to improve the signal to noise ratio of the processed audio signals. The processing tasks may be associated with a second set of audio processing algorithms, and may include one or more of a higher resolution echo cancellation, beamforming method, and/or subtraction of known signal method. The echo cancellation method and the subtraction of known signal methods may be higher resolution because a longer impulse response of the audio signal is processed as compared the signal measures processed with the first set of signal improvement algorithms. The processing over a longer impulse results in an improved identification and cancellation of echoes and noise. The beamforming may be higher resolution because the audio signal is processed in smaller angular intervals and/or over a greater number of directions. For example, the audio signal is processed at 5 degree intervals rather than 20 degree intervals for a 200 degree angular range rather than a 100 degree angular range. Other arrangements are also possible.

The processing tasks may be assigned to devices based on available spare processing power available in the media playback system. The echo cancellation and beamforming may require a certain computational power to be performed. Further, the computational power for performing echo cancellation may be less than that for performing beamforming to improve a signal to noise ratio. Accordingly, processing tasks may be assigned based on what spare computational power is available on a device (e.g., a threshold level) and the computational power needed for a processing task. For example, using table 1008, the processing tasks requiring the most computational power may be assigned to the device with highest available spare processing power, and then the processing task requiring the next most computational power may be assigned to the device with the next highest available spare processing power etc. As another example, processing tasks associated with only the echo cancellation algorithm may be assigned to all of the devices in the media playback system if the spare computational power across all device is low but enough to support echo cancellation. As yet another example, processing tasks associated with both the beamforming algorithm and echo cancellation may be assigned if the spare computational power across all device high and enough to support both algorithms. In yet another example, some devices may be assigned a processing task of echo cancellation and other devices may be assigned a processing task of beamforming depending on each individual spare processing power. Other arrangements are also possible.

In some embodiments, a total spare processing power available (e.g., sum of spare processing power for each device) may be less than what is needed to process all of the audio signals that are received by the devices in the media playback system with desired processing algorithms. In this situation, the processing tasks may be assigned based on goals as a result of the audio signal processing. For example, a decision may be made that a high signal to noise ratio is desired for the audio signals that are received from some of the devices. If a high signal to noise ratio is desired, then processing tasks such as both the beamforming algorithm and echo cancellation may be assigned to the one or more devices. On the other hand, a decision may be made that a lower signal to noise ratio is acceptable so that audio signals that are received from all or many of the devices are processed. If the lower signal to noise ratio is acceptable, then processing tasks that use low computational power such as only echo cancellation may be assigned to the one or more devices.

The processing tasks may be assigned until the spare computational resources is exhausted, or some threshold level of spare computational resources remain for a device or across all devices. Alternatively, the processing tasks may be assigned across the devices so that the spare computational power is reduced across all devices in proportion. Other arrangements are also possible.

At 912, certain of the audio signals identified by corresponding signal measures may be processed. The processing may be based on the processing tasks assigned to the devices to result in improved audio signals. For example, the audio signal for the device, microphone array, or direction of the microphone array that has the highest signal to noise ratio as defined by the table of signal to noise ratios may be assigned to the device with the highest spare processing power for processing. Then, the audio signal associated with the next highest signal to noise ratio may be assigned to the device with the next highest signal to noise ratio for processing until all desired audio signals are assigned to the devices associated with processing tasks. By assigning processing tasks in this manner, the overall performance of the media playback device does not degrade because the processing is performed based on spare processing power and not processing power which would otherwise be used to play back audio.

Other arrangements are also possible for assigning the audio signals to be processed. For instance, a user may specify that certain audio signals may be processed based on knowledge of a relationship between the audio source and microphone array. For instance, if it is known that the sonic input is received directly the microphone array, then the audio signal should be processed regardless of the actual signal to noise ratio of the audio signal. Similarly, if it is known, that if the sonic input is received indirectly by the microphone array, then the audio signal should not be processed further regardless of the signal to noise ratio of the audio signal.

The audio signals processed by each device result in an improved audio signal with a higher signal to noise ratio than what was determined by the first set of audio processing algorithms. The improved audio signal may also be weighted based on a confidence or likelihood that the improved audio signal accurately represents the sonic input. For example, the improved audio associated with a certain direction may be weighed more heavily than the improved audio associated with another direction if the likelihood is higher that the sonic input is coming from the certain directions. As another example, the improved audio signal of one device may be weighted heavier than the improved audio signals of another device if one device is closer to the sonic input than the other device. Other arrangements are also possible.

At 914, the improved audio signals (with or without weighing) may be combined to form a combined audio signal. By combining the improved audio signals, noise is cancelled resulting in a combined audio signal with a higher signal to noise ratio than any of the improved audio signals making up the combined audio signal. At 916, this combined audio signal may be then passed to a computing device such as a server. In the event that the audio signal has a voice input, the computing device may attempt to interpret the voice input to determine a function associated with the voice input.

Methods and the other process disclosed herein may include one or more operations, functions, or actions. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

IV. Conclusion

The description above discloses, among other things, various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. It is understood that such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of the firmware, hardware, and/or software aspects or components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.

Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of an invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.

When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible, non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware.

Claims

1. A media system comprising a first playback device and a second playback device, the media system comprising: the first playback device comprising: one or more microphones;a network interface;a processor;a non-transitory computer-readable medium;program instructions stored on the non-transitory computer-readable medium that, when executed by the processor, cause the first playback device to perform functions comprising: receiving an indication of an available amount of computational power of the second playback device; andbased on the received indication of the available amount of computational power of the second playback device, sending, to the second playback device, a set of audio signals received by the one or more microphones of the first playback device, wherein the set of audio signals includes at least one voice input;the second playback device comprising: a network interface;a processor;a non-transitory computer-readable medium;program instructions stored on the non-transitory computer-readable medium that, when executed by the processor, cause the second playback device to perform functions comprising: receiving, from the first playback device, the set of audio signals received by the one or more microphones of the first playback device;processing the set of audio signals using a first set of audio processing algorithms to determine a set of signal measures corresponding to the set of audio signals;based on the set of signal measures, identifying, from the set of audio signals, at least two audio signals that are to be re-processed using a second set of audio processing algorithms so as to improve the respective signal measures of the at least two audio signals;re-processing the at least two audio signals using the second set of audio processing algorithms;combining the re-processed at least two audio signals into a combined audio signal; andsending the combined audio signal to a network device.
2. The media system of claim 1, wherein the network device comprises a server, the server comprising: a network interface;a processor;a non-transitory computer-readable medium;program instructions stored on the non-transitory computer-readable medium that are executable by the processor to cause the server to perform functions comprising: determining the available amount of computational power of the second playback device; andsending, to the first playback device, the indication of the available amount of computational power of the second playback device.
3. The media system of claim 1, wherein the second playback device further comprises program instructions stored on the non-transitory computer-readable medium that are executable by the processor to cause the second playback device to perform functions comprising: determining the available amount of computational power of the second playback device; andsending, to the first playback device, the indication of the available amount of computational power of the second playback device.
4. The media system of claim 1, the second playback device further comprising one or more microphones.
5. The media system of claim 4, wherein at least a portion of the set of audio signals received by the one or more microphones of the first playback device is additionally received by the one or more microphones of the second playback device.
6. The media system of claim 1, the media system further comprising a third playback device, and wherein the first playback device further comprises program instructions stored on the non-transitory computer-readable medium that are executable by the processor to cause the first playback device to perform functions comprising: receiving an indication of an available amount of computational power of the third playback device;comparing the available amount of computational power of the second playback device with the available amount of computational power of the third playback device; andbased on comparing the available amount of computational power of the second playback device with the available amount of computational power of the third playback device, deciding to send the set of audio signals received by the one or more microphones of the first playback device to the second playback device.
7. The media system of claim 1, wherein each of the first set of audio processing algorithms and the second set of audio processing algorithms comprises at least one of an echo cancellation algorithm or a beamforming algorithm.
8. The media system of claim 1, wherein the first playback device further comprises program instructions stored on the non-transitory computer-readable medium that are executable by the processor to cause the first playback device to perform functions comprising: based on the received indication of the available amount of computational power of the second playback device, determining that the available amount of computational power of the second playback device is above a threshold amount of computational power.
9. The media system of claim 1, wherein the at least one voice input comprises at least one command, and wherein the network device comprises a server, the server comprising: a network interface;a processor;a non-transitory computer-readable medium;program instructions stored on the non-transitory computer-readable medium that are executable by the processor to cause the server to perform functions comprising: receiving the combined audio signal from the second playback device;based on the combined audio signal, recognizing the at least one command; andtransmitting an indication of the recognized at least one command to the first playback device.
10. The media system of claim 1, wherein the at least two audio signals comprise audio signals having signal to noise ratios meeting a threshold amount.
11. The media system of claim 1, wherein a resolution of the first set of audio processing algorithms is lower than a resolution of the second set of audio processing algorithms.
12. The media system of claim 1, wherein a signal measure of the combined audio signal is higher than a respective signal measure of any of the set of audio signals or any of the re-processed at least two audio signals.
13. The media system of claim 1, wherein the signal measure is a signal to noise ratio.
14. The media system of claim 1, wherein the network device is one of the first playback device or a server.
15. A method comprising: receiving, by a first playback device from a second playback device, an indication of an available amount of computational power of the second playback device; andbased on the received indication of the available amount of computational power of the second playback device, sending, from the first playback device to the second playback device, a set of audio signals received by one or more microphones of the first playback device wherein the set of audio signals includes at least one voice input;receiving, by the second playback device from the first playback device, the set of audio signals received by the one or more microphones of the first playback device;processing, by the second playback device, the set of audio signals using a first set of audio processing algorithms to determine a set of signal measures corresponding to the set of audio signals;based on the set of signal measures, identifying, by the second playback device from the set of audio signals, at least two audio signals that are to be re-processed using a second set of audio processing algorithms so as to improve the respective signal measures of the at least two audio signals;re-processing, by the second playback device, the at least two audio signals using the second set of audio processing algorithms;combining, by the second playback device, the re-processed at least two audio signals into a combined audio signal; andsending, by the second playback device, the combined audio signal to a network device.
16. The method of claim 15, wherein the network device is one of the first playback device or a server.
17. The method of claim 15, the second playback device further comprising one or more microphones.
18. The method of claim 15, further comprising: based on the received indication of the available amount of computational power of the second playback device, determining, by the first playback device, that the available amount of computational power of the second playback device is above a threshold amount of computational power.
19. The method of claim 15, wherein the at least two audio signals comprise audio signals having signal to noise ratios meeting a threshold amount.
20. The method of claim 15, wherein the signal measure is a signal to noise ratio.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to, and is a continuation of, U.S. Non-Provisional patent application Ser. No. 15/959,907, filed on Apr. 23, 2018, and titled “Dynamic Player Selection for Audio Signal Processing,” which is a continuation of U.S. Non-Provisional patent application Ser. No. 15/178,180, filed on Jun. 9, 2016, and titled “Dynamic Player Selection for Audio Signal Processing”, the contents of each of which is incorporated herein in its entirety.

US Referenced Citations (583)

Number	Name	Date	Kind
4741038	Elko et al.	Apr 1988	A
4941187	Slater	Jul 1990	A
5440644	Farinelli et al.	Aug 1995	A
5588065	Tanaka et al.	Dec 1996	A
5740260	Odom	Apr 1998	A
5761320	Farinelli et al.	Jun 1998	A
5923902	Inagaki	Jul 1999	A
5949414	Namikata et al.	Sep 1999	A
6032202	Lea et al.	Feb 2000	A
6088459	Hobelsberger	Jul 2000	A
6256554	DiLorenzo	Jul 2001	B1
6301603	Maher et al.	Oct 2001	B1
6311157	Strong	Oct 2001	B1
6404811	Cvetko et al.	Jun 2002	B1
6408078	Hobelsberger	Jun 2002	B1
6469633	Wachter et al.	Oct 2002	B1
6522886	Youngs et al.	Feb 2003	B1
6594347	Calder et al.	Jul 2003	B1
6594630	Zlokarnik et al.	Jul 2003	B1
6611537	Edens et al.	Aug 2003	B1
6611604	Irby et al.	Aug 2003	B1
6631410	Kowalski et al.	Oct 2003	B1
6757517	Chang et al.	Jun 2004	B2
6778869	Champion	Aug 2004	B2
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7236773	Thomas	Jun 2007	B2
7295548	Blank et al.	Nov 2007	B2
7391791	Balassanian et al.	Jun 2008	B2
7483538	McCarty et al.	Jan 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7630501	Blank et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7661107	Van Dyke et al.	Feb 2010	B1
7702508	Bennett	Apr 2010	B2
7792311	Holmgren et al.	Sep 2010	B1
7853341	McCarty et al.	Dec 2010	B2
7961892	Fedigan	Jun 2011	B2
7987294	Bryce et al.	Jul 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8032383	Bhardwaj et al.	Oct 2011	B1
8041565	Bhardwaj et al.	Oct 2011	B1
8045952	Qureshey et al.	Oct 2011	B2
8073125	Zhang et al.	Dec 2011	B2
8073681	Baldwin et al.	Dec 2011	B2
8103009	McCarty et al.	Jan 2012	B2
8136040	Fleming	Mar 2012	B2
8234395	Millington et al.	Jul 2012	B2
8239206	Lebeau et al.	Aug 2012	B1
8255224	Singleton et al.	Aug 2012	B2
8284982	Bailey	Oct 2012	B2
8290603	Lambourne	Oct 2012	B1
8340975	Rosenberger et al.	Dec 2012	B1
8364481	Strope et al.	Jan 2013	B2
8385557	Tashev et al.	Feb 2013	B2
8386261	Mellott et al.	Feb 2013	B2
8423893	Ramsay et al.	Apr 2013	B2
8428758	Naik et al.	Apr 2013	B2
8453058	Coccaro et al.	May 2013	B1
8473618	Spear et al.	Jun 2013	B2
8483853	Lambourne	Jul 2013	B1
8484025	Moreno et al.	Jul 2013	B1
8738925	Park et al.	May 2014	B1
8831761	Kemp et al.	Sep 2014	B2
8831957	Taubman et al.	Sep 2014	B2
8848879	Coughlan et al.	Sep 2014	B1
8874448	Kauffmann et al.	Oct 2014	B1
8938394	Faaborg et al.	Jan 2015	B1
8942252	Balassanian et al.	Jan 2015	B2
8983383	Haskin	Mar 2015	B1
8983844	Thomas et al.	Mar 2015	B1
9015049	Baldwin et al.	Apr 2015	B2
9042556	Kallai et al.	May 2015	B2
9060224	List	Jun 2015	B1
9094539	Noble	Jul 2015	B1
9215545	Dublin et al.	Dec 2015	B2
9251793	Lebeau et al.	Feb 2016	B2
9253572	Bedingfield, Sr. et al.	Feb 2016	B2
9262612	Cheyer	Feb 2016	B2
9275637	Salvador et al.	Mar 2016	B1
9288597	Carlsson et al.	Mar 2016	B2
9300266	Grokop	Mar 2016	B2
9304736	Whiteley et al.	Apr 2016	B1
9307321	Unruh	Apr 2016	B1
9318107	Sharifi	Apr 2016	B1
9319816	Narayanan	Apr 2016	B1
9324322	Torok et al.	Apr 2016	B1
9335819	Jaeger et al.	May 2016	B1
9361878	Boukadakis	Jun 2016	B2
9368105	Freed et al.	Jun 2016	B1
9374634	Macours	Jun 2016	B2
9386154	Baciu et al.	Jul 2016	B2
9401058	De La Fuente et al.	Jul 2016	B2
9412392	Lindahl et al.	Aug 2016	B2
9426567	Lee et al.	Aug 2016	B2
9431021	Scalise et al.	Aug 2016	B1
9443527	Watanabe et al.	Sep 2016	B1
9472201	Sleator	Oct 2016	B1
9472203	Ayrapetian et al.	Oct 2016	B1
9484030	Meaney et al.	Nov 2016	B1
9489948	Chu et al.	Nov 2016	B1
9494683	Sadek	Nov 2016	B1
9509269	Rosenberg	Nov 2016	B1
9510101	Polleros	Nov 2016	B1
9514476	Kay et al.	Dec 2016	B2
9514752	Sharifi	Dec 2016	B2
9516081	Tebbs et al.	Dec 2016	B2
9536541	Chen et al.	Jan 2017	B2
9548053	Basye et al.	Jan 2017	B1
9548066	Jain et al.	Jan 2017	B2
9552816	Vanlund et al.	Jan 2017	B2
9554210	Ayrapetian et al.	Jan 2017	B1
9560441	McDonough, Jr. et al.	Jan 2017	B1
9576591	Kim et al.	Feb 2017	B2
9601116	Casado et al.	Mar 2017	B2
9615170	Kirsch et al.	Apr 2017	B2
9615171	O'Neill et al.	Apr 2017	B1
9626695	Balasubramanian et al.	Apr 2017	B2
9632748	Faaborg et al.	Apr 2017	B2
9633186	Ingrassia, Jr. et al.	Apr 2017	B2
9633368	Greenzeiger et al.	Apr 2017	B2
9633660	Haughay et al.	Apr 2017	B2
9633671	Giacobello et al.	Apr 2017	B2
9633674	Sinha et al.	Apr 2017	B2
9640179	Hart et al.	May 2017	B1
9640183	Jung et al.	May 2017	B2
9641919	Poole et al.	May 2017	B1
9646614	Bellegarda et al.	May 2017	B2
9653060	Hilmes et al.	May 2017	B1
9653075	Chen et al.	May 2017	B1
9659555	Hilmes et al.	May 2017	B1
9672821	Krishnaswamy et al.	Jun 2017	B2
9674587	Triplett et al.	Jun 2017	B2
9685171	Yang	Jun 2017	B1
9691378	Meyers et al.	Jun 2017	B1
9691379	Mathias et al.	Jun 2017	B1
9697826	Sainath et al.	Jul 2017	B2
9697828	Prasad et al.	Jul 2017	B1
9698999	Mutagi et al.	Jul 2017	B2
9704478	Vitaladevuni et al.	Jul 2017	B1
9721566	Newendorp et al.	Aug 2017	B2
9721568	Polansky et al.	Aug 2017	B1
9721570	Beal et al.	Aug 2017	B1
9728188	Rosen et al.	Aug 2017	B1
9734822	Sundaram et al.	Aug 2017	B1
9743204	Welch et al.	Aug 2017	B1
9747011	Lewis et al.	Aug 2017	B2
9747899	Pogue et al.	Aug 2017	B2
9747920	Ayrapetian et al.	Aug 2017	B2
9747926	Sharifi et al.	Aug 2017	B2
9754605	Chhetri	Sep 2017	B1
9762967	Clarke et al.	Sep 2017	B2
9811314	Plagge et al.	Nov 2017	B2
9813810	Nongpiur	Nov 2017	B1
9813812	Berthelsen et al.	Nov 2017	B2
9820036	Tritschler et al.	Nov 2017	B1
9820039	Lang	Nov 2017	B2
9826306	Lang	Nov 2017	B2
9865259	Typrin et al.	Jan 2018	B1
9865264	Gelfenbeyn et al.	Jan 2018	B2
9881616	Beckley et al.	Jan 2018	B2
9900723	Choisel et al.	Feb 2018	B1
9916839	Scalise et al.	Mar 2018	B1
9947316	Millington et al.	Apr 2018	B2
9947333	David	Apr 2018	B1
9973849	Zhang et al.	May 2018	B1
10013995	Lashkari et al.	Jul 2018	B1
10026401	Mutagi et al.	Jul 2018	B1
10048930	Vega et al.	Aug 2018	B1
10051366	Buoni et al.	Aug 2018	B1
10051600	Zhong et al.	Aug 2018	B1
10079015	Lockhart et al.	Sep 2018	B1
10134399	Lang et al.	Nov 2018	B2
10136204	Poole et al.	Nov 2018	B1
10152969	Reilly et al.	Dec 2018	B2
10224056	Torok et al.	Mar 2019	B1
10276161	Hughes et al.	Apr 2019	B2
10297256	Reilly et al.	May 2019	B2
10339917	Aleksic et al.	Jul 2019	B2
10346122	Morgan	Jul 2019	B1
10354650	Gruenstein et al.	Jul 2019	B2
10366688	Gunn et al.	Jul 2019	B2
10381001	Gunn et al.	Aug 2019	B2
10381002	Gunn et al.	Aug 2019	B2
10381003	Wakisaka et al.	Aug 2019	B2
20010042107	Palm	Nov 2001	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020034280	Infosino	Mar 2002	A1
20020072816	Shdema et al.	Jun 2002	A1
20020116196	Tran	Aug 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20030038848	Lee et al.	Feb 2003	A1
20030040908	Yang et al.	Feb 2003	A1
20030070869	Hlibowicki	Apr 2003	A1
20030072462	Hlibowicki	Apr 2003	A1
20030095672	Hobelsberger	May 2003	A1
20030157951	Hasty	Aug 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040093219	Shin et al.	May 2004	A1
20040127241	Shostak	Jul 2004	A1
20040128135	Anastasakos et al.	Jul 2004	A1
20050031131	Browning et al.	Feb 2005	A1
20050031132	Browning et al.	Feb 2005	A1
20050031133	Browning et al.	Feb 2005	A1
20050031134	Leske	Feb 2005	A1
20050031137	Browning et al.	Feb 2005	A1
20050031138	Browning et al.	Feb 2005	A1
20050031139	Browning et al.	Feb 2005	A1
20050031140	Browning	Feb 2005	A1
20050047606	Lee et al.	Mar 2005	A1
20050077843	Benditt	Apr 2005	A1
20050164664	Difonzo et al.	Jul 2005	A1
20050195988	Tashev et al.	Sep 2005	A1
20050201254	Looney et al.	Sep 2005	A1
20050207584	Bright	Sep 2005	A1
20050268234	Rossi, Jr. et al.	Dec 2005	A1
20050283330	Laraia et al.	Dec 2005	A1
20060004834	Pyhalammi et al.	Jan 2006	A1
20060023945	King et al.	Feb 2006	A1
20060104451	Browning et al.	May 2006	A1
20060147058	Wang	Jul 2006	A1
20060190269	Tessel et al.	Aug 2006	A1
20060190968	Jung et al.	Aug 2006	A1
20060247913	Huerta et al.	Nov 2006	A1
20060262943	Oxford	Nov 2006	A1
20070018844	Sutardja	Jan 2007	A1
20070019815	Asada et al.	Jan 2007	A1
20070033043	Hyakumoto	Feb 2007	A1
20070071255	Schobben	Mar 2007	A1
20070076131	Li et al.	Apr 2007	A1
20070076906	Takagi et al.	Apr 2007	A1
20070140058	McIntosh et al.	Jun 2007	A1
20070140521	Mitobe et al.	Jun 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20070147651	Mitobe et al.	Jun 2007	A1
20080037814	Shau	Feb 2008	A1
20080090537	Sutardja	Apr 2008	A1
20080146289	Korneluk et al.	Jun 2008	A1
20080208594	Cross et al.	Aug 2008	A1
20080221897	Cerra et al.	Sep 2008	A1
20080247530	Barton et al.	Oct 2008	A1
20080248797	Freeman et al.	Oct 2008	A1
20080291896	Tuubel et al.	Nov 2008	A1
20080301729	Broos et al.	Dec 2008	A1
20090003620	McKillop et al.	Jan 2009	A1
20090005893	Sugii et al.	Jan 2009	A1
20090010445	Matsuo et al.	Jan 2009	A1
20090018828	Nakadai et al.	Jan 2009	A1
20090052688	Ishibashi et al.	Feb 2009	A1
20090076821	Brenner et al.	Mar 2009	A1
20090153289	Hope et al.	Jun 2009	A1
20090197524	Haff et al.	Aug 2009	A1
20090220107	Every et al.	Sep 2009	A1
20090228919	Zott et al.	Sep 2009	A1
20090238377	Ramakrishnan et al.	Sep 2009	A1
20090248397	Garcia et al.	Oct 2009	A1
20090264072	Dai	Oct 2009	A1
20090323907	Gupta et al.	Dec 2009	A1
20090326949	Douthitt et al.	Dec 2009	A1
20100014690	Wolff et al.	Jan 2010	A1
20100023638	Bowman	Jan 2010	A1
20100035593	Franco et al.	Feb 2010	A1
20100070922	Demaio et al.	Mar 2010	A1
20100075723	Min et al.	Mar 2010	A1
20100092004	Kuze	Apr 2010	A1
20100172516	Lastrucci	Jul 2010	A1
20100178873	Lee et al.	Jul 2010	A1
20100179874	Higgins et al.	Jul 2010	A1
20100185448	Meisel	Jul 2010	A1
20100211199	Naik et al.	Aug 2010	A1
20110033059	Bhaskar et al.	Feb 2011	A1
20110035580	Wang et al.	Feb 2011	A1
20110044461	Kuech et al.	Feb 2011	A1
20110044489	Saiki et al.	Feb 2011	A1
20110066634	Phillips et al.	Mar 2011	A1
20110091055	Leblanc	Apr 2011	A1
20110103615	Sun	May 2011	A1
20110145581	Malhotra et al.	Jun 2011	A1
20110170707	Yamada et al.	Jul 2011	A1
20110182436	Murgia et al.	Jul 2011	A1
20110267985	Wilkinson et al.	Nov 2011	A1
20110276333	Wang et al.	Nov 2011	A1
20110280422	Neumeyer et al.	Nov 2011	A1
20110289506	Trivi et al.	Nov 2011	A1
20110299706	Sakai	Dec 2011	A1
20120020486	Fried et al.	Jan 2012	A1
20120022863	Cho et al.	Jan 2012	A1
20120022864	Leman et al.	Jan 2012	A1
20120078635	Rothkopf et al.	Mar 2012	A1
20120123268	Tanaka et al.	May 2012	A1
20120128160	Kim et al.	May 2012	A1
20120131125	Seidel et al.	May 2012	A1
20120148075	Goh et al.	Jun 2012	A1
20120163603	Abe et al.	Jun 2012	A1
20120177215	Bose et al.	Jul 2012	A1
20120297284	Matthews, III et al.	Nov 2012	A1
20120308044	Vander Mey et al.	Dec 2012	A1
20120308046	Muza	Dec 2012	A1
20130006453	Wang et al.	Jan 2013	A1
20130024018	Chang et al.	Jan 2013	A1
20130034241	Pandey et al.	Feb 2013	A1
20130039527	Jensen et al.	Feb 2013	A1
20130058492	Silzle et al.	Mar 2013	A1
20130066453	Seefeldt	Mar 2013	A1
20130080146	Kato et al.	Mar 2013	A1
20130124211	McDonough	May 2013	A1
20130148821	Sorensen	Jun 2013	A1
20130179173	Lee et al.	Jul 2013	A1
20130183944	Mozer et al.	Jul 2013	A1
20130191119	Sugiyama	Jul 2013	A1
20130191122	Mason	Jul 2013	A1
20130198298	Li et al.	Aug 2013	A1
20130216056	Thyssen	Aug 2013	A1
20130315420	You	Nov 2013	A1
20130317635	Bates et al.	Nov 2013	A1
20130322665	Bennett et al.	Dec 2013	A1
20130324031	Loureiro	Dec 2013	A1
20130329896	Krishnaswamy et al.	Dec 2013	A1
20130331970	Beckhardt et al.	Dec 2013	A1
20130332165	Beckley et al.	Dec 2013	A1
20130339028	Rosner et al.	Dec 2013	A1
20140003611	Mohammad et al.	Jan 2014	A1
20140003625	Sheen et al.	Jan 2014	A1
20140003635	Mohammad et al.	Jan 2014	A1
20140006026	Lamb et al.	Jan 2014	A1
20140034929	Hamada et al.	Feb 2014	A1
20140046464	Reimann	Feb 2014	A1
20140064501	Olsen et al.	Mar 2014	A1
20140075306	Rega	Mar 2014	A1
20140075311	Boettcher et al.	Mar 2014	A1
20140094151	Klappert et al.	Apr 2014	A1
20140100854	Chen et al.	Apr 2014	A1
20140122075	Bak et al.	May 2014	A1
20140136195	Abdossalami et al.	May 2014	A1
20140145168	Ohsawa et al.	May 2014	A1
20140146983	Kim et al.	May 2014	A1
20140163978	Basye et al.	Jun 2014	A1
20140164400	Kruglick	Jun 2014	A1
20140167931	Lee et al.	Jun 2014	A1
20140168344	Shoemake et al.	Jun 2014	A1
20140172953	Blanksteen	Jun 2014	A1
20140195252	Gruber et al.	Jul 2014	A1
20140219472	Huang et al.	Aug 2014	A1
20140222436	Binder et al.	Aug 2014	A1
20140244013	Reilly	Aug 2014	A1
20140244712	Walters et al.	Aug 2014	A1
20140249817	Hart et al.	Sep 2014	A1
20140252386	Ito et al.	Sep 2014	A1
20140254805	Su et al.	Sep 2014	A1
20140258292	Thramann et al.	Sep 2014	A1
20140259075	Chang et al.	Sep 2014	A1
20140270282	Tammi et al.	Sep 2014	A1
20140274185	Luna et al.	Sep 2014	A1
20140274203	Ganong, III et al.	Sep 2014	A1
20140274218	Kadiwala et al.	Sep 2014	A1
20140277650	Zurek et al.	Sep 2014	A1
20140291642	Watabe et al.	Oct 2014	A1
20140310002	Nitz et al.	Oct 2014	A1
20140310614	Jones	Oct 2014	A1
20140340888	Ishisone et al.	Nov 2014	A1
20140357248	Tonshal et al.	Dec 2014	A1
20140363022	Dizon et al.	Dec 2014	A1
20140363024	Apodaca	Dec 2014	A1
20140365227	Cash et al.	Dec 2014	A1
20140369491	Kloberdans et al.	Dec 2014	A1
20140372109	Iyer et al.	Dec 2014	A1
20150006176	Pogue et al.	Jan 2015	A1
20150006184	Marti et al.	Jan 2015	A1
20150010169	Popova et al.	Jan 2015	A1
20150014680	Yamazaki et al.	Jan 2015	A1
20150016642	Walsh et al.	Jan 2015	A1
20150019201	Schoenbach	Jan 2015	A1
20150036831	Klippel	Feb 2015	A1
20150063580	Huang et al.	Mar 2015	A1
20150086034	Lombardi et al.	Mar 2015	A1
20150091709	Reichert et al.	Apr 2015	A1
20150092947	Gossain et al.	Apr 2015	A1
20150104037	Lee et al.	Apr 2015	A1
20150106085	Lindahl	Apr 2015	A1
20150110294	Chen et al.	Apr 2015	A1
20150112672	Giacobello et al.	Apr 2015	A1
20150128065	Torii et al.	May 2015	A1
20150154976	Mutagi	Jun 2015	A1
20150169279	Duga	Jun 2015	A1
20150170645	Di Censo et al.	Jun 2015	A1
20150180432	Gao et al.	Jun 2015	A1
20150181318	Gautama et al.	Jun 2015	A1
20150189438	Hampiholi et al.	Jul 2015	A1
20150200454	Heusdens et al.	Jul 2015	A1
20150221678	Yamazaki et al.	Aug 2015	A1
20150222563	Burns et al.	Aug 2015	A1
20150222987	Angel, Jr. et al.	Aug 2015	A1
20150228274	Leppänen et al.	Aug 2015	A1
20150228803	Koezuka et al.	Aug 2015	A1
20150237406	Ochoa et al.	Aug 2015	A1
20150245152	Ding et al.	Aug 2015	A1
20150249889	Iyer et al.	Sep 2015	A1
20150253292	Larkin et al.	Sep 2015	A1
20150253960	Lin et al.	Sep 2015	A1
20150263174	Yamazaki et al.	Sep 2015	A1
20150271593	Sun et al.	Sep 2015	A1
20150277846	Yen et al.	Oct 2015	A1
20150280676	Holman et al.	Oct 2015	A1
20150296299	Klippel et al.	Oct 2015	A1
20150302856	Kim et al.	Oct 2015	A1
20150319529	Klippel	Nov 2015	A1
20150325267	Lee et al.	Nov 2015	A1
20150334471	Innes et al.	Nov 2015	A1
20150338917	Steiner et al.	Nov 2015	A1
20150341406	Rockefeller et al.	Nov 2015	A1
20150346845	Di Censo et al.	Dec 2015	A1
20150348551	Gruber et al.	Dec 2015	A1
20150363061	De Nigris, III et al.	Dec 2015	A1
20150363401	Chen et al.	Dec 2015	A1
20150371657	Gao et al.	Dec 2015	A1
20150371664	Bar-Or et al.	Dec 2015	A1
20150380010	Srinivasan et al.	Dec 2015	A1
20160007116	Holman	Jan 2016	A1
20160021458	Johnson et al.	Jan 2016	A1
20160026428	Morganstern et al.	Jan 2016	A1
20160029142	Isaac et al.	Jan 2016	A1
20160035321	Cho et al.	Feb 2016	A1
20160036962	Rand et al.	Feb 2016	A1
20160042748	Jain et al.	Feb 2016	A1
20160044151	Shoemaker et al.	Feb 2016	A1
20160050488	Matheja et al.	Feb 2016	A1
20160057522	Choisel et al.	Feb 2016	A1
20160077710	Lewis et al.	Mar 2016	A1
20160088036	Corbin et al.	Mar 2016	A1
20160088392	Huttunen et al.	Mar 2016	A1
20160093304	Kim et al.	Mar 2016	A1
20160094917	Wilk et al.	Mar 2016	A1
20160098393	Hebert	Apr 2016	A1
20160098992	Renard et al.	Apr 2016	A1
20160103653	Jang	Apr 2016	A1
20160104480	Sharifi	Apr 2016	A1
20160111110	Gautama et al.	Apr 2016	A1
20160127780	Roberts et al.	May 2016	A1
20160133259	Rubin et al.	May 2016	A1
20160134982	Iyer	May 2016	A1
20160155442	Kannan et al.	Jun 2016	A1
20160155443	Khan et al.	Jun 2016	A1
20160157035	Russell et al.	Jun 2016	A1
20160162469	Santos	Jun 2016	A1
20160173578	Sharma et al.	Jun 2016	A1
20160173983	Berthelsen et al.	Jun 2016	A1
20160180853	Vanlund et al.	Jun 2016	A1
20160189716	Lindahl et al.	Jun 2016	A1
20160196499	Khan et al.	Jul 2016	A1
20160203331	Khan et al.	Jul 2016	A1
20160212538	Fullam et al.	Jul 2016	A1
20160216938	Millington	Jul 2016	A1
20160225385	Hammarqvist	Aug 2016	A1
20160232451	Scherzer	Aug 2016	A1
20160234204	Rishi et al.	Aug 2016	A1
20160239255	Chavez et al.	Aug 2016	A1
20160253050	Mishra et al.	Sep 2016	A1
20160260431	Newendorp et al.	Sep 2016	A1
20160302018	Russell et al.	Oct 2016	A1
20160314782	Klimanis	Oct 2016	A1
20160336519	Seo et al.	Nov 2016	A1
20160343866	Koezuka et al.	Nov 2016	A1
20160343949	Seo et al.	Nov 2016	A1
20160343954	Seo et al.	Nov 2016	A1
20160345114	Hanna et al.	Nov 2016	A1
20160352915	Gautama	Dec 2016	A1
20160353218	Starobin et al.	Dec 2016	A1
20160357503	Triplett et al.	Dec 2016	A1
20160366515	Mendes et al.	Dec 2016	A1
20160372688	Seo et al.	Dec 2016	A1
20160373269	Okubo et al.	Dec 2016	A1
20160373909	Rasmussen et al.	Dec 2016	A1
20160379634	Yamamoto et al.	Dec 2016	A1
20170003931	Dvortsov et al.	Jan 2017	A1
20170012207	Seo et al.	Jan 2017	A1
20170012232	Kataishi et al.	Jan 2017	A1
20170019732	Mendes et al.	Jan 2017	A1
20170025615	Seo et al.	Jan 2017	A1
20170025630	Seo et al.	Jan 2017	A1
20170026769	Patel	Jan 2017	A1
20170039025	Kielak	Feb 2017	A1
20170060526	Barton et al.	Mar 2017	A1
20170062734	Suzuki et al.	Mar 2017	A1
20170070478	Park et al.	Mar 2017	A1
20170076720	Gopalan et al.	Mar 2017	A1
20170078824	Heo	Mar 2017	A1
20170083285	Meyers et al.	Mar 2017	A1
20170084292	Yoo	Mar 2017	A1
20170084295	Tsiartas et al.	Mar 2017	A1
20170090864	Jorgovanovic	Mar 2017	A1
20170092278	Evermann et al.	Mar 2017	A1
20170092297	Sainath et al.	Mar 2017	A1
20170092299	Matsuo	Mar 2017	A1
20170092889	Seo et al.	Mar 2017	A1
20170092890	Seo et al.	Mar 2017	A1
20170103754	Higbie et al.	Apr 2017	A1
20170103755	Jeon et al.	Apr 2017	A1
20170110124	Boesen et al.	Apr 2017	A1
20170110144	Sharifi et al.	Apr 2017	A1
20170117497	Seo et al.	Apr 2017	A1
20170123251	Nakada et al.	May 2017	A1
20170125037	Shin	May 2017	A1
20170125456	Kasahara	May 2017	A1
20170134872	Silva et al.	May 2017	A1
20170139720	Stein	May 2017	A1
20170140748	Roberts et al.	May 2017	A1
20170140759	Kumar et al.	May 2017	A1
20170177585	Rodger et al.	Jun 2017	A1
20170178662	Ayrapetian et al.	Jun 2017	A1
20170180561	Kadiwala et al.	Jun 2017	A1
20170188150	Brunet et al.	Jun 2017	A1
20170193999	Aleksic et al.	Jul 2017	A1
20170206896	Ko et al.	Jul 2017	A1
20170206900	Lee et al.	Jul 2017	A1
20170214996	Yeo	Jul 2017	A1
20170236512	Williams et al.	Aug 2017	A1
20170236515	Pinsky et al.	Aug 2017	A1
20170242649	Jarvis et al.	Aug 2017	A1
20170242651	Lang et al.	Aug 2017	A1
20170242653	Lang et al.	Aug 2017	A1
20170242657	Jarvis et al.	Aug 2017	A1
20170243587	Plagge et al.	Aug 2017	A1
20170245076	Kusano et al.	Aug 2017	A1
20170257686	Gautama et al.	Sep 2017	A1
20170270919	Parthasarathi et al.	Sep 2017	A1
20170287485	Civelli et al.	Oct 2017	A1
20170332168	Moghimi	Nov 2017	A1
20170353789	Kim et al.	Dec 2017	A1
20170357478	Piersol et al.	Dec 2017	A1
20170366393	Shaker et al.	Dec 2017	A1
20180025733	Qian et al.	Jan 2018	A1
20180033428	Kim et al.	Feb 2018	A1
20180040324	Wilberding	Feb 2018	A1
20180047394	Tian et al.	Feb 2018	A1
20180053504	Wang et al.	Feb 2018	A1
20180054506	Hart et al.	Feb 2018	A1
20180062871	Jones et al.	Mar 2018	A1
20180084367	Greff et al.	Mar 2018	A1
20180091898	Yoon et al.	Mar 2018	A1
20180091913	Hartung et al.	Mar 2018	A1
20180096683	James et al.	Apr 2018	A1
20180096696	Mixter	Apr 2018	A1
20180122378	Mixter et al.	May 2018	A1
20180130469	Gruenstein et al.	May 2018	A1
20180132298	Birnam et al.	May 2018	A1
20180137861	Ogawa et al.	May 2018	A1
20180165055	Yu et al.	Jun 2018	A1
20180167981	Jonna et al.	Jun 2018	A1
20180190285	Heckmann et al.	Jul 2018	A1
20180199146	Sheen	Jul 2018	A1
20180210698	Park et al.	Jul 2018	A1
20180219976	Decenzo et al.	Aug 2018	A1
20180228006	Baker et al.	Aug 2018	A1
20180233136	Torok et al.	Aug 2018	A1
20180233137	Torok et al.	Aug 2018	A1
20180262793	Lau et al.	Sep 2018	A1
20180277113	Hartung et al.	Sep 2018	A1
20180293484	Wang et al.	Oct 2018	A1
20180335903	Coffman et al.	Nov 2018	A1
20180367944	Heo et al.	Dec 2018	A1
20190013019	Lawrence	Jan 2019	A1
20190033446	Bultan et al.	Jan 2019	A1
20190043492	Lang	Feb 2019	A1
20190074025	Lashkari et al.	Mar 2019	A1
20190079721	Vega et al.	Mar 2019	A1
20190081507	Ide	Mar 2019	A1
20190088261	Lang et al.	Mar 2019	A1
20190090056	Rexach et al.	Mar 2019	A1
20190098400	Buoni et al.	Mar 2019	A1
20190104373	Wodrich et al.	Apr 2019	A1
20190108839	Reilly et al.	Apr 2019	A1
20190130906	Kobayashi et al.	May 2019	A1
20190172452	Smith et al.	Jun 2019	A1
20190173687	Mackay et al.	Jun 2019	A1
20190179607	Thangarathnam et al.	Jun 2019	A1
20190220246	Orr et al.	Jul 2019	A1
20190237067	Friedman et al.	Aug 2019	A1
20190295563	Kamdar et al.	Sep 2019	A1
20190304443	Bhagwan	Oct 2019	A1
20190311710	Eraslan et al.	Oct 2019	A1

Foreign Referenced Citations (42)

Number	Date	Country
2017100486	Jun 2017	AU
2017100581	Jun 2017	AU
101661753	Mar 2010	CN
102256098	Nov 2011	CN
103181192	Jun 2013	CN
103546616	Jan 2014	CN
104010251	Aug 2014	CN
104053088	Sep 2014	CN
104092936	Oct 2014	CN
105284076	Jan 2016	CN
107919123	Apr 2018	CN
1349146	Oct 2003	EP
1389853	Feb 2004	EP
2683147	Jan 2014	EP
2351021	Sep 2017	EP
3285502	Feb 2018	EP
2001236093	Aug 2001	JP
2003223188	Aug 2003	JP
2004347943	Dec 2004	JP
2004354721	Dec 2004	JP
2005284492	Oct 2005	JP
2007013400	Jan 2007	JP
2007142595	Jun 2007	JP
2008079256	Apr 2008	JP
2008158868	Jul 2008	JP
2010141748	Jun 2010	JP
2013037148	Feb 2013	JP
2014071138	Apr 2014	JP
2014137590	Jul 2014	JP
2015161551	Sep 2015	JP
20100111071	Oct 2010	KR
200153994	Jul 2001	WO
2003093950	Nov 2003	WO
2015037396	Mar 2015	WO
2015178950	Nov 2015	WO
2016014142	Jan 2016	WO
2016022926	Feb 2016	WO
2016033364	Mar 2016	WO
2016057268	Apr 2016	WO
2017039632	Mar 2017	WO
2018027142	Feb 2018	WO
2018067404	Apr 2018	WO

Non-Patent Literature Citations (237)

Entry
US 9,299,346 B1, 03/2016, Hart et al. (withdrawn)
Australian Patent Office, Australian Examination Report Action dated Oct. 3, 2019, issued in connection with Australian Application No. 2018230932, 3 pages.
Chinese Patent Office, First Office Action and Translation dated Nov. 5, 2019, issued in connection with Chinese Application No. 201780072651.3, 19 pages.
Chinese Patent Office, Second Office Action and Translation dated Sep. 23, 2019, issued in connection with Chinese Application No. 201780025028.2, 15 pages.
Chinese Patent Office, Third Office Action and Translation dated Sep. 16, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
European Patent Office, European Office Action dated Jan. 14, 2020, issued in connection with European Application No. 17757070.2, 7 pages.
European Patent Office, European Office Action dated Aug. 30, 2019, issued in connection with European Application No. 17781608.9, 6 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Dec. 20, 2019, issued in connection with European Application No. 17174435.2, 13 pages.
Final Office Action dated Dec. 11. 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 10 pages.
Final Office Action dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1. 2018, 13 pages.
First Action Interview Office Action dated Jan. 22, 2020, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 3 pages.
International Bureau, International Search Report and Written Opinion dated Nov. 18, 2019, issued in connection with International Application No. PCT/US2019052841, filed on Sep. 25, 2019, 12 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 20, 2019, issued in connection with International Application No. PCT/US2019052654, filed on Sep. 24, 2019, 11 pages.
International Bureau, International Search Report and Written Opinion dated Dec. 6, 2019, issued in connection with International Application No. PCT/US2019050852, filed on Sep. 12, 2019, 10 pages.
Japanese Patent Office, Non-Final Office Action and Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 6 pages.
Japanese Patent Office, Office Action and Translation dated Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 5 pages.
Japanese Patent Office, Office Action Translation dated Nov. 5, 2019, issued in connection with Japanese Patent Application No. 2019-517281, 2 pages.
Japanese Patent Office, Office Action Translation dated Oct. 8, 2019, issued in connection with Japanese Patent Application No. 2019-521032, 8 pages.
Korean Patent Office, Korean Office Action and Translation dated Sep. 9, 2019, issued in connection with Korean Application No. 10-2018-7027451, 21 pages.
Non-Final Office Action dated Nov. 4, 2019, issued in connection with U.S. Appl. No. 16/022,662, filed Jun. 28, 2018, 16 pages.
Non-Final Office Action dated Sep. 5, 2019, issued in connection with U.S. Appl. No. 16/416,752, filed May 20, 2019, 14 pages.
Non-Final Office Action dated Oct. 9, 2019, issued in connection with U.S. Appl. No. 15/936,177, filed Mar. 26, 2018, 16 pages.
Non-Final Office Action dated Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/177,185, filed Oct. 31, 2018, 14 pages.
Non-Final Office Action dated Nov. 13, 2019, issued in connection with U.S. Appl. No. 15/984,073, filed May 18, 2018, 18 pages.
Non-Final Office Action dated Nov. 15, 2019, issued in connection with U.S. Appl. No. 16/153,530, filed Oct. 5, 2018, 17 pages.
Non-Final Office Action dated Oct. 18, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 27 pages.
Non-Final Office Action dated Sep. 18, 2019, issued in connection with U.S. Appl. No. 16/179,779, filed Nov. 2, 2018, 14 pages.
Non-Final Office Action dated Dec. 19, 2019, issued in connection with U.S. Appl. No. 16/147,710, filed Sep. 29, 2018, 10 pages.
Non-Final Office Action dated Jun. 20, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 10 pages.
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 9 pages.
Non-Final Office Action dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/598,125, filed Oct. 10, 2019, 25 pages.
Non-Final Office Action dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/973,413, filed May 7, 2018, 10 pages.
Non-Final Office Action dated Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/145,275, filed Sep. 28, 2018, 11 pages.
Notice of Allowance dated Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 15 pages.
Notice of Allowance dated Oct. 11, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 9 pages.
Notice of Allowance dated Sep. 11, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 5 pages.
Notice of Allowance dated Jan. 13, 2020, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 6 pages.
Notice of Allowance dated Jan. 15, 2020, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 9 pages.
Notice of Allowance dated Oct. 15, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 9 pages.
Notice of Allowance dated Dec. 18, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 13 pages.
Notice of Allowance dated Jan. 21, 2020, issued in connection with U.S. Appl. No. 16/672,764, filed Nov. 4, 2019, 10 pages.
Notice of Allowance dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 15/946,585, filed Apr. 5, 2018, 5 pages.
Notice of Allowance dated Oct. 30, 2019, issued in connection with U.S. Appl. No. 16/131,392, filed Sep. 14, 2018, 9 pages.
Optimizing Siri on HomePod in Far-Field Settings. Audio Software Engineering and Siri Speech Team, Machine Learning Journal vol. 1, Issue 12. https://machinelearning.apple.com/2018/12/03/optimizing-siri-on-homepod-in-far-field-settings.html. Dec. 2018, 18 pages.
Preinterview First Office Action dated Sep. 30, 2019, issued in connection with U.S. Appl. No. 15/989,715, filed May 25, 2018, 4 pages.
Anonymous,. S Voice or Google Now—The Lowdown. Apr. 28, 2015, 9 pages. [online], [retrieved on Nov. 29, 2017]. Retrieved from the Internet <URL:http://web.archive.org/web/20160807040123/http://lowdown.carphonewarehouse.com/news/s-voice-or-google-now/29958/.
Cipriani,. The complete list of ‘OK, Google’ commands—CNET. Jul. 1, 2016, 5 pages. [online], [retrieved on Jan. 15, 2020]. Retrieved from the Internet: <URL:https://web.archive.org/web/20160803230926/https://www.cnet.com/how-to/complete-list-of-ok-google--commands/.
European Patent Office, European Extended Search Report dated Feb. 3, 2020, issued in connection with European Application No. 19197116.7, 9 pages.
Final Office Action dated Feb. 7, 2020, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 8 pages.
Notice of Allowance dated Feb. 5, 2020, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 9 pages.
Notice of Allowance dated Feb. 6, 2020, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 7 pages.
International Searching Authority, International Search Report and Written Opinion dated Jan. 23, 2018, issued in connection with International Application No. PCT/US2017/57220, filed on Oct. 18, 2017, 8 pages.
International Searching Authority, International Search Report and Written Opinion dated May 23, 2017, issued in connection with International Application No. PCT/US2017/018739, Filed on Feb. 21, 2017, 10 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 23, 2017, issued in connection with International Application No. PCT/US2017/042170, filed on Jul. 14, 2017, 15 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2017/042227, filed on Jul. 14, 2017, 16 pages.
International Searching Authority, International Search Report and Written Opinion dated May 30, 2017, issued in connection with International Application No. PCT/US2017/018728, Filed on Feb. 21, 2017, 11 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 retrieved Jun. 18, 2014, 2 pages.
Jose Alvarez and Mathieu Salzmann “Compression-aware Training of Deep Networks” 31st Conference on Neural Information Processing Systems, Nov. 13, 2017, 12pages.
Korean Patent Office, Korean Office Action and Translation dated Aug. 16, 2019, issued in connection with Korean Application No. 10-2018-7027452, 14 pages.
Korean Patent Office, Korean Office Action dated May 8, 2019, issued in connection with Korean Application No. 10-2018-7027451, 7 pages.
Korean Patent Office, Korean Office Action dated May 8, 2019, issued in connection with Korean Application No. 10-2018-7027452, 5 pages.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Maja Taseska and Emanual A.P. Habets, “MMSE-Based Blind Source Extraction in Diffuse Noise Fields Using a Complex Coherence-Based a Priori Sap Estimator.” International Workshop on Acoustic Signal Enhancement 2012, Sep. 4-6, 2012, 4pages.
Morales-Cordovilla et al. “Room Localization for Distant Speech Recognition,” Proceedings of Interspeech 2014, Sep. 14, 2014, 4 pages.
Newman, Jared. “Chromecast Audio's multi-room support has arrived,” Dec. 11, 2015, https://www.pcworld.com/article/3014204/customer-electronic/chromcase-audio-s-multi-room-support-has . . . , 1 page.
Ngo et al. “Incorporating the Conditional Speech Presence Probability in Multi-Channel Wiener Filter Based Noise in Hearing Aids.” EURASIP Journal on Advances in Signal Processing vol. 2009, Jun. 2, 2009, 11 pages.
Non-Final Office Action dated Jul. 1, 2016, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Non-Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 11 pages.
Non-Final Office Action dated Nov. 3, 2017, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 11 pages.
Non-Final Office Action dated Feb. 7, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Feb. 8, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 17 pages.
Non-Final Office Action dated Mar. 9, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 13 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 13 pages.
Non-Final Office Action dated Jan. 10, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 15 pages.
Non-Final Office Action dated Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 17 pages.
Non-Final Office Action dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Feb. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 13 pages.
Non-Final Office Action dated Jan. 13, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 11 pages.
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 23 pages.
Non-Final Office Action dated Nov. 13, 2018, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 8 pages.
Non-Final Office Action dated Sep. 14, 2017, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 16 pages.
Non-Final Office Action dated Sep. 14, 2018, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 15 pages.
Non-Final Office Action dated Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 6 pages.
Non-Final Office Action dated Mar. 16, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 5 pages.
Non-Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 16 pages.
Non-Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 14 pages.
Non-Final Office Action dated Jan. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 18 pages.
Non-Final Office Action dated Apr. 19, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 12 pages.
Non-Final Office Action dated Feb. 20, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2016, 31 pages.
Non-Final Office Action dated Aug. 21, 2019, issued in connection with U.S. Appl. No. 16/192,126, filed Nov. 15, 2018, 8 pages.
Non-Final Office Action dated Feb. 21, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 12 pages.
Non-Final Office Action dated May 22, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 19 pages.
Non-Final Office Action dated May 23, 2019, issued in connection with U.S. Appl. No. 16/154,071, filed Oct. 8, 2018, 36 pages.
Non-Final Office Action dated Aug. 24, 2017, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 13 pages.
Non-Final Office Action dated Jul. 24, 2019, issued in connection with U.S. Appl. No. 16/439,009, filed Jun. 12, 2019, 26 pages.
Non-Final Office Action dated Jul. 25, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Jul. 22, 2016, 11 pages.
Non-Final Office Action dated Dec. 26, 2018, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 8, 2018, 7 pages.
Non-Final Office Action dated Jan. 26, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 16 pages.
Non-Final Office Action dated Oct. 26, 2017, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 12 pages.
Notice of Allowance dated Mar. 27, 2019, issued in connection with U.S. Appl. No. 16/214,666, filed Dec. 10, 2018, 6 pages.
Notice of Allowance dated Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/699,982, filed Sep. 8, 2017, 17 pages.
Notice of Allowance dated Dec. 29, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 13 pages.
Notice of Allowance dated Apr. 3, 2019, issued in connection with U.S. Appl. No. 16/160,107, filed Oct. 15, 2018, 7 pages.
Notice of Allowance dated Jul. 30, 2018, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 5 pages.
Notice of Allowance dated Jul. 30, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 9 pages.
Notice of Allowance dated Nov. 30, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 5 pages.
Notice of Allowance dated May 31, 2019, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 9 pages.
Notice of Allowance dated Oct. 5, 2018, issued in connection with U.S. Appl. No. 15/211,748, filed Jul. 15, 2018, 10 pages.
Notice of Allowance dated Feb. 6, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance dated Jun. 7, 2019, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 9 pages.
Notice of Allowance dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/229,868, filed Aug. 5, 2016, 11 pages.
Notice of Allowance dated Mar. 9, 2018, issued in connection with U.S. Appl. No. 15/584,782, filed May 2, 2017, 8 pages.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Preinterview First Office Action dated Aug. 5, 2019, issued in connection with U.S. Appl. No. 16/434,426, filed Jun. 7, 2019, 4 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
Restriction Requirement dated Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/214,711, filed Dec. 10, 2018, 5 pages.
Restriction Requirement dated Aug. 9, 2018, issued in connection with U.S. Appl. No. 15/717,621, filed Sep. 27, 2017, 8 pages.
Souden et al. “An Integrated Solution for Online Multichannel Noise Tracking and Reduction.” IEEE Transactions on Audio, Speech, and Language Processing, vol. 19. No. 7, Sep. 7, 2011, 11 pages.
Souden et al. “Gaussian Model-Based Multichannel Speech Presence Probability” IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 5, Jul. 5, 2010, 6pages.
Souden et al. “On Optimal Frequency-Domain Multichannel Linear Filtering for Noise Reduction.” IEEE Transactions on Audio, Speech, and Language Processing, vol. 18, No. 2, Feb. 2010, 17pages.
Steven J. Nowlan and Geoffrey E. Hinton “Simplifying Neural Networks by Soft Weight-Sharing” Neural Computation 4, 1992, 21 pages.
Tsiami et al. “Experiments in acoustic source localization using sparse arrays in adverse indoors environments”, 2014 22nd European Signal Processing Conference, Sep. 1, 2014, 5 pages.
Tweet: “How to start using Google app voice commands to make your life easier SHARE THIS STORY shop @Bullet”, Jan. 21, 2016, https://bgr.com/2016/01/21/best-ok-google-voice-commands/, 3 page.
Ullrich et al. “Soft Weight-Sharing for Neural Network Compression.” ICLR 2017, 16 pages.
U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages.
U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages.
UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54.
Vacher at al. “Recognition of voice commands by multisource ASR and noise cancellation in a smart home environment” Signal Processing Conference 2012 Proceedings of the 20th European, IEEE, Aug. 27, 2012, 5 pages.
Vacher et al. “Speech Recognition in a Smart Home: Some Experiments for Telemonitoring,” 2009 Proceedings of the 5th Conference on Speech Technology and Human-Computer Dialogoue, Constant, 2009, 10 pages.
“S Voice or Google Now?”; https://web.archive.org/web/20160807040123/lowdown.carphonewarehouse.com/news/s-voice-or-google-now/ . . . , Apr. 28, 2015; 4 pages.
Wung et al. “Robust Acoustic Echo Cancellation in the Short-Time Fourier Transform Domain Using Adaptive Crossband Filters” IEEE International Conference on Acoustic, Speech and Signal Processing ICASSP, 2014, p. 1300-1304.
Xiao et al. “A Learning-Based Approach to Direction of Arrival Estimation in Noisy and Reverberant Environments,” 2015 IEEE International Conference on Acoustics, Speech and Signal Processing, Apr. 19, 2015, 5 pages.
Yamaha DME 64 Owner's Manual; copyright 2004, 80 pages.
Yamaha DME Designer 3.5 setup manual guide; copyright 2004, 16 pages.
Yamaha DME Designer 3.5 User Manual; Copyright 2004, 507 pages.
Advisory Action dated Jun. 28, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 3 pages.
Advisory Action dated Dec. 31, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 4 pages.
AudioTron Quick Start Guide, Version 1.0, Mar. 2001, 24 pages.
AudioTron Reference Manual, Version 3.0, May 2002, 70 pages.
AudioTron Setup Guide, Version 3.0, May 2002, 38 pages.
Australian Patent Office, Examination Report dated Oct. 30, 2018, issued in connection with Australian Application No. 2017222436, 3 pages.
“Automatic Parameter Tying in Neural Networks” ICLR 2018, 14 pages.
Bluetooth. “Specification of the Bluetooth System: The ad hoc SCATTERNET for affordable and highly functional wireless connectivity,” Core, Version 1.0 A, Jul. 26, 1999, 1068 pages.
Bluetooth. “Specification of the Bluetooth System: Wireless connections made easy,” Core, Version 1.0 B, Dec. 1, 1999, 1076 pages.
Canadian Patent Office, Canadian Office Action dated Nov. 14, 2018, issued in connection with Canadian Application No. 3015491, 3 pages.
Chinese Patent Office, First Office Action and Translation dated Mar. 20, 2019, issued in connection with Chinese Application No. 201780025028.2, 18 pages.
Chinese Patent Office, First Office Action and Translation dated Mar. 27, 2019, issued in connection with Chinese Application No. 201780025029.7, 9 pages.
Chinese Patent Office, Second Office Action and Translation dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 14 pages.
Chinese Patent Office, Translation of Office Action dated Jul. 18, 2019, issued in connection with Chinese Application No. 201780025029.7, 8 pages.
Corrected Notice of Allowability dated Mar. 8, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 6 pages.
Dell, Inc. “Dell Digital Audio Receiver: Reference Guide,” Jun. 2000, 70 pages.
Dell, Inc. “Start Here,” Jun. 2000, 2 pages.
“Denon 2003-2004 Product Catalog,” Denon, 2003-2004, 44 pages.
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 177570702, 8 pages.
European Patent Office, European Extended Search Report dated Jan. 3, 2019, issued in connection with European Application No. 17757075.1, 9 pages.
European Patent Office, European Extended Search Report dated Oct. 30, 2017, issued in connection with EP Application No. 17174435.2, 11 pages.
European Patent Office, European Office Action dated Jan. 22, 2019, issued in connection with European Application No. 17174435.2, 9 pages.
Fadilpasic,“Cortana can now be the default PDA on your Android”, IT Pro Portal: Accessed via WayBack Machine; http://web.archive.org/web/20171129124915/https://www.itproportal.com/2015/08/11/cortana-can-now-be- . . . , Aug. 11, 2015, 6 pages.
Final Office Action dated Oct. 6, 2017, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 25 pages.
Final Office Action dated Apr. 11, 2019, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 17 pages.
Final Office Action dated Aug. 11, 2017, issued in connection with U.S. Appl. No. 15/131,776, filed Apr. 18, 2016, 7 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 18 pages.
Final Office Action dated Apr. 13, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 20 pages.
Final Office Action dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/098,718, filed Apr. 14, 2016, 15 pages.
Final Office Action dated Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Final Office Action dated Oct. 16, 2018, issued in connection with U.S. Appl. No. 15/438,725, filed Feb. 21, 2017, 10 pages.
Final Office Action dated Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 12 pages.
Final Office Action dated Apr. 26, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 20 pages.
Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 6 pages.
Final Office Action dated Feb. 5, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 17 pages.
Fiorenza Arisio et al. “Deliverable 1.1 User Study, analysis of requirements and definition of the application task,” May 31, 2012, http://dirha.fbk.eu/sites/dirha.fbk.eu/files/docs/DIRHA_D1.1., 31 pages.
First Action Interview Office Action dated Aug. 14, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages.
First Action Interview Office Action dated Jul. 5, 2019, issued in connection with U.S. Appl. No. 16/227,308, filed Dec. 20, 2018, 4 pages.
Freiberger, Karl, “Development and Evaluation of Source Localization Algorithms for Coincident Microphone Arrays,” Diploma Thesis, Apr. 1, 2010, 106 pages.
Giacobello et al. “A Sparse Nonuniformly Partitioned Multidelay Filter for Acoustic Echo Cancellation,” 2013, IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, Oct. 2013, New Paltz, NY, 4 pages.
Giacobello et al. “Tuning Methodology for Speech Enhancement Algorithms using a Simulated Conversational Database and Perceptual Objective Measures,” 2014, 4th Joint Workshop on Hands-free Speech Communication and Microphone Arrays HSCMA, 2014, 5 pages.
Han et al. “Deep Compression: Compressing Deep Neural Networks with Pruning, Trained Quantization and Huffman Coding.” ICLR 2016, Feb. 15, 2016, 14 pages.
Helwani et al “Source-domain adaptive filtering for MIMO systems with application to acoustic echo cancellation”, Acoustics Speech and Signal Processing, 2010 IEEE International Conference, Mar. 14, 2010, 4 pages.
Hirano et al. “A Noise-Robust Stochastic Gradient Algorithm with an Adaptive Step-Size Suitable for Mobile Hands-Free Telephones,” 1995, International Conference on Acoustics, Speech, and Signal Processing, vol. 2, 4 pages.
International Bureau, International Preliminary Report on Patentability, dated Apr. 11, 2019, issued in connection with International Application No. PCT/US2017/0054063, filed on Sep. 28, 2017, 9 pages.
International Bureau, International Preliminary Report on Patentability, dated Apr. 23, 2019, issued in connection with International Application No. PCT/US2017/057220, filed on Oct. 18, 2017, 7 pages.
International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018728, filed on Feb. 21, 2017, 8 pages.
International Bureau, International Preliminary Report on Patentability, dated Sep. 7, 2018, issued in connection with International Application No. PCT/US2017/018739, filed on Feb. 21, 2017, 7 pages.
International Searching Authority, International Search Report and Written Opinion dated Dec. 19, 2018, in connection with International Application No. PCT/US2018/053517, 13 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 22, 2017, issued in connection with International Application No. PCT/US2017/054063, filed on Sep. 28, 2017, 11 pages.
Non-Final Office Action dated Jun. 27, 2018, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 16 pages.
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,437, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action dated Jun. 27, 2019, issued in connection with U.S. Appl. No. 16/437,476, filed Jun. 11, 2019, 8 pages.
Non-Final Office Action dated Mar. 29, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 11 pages.
Non-Final Office Action dated Jul. 3, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 7 pages.
Non-Final Office Action dated May 3, 2019, issued in connection with U.S. Appl. No. 16/178,122, filed Nov. 1, 2018, 14 pages.
Non-Final Office Action dated Oct. 3, 2018, issued in connection with U.S. Appl. No. 16/102,153, filed Aug. 13, 2018, 20 pages.
Non-Final Office Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/718,521, filed Sep. 28, 2017, 39 pages.
Non-Final Office Action dated Jun. 30, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 13 pages.
Non-Final Office Action dated Apr. 4, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 21 pages.
Non-Final Office Action dated Jan. 4, 2019, issued in connection with U.S. Appl. No. 15/948,541, filed Apr. 9, 2018, 6 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 32 pages.
Non-Final Office Action dated Feb. 6, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 6 pages.
Non-Final Office Action dated Sep. 6, 2017, issued in connection with U.S. Appl. No. 15/131,254, filed Apr. 18, 2016, 13 pages.
Non-Final Office Action dated Sep. 6, 2018, issued in connection with U.S. Appl. No. 15/098,760, filed Apr. 14, 2016, 29 pages.
Non-Final Office Action dated Apr. 9, 2018, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 18 pages.
Non-Final Office Action dated May 9, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 22 pages.
Notice of Allowance dated Dec. 4, 2017, issued in connection with U.S. Appl. No. 15/277,810, filed Sep. 27, 2016, 5 pages.
Notice of Allowance dated Jul. 5, 2018, issued in connection with U.S. Appl. No. 15/237,133, filed Aug. 15, 2016, 5 pages.
Notice of Allowance dated Jul. 9, 2018, issued in connection with U.S. Appl. No. 15/438,741, filed Feb. 21, 2017, 5 pages.
Notice of Allowance dated Apr. 1, 2019, issued in connection with U.S. Appl. No. 15/935,966, filed Mar. 26, 2018, 5 pages.
Notice of Allowance dated Aug. 1, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 9 pages.
Notice of Allowance dated Apr. 11, 2018, issued in connection with U.S. Appl. No. 15/719,454, filed Sep. 28, 2017, 15 pages.
Notice of Allowance dated Dec. 12, 2018, issued in connection with U.S. Appl. No. 15/811,468, filed Nov. 13, 2017, 9 pages.
Notice of Allowance dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 15/098,805, filed Apr. 14, 2016, 8 pages.
Notice of Allowance dated Jun. 12, 2019, issued in connection with U.S. Appl. No. 15/670,361, filed Aug. 7, 2017, 7 pages.
Notice of Allowance dated Sep. 12, 2018, issued in connection with U.S. Appl. No. 15/438,744, filed Feb. 21, 2017, 15 pages.
Notice of Allowance dated Dec. 13, 2017, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 9 pages.
Notice of Allowance dated Feb. 13, 2019, issued in connection with U.S. Appl. No. 15/959,907, filed Apr. 23, 2018, 10 pages.
Notice of Allowance dated Aug. 14, 2017, issued in connection with U.S. Appl. No. 15/098,867, filed Apr. 14, 2016, 10 pages.
Notice of Allowance dated Feb. 14, 2017, issued in connection with U.S. Appl. No. 15/229,855, filed Aug. 5, 2016, 11 pages.
Notice of Allowance dated Jun. 14, 2017, issued in connection with U.S. Appl. No. 15/282,554, filed Sep. 30, 2016, 11 pages.
Notice of Allowance dated Nov. 14, 2018, issued in connection with U.S. Appl. No. 15/297,627, filed Oct. 19, 2016, 5 pages.
Notice of Allowance dated Dec. 15, 2017, issued in connection with U.S. Appl. No. 15/223,218, filed Jul. 29, 2016, 7 pages.
Notice of Allowance dated Mar. 15, 2019, issued in connection with U.S. Appl. No. 15/804,776, filed Nov. 6, 2017, 9 pages.
Notice of Allowance dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 15/098,892, filed Apr. 14, 2016, 9 pages.
Notice of Allowance dated Aug. 17, 2017, issued in connection with U.S. Appl. No. 15/131,244, filed Apr. 18, 2016, 9 pages.
Notice of Allowance dated Jul. 17, 2019, issued in connection with U.S. Appl. No. 15/718,911, filed Sep. 28, 2017, 5 pages.
Notice of Allowance dated Sep. 17, 2018, issued in connection with U.S. Appl. No. 15/211,689, filed Jul. 15, 2016, 6 pages.
Notice of Allowance dated Apr. 18, 2019, issued in connection with U.S. Appl. No. 16/173,797, filed Oct. 29, 2018, 9 pages.
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/438,749, filed Feb. 21, 2017, 9 pages.
Notice of Allowance dated Jul. 18, 2019, issued in connection with U.S. Appl. No. 15/721,141, filed Sep. 29, 2017, 8 pages.
Notice of Allowance dated Dec. 19, 2018, issued in connection with U.S. Appl. No. 15/818,051, filed Nov. 20, 2017, 9 pages.
Notice of Allowance dated Jul. 19, 2018, issued in connection with U.S. Appl. No. 15/681,937, filed Aug. 21, 2017, 7 pages.
Notice of Allowance dated Aug. 2, 2019, issued in connection with U.S. Appl. No. 16/102,650, filed Aug. 13, 2018, 5 pages.
Notice of Allowance dated Mar. 20, 2018, issued in connection with U.S. Appl. No. 15/784,952, filed Oct. 16, 2017, 7 pages.
Notice of Allowance dated Sep. 20, 2018, issued in connection with U.S. Appl. No. 15/946,599, filed Apr. 5, 2018, 7 pages.
Notice of Allowance dated Aug. 22, 2017, issued in connection with U.S. Appl. No. 15/273,679, filed Sep. 22, 2016, 5 pages.
Notice of Allowance dated Jan. 22, 2018, issued in connection with U.S. Appl. No. 15/178,180, filed Jun. 9, 2016, 9 pages.
Notice of Allowance dated Apr. 24, 2019, issued in connection with U.S. Appl. No. 16/154,469, filed Oct. 3, 2018, 5 pages.

Related Publications (1)

	Number	Date	Country
	20190304481 A1	Oct 2019	US

Continuations (2)

	Number	Date	Country
Parent	15959907	Apr 2018	US
Child	16444975		US
Parent	15178180	Jun 2016	US
Child	15959907		US

Dynamic player selection for audio signal processing

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract