Calibration of a playback device based on an estimated frequency response

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 of functions associated with calibrating an example playback device;

FIG. 9 shows an example of frequency binning;

FIG. 10 shows an example audio pipeline of an example playback device; and

FIG. 11 shows an example graphical user interface associated with calibration of an example playback device.

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

Rooms have certain acoustics which define how sound travels within the room. For example, a size and shape of the room may affect how sound reflects off a wall and ceiling of the room. As another example, types of surfaces in the room may affect how sound travels in the room. Hard surfaces such as wood or glass may reflect sound whereas soft surfaces such as leather or fabric may absorb sound.

An audio playback device may be located in the room. The audio playback device may have one or more speakers for playing audio content in the room. It may be desirable to calibrate (e.g., adjust) acoustics of the audio playback device so as to improve a listening experience in the room.

The calibration may be based on audio content played by the audio playback device. For example, the audio content may be music provided by a music content provider such as Spotify, Pandora, Amazon Music, among others, via a wide area network such as the Internet. The calibration may involve receiving a first stream of audio and a second stream of audio. The first stream of audio may be source audio content to be played back by the audio playback device. The second stream of audio may be a recording of an audio signal output by the audio playback device based on the audio playback device playing the source audio content. A frequency response of an audio playback device may be estimated based on the source audio content and the recording of the audio content, which may then be used to adjust acoustics of the audio playback device.

The calibration may be performed during a discrete or continuous calibration period. The discrete calibration period may be a calibration of the audio playback device that is performed as a result of a condition being met. For example, the condition may be that the audio playback device is being setup for use. Additionally, or alternatively, the condition may be that the audio playback device has not been calibrated before or a previous attempt to calibrate the audio playback device was unsuccessful. Still additionally, or alternatively, the condition may be that the audio playback device has moved or changed orientation. On the other hand, the continuous calibration period may be a calibration of the audio playback device that continues so long as the audio playback device plays audio content. Unlike the discrete calibration process, the calibration of the audio playback device may be generally ongoing and/or continuous, e.g., as a background process, while the audio playback device plays audio content.

The discrete or continuous calibration process may begin with the audio playback device playing source audio content. The source audio content may be spectral content such as music. The music may have frequencies substantially covering a render-able frequency range of the playback device, a detectable frequency range of the microphone, and/or an audible frequency range for an average human.

The playback of the source audio content may take the form of the audio playback device outputting an audio signal. This audio signal output by the playback device may be recorded.

The audio playback device may have a microphone in proximity to the audio playback device. For example, the microphone may be co-located physically on or in the playback device or wired or wirelessly connected to the audio playback device. This microphone may record the audio signal output by the audio playback device.

In another example, an audio signal output by the audio playback device may be recorded at a spatial location different from the spatial location of the audio playback device. The different spatial location may be where another device (such as a playback device, a controller device, or a network microphone device, among other examples) is located. Via its microphone, the other device may record the audio signal output by the audio playback device.

Acoustic echo cancellation is a process for cancelling reflected acoustic sounds from a speaker that are recorded by a microphone. The acoustic cancellation algorithm may be modified to determine a transfer function between a frequency response of the source audio content and a frequency response of the recorded audio signal output by the audio playback device. In turn, the transfer function and a self-response of the audio playback device in an anechoic chamber may be used to determine an estimated frequency response of the audio playback device. In the case of a controller device recording the audio signal output by the audio playback device, this estimated frequency response may be an approximation of the response curve as described in U.S. patent application Ser. No. 14/864,393, entitled “Facilitating Calibration of an Audio Playback Device”, the contents of which is herein incorporated by reference in its entirety. In the case of the audio playback device itself recording the audio signal output by the audio playback device, this estimated frequency response may represent a self-response of the audio playback device as described in U.S. patent application Ser. No. 15/096,827, entitled “Calibration of Audio Playback Devices”, the contents of which is herein incorporated by reference in its entirety. Other arrangements are also possible.

The estimated frequency response may be used to calibrate (e.g. adjust) acoustics of the audio playback device. For example, the estimated frequency response may be used to select an audio processing algorithm such as a filter or equalization to adjust acoustic settings of the audio playback device. 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, discloses various audio processing algorithms to adjust acoustics of an audio playback device. The filter or equalization may be applied to audio content played by the audio playback device until such time that the filter or equalization is no longer valid or not needed.

In one example, functions associated with the disclosed calibration may be coordinated and at least partially performed by an audio playback device, such as one of the one or more audio playback devices to be calibrated for the playback environment. The audio playback device may calculate an estimated frequency response based on a first stream and second stream of audio and adjust acoustics of the audio playback device based on the estimated frequency response.

In another example, functions associated with the disclosed calibration may be coordinated and at least partially performed by a computing device. The computing device may be a server associated with a media playback system that includes one or more audio playback devices. The computing device may calculate an estimated frequency response based on a first stream and second stream of audio and adjust acoustics of the audio playback device based on the estimated frequency response.

In yet another example, functions associated with the disclosed calibration may be coordinated and at least partially performed by a controller device. The controller device may be used to control the audio playback device. The controller device may calculate an estimated frequency response based on a first stream and second stream of audio and adjust acoustics of the audio playback device based on the estimated frequency response.

Moving on from the above illustration, an example embodiment may include a method which comprises receiving, via a wide area network (WAN), a first stream of audio comprising source audio content to be played back by the audio playback device; receiving a second stream of audio comprising a recording of an audio signal output by the audio playback device based on the audio playback device playing the source audio content; calculating an estimated frequency response of the audio playback device based on the received first stream of audio and the received second stream of audio; and adjusting acoustics of the audio playback device based on the estimated frequency response. Calculating an estimated frequency response of an audio playback device based on the received first stream of audio and second stream of audio may comprise determining a transfer function between a frequency response of the first stream of audio and a frequency response of the second stream of audio. Determining a transfer function between a frequency response of the first stream of audio and a frequency response of the second stream of audio may comprise determining whether the transfer function has converged. The estimated frequency response of an audio playback device may be calculated based on an acoustic echo cancellation algorithm. Receiving, via a wide area network (WAN), a first stream of audio may comprise receiving, via the WAN, music from a music service provider. The method may further comprise determining that the audio playback device has moved. The estimated frequency response may be calculated in response to determining that the audio playback device has moved. The method may further comprise determining a spectral coverage of the source audio content prior to calculating the estimated frequency response. The method may further comprise playing back the source audio content based on the adjusted acoustics. The audio signal output by the audio playback device may be recorded at a spatial location different from the audio playback device. The audio signal output by the audio playback device may be recorded by the audio playback device.

Another example embodiment may include a tangible non-transitory computer readable storage medium including instructions executable by a processor to cause the processor to implement a method of receiving, via a wide area network (WAN), a first stream of audio comprising source audio content to be played back by the audio playback device; receiving a second stream of audio comprising a recording of an audio signal output by the audio playback device based on the audio playback device playing the source audio content; calculating an estimated frequency response of the audio playback device based on the received first stream of audio and the received second stream of audio; and adjusting acoustics of the audio playback device based on the estimated frequency response. The instructions for calculating an estimated frequency response of an audio playback device based on the received first stream of audio and second stream of audio may comprise determining a transfer function between a frequency response of the first stream of audio and a frequency response of the second stream of audio. The instructions for determining a transfer function between a frequency response of the first stream of audio and a frequency response of the second stream of audio may comprise determining whether the transfer function has converged. The tangible non-transitory computer readable storage may further comprise instructions for determining that the audio playback device has moved. The estimated frequency response may be calculated in response to determining that the audio playback device has moved. The tangible non-transitory computer readable storage may further comprise instructions for determining a spectral coverage of the source audio content prior to calculating the estimated frequency response. The tangible non-transitory computer readable storage may further comprise instructions for playing back the source audio content based on the adjusted acoustics. The audio signal output by the audio playback device may be recorded at a spatial location different from the audio playback device. The audio signal output by the audio playback device may be recorded by the audio playback device. The instructions for receiving, via a wide area network (WAN), a first stream of audio may comprise receiving music from a music service provider via the WAN. The estimated frequency response of an audio playback device may be calculated based on an acoustic echo cancellation algorithm.

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

Embodiments described herein involve calibrating (e.g., adjusting) acoustics of an audio playback device for an environment, e.g., room, in which the audio playback device is located based on an estimated frequency response of the audio playback device.

FIG. 7 illustrates such an example environment 700 in which the audio playback device may be calibrated in accordance with disclosed embodiments. The example environment may be, for example, a living room or bedroom of a home. The environment 700 may have an audio playback device 702 capable of outputting audio content in one or more directions via one or more speakers. In embodiments, the audio content may not be limited to one or more predetermined test tones at one or more frequencies, but may include spectral content which may take the form of one or more of digital or analog music, television audio, and radio. The spectral content may be provided by the computing device 508 via the cloud network 502. For example, the computing device may be a music service provider such as Spotify, Amazon Music, Pandora, among others, and the cloud network may be a wide area network (WAN) such as the Internet. The audio content may have frequencies substantially covering a renderable frequency range of the playback device, a detectable frequency range of the microphone, and/or an audible frequency range for an average human.

The audio playback device 702 may have one or more microphones 704 for recording an audio signal output by the audio playback device. The one or more microphones 704 may be proximate to the audio playback device. For example, the microphone may be co-located physically on or in the playback device or wired or wirelessly connected to the audio playback device. The audio signal output by the audio playback device recorded at the audio playback device may be used to determine an estimated frequency response of the audio playback device (i.e., a self-response). The self-response may be used to calibrate the audio playback device.

The room 700 may also have one or more network devices 706. The network device 706 may be a controller device, NMD, or another audio playback device. The network device 706 may have one or more microphones 708 for recording an audio signal output by the audio playback device 702 at a spatial location in the environment 700 different from the spatial location of the audio playback device 702. The different location might be in front of the audio playback device 702, behind the audio playback device 702, or adjacent to the audio playback device 702. The audio signal output by the audio playback device recorded at the network device may be used to determine an estimated frequency response of the audio playback device (i.e., a test response). The test response may be used to calibrate the audio playback device.

In some embodiments, the network device 706 may also be physically movable. In this regard, the microphone of the network device 706 may record the audio signal output by the audio playback device 702 at one or more spatial locations in the environment. For example, the controller device may be physically moved to one or more spatial locations in the environment and the microphone of the controller device may record the audio signal output by the audio playback device 702. Alternatively, a wired or wireless microphone of the audio playback device 702 may be moved to the different spatial locations to record the audio signal output by the audio playback device 702 in a manner similar to that of the controller device. Still alternatively, an NMD may be moved to various spatial locations in the environment to record the audio signal output by the audio playback device 702. Additionally, or alternatively, a plurality of NMDs fixed at various locations in the room may be used to record the audio signal output by the audio playback device 702 at different spatial locations in the room rather than physically moving the NMD in the environment 700. The recorded audio signal output by the audio playback device may be used to determine an estimated frequency response of the audio playback device. The estimated frequency response may be used to calibrate (e.g., adjust) acoustics of the audio playback device.

FIG. 8 shows an example flow diagram of functions associated with calibrating a playback device in accordance with the disclosed embodiments. 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.

In one example, the disclosed functions for the calibration may be at least partially performed by the audio playback device 200. In another example, the disclosed functions for the calibration may be at least partially performed by the computing device 504-508. In yet another example, functions for the calibration may be at least partially performed by the controller device 300. In another example, functions for the calibration may be at least partially performed by an NMD 512-516. Other arrangements are also possible.

Briefly, at 802, a determination is made that the audio playback device is in a calibration period. At 804, a first stream of audio is received, e.g., via a wide area network. The first stream of audio comprises source audio content to be played back by the audio playback device. At 806, a second stream of audio is received. The second stream of audio comprises a recording of an audio signal output by the audio playback device based on the audio playback device playing the source audio content. At 808, an estimated frequency response of an audio playback device is calculated based on the received first stream of audio and the received second stream of audio. At 810, acoustics of the audio playback device is adjusted based on the estimated frequency response. The functions of the example process shown in FIG. 8 will now be described in further detail.

Starting at 802, a determination is made that the audio playback device is in a calibration period. The calibration period may be a time when the audio content output by the playback device may be calibrated. The calibration period may take the form of a discrete or a continuous calibration period.

The discrete calibration period may be a calibration which occurs when a condition is satisfied. For example, the condition may be that a user is setting up or configuring the audio playback device for a first time or after being reset. Alternatively, the condition may be a determination that a calibration has not been performed before on the audio playback device. Still alternatively, the condition may be a determination that a previous calibration is invalid or a previous calibration attempt on the playback device was unsuccessful. For example, the condition may be a time elapsed since a last calibration of the audio playback device or after a “break in” period of the audio playback device. The “break in” period may be the period of time until acoustic components of a speaker such as the cones, diaphragms, and/or drivers move freely and experience a full range of motion. The condition associated with calibration period may be met once the “break in” period is complete.

Movement and/or change in orientation of the audio playback device may also be a condition for triggering calibration. Movement may be a change in spatial location of the audio playback device. Change in orientation may be a change in angular position of the audio playback device. For example, the audio playback device may be not longer resting parallel with a supporting surface such as a shelf but rather angled upwards or downwards. The change in orientation may result in the audio playback device outputting audio on one direction versus another direction. Additionally, or alternatively, the change in orientation may be a rotation of the audio playback device. For example, the audio playback device may be rotated by 90 degrees so that the audio playback device rests on one of its sides rather than another of its sides. Movement and/or change in orientation of the device may be suggestive of a change in an acoustic response of the audio playback device and a need for calibration.

In one example, the audio playback device may be equipped with a sensor such as an accelerometer, global positioning system (GPS), and/or gyroscope for detecting movement and/or a change in orientation of the audio playback device. The sensor may output a signal when the audio playback device moves or changes orientation. In another example, the audio playback device may have an IP address associated with its current location. If the audio playback device is disconnected from the communication means 546 and then reconnected, e.g., it is moved from a bedroom to a living room, the audio playback device may be assigned a new IP address. A change in the IP address may indicate that the audio playback device has moved. In still another example, a change in a label of the audio playback device may indicate that the audio playback device has moved. The audio playback device may be labeled such as “Bedroom Device” or “Living Room Device” to facilitate identification of the audio playback device by a user. A change in the label of the audio playback device, e.g., from “Bedroom Device” to “Living Room Device” may be indicative of the audio playback device being moved.

In some configurations, a change in bonding of the audio playback device may be a condition for triggering calibration. The audio playback device may be bonded to one or more other playback devices to form a bonded zone. The bonded zone may represent one or more audio playback devices playing audio in synchrony. Calibration may be triggered if the audio playback device is bonded with another one or more playback devices and in the new bond the audio playback device changes its equalization, spatial, and/or temporal response. The equalization response may define adjustments to frequencies output by the playback device. The spatial response may define a direction in which the audio content is directed, e.g., using beamforming techniques. The temporal response may define a phase of the audio played by the playback device.

The audio playback device may refer to a state variable in determining whether to trigger the calibration. The state variable may define a state of the audio playback device. For example, the state variable may indicate a position/orientation of the device. A change in position/orientation indicated by the state variable suggests that the playback device moved. As another example, the state variable may indicate which devices a playback device is bonded to. A change in the bonded device(s) may indicate a change in bonding. As yet another example, the state variable may indicate whether the playback device has been set up, calibrated previously, or when it was last calibrated. The state variable may indicate other states of the audio playback device as well. The state variable may be maintained at the audio playback device, the controller device, and/or computing device and exchanged among audio playback devices via the communications means 546.

The continuous calibration process may be a calibration of the audio playback device which continues so long as the playback device plays audio content. The continuous calibration process may normally run as a background process while the audio playback device plays back audio content.

The continuous calibration may be suspended in some instances. In one example, the continuous calibration may be suspended when non-linearities are introduced during signal processing of the source audio content. Such non-linearities could occur at upper and lower volume range extremes. The non-linearities may degrade a signal to noise ratio of the audio signal output by the audio playback device. In this regard, non-linearities in processing the source audio content may determine whether continuous calibration is performed.

As another example, a magnitude of an audio signal output by the audio playback device may cause the continuous calibration to be suspended. A volume setting of an audio playback device may be compared to a threshold level. If the volume setting of the audio playback device is below the threshold level, then a signal to noise ratio of the audio signal output by the audio playback device may be too low to perform the continuous calibration. The volume setting that is compared may be the actual volume setting or a filtered volume setting such as an average volume setting. Additionally, or alternatively, if a sound level of the source audio content is below a threshold level, then a signal to noise ratio of the audio signal output by the audio playback device may be too low to perform the continuous calibration. A magnitude of digital samples of the source audio content may define the sound level of the source audio content. The sound level that is compared to the threshold may be the actual sound level or a filtered sound level such as an average sound level.

The source audio content may span a frequency range from a low frequency to a high frequency. For example, the frequency range may be one or more frequencies between 20 Hz and 20,000 Hz which is the typical audio frequency range for music. The source audio content may comprise digital samples of audio. A frequency and magnitude may be associated with one or more digital samples.

A spectral coverage of the source audio content may determine whether the continuous calibration is suspended. Digital samples of the source audio content may in a time domain. The digital samples of the source audio content may be transformed from the time domain into a frequency domain representation by a transform function such as a Fast Fourier Transform (FFT). The frequency domain representation of the source audio content may represent the spectral coverage of the source audio content.

The spectral coverage of the source audio content may be subdivided into frequency bins. FIG. 9 illustrates an example of frequency binning. In FIG. 9, the frequency domain representation of the source audio content may be subdivided in frequency bins, shown as exemplary frequency bins Freq. 1 to Freq. 8. The frequency bins may be arranged along an X axis 900 and represent a subset of uniform or non-uniform frequency ranges between a low frequency, e.g., 20 Hz, and a high frequency, e.g., 20,000 Hz. A magnitude of each of the frequency bins may then represent an amount of spectral content within the frequency bin as shown by the Y axis 902. The magnitude may be an average of the magnitudes in the frequency bin, a maximum magnitude in the frequency bin, or some other measure.

If a magnitude of the spectral content in one or more frequency bins is less than a threshold level, then continuous calibration (and perhaps also discrete calibration) may not be performed. Referring to FIG. 9, the magnitude of the frequency content in Freq. 3 and Freq. 6 bins may be less than the threshold 902. As a result, the continuous calibration may not be performed.

In another example, a continuous calibration may be performed even though a magnitude of the spectral content in one or more frequency bins is less than a threshold level. For example, the frequency bins with insufficient spectral coverage may be “logged” and filled in with spectral content when the source audio content has sufficient spectral content in those frequency bins. In the meantime, other sufficient spectral content (e.g., covering a same frequency range of the frequency bin) may be used during the calibration. The other sufficient spectral content may be based on source audio content previously played back by the audio playback device or predetermined spectral content. As another example, the spectral content in those frequency bins with insufficient spectral content may be estimated through a filtering process such as interpolation. Spectral content in adjacent frequency bins may be interpolated to fill in the frequency bins with insufficient spectral content. Other arrangements are also possible.

At 804, a first stream of audio may be received, e.g., via a wide area network. The first stream may comprise source audio content to be played back by the audio playback device. Further, the stream may be segmented into one or more chunks of data. For example, the chunks may take the form of packets of digital samples of audio content. These chunks of data may be stored on the audio playback device being calibrated and/or stored on a computing device associated with the calibration of the audio playback device.

This source content may be received via an audio pipeline. FIG. 10 shows such an exemplary audio pipeline 1000. The audio pipeline 1000 may include a source 1002, a signal processor 1004, a digital to analog converter 1006, and a speaker 1008 coupled via one or more communication links.

The audio pipeline 1000 may reside on an audio playback device, the controller device, computing device, NMD, or a combination thereof. In the case of the audio pipeline residing on an audio playback device, the communication links may take the form of traces on a printed circuit board. In the case of the audio pipeline residing on the combination thereof, the communication links may take the form of a wired or wireless network such as an Ethernet or WiFi network.

The source 1002 may be a storage device such as memory or a hard drive which stores source audio content. Alternatively, the source 1002 may be a computing device such as a music service provider which stores and provides the source audio content to the audio playback device. The source audio content may take the form of an audio file of digital samples defining audio content in a time domain.

The signal processor 1004 may apply one or more filtering algorithms to the source audio content prior to the audio playback device outputting an audio signal. The filtering algorithms may vary based one or more of a volume setting of the audio playback device, previous calibration of the playback device, device orientation, content type, etc. Further, the signal processor 1004 include one or more of a sample rate converter, bit depth converter, and channel up/down mixer. The sample rate converter may change a sample rate of the source audio content. The sample rate may define a number of samples representing the source audio content per unit time. The bit depth converter may change a bit depth of the source audio content signal. The bit depth may be a number of bits used to represent a digital sample. The channel up/down mixer may mix source audio content from different channels such as a left and right channel of stereo sound. The signal processor 1004 may perform other functions as well.

In embodiments, the signal processor 1004 may process the source audio content in a digital domain and output a processed digital signal. The digital to analog converter 1006 may convert the digital signal of the signal processor 1004 to an analog signal. The analog signal may be output to the speaker 1008 which converts the analog signal to audible audio.

The source audio content that is used in calibration may be received at the tap 1010 or tap 1012 of FIG. 10. In the case that the source audio content is received at 1010, then processing that would otherwise be applied by the signal processor 1004 may need to be applied to the source audio content prior to calculating the estimated frequency response at 808 which is discussed below.

At 806, a second stream of audio may be received. The second stream may be a recorded audio signal output by the audio playback device based on the audio playback device playing the source audio content. The audio signal may be a time domain representation of the audio content output by the playback device. The stream may be segmented into one or more chunks of data, e.g., packets. The received audio signal may be stored on the audio playback device or passed to another network device, such as a computing device, another audio playback device, control device or NMD.

The audio playback device that is being calibrated may record the audio signal. The audio signal may be recorded via one or more microphones co-located on the audio playback device being calibrated. Alternatively, the audio signal may be recorded via one or more microphones in a spatially different location from the audio playback device being calibrated. For example, another audio playback device may record this audio signal, a network device may receive this audio signal, and/or a NMD may record this audio signal.

At 808, the received first stream of audio, e.g., source audio content, and the received second stream of audio, e.g., recorded audio signal, may be processed to calculate an estimated frequency response of the audio playback device. The processing may be performed by one or more of a computing device, audio playback device being calibrated, another audio playback device, NMD, and/or controller device. The processing may be performed in real time as chunks of source audio content is received and audio signal output by the audio playback device is recorded. This real-time processing may be performed when there is sufficient processing power available. Alternatively, when limited processing power is available, processing may be performed after a “sufficient” amount of chunks of source audio content and audio signal is recorded. Sufficient may be dependent on implementation but may be when a certain number of chunks or packets associated with the source audio content and/or the recorded audio signal output by the audio playback device is received. For example, sufficient may be the source audio content received/audio output signal recorded in a one second interval, a one-minute interval, or some time interval in between. Alternatively, sufficient may be a certain number of packets. Other arrangements are also possible.

Chunks of the source audio content and the audio signal output by the audio playback device may be in a time domain. The chunks in the time domain may be transformed into a frequency domain representation using a transformation technique such as the Fast Fourier Transform (FFT). The frequency domain representation identifies spectral content of the chunks. In some embodiments, spectral content may be added to the spectral content of the chunks of the source audio content and/or the audio signal output by the audio playback device. Consistent with the discussion above with respect to FIG. 9, the spectral content added may be based on spectral content already in one or more frequency bins associated the frequency domain representation. The spectral content added may be source audio content previously played back by the audio playback device, the audio signal output by the audio playback previously, and/or predetermined spectral content. Additionally, or alternatively, the spectral content added may be based on a filtering process such as interpolation being performed on the spectral content already in one or more bins. Other arrangements are also possible.

The source audio content and the audio signal output may be each represented as a vector of data with a magnitude and phase in the frequency domain. A transfer function may be a difference between the source audio content vector (S) and the output audio signal vector (M).

This transfer function may be calculated based on an adaptive echo cancellation algorithm. The characteristic equation for adaptive echo cancellation may be represented as:

M=[S*H+X] (1)

where M is a complex vector in the frequency domain representing a magnitude and phase of the recorded audio signal output by the audio playback device;

S is a complex vector in the frequency domain representing a magnitude and phase of the source audio content vector;

H is a complex transfer function in the frequency domain representing a difference between the S and M in the absence of any recorded interference in M; and

X represents the recorded interference, e.g., static noise (e.g., buzz) or background noise (e.g., speech) in M. If there is no recorded interference in M, then M=S*X and X=0.

A real part of H, e.g., a magnitude component of the S to M transfer function may be calculated as:

magH_n=(magS_n−magM_n)a_n+(1−a_n)(magH_n-1) (2)

where a is a signal to interference ratio, e.g., the signal may be S and the interference may be the recorded interference X. a may be represented as a function of a logarithmic value normalized between 0 and 1;

magS_nis a magnitude component vector of the source audio content vector;

magM_nis a magnitude component vector of the recorded output audio signal vector; and

n is an iteration.

With each iteration, a magnitude component vector of the output audio signal vector magM, a magnitude component vector of the source audio content magS, and the magnitude component of the S to M transfer function magH from one iteration is used to calculate the magnitude component of the S to M transfer function for the next iteration.

The following calculation may be performed for each iteration:

magM_n−magS_n*magH_n (3)

where magM_nis a magnitude component vector of the recorded output audio signal vector;

magS_nis a magnitude component vector of the source audio content vector;

magH_nis a magnitude component of the S to M transfer function.

The transfer function may converge when a result of equation (3) is substantially zero. Alternatively, for each iteration n an average may be calculated based on a result of equation (3) for the current iteration and results of equation (3) for one or more past iterations. The transfer function may converge when a slope of averages based on equation (3) over a plurality of iterations is substantially zero. Various well known convergence algorithms such as L2 norm may also indicate convergence.

An estimated frequency response of the audio playback device may be determined based on magH and a self-response of the audio playback device in an anechoic chamber. The self-response of the audio playback device in an anechoic chamber may involve playing audio by the audio playback device in an anechoic chamber and recording the audio signal output by the audio playback device at the audio playback device. This self-response may be determined during a testing phase of the audio playback device (either of the audio playback device itself or another audio playback device which is similar to the audio playback device) and stored in the computing device, controller device, NMD, or the audio playback device itself. In some instances, the estimated frequency response may be a difference between magH and the self-response of the audio playback device in the anechoic chamber.

In one example, the network device which records the audio signal output by the audio playback device may be a controller device, NMD, or another playback device at a spatial location different from where the audio playback device is located. In this regard, the estimated frequency response may be a test response, e.g., a response of the audio playback device at the spatial location of the network device. In another example, the audio playback device may play back the source audio content and record the audio signal output by the playback device via one or more microphones proximate to the audio playback device. For example, the microphone may be co-located physically on or in the playback device or wired or wirelessly connected to the audio playback device. The estimated frequency response may be a self-response, i.e., a response of the audio playback device determined based on receiving the audio signal output by the audio playback device at the one or more microphones of the audio playback device.

Further, the estimated frequency response may be an absolute response of the audio playback device or a filtered response of the audio playback device. The absolute response may be the estimated frequency response of the audio playback device based on the source audio content and recorded audio signal output received over a given period of time. The filtered response may be an average of estimated frequency responses calculated at different periods of time. In some examples, the estimated frequency response may also be weighted with higher weightings applied to estimated frequency responses which may have been determined more recently and lower weightings applied to estimated frequency responses which may have been determined less recently. The filtered response may continue to be updated as estimated responses are determined for different periods of time (i.e., a moving average). Additionally, if the network device is spatially moving, the filtered response may also be a space averaged response across the portion of space covered by the network device during the period of time.

In the case of discrete calibration, processing associated with frequency response estimation may stop once the estimated frequency response is determined. In the case of a continuous calibration, processing may continue with calculation of updated frequency response estimation as source audio content is received and audio signal output by the audio playback device is recorded.

In either case, at 810, the estimated frequency response may be used to adjust (e.g., calibrate) acoustics of the audio playback device. The adjustment may be performed by one or more of the audio playback device being calibrated, another audio playback device, an NMD, a controller device, and/or a computing device such as a server.

The calibration may be performed in a plurality of ways. In one example, an audio processing algorithm may be selected from a database of audio processing algorithms based on the estimated frequency response of the audio playback device. In another example, the audio processing algorithm may be dynamically computed based on the estimated frequency response of the audio playback device. The audio processing algorithm may take the form of a filter or equalization setting which is used to adjust acoustics of the audio playback device for the environment. This filter or equalization may be applied to the audio content played by the playback device until such time that the filter or equalization is changed or is no longer valid.

The filter or equalization setting may be applied by the audio playback device. Alternatively, the filter or equalization may be applied by another audio playback device, the server, and/or the controller device which then provides the processed audio content to the audio playback device for playback via a communication network. Other arrangements are also possible.

In some situations, the audio playback device cannot be calibrated because the transfer function H does not converge. The audio playback device may have a plurality of microphones. Each of the microphones may record source audio content. In this regard, a transfer function H may be calculated for each microphone of a plurality of microphones in a playback device. Failure to converge may be indicated by a lack of correlation between a transfer function H associated with one microphone of the audio playback device and transfer functions H associated with one or more of the other microphones of the audio playback device. In this situation, the lack of correlation may indicate that the playback device should be moved. Then, the calibration process can be started again.

FIG. 11 illustrates an exemplary user interface 1100 in the event that the audio playback device is unable to be calibrated. A user may be requested to select whether to perform the calibration again. If the user selects to calibrate again, a user interface 1102 may be presented that requests the user to take some action. The action illustrated in FIG. 11 is for the user to move the audio playback device and confirm the audio playback device has moved to complete the calibration.

Alternatives to moving the playback device when the calibration is not successful. may include, but is not limited to those described in U.S. patent application Ser. No. 14/864,393, entitled “Facilitating Calibration of an Audio Playback Device” and/or U.S. patent application Ser. No. 15/096,827, entitled “Calibration of Audio Playback Devices”, the contents each of which is herein incorporated by reference in its entirety. Further, in other embodiments, the user interface may provide an indication that calibration cannot be performed.

In other situations, the audio playback device cannot be calibrated at all. The audio playback device may be impaired, e.g., a microphone or speaker of the audio playback device may be broken. Impairments in the audio playback device may be detected based on analyzing the transfer function H determined for the audio playback device. The transfer function H may define a response for a range of frequencies. If the transfer function H for the audio playback device (and/or a microphone of the audio playback device) does not have a frequency response for a subset of the range of frequencies (e.g., the response is substantially zero) while the transfer function H of other audio playback devices (and/or a microphone of the audio playback device) in the environment do have a frequency response for the subset of the range of frequencies (e.g., the response is substantially non-zero), then the audio playback device may be impaired such that calibration cannot be performed. To facilitate determining whether the audio playback device is impaired, the network device performing the calibration may receive from an audio playback device, computing device, or NMD the transfer function H of one or more audio playback also in the environment.

Methods and the other processes 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 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.

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 playback device comprising: at least one processor;non-transitory computer-readable medium; andprogram instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor and thereby cause the playback device to be configured to: receive a first stream of audio comprising source audio content to be played back by the playback device in a given playback environment;record, via one or more microphones of the playback device, an audio signal output by the playback device based on the playback device playing the source audio content in the given playback environment;determine a transfer function between a frequency-domain representation of the first stream of audio and a frequency-domain representation of the recorded audio signal;determine an estimated frequency response of the playback device in the given playback environment based on a difference between (i) the transfer function and (ii) a self-response of the playback device, wherein the self-response of the playback device comprises a predetermined value stored in a memory of the playback device; andbased on the estimated frequency response of the playback device in the given playback environment, determine an acoustic calibration adjustment for the playback device; andimplement the acoustic calibration adjustment.
2. The playback device of claim 1, further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor and thereby cause the playback device to be configured to: determine that a volume setting of the playback device during playback of the source audio content is within a threshold volume range, wherein determining the estimated frequency response of the playback device in the given playback environment is based on determining that the volume setting of the playback device during playback of the source audio content is within a threshold volume range.
3. The playback device of claim 1, further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor and thereby cause the playback device to be configured to: transmit, to a computing device, at least the recorded audio signal; andreceive, from the computing device, the transfer function.
4. The playback device of claim 1, wherein the program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to receive the first stream of audio comprise program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to receive music content from a cloud-based music service provider.
5. The playback device of claim 1, further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor and thereby cause the playback device to be configured to: determine that the audio playback device has changed at least one of spatial location or orientation, wherein determining the estimated frequency response comprises calculating the estimated frequency response in response to determining that the audio playback device has changed at least one of spatial location or orientation.
6. The playback device of claim 5, wherein the playback device further comprises at least one motion sensor, and wherein the program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to determine that the audio playback device has changed at least one of spatial location or orientation comprise program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to detect, via the at least one motion sensor, that the audio playback device has changed at least one of spatial location or orientation.
7. The playback device of claim 1, further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor and thereby cause the playback device to be configured to: determine a spectral coverage of the source audio content prior to calculating the estimated frequency response.
8. The playback device of claim 1, wherein the program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to implement the acoustic calibration adjustment comprise program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to implement the acoustic calibration adjustment during playback of the source audio content by the playback device in the given playback environment.
9. The playback device of claim 1, wherein the program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to determine an acoustic calibration adjustment for the playback device comprise program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to select an audio processing algorithm from a database of audio processing algorithms stored in the memory of the playback device.
10. The playback device of claim 1, wherein the program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to determine an acoustic calibration adjustment for the playback device comprise program instructions that are executable by the at least one processor and thereby cause the playback device to be configured to calculate an audio processing algorithm based on the estimated frequency response.
11. The playback device of claim 1, further comprising program instructions stored on the non-transitory computer-readable medium that are executable by the at least one processor and thereby cause the playback device to be configured to: determine that the playback device has been configured in a bonded zone with a second playback device for synchronous playback of separate channels of the source audio content, wherein determining the estimated frequency response comprises determining the estimated frequency response in response to determining that the playback device has been configured in a bonded zone with the second playback device.
12. The playback device of claim 1, wherein the estimated frequency response is an estimated sound pressure level output of the audio playback device as a function of input frequency.
13. The playback device of claim 1, wherein the self-response of the audio playback device is determined during a testing phase in an anechoic chamber of another audio playback device that is similar to the audio playback device.
14. A non-transitory computer-readable medium, wherein the non-transitory computer-readable medium is provisioned with program instructions that are executable by at least one processor such that a playback device is configured to: receive a first stream of audio comprising source audio content to be played back by the playback device in a given playback environment;record, via one or more microphones of the playback device, an audio signal output by the playback device based on the playback device playing the source audio content in the given playback environment;determine a transfer function between a frequency-domain representation of the first stream of audio and a frequency-domain representation of the recorded audio signal;determine an estimated frequency response of the playback device in the given playback environment based on a difference between (i) the transfer function and (ii) a self-response of the playback device, wherein the self-response of the playback device comprises a predetermined value stored in a memory of the playback device; andbased on the estimated frequency response of the playback device in the given playback environment, determine an acoustic calibration adjustment for the playback device; andimplement the acoustic calibration adjustment.
15. The non-transitory computer-readable medium of claim 14, wherein the non-transitory computer-readable medium is also provisioned with program instructions that are executable by the at least one processor such that the playback device is configured to: determine that a volume setting of the playback device during playback of the source audio content in the given playback environment is within a threshold volume range, wherein determining the estimated frequency response of the playback device is based on determining that the volume setting of the playback device during playback of the source audio content is within a threshold volume range.
16. The non-transitory computer-readable medium of claim 14, wherein the non-transitory computer-readable medium is also provisioned with program instructions that are executable by the at least one processor such that the playback device is configured to: transmit, to a computing device, at least the recorded audio signal; andreceive, from the computing device, the transfer function.
17. The non-transitory computer-readable medium of claim 14, wherein the non-transitory computer-readable medium is also provisioned with program instructions that are executable by the at least one processor such that the playback device is configured to: determine that the audio playback device has changed at least one of spatial location or orientation, wherein determining the estimated frequency response comprises calculating the estimated frequency response in response to determining that the audio playback device has changed at least one of spatial location or orientation.
18. The non-transitory computer-readable medium of claim 14, wherein the program instructions that are executable by at least one processor such that the playback device is configured to implement the acoustic calibration adjustment comprise program instructions that are executable by at least one processor such that the playback device is configured to implement the acoustic calibration adjustment during playback of the source audio content by the playback device in the given playback environment.
19. The non-transitory computer-readable medium of claim 14, wherein the program instructions that are executable by at least one processor such that the playback device is configured to determine an acoustic calibration adjustment for the playback device comprise program instructions that are executable by at least one processor such that the playback device is configured to select an audio processing algorithm from a database of audio processing algorithms stored in the memory of the playback device.
20. A method implemented by a playback device, the method comprising: receiving a first stream of audio comprising source audio content to be played back by the playback device in a given playback environment;recording, via one or more microphones of the playback device, an audio signal output by the playback device based on the playback device playing the source audio content in the given playback environment;determining a transfer function between a frequency-domain representation of the first stream of audio and a frequency-domain representation of the recorded audio signal;determining an estimated frequency response of the playback device in the given playback environment based on a difference between (i) the transfer function and (ii) a self-response of the playback device, wherein the self-response of the playback device comprises a predetermined value stored in a memory of the playback device; andbased on the estimated frequency response of the playback device in the given playback environment, determining an acoustic calibration adjustment for the playback device; andimplementing the acoustic calibration adjustment.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patent application Ser. No. 15/229,693, filed on Aug. 5, 2016, entitled “Calibration of a Playback Device Based on an Estimated Frequency Response,” the contents of which is hereby incorporated by reference in its entirety for all purposes.

US Referenced Citations (467)

Number	Name	Date	Kind
4306113	Morton	Dec 1981	A
4342104	Jack	Jul 1982	A
4504704	Ohyaba et al.	Mar 1985	A
4592088	Shimada	May 1986	A
4628530	Op De Beek	Dec 1986	A
4631749	Rapaich	Dec 1986	A
4694484	Atkinson et al.	Sep 1987	A
4773094	Dolby	Sep 1988	A
4995778	Bruessel	Feb 1991	A
5218710	Yamaki et al.	Jun 1993	A
5255326	Stevenson	Oct 1993	A
5323257	Abe et al.	Jun 1994	A
5386478	Plunkett	Jan 1995	A
5440644	Farinelli et al.	Aug 1995	A
5553147	Pineau	Sep 1996	A
5581621	Koyama et al.	Dec 1996	A
5757927	Gerzon et al.	May 1998	A
5761320	Farinelli et al.	Jun 1998	A
5910991	Farrar	Jun 1999	A
5923902	Inagaki	Jul 1999	A
5939656	Suda	Aug 1999	A
6018376	Nakatani	Jan 2000	A
6032202	Lea et al.	Feb 2000	A
6072879	Ouchi et al.	Jun 2000	A
6111957	Thomasson	Aug 2000	A
6256554	DiLorenzo	Jul 2001	B1
6363155	Horbach	Mar 2002	B1
6404811	Cvetko et al.	Jun 2002	B1
6469633	Wachter et al.	Oct 2002	B1
6522886	Youngs et al.	Feb 2003	B1
6573067	Dib-Hajj et al.	Jun 2003	B1
6611537	Edens et al.	Aug 2003	B1
6631410	Kowalski et al.	Oct 2003	B1
6639989	Zacharov et al.	Oct 2003	B1
6643744	Cheng	Nov 2003	B1
6704421	Kitamura	Mar 2004	B1
6721428	Allred et al.	Apr 2004	B1
6757517	Chang et al.	Jun 2004	B2
6760451	Craven	Jul 2004	B1
6766025	Levy et al.	Jul 2004	B1
6778869	Champion	Aug 2004	B2
6798889	Dicker et al.	Sep 2004	B1
6862440	Sampath	Mar 2005	B2
6916980	Ishida et al.	Jul 2005	B2
6931134	Waller, Jr. et al.	Aug 2005	B1
6985694	De Bonet et al.	Jan 2006	B1
6990211	Parker	Jan 2006	B2
7031476	Chrisop et al.	Apr 2006	B1
7039212	Poling et al.	May 2006	B2
7058186	Tanaka	Jun 2006	B2
7072477	Kincaid	Jul 2006	B1
7103187	Neuman	Sep 2006	B1
7130608	Hollstrom et al.	Oct 2006	B2
7130616	Janik	Oct 2006	B2
7143939	Henzerling	Dec 2006	B2
7187947	White et al.	Mar 2007	B1
7236773	Thomas	Jun 2007	B2
7289637	Montag et al.	Oct 2007	B2
7295548	Blank et al.	Nov 2007	B2
7312785	Tsuk et al.	Dec 2007	B2
7391791	Balassanian et al.	Jun 2008	B2
7477751	Lyon et al.	Jan 2009	B2
7483538	McCarty et al.	Jan 2009	B2
7483540	Rabinowitz et al.	Jan 2009	B2
7489784	Yoshino	Feb 2009	B2
7490044	Kulkarni	Feb 2009	B2
7492909	Carter et al.	Feb 2009	B2
7519188	Berardi et al.	Apr 2009	B2
7529377	Nackvi et al.	May 2009	B2
7571014	Lambourne et al.	Aug 2009	B1
7590772	Marriott et al.	Sep 2009	B2
7630500	Beckman et al.	Dec 2009	B1
7630501	Blank et al.	Dec 2009	B2
7643894	Braithwaite et al.	Jan 2010	B2
7657910	McAulay et al.	Feb 2010	B1
7664276	McKee	Feb 2010	B2
7676044	Sasaki et al.	Mar 2010	B2
7689305	Kreifeldt et al.	Mar 2010	B2
7720237	Bharitkar et al.	May 2010	B2
7742740	Goldberg et al.	Jun 2010	B2
7769183	Bharitkar et al.	Aug 2010	B2
7796068	Raz et al.	Sep 2010	B2
7835689	Goldberg et al.	Nov 2010	B2
7853341	McCarty et al.	Dec 2010	B2
7876903	Sauk	Jan 2011	B2
7925203	Lane et al.	Apr 2011	B2
7949140	Kino	May 2011	B2
7949707	McDowall et al.	May 2011	B2
7961893	Kino	Jun 2011	B2
7970922	Svendsen	Jun 2011	B2
7987294	Bryce et al.	Jul 2011	B2
8005228	Bharitkar et al.	Aug 2011	B2
8014423	Thaler et al.	Sep 2011	B2
8045721	Burgan et al.	Oct 2011	B2
8045952	Qureshey et al.	Oct 2011	B2
8050652	Qureshey et al.	Nov 2011	B2
8063698	Howard	Nov 2011	B2
8074253	Nathan	Dec 2011	B1
8103009	McCarty et al.	Jan 2012	B2
8116476	Inohara	Feb 2012	B2
8126172	Horbach et al.	Feb 2012	B2
8131390	Braithwaite et al.	Mar 2012	B2
8139774	Berardi et al.	Mar 2012	B2
8144883	Pdersen et al.	Mar 2012	B2
8160276	Liao et al.	Apr 2012	B2
8160281	Kim et al.	Apr 2012	B2
8170260	Reining et al.	May 2012	B2
8175292	Aylward et al.	May 2012	B2
8175297	Ho et al.	May 2012	B1
8194874	Starobin et al.	Jun 2012	B2
8229125	Short	Jul 2012	B2
8233632	MacDonald et al.	Jul 2012	B1
8234395	Millington	Jul 2012	B2
8238547	Ohki et al.	Aug 2012	B2
8238578	Aylward	Aug 2012	B2
8243961	Morrill	Aug 2012	B1
8264408	Kainulainen et al.	Sep 2012	B2
8265310	Berardi et al.	Sep 2012	B2
8270620	Christensen et al.	Sep 2012	B2
8279709	Choisel et al.	Oct 2012	B2
8281001	Busam et al.	Oct 2012	B2
8290185	Kim	Oct 2012	B2
8291349	Park et al.	Oct 2012	B1
8300845	Zurek et al.	Oct 2012	B2
8306235	Mahowald	Nov 2012	B2
8325931	Howard et al.	Dec 2012	B2
8325935	Rutschman	Dec 2012	B2
8325944	Duwenhorst et al.	Dec 2012	B1
8331585	Hagen et al.	Dec 2012	B2
8332414	Nguyen et al.	Dec 2012	B2
8379876	Zhang	Feb 2013	B2
8391501	Khawand et al.	Mar 2013	B2
8392505	Haughay et al.	Mar 2013	B2
8401202	Brooking	Mar 2013	B2
8433076	Zurek et al.	Apr 2013	B2
8452020	Gregg et al.	May 2013	B2
8463184	Dua	Jun 2013	B2
8483853	Lambourne	Jul 2013	B1
8488799	Goldstein et al.	Jul 2013	B2
8503669	Mao	Aug 2013	B2
8527876	Wood et al.	Sep 2013	B2
8577045	Gibbs	Nov 2013	B2
8577048	Chaikin et al.	Nov 2013	B2
8600075	Lim	Dec 2013	B2
8620006	Berardi et al.	Dec 2013	B2
8682002	Wihardja et al.	Mar 2014	B2
8731206	Park	May 2014	B1
8755538	Kwon	Jun 2014	B2
8798280	Goldberg et al.	Aug 2014	B2
8819554	Basso et al.	Aug 2014	B2
8831244	Apfel	Sep 2014	B2
8855319	Liu et al.	Oct 2014	B2
8862273	Karr	Oct 2014	B2
8879761	Johnson et al.	Nov 2014	B2
8903526	Beckhardt et al.	Dec 2014	B2
8914559	Kalayjian et al.	Dec 2014	B2
8930005	Reimann et al.	Jan 2015	B2
8934647	Joyce et al.	Jan 2015	B2
8934655	Breen et al.	Jan 2015	B2
8942252	Balassanian et al.	Jan 2015	B2
8965033	Wiggins	Feb 2015	B2
8965546	Visser et al.	Feb 2015	B2
8977974	Kraut	Mar 2015	B2
8984442	Pirnack et al.	Mar 2015	B2
8989406	Wong et al.	Mar 2015	B2
8995687	Marino, Jr. et al.	Mar 2015	B2
8996370	Ansell	Mar 2015	B2
9020153	Britt, Jr.	Apr 2015	B2
9021153	Lu	Apr 2015	B2
9065929	Chen et al.	Jun 2015	B2
9084058	Reilly et al.	Jul 2015	B2
9100766	Soulodre et al.	Aug 2015	B2
9106192	Sheen et al.	Aug 2015	B2
9179233	Kang	Nov 2015	B2
9215545	Dublin et al.	Dec 2015	B2
9219460	Bush	Dec 2015	B2
9231545	Agustin et al.	Jan 2016	B2
9286384	Kuper et al.	Mar 2016	B2
9288597	Carlsson et al.	Mar 2016	B2
9300266	Grokop	Mar 2016	B2
9319816	Narayanan	Apr 2016	B1
9451377	Massey et al.	Sep 2016	B2
9462399	Bharitkar et al.	Oct 2016	B2
9467779	Iyengar et al.	Oct 2016	B2
9472201	Sleator	Oct 2016	B1
9489948	Chu et al.	Nov 2016	B1
9524098	Griffiths et al.	Dec 2016	B2
9538305	Lehnert et al.	Jan 2017	B2
9538308	Isaac et al.	Jan 2017	B2
9560449	Carlsson et al.	Jan 2017	B2
9560460	Chaikin et al.	Jan 2017	B2
9609383	Hirst	Mar 2017	B1
9615171	O'Neill et al.	Apr 2017	B1
9648422	Sheen et al.	May 2017	B2
9674625	Armstrong-Muntner et al.	Jun 2017	B2
9678708	Bierbower et al.	Jun 2017	B2
9689960	Barton et al.	Jun 2017	B1
9690271	Sheen et al.	Jun 2017	B2
9690539	Sheen et al.	Jun 2017	B2
9706323	Sheen et al.	Jul 2017	B2
9715365	Kusano et al.	Jul 2017	B2
9723420	Family et al.	Aug 2017	B2
9736584	Sheen et al.	Aug 2017	B2
9743207	Hartung	Aug 2017	B1
9743208	Oishi et al.	Aug 2017	B2
9749763	Sheen	Aug 2017	B2
9763018	McPherson et al.	Sep 2017	B1
9781532	Sheen	Oct 2017	B2
9788113	Wilberding et al.	Oct 2017	B2
9860662	Jarvis et al.	Jan 2018	B2
9864574	Hartung et al.	Jan 2018	B2
9910634	Sheen et al.	Mar 2018	B2
9916126	Lang	Mar 2018	B2
9952825	Sheen	Apr 2018	B2
9984703	Ur et al.	May 2018	B2
10045142	McPherson et al.	Aug 2018	B2
10154359	Sheen	Dec 2018	B2
10206052	Perianu	Feb 2019	B2
20010038702	Lavoie et al.	Nov 2001	A1
20010042107	Palm	Nov 2001	A1
20010043592	Jimenez et al.	Nov 2001	A1
20010053228	Jones	Dec 2001	A1
20020022453	Balog et al.	Feb 2002	A1
20020026442	Lipscomb et al.	Feb 2002	A1
20020078161	Cheng	Jun 2002	A1
20020089529	Robbin	Jul 2002	A1
20020124097	Isely et al.	Sep 2002	A1
20020126852	Kashani et al.	Sep 2002	A1
20020136414	Jordan et al.	Sep 2002	A1
20020146136	Carter et al.	Oct 2002	A1
20030002689	Folio	Jan 2003	A1
20030031334	Layton et al.	Feb 2003	A1
20030081115	Curry	May 2003	A1
20030157951	Hasty	Aug 2003	A1
20030161479	Yang et al.	Aug 2003	A1
20030161492	Miller et al.	Aug 2003	A1
20030179891	Rabinowitz et al.	Sep 2003	A1
20030235311	Grancea et al.	Dec 2003	A1
20040024478	Hans et al.	Feb 2004	A1
20040131338	Asada et al.	Jul 2004	A1
20040237750	Smith et al.	Dec 2004	A1
20050031143	Devantier et al.	Feb 2005	A1
20050063554	Devantier et al.	Mar 2005	A1
20050147261	Yeh	Jul 2005	A1
20050157885	Olney et al.	Jul 2005	A1
20050276425	Forrester	Dec 2005	A1
20060008256	Khedouri et al.	Jan 2006	A1
20060026521	Hotelling et al.	Feb 2006	A1
20060032357	Roovers et al.	Feb 2006	A1
20060195480	Spiegelman et al.	Aug 2006	A1
20060225097	Lawrence-Apfelbaum	Oct 2006	A1
20070003067	Gierl et al.	Jan 2007	A1
20070025559	Mihelich et al.	Feb 2007	A1
20070032895	Nackvi et al.	Feb 2007	A1
20070038999	Millington	Feb 2007	A1
20070086597	Kino	Apr 2007	A1
20070116254	Looney et al.	May 2007	A1
20070121955	Johnston et al.	May 2007	A1
20070142944	Goldberg et al.	Jun 2007	A1
20080002839	Eng	Jan 2008	A1
20080014989	Sandegard et al.	Jan 2008	A1
20080065247	Igoe	Mar 2008	A1
20080069378	Rabinowitz et al.	Mar 2008	A1
20080077261	Baudino	Mar 2008	A1
20080098027	Aarts	Apr 2008	A1
20080136623	Calvarese	Jun 2008	A1
20080144864	Huon et al.	Jun 2008	A1
20080175411	Greve	Jul 2008	A1
20080214160	Jonsson	Sep 2008	A1
20080232603	Soulodre et al.	Sep 2008	A1
20080266385	Smith et al.	Oct 2008	A1
20080281523	Dahl et al.	Nov 2008	A1
20090003613	Christensen et al.	Jan 2009	A1
20090024662	Park et al.	Jan 2009	A1
20090047993	Vasa	Feb 2009	A1
20090063274	Dublin, III et al.	Mar 2009	A1
20090110218	Swain	Apr 2009	A1
20090138507	Burckart et al.	May 2009	A1
20090147134	Iwamatsu	Jun 2009	A1
20090175476	Bottum	Jul 2009	A1
20090180632	Goldberg et al.	Jul 2009	A1
20090196428	Kim	Aug 2009	A1
20090202082	Bharitkar et al.	Aug 2009	A1
20090252481	Ekstrand	Oct 2009	A1
20090304194	Eggleston et al.	Dec 2009	A1
20090304205	Hardacker et al.	Dec 2009	A1
20090316923	Tashev et al.	Dec 2009	A1
20100013550	Tanaka	Jan 2010	A1
20100095332	Gran et al.	Apr 2010	A1
20100128902	Liu et al.	May 2010	A1
20100135501	Corbett et al.	Jun 2010	A1
20100142735	Yoon et al.	Jun 2010	A1
20100146445	Kraut	Jun 2010	A1
20100162117	Basso et al.	Jun 2010	A1
20100189203	Wilhelmsson	Jul 2010	A1
20100195846	Yokoyama	Aug 2010	A1
20100272270	Chaikin et al.	Oct 2010	A1
20100296659	Tanaka	Nov 2010	A1
20100303248	Tawada	Dec 2010	A1
20100303250	Goldberg et al.	Dec 2010	A1
20100323793	Andall	Dec 2010	A1
20110007904	Tomoda et al.	Jan 2011	A1
20110007905	Sato et al.	Jan 2011	A1
20110087842	Lu et al.	Apr 2011	A1
20110091055	Leblanc	Apr 2011	A1
20110135103	Sun et al.	Jun 2011	A1
20110150228	Yoon et al.	Jun 2011	A1
20110150230	Tanaka	Jun 2011	A1
20110150247	Oliveras	Jun 2011	A1
20110170710	Son	Jul 2011	A1
20110234480	Fino et al.	Sep 2011	A1
20110235808	Kon	Sep 2011	A1
20110268281	Florencio et al.	Nov 2011	A1
20120032928	Alberth et al.	Feb 2012	A1
20120051558	Kim et al.	Mar 2012	A1
20120057724	Rabinowitz	Mar 2012	A1
20120063615	Crockett et al.	Mar 2012	A1
20120093320	Flaks et al.	Apr 2012	A1
20120127831	Gicklhorn et al.	May 2012	A1
20120140936	Bonnick et al.	Jun 2012	A1
20120148075	Goh et al.	Jun 2012	A1
20120183156	Schlessinger et al.	Jul 2012	A1
20120213391	Usami et al.	Aug 2012	A1
20120215530	Harsch et al.	Aug 2012	A1
20120237037	Ninan et al.	Sep 2012	A1
20120243697	Frye et al.	Sep 2012	A1
20120263325	Freeman et al.	Oct 2012	A1
20120268145	Chandra et al.	Oct 2012	A1
20120269356	Sheerin et al.	Oct 2012	A1
20120275613	Soulodre et al.	Nov 2012	A1
20120283593	Searchfield et al.	Nov 2012	A1
20120288124	Fejzo et al.	Nov 2012	A1
20130010970	Hegarty et al.	Jan 2013	A1
20130028443	Pance et al.	Jan 2013	A1
20130051572	Goh et al.	Feb 2013	A1
20130066453	Seefeldt	Mar 2013	A1
20130108055	Hanna et al.	May 2013	A1
20130129102	Li et al.	May 2013	A1
20130129122	Johnson et al.	May 2013	A1
20130166227	Hermann	Jun 2013	A1
20130170647	Reilly et al.	Jul 2013	A1
20130202131	Kemmochi et al.	Aug 2013	A1
20130211843	Clarkson	Aug 2013	A1
20130216071	Maher et al.	Aug 2013	A1
20130223642	Warren et al.	Aug 2013	A1
20130230175	Bech et al.	Sep 2013	A1
20130259254	Xiang et al.	Oct 2013	A1
20130279706	Marti et al.	Oct 2013	A1
20130305152	Griffiths et al.	Nov 2013	A1
20130315405	Kanishima et al.	Nov 2013	A1
20130329896	Krishnaswamy et al.	Dec 2013	A1
20130331970	Beckhardt et al.	Dec 2013	A1
20140003611	Mohammad et al.	Jan 2014	A1
20140003622	Ikizyan et al.	Jan 2014	A1
20140003623	Lang	Jan 2014	A1
20140003625	Sheen	Jan 2014	A1
20140003626	Holman et al.	Jan 2014	A1
20140003635	Mohammad et al.	Jan 2014	A1
20140016784	Sen et al.	Jan 2014	A1
20140016786	Sen	Jan 2014	A1
20140016802	Sen	Jan 2014	A1
20140023196	Xiang et al.	Jan 2014	A1
20140029201	Yang et al.	Jan 2014	A1
20140032709	Saussy et al.	Jan 2014	A1
20140037097	Labosco	Feb 2014	A1
20140037107	Marino, Jr. et al.	Feb 2014	A1
20140052770	Gran et al.	Feb 2014	A1
20140064501	Olsen et al.	Mar 2014	A1
20140079242	Nguyen et al.	Mar 2014	A1
20140084014	Sim	Mar 2014	A1
20140086423	Domingo Yaguez et al.	Mar 2014	A1
20140112481	Li et al.	Apr 2014	A1
20140119551	Bharitkar et al.	May 2014	A1
20140126730	Crawley et al.	May 2014	A1
20140161265	Chaikin et al.	Jun 2014	A1
20140169569	Toivanen et al.	Jun 2014	A1
20140180684	Strub	Jun 2014	A1
20140192986	Lee et al.	Jul 2014	A1
20140219456	Morrell et al.	Aug 2014	A1
20140219483	Hong	Aug 2014	A1
20140226823	Sen et al.	Aug 2014	A1
20140242913	Pang	Aug 2014	A1
20140267148	Luna et al.	Sep 2014	A1
20140270202	Ivanov et al.	Sep 2014	A1
20140270282	Tammi et al.	Sep 2014	A1
20140273859	Luna et al.	Sep 2014	A1
20140279889	Luna et al.	Sep 2014	A1
20140285313	Luna et al.	Sep 2014	A1
20140286496	Luna et al.	Sep 2014	A1
20140294200	Baumgarte et al.	Oct 2014	A1
20140294201	Johnson et al.	Oct 2014	A1
20140310269	Zhang et al.	Oct 2014	A1
20140321670	Nystrom et al.	Oct 2014	A1
20140323036	Daley et al.	Oct 2014	A1
20140334644	Selig et al.	Nov 2014	A1
20140341399	Dusse	Nov 2014	A1
20140344689	Scott et al.	Nov 2014	A1
20140355768	Sen et al.	Dec 2014	A1
20140355794	Morrell et al.	Dec 2014	A1
20150011195	Li	Jan 2015	A1
20150016642	Walsh et al.	Jan 2015	A1
20150023509	Devantier et al.	Jan 2015	A1
20150031287	Pang et al.	Jan 2015	A1
20150032844	Tarr et al.	Jan 2015	A1
20150036847	Donaldson	Feb 2015	A1
20150036848	Donaldson	Feb 2015	A1
20150043736	Olsen et al.	Feb 2015	A1
20150063610	Mossner	Mar 2015	A1
20150078586	Ang et al.	Mar 2015	A1
20150078596	Sprogis et al.	Mar 2015	A1
20150100991	Risberg et al.	Apr 2015	A1
20150146886	Baumgarte	May 2015	A1
20150149943	Nguyen et al.	May 2015	A1
20150161360	Paruchuri et al.	Jun 2015	A1
20150195666	Massey et al.	Jul 2015	A1
20150201274	Ellner et al.	Jul 2015	A1
20150208184	Tan et al.	Jul 2015	A1
20150220558	Snibbe et al.	Aug 2015	A1
20150223002	Mehta	Aug 2015	A1
20150229699	Liu	Aug 2015	A1
20150260754	Perotti et al.	Sep 2015	A1
20150264023	Reno	Sep 2015	A1
20150271616	Kechichian et al.	Sep 2015	A1
20150281866	Williams et al.	Oct 2015	A1
20150289064	Jensen et al.	Oct 2015	A1
20150358756	Harma et al.	Dec 2015	A1
20150382128	Ridihalgh et al.	Dec 2015	A1
20160007116	Holman	Jan 2016	A1
20160011850	Sheen et al.	Jan 2016	A1
20160014509	Hansson et al.	Jan 2016	A1
20160014536	Sheen	Jan 2016	A1
20160021458	Johnson et al.	Jan 2016	A1
20160021473	Riggi et al.	Jan 2016	A1
20160021481	Johnson et al.	Jan 2016	A1
20160027467	Proud	Jan 2016	A1
20160029142	Isaac et al.	Jan 2016	A1
20160035337	Aggarwal et al.	Feb 2016	A1
20160036881	Tembey et al.	Feb 2016	A1
20160037277	Matsumoto et al.	Feb 2016	A1
20160061597	De Bruijn et al.	Mar 2016	A1
20160073210	Sheen	Mar 2016	A1
20160088438	O'Keeffe	Mar 2016	A1
20160119730	Virtanen	Apr 2016	A1
20160140969	Srinivasan et al.	May 2016	A1
20160165297	Jamal-Syed et al.	Jun 2016	A1
20160192098	Oishi et al.	Jun 2016	A1
20160192099	Oishi et al.	Jun 2016	A1
20160212535	Le Nerriec et al.	Jul 2016	A1
20160239255	Chavez et al.	Aug 2016	A1
20160260140	Shirley et al.	Sep 2016	A1
20160309276	Ridihalgh et al.	Oct 2016	A1
20160330562	Crockett	Nov 2016	A1
20160366517	Chandran et al.	Dec 2016	A1
20170069338	Elliot	Mar 2017	A1
20170083279	Sheen	Mar 2017	A1
20170086003	Rabinowitz et al.	Mar 2017	A1
20170105084	Holman	Apr 2017	A1
20170142532	Pan	May 2017	A1
20170207762	Porter et al.	Jul 2017	A1
20170223447	Johnson et al.	Aug 2017	A1
20170230772	Johnson et al.	Aug 2017	A1
20170257722	Kerdranvat et al.	Sep 2017	A1
20170280265	Po	Sep 2017	A1
20170303039	Iyer	Oct 2017	A1
20170311108	Patel	Oct 2017	A1
20170374482	McPherson et al.	Dec 2017	A1
20190037328	McPherson et al.	Jan 2019	A1

Foreign Referenced Citations (67)

Number	Date	Country
1447624	Oct 2003	CN
101366177	Feb 2009	CN
101491116	Jul 2009	CN
102318325	Jan 2012	CN
102893633	Jan 2013	CN
103988523	Aug 2014	CN
105163221	Dec 2015	CN
0505949	Sep 1992	EP
0772374	May 1997	EP
1133896	Aug 2002	EP
1349427	Oct 2003	EP
1389853	Feb 2004	EP
2043381	Apr 2009	EP
1349427	Dec 2009	EP
2161950	Mar 2010	EP
2194471	Jun 2010	EP
2197220	Jun 2010	EP
2429155	Mar 2012	EP
1825713	Oct 2012	EP
2613573	Jul 2013	EP
2591617	Jun 2014	EP
2835989	Feb 2015	EP
2860992	Apr 2015	EP
3128767	Feb 2017	EP
2974382	Apr 2017	EP
H02280199	Nov 1990	JP
H05199593	Aug 1993	JP
H05211700	Aug 1993	JP
H06327089	Nov 1994	JP
H0723490	Jan 1995	JP
H1069280	Mar 1998	JP
2002502193	Jan 2002	JP
2003143252	May 2003	JP
2003304590	Oct 2003	JP
2005086686	Mar 2005	JP
2005538633	Dec 2005	JP
2006017893	Jan 2006	JP
2006180039	Jul 2006	JP
2007068125	Mar 2007	JP
2007271802	Oct 2007	JP
2008228133	Sep 2008	JP
2009188474	Aug 2009	JP
2010081124	Apr 2010	JP
2010141892	Jun 2010	JP
2011123376	Jun 2011	JP
2011130212	Jun 2011	JP
2011164166	Aug 2011	JP
2011217068	Oct 2011	JP
2013253884	Dec 2013	JP
1020060116383	Nov 2006	KR
1020080011831	Feb 2008	KR
200153994	Jul 2001	WO
0182650	Nov 2001	WO
200182650	Nov 2001	WO
2003093950	Nov 2003	WO
2004066673	Aug 2004	WO
2007016465	Feb 2007	WO
2011139502	Nov 2011	WO
2013016500	Jan 2013	WO
2014032709	Mar 2014	WO
2014032709	Mar 2014	WO
2014036121	Mar 2014	WO
2015024881	Feb 2015	WO
2015108794	Jul 2015	WO
2015178950	Nov 2015	WO
2016040324	Mar 2016	WO
2017049169	Mar 2017	WO

Non-Patent Literature Citations (328)

Entry
Non-Final Office Action dated May 30, 2017, issued in connection with U.S. Appl. No. 15/478,770, filed Apr. 4, 2017, 9 pages.
Non-Final Office Action dated May 31, 2019, issued in connection with U.S. Appl. No. 16/185,906, filed Nov. 9, 2018, 7 pages.
Non-Final Office Action dated Nov. 6, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 13 pages.
Non-Final Office Action dated Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/859,311, filed Dec. 29, 2017, 9 pages.
Non-Final Office Action dated Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/865,221, filed Jan. 8, 2018, 10 pages.
Non-Final Office Action dated Jan. 9, 2018, issued in connection with U.S. Appl. No. 15/698,283, filed Sep. 7, 2017, 18 pages.
Non-Final Office Action dated Jan. 9, 2018, issued in connection with U.S. Appl. No. 15/727,913, filed Oct. 9, 2017, 8 pages.
Notice of Allowance dated May 1, 2017, issued in connection with U.S. Appl. No. 14/805,140, filed Jul. 21, 2015, 13 pages.
Notice of Allowance dated Nov. 2, 2016, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages.
Notice of Allowance dated Jun. 3, 2016, issued in connection with U.S. Appl. No. 14/921,799, filed Oct. 23, 2015, 8 pages.
Notice of Allowance dated Nov. 4, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages.
Notice of Allowance dated Jun. 6, 2018, issued in connection with U.S. Appl. No. 15/727,913, filed Oct. 9, 2017, 5 pages.
Notice of Allowance dated Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/216,325, filed Mar. 17, 2014, 7 pages.
Notice of Allowance dated Nov. 9, 2016, issued in connection with U.S. Appl. No. 14/805,340, filed Jul. 21, 2015, 13 pages.
Notice of Allowance dated Feb. 1, 2018, issued in connection with U.S. Appl. No. 15/480,265, filed Apr. 5, 2017, 8 pages.
Notice of Allowance dated Apr. 10, 2015, issued in connection with U.S. Appl. No. 13/536,493, filed Jun. 28, 2012, 8 pages.
Notice of Allowance dated Aug. 10, 2018, issued in connection with U.S. Appl. No. 15/785,088, filed Oct. 16, 2017, 6 pages.
Notice of Allowance dated Jul. 10, 2018, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 2 pages.
Notice of Allowance dated Dec. 11, 2018, issued in connection with U.S. Appl. No. 15/909,327, filed Mar. 1, 2018, 10 pages.
Notice of Allowance dated Feb. 11, 2019, issued in connection with U.S. Appl. No. 15/588,186, filed May 5, 2017, 5 pages.
Notice of Allowance dated Jul. 11, 2017, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 11 pages.
Notice of Allowance dated Mar. 11, 2015, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 7 pages.
Notice of Allowance dated Apr. 12, 2016, issued in connection with U.S. Appl. No. 14/681,465, filed Apr. 8, 2015, 13 pages.
Notice of Allowance dated Aug. 12, 2019, issued in connection with U.S. Appl. No. 16/416,648, filed May 20, 2019, 7 pages.
Notice of Allowance dated Dec. 12, 2016, issued in connection with U.S. Appl. No. 14/805,140, filed Jul. 21, 2015, 24 pages.
Notice of Allowance dated Dec. 12, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 9 pages.
Notice of Allowance dated Nov. 12, 2019, issued in connection with U.S. Appl. No. 15/955,545, filed Apr. 17, 2018, 9 pages.
Notice of Allowance dated Sep. 12, 2016, issued in connection with U.S. Appl. No. 15/066,072, filed Mar. 10, 2016, 7 pages.
Notice of Allowance dated Sep. 12, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 8 pages.
Notice of Allowance dated Feb. 13, 2017, issued in connection with U.S. Appl. No. 14/864,506, filed Sep. 24, 2015, 8 pages.
Notice of Allowance dated Nov. 13, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 8 pages.
Notice of Allowance dated Mar. 14, 2019, issued in connection with U.S. Appl. No. 15/343,996, filed Nov. 4, 2016, 8 pages.
Notice of Allowance dated Jan. 15, 2019, issued in connection with U.S. Appl. No. 16/115,524, filed Aug. 28, 2018, 8 pages.
Notice of Allowance dated Jun. 15, 2017, issued in connection with U.S. Appl. No. 15/096,827, filed Apr. 12, 2016, 5 pages.
Notice of Allowance dated Mar. 15, 2017, issued in connection with U.S. Appl. No. 14/826,856, filed Aug. 14, 2015, 7 pages.
Notice of Allowance dated May 15, 2019, issued in connection with U.S. Appl. No. 16/113,032, filed Aug. 27, 2018, 9 pages.
Notice of Allowance dated Oct. 15, 2018, issued in connection with U.S. Appl. No. 15/716,313, filed Sep. 26, 2017, 10 pages.
Notice of Allowance dated Jun. 16, 2017, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages.
Notice of Allowance dated May 16, 2019, issued in connection with U.S. Appl. No. 16/181,213, filed Nov. 5, 2018, 10 pages.
Notice of Allowance dated Oct. 16, 2017, issued in connection with U.S. Appl. No. 15/478,770, filed Apr. 4, 2017, 10 pages.
Notice of Allowance dated Oct. 16, 2019, issued in connection with U.S. Appl. No. 16/401,981, filed May 2, 2019, 8 pages.
Notice of Allowance dated Sep. 16, 2016, issued in connection with U.S. Appl. No. 15/066,049, filed Mar. 10, 2016, 7 pages.
Notice of Allowance dated Dec. 17, 2018, issued in connection with U.S. Appl. No. 16/055,884, filed Aug. 6, 2018, 5 pages.
Notice of Allowance dated May 17, 2017, issued in connection with U.S. Appl. No. 15/339,260, filed Oct. 31, 2016, 7 pages.
Notice of Allowance dated Oct. 17, 2019, issued in connection with U.S. Appl. No. 16/542,433, filed Aug. 16, 2019, 9 pages.
Notice of Allowance dated Mar. 18, 2019, issued in connection with U.S. Appl. No. 16/056,862, filed Aug. 7, 2018, 12 pages.
Notice of Allowance dated Aug. 19, 2016, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 12 pages.
Notice of Allowance dated Jun. 19, 2017, issued in connection with U.S. Appl. No. 14/793,190, filed Jul. 7, 2015, 5 pages.
Notice of Allowance dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 16 pages.
Notice of Allowance dated Sep. 19, 2018, issued in connection with U.S. Appl. No. 14/864,393, filed Sep. 24, 2015, 10 pages.
Notice of Allowance dated Apr. 20, 2017, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 11 pages.
Notice of Allowance dated Nov. 20, 2017, issued in connection with U.S. Appl. No. 15/298,115, filed Oct. 19, 2016, 10 pages.
Notice of Allowance dated Sep. 20, 2017, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages.
Notice of Allowance dated Dec. 21, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 8 pages.
Notice of Allowance dated Feb. 21, 2018, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 5 pages.
Notice of Allowance dated Jul. 21, 2017, issued in connection with U.S. Appl. No. 15/211,835, filed Jul. 15, 2016, 10 pages.
Notice of Allowance dated Jun. 21, 2019, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 11 pages.
Notice of Allowance dated Oct. 21, 2019, issued in connection with U.S. Appl. No. 16/182,886, filed Nov. 7, 2018, 10 pages.
Notice of Allowance dated Jun. 22, 2017, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 12 pages.
Notice of Allowance dated Aug. 23, 2018, issued in connection with U.S. Appl. No. 15/909,529, filed Mar. 1, 2018, 8 pages.
Notice of Allowance dated Jun. 23, 2016, issued in connection with U.S. Appl. No. 14/921,781, filed Oct. 23, 2015, 8 pages.
Notice of Allowance dated May 23, 2018, issued in connection with U.S. Appl. No. 15/698,283, filed Sep. 1, 2017, 8 pages.
Notice of Allowance dated Oct. 23, 2017, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 16 pages.
Notice of Allowance dated Sep. 23, 2016, issued in connection with U.S. Appl. No. 15/070,160, filed Mar. 15, 2016, 7 pages.
Notice of Allowance dated Jul. 24, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 13 pages.
Notice of Allowance dated May 24, 2017, issued in connection with U.S. Appl. No. 14/997,868, filed Jan. 18, 2016, 5 pages.
Notice of Allowance dated Nov. 24, 2017, issued in connection with U.S. Appl. No. 15/681,640, filed Aug. 21, 2017, 8 pages.
Notice of Allowance dated Apr. 25, 2017, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 7 pages.
Notice of Allowance dated Apr. 25, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 7 pages.
Notice of Allowance dated Apr. 25, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 8 pages.
Notice of Allowance dated Oct. 25, 2016, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 5 pages.
Notice of Allowance dated Feb. 26, 2016, issued in connection with U.S. Appl. No. 14/921,762, filed Oct. 23, 2015, 7 pages.
Notice of Allowance dated Jul. 26, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 12 pages.
Notice of Allowance dated Oct. 26, 2016, issued in connection with U.S. Appl. No. 14/811,587, filed Jul. 28, 2015, 11 pages.
Notice of Allowance dated Feb. 27, 2017, issued in connection with U.S. Appl. No. 14/805,340, filed Jul. 21, 2015, 9 pages.
Notice of Allowance dated Jul. 27, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 5 pages.
Notice of Allowance dated Jun. 27, 2017, issued in connection with U.S. Appl. No. 15/344,069, filed Nov. 4, 2016, 8 pages.
Notice of Allowance dated Aug. 28, 2017, issued in connection with U.S. Appl. No. 15/089,004, filed Apr. 1, 2016, 5 pages.
Notice of Allowance dated Jul. 28, 2017, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 10 pages.
Notice of Allowance dated Jul. 28, 2017, issued in connection with U.S. Appl. No. 15/211,822, filed Jul. 15, 2016, 9 pages.
Notice of Allowance dated Mar. 28, 2018, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 5 pages.
Notice of Allowance dated Aug. 29, 2018, issued in connection with U.S. Appl. No. 15/357,520, filed Nov. 21, 2016, 11 pages.
Notice of Allowance dated Aug. 29, 2018, issued in connection with U.S. Appl. No. 15/718,556, filed Sep. 28, 2017, 8 pages.
Notice of Allowance dated Aug. 29, 2019, issued in connection with U.S. Appl. No. 16/185,906, filed Nov. 9, 2018, 8 pages.
Notice of Allowance dated Dec. 29, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 5 pages.
Notice of Allowance dated Jul. 29, 2016, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 11 pages.
Notice of Allowance dated Oct. 29, 2015, issued in connection with U.S. Appl. No. 14/216,306, filed Mar. 17, 2014, 9 pages.
Notice of Allowance dated May 3, 2019, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 7 pages.
Notice of Allowance dated May 3, 2019, issued in connection with U.S. Appl. No. 16/181,583, filed Nov. 6, 2018, 7 pages.
Notice of Allowance dated Aug. 30, 2017, issued in connection with U.S. Appl. No. 15/088,994, filed Apr. 1, 2016, 10 pages.
Notice of Allowance dated Dec. 30, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 13 pages.
Notice of Allowance dated Jan. 30, 2017, issued in connection with U.S. Appl. No. 15/339,260, filed Oct. 31, 2016, 8 pages.
Notice of Allowance dated Aug. 31, 2018, issued in connection with U.S. Appl. No. 15/872,979, filed Jan. 16, 2018, 7 pages.
Notice of Allowance dated Aug. 31, 2018, issued in connection with U.S. Appl. No. 16/055,884, filed Aug. 6, 2018, 8 pages.
Notice of Allowance dated Apr. 4, 2017, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 8 pages.
Notice of Allowance dated Feb. 4, 2019, issued in connection with U.S. Appl. No. 15/166,241, filed Aug. 26, 2016, 8 pages.
Notice of Allowance dated Feb. 4, 2019, issued in connection with U.S. Appl. No. 16/181,583, filed Nov. 6, 2018, 9 pages.
Notice of Allowance dated Oct. 4, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 7 pages.
Notice of Allowance dated Apr. 5, 2018, issued in connection with U.S. Appl. No. 15/681,640, filed Aug. 21, 2017, 8 pages.
Notice of Allowance dated Jun. 5, 2019, issued in connection with U.S. Appl. No. 15/859,311, filed Dec. 29, 2017, 8 pages.
Notice of Allowance dated Jun. 5, 2019, issued in connection with U.S. Appl. No. 15/865,221, filed Jan. 3, 2018, 8 pages.
Notice of Allowance dated Mar. 5, 2019, issued in connection with U.S. Appl. No. 16/102,499, filed Aug. 13, 2018, 8 pages.
Notice of Allowance dated May 5, 2017, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 5 pages.
Notice of Allowance dated Oct. 5, 2018, issued in connection with U.S. Appl. No. 16/115,524, filed Aug. 28, 2018, 10 pages.
Notice of Allowance dated Feb. 6, 2019, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 8 pages.
Notice of Allowance dated Apr. 8, 2019, issued in connection with U.S. Appl. No. 16/011,402, filed Jun. 18, 2018, 8 pages.
Notice of Allowance dated Jul. 8, 2019, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 5 pages.
Notice of Allowance dated May 8, 2018, issued in connection with U.S. Appl. No. 15/650,386, filed Jul. 14, 2017, 13 pages.
Notice of Allowance dated May 9, 2019, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 7 pages.
Notice of Allowance dated Apr. 19, 2017, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 10 pages.
Palm, Inc., “Handbook for the Palm VII Handheld,” May 2000, 311 pages.
Papp Istvan et al. “Adaptive Microphone Array for Unknown Desired Speaker's Transfer Function”, The Journal of the Acoustical Society of America, American Institute of Physics for the Acoustical Society of America, New York, NY vol. 122, No. 2, Jul. 19, 2007, pp. 44-49.
Pre-Brief Appeal Conference Decision dated Mar. 19, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 2 pages.
Preinterview First Office Action dated Oct. 6, 2016, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 6 pages.
Preinterview First Office Action dated Jul. 12, 2017, issued in connection with U.S. Appl. No. 14/793,205, filed Jul. 7, 2015, 5 pages.
Preinterview First Office Action dated May 17, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 7 pages.
Preinterview First Office Action dated May 25, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 7 pages.
Presentations at WinHEC 2000, May 2000, 138 pages.
PRISMIQ, Inc., “PRISMIQ Media Player User Guide,” 2003, 44 pages.
Ross, Alex, “Wizards of Sound: Retouching acoustics, from the restaurant to the concert hall,” The New Yorker, Feb. 23, 2015. Web. Feb. 26, 2015, 9 pages.
Supplemental Notice of Allowability dated Oct. 27, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 6 pages.
United States Patent and Trademark Office, U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages.
United States Patent and Trademark Office, 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.
Wikipedia, Server(Computing) https://web.archive.org/web/20160703173710/https://en.wikipedia.org/wiki/Server_(computing), published Jul. 3, 2016, 7 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.
Non-Final Office Action dated Dec. 9, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages.
Non-Final Office Action dated Apr. 10, 2018, issued in connection with U.S. Appl. No. 15/909,529, filed Mar. 1, 2018, 8 pages.
Non-Final Office Action dated Mar. 10, 2017, issued in connection with U.S. Appl. No. 14/997,868, filed Jan. 18, 2016, 10 pages.
Non-Final Office Action dated Sep. 10, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 8 pages.
Non-Final Office Action dated Apr. 11, 2017, issued in connection with U.S. Appl. No. 15/088,994, filed Apr. 1, 2016, 13 pages.
Non-Final Office Action dated Apr. 11, 2017, issued in connection with U.S. Appl. No. 15/089,004, filed Apr. 1, 2016, 9 pages.
Non-Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/556,297, filed Aug. 30, 2019, 9 pages.
Non-Final Office Action dated Dec. 11, 2019, issued in connection with U.S. Appl. No. 16/658,896, filed Oct. 21, 2019, 14 pages.
Non-Final Office Action dated Oct. 11, 2017, issued in connection with U.S. Appl. No. 15/480,265, filed Apr. 5, 2017, 8 pages.
Non-Final Office Action dated Oct. 11, 2018, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 13 pages.
Non-Final Office Action dated Sep. 12, 2016, issued in connection with U.S. Appl. No. 14/811,587, filed Jul. 28, 2015, 24 pages.
Non-Final Office Action dated Jul. 13, 2016, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 16 pages.
Non-Final Office Action dated Dec. 14, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 19 pages.
Non-Final Office Action dated Mar. 14, 2017, issued in connection with U.S. Appl. No. 15/096,827, filed Apr. 12, 2016, 12 pages.
Non-Final Office Action dated May 14, 2019, issued in connection with U.S. Appl. No. 15/955,545, filed Apr. 17, 2018, 15 pages.
Non-Final Office Action dated Oct. 14, 2015, issued in connection with U.S. Appl. No. 14/216,325, filed Mar. 17, 2014, 7 pages.
Non-Final Office Action dated May 15, 2018, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 17 pages.
Non-Final Office Action dated Jun. 16, 2017, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 15 pages.
Non-Final Office Action dated Nov. 16, 2018, issued in connection with U.S. Appl. No. 15/996,878, filed Jun. 4, 2018, 8 pages.
Non-Final Office Action dated Dec. 18, 2018, issued in connection with U.S. Appl. No. 16/011,402, filed Jun. 18, 2018, 10 pages.
Non-Final Office Action dated Feb. 18, 2016, issued in connection with U.S. Appl. No. 14/644,136, filed Mar. 10, 2015, 10 pages.
Non-Final Office Action dated Jun. 18, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 15 pages.
Non-Final Office Action dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 7 pages.
Non-Final Office Action dated Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/872,979, filed Jan. 16, 2018, 6 pages.
Non-Final Office Action dated Aug. 2, 2017, issued in connection with U.S. Appl. No. 15/298,115, filed Oct. 19, 2016, 22 pages.
Non-Final Office Action dated Apr. 20, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 8 pages.
Non-Final Office Action dated Jul. 20, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 13 pages.
Non-Final Office Action dated Jun. 20, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 17 pages.
Non-Final Office Action dated Dec. 21, 2018, issued in connection with U.S. Appl. No. 16/181,213, filed Nov. 5, 2018, 13 pages.
Non-Final Office Action dated Jun. 21, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 10 pages.
Non-Final Office Action dated Jun. 21, 2019, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 12 pages.
Non-Final Office Action dated Nov. 21, 2014, issued in connection with U.S. Appl. No. 13/536,493, filed Jun. 28, 2012, 20 pages.
Non-Final Office Action dated Jun. 22, 2018, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 33 pages.
Non-Final Office Action dated Oct. 22, 2019, issued in connection with U.S. Appl. No. 16/416,619, filed May 20, 2019, 12 pages.
Non-Final Office Action dated Jan. 23, 2019, issued in connection with U.S. Appl. No. 16/113,032, filed Aug. 27, 2018, 8 pages.
Non-Final Office Action dated May 24, 2019, issued in connection with U.S. Appl. No. 16/401,981, filed May 2, 2019, 14 pages.
Non-Final Office Action dated Oct. 25, 2016, issued in connection with U.S. Appl. No. 14/864,506, filed Sep. 24, 2015, 9 pages.
Non-Final Office Action dated Sep. 26, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 25 pages.
Non-Final Office Action dated Dec. 27, 2017, issued in connection with U.S. Appl. No. 15/357,520, filed Nov. 21, 2016, 28 pages.
Non-Final Office Action dated Feb. 27, 2018, issued in connection with U.S. Appl. No. 14/864,393, filed Sep. 24, 2015, 19 pages.
Non-Final Office Action dated Feb. 27, 2018, issued in connection with U.S. Appl. No. 15/718,556, filed Sep. 28, 2017, 19 pages.
Non-Final Office Action dated Jul. 27, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 11 pages.
Non-Final Office Action dated Mar. 27, 2017, issued in connection with U.S. Appl. No. 15/211,835, filed Jul. 15, 2016, 30 pages.
Non-Final Office Action dated Mar. 27, 2018, issued in connection with U.S. Appl. No. 15/785,088, filed Oct. 16, 2017, 11 pages.
Non-Final Office Action dated Jul. 28, 2016, issued in connection with U.S. Appl. No. 14/884,001, filed Oct. 15, 2015, 8 pages.
Non-Final Office Action dated Nov. 28, 2017, issued in connection with U.S. Appl. No. 15/673,170, filed Aug. 9, 2017, 7 pages.
Non-Final Office Action dated Sep. 28, 2018, issued in connection with U.S. Appl. No. 15/588,186, filed May 5, 2017, 12 pages.
Non-Final Office Action dated Sep. 28, 2018, issued in connection with U.S. Appl. No. 15/595,519, filed May 15, 2017, 12 pages.
Non-Final Office Action dated Mar. 29, 2018, issued in connection with U.S. Appl. No. 15/716,313, filed Sep. 26, 2017, 16 pages.
Non-Final Office Action dated Aug. 30, 2019, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 13 pages.
Advisory Action dated Jul. 1, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 2 pages.
Advisory Action dated Jul. 10, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 3 pages.
Advisory Action dated Jul. 12, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 3 pages.
Advisory Action dated Jul. 12, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 3 pages.
Advisory Action dated Aug. 16, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 3 pages.
Advisory Action dated Jun. 19, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 3 pages.
Advisory Action dated Sep. 19, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 3 pages.
Advisory Action dated Apr. 30, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 3 pages.
Advisory Action dated Feb. 7, 2019, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 1, 2017, 3 pages.
An Overview of IEEE 1451.4 Transducer Electronic Data Sheets (TEDS) National Instruments, 19 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.
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.
Burger, Dennis, “Automated Room Correction Explained,” hometheaterreview.com, Nov. 18, 2013, Retrieved Oct. 10, 2014, 3 pages.
Chinese Patent Office, First Office Action and Translation dated Jun. 19, 2019, issued in connection with Chinese Application No. 201680054189.X, 11 pages.
Chinese Patent Office, First Office Action dated Aug. 11, 2017, issued in connection with Chinese Patent Application No. 201580013837.2, 8 pages.
Chinese Patent Office, First Office Action dated Nov. 20, 2018, issued in connection with Chinese Application No. 201580047998.3, 21 pages.
Chinese Patent Office, First Office Action dated Sep. 25, 2017, issued in connection with Chinese Patent Application No. 201580013894.0, 9 pages.
Chinese Patent Office, First Office Action dated Nov. 5, 2018, issued in connection with Chinese Application No. 201680044080.8, 5 pages.
Chinese Patent Office, Second Office Action and Translation dated Aug. 26, 2019, issued in connection with Chinese Application No. 201580047998.3, 25 pages.
Chinese Patent Office, Second Office Action dated Jan. 11, 2019, issued in connection with Chinese Application No. 201680044080.8, 4 pages.
Chinese Patent Office, Second Office Action dated Feb. 3, 2019, issued in connection with Chinese Application No. 201580048594.6, 11 pages.
Chinese Patent Office, Second Office Action with Translation dated Jan. 9, 2018, issued in connection with Chinese Patent Application No. 201580013837.2, 10 pages.
Chinese Patent Office, Third Office Action dated Apr. 11, 2019, issued in connection with Chinese Application No. 201580048594.6, 4 pages.
“Constellation Acoustic System: a revolutionary breakthrough in acoustical design,” Meyer Sound Laboratories, Inc. 2012, 32 pages.
“Constellation Microphones,” Meyer Sound Laboratories, Inc. 2013, 2 pages.
Corrected Notice of Allowability dated Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 11 pages.
Daddy, B., “Calibrating Your Audio with a Sound Pressure Level (SPL) Meter,” Blue-ray.com, Feb. 22, 2008 Retrieved Oct. 10, 2014, 15 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 Examination Report dated May 11, 2018, issued in connection with European Application No. 16748186.0, 6 pages.
European Patent Office, European Extended Search Report dated Oct. 16, 2018, issued in connection with European Application No. 17185193.4, 6 pages.
European Patent Office, European Extended Search Report dated Jul. 17, 2019, issued in connection with European Application No. 19167365.6, 7 pages.
European Patent Office, European Extended Search Report dated Jun. 26, 2018, issued in connection with European Application No. 18171206.8, 9 pages.
European Patent Office, European Extended Search Report dated Sep. 8, 2017, issued in connection with European Application No. 17000460.0, 8 pages.
European Patent Office, European Office Action dated Dec. 11, 2018, issued in connection with European Application No. 15778787.0, 6 pages.
European Patent Office, European Office Action dated Jul. 11, 2019, issued in connection with European Application No. 15778787.0, 10 pages.
European Patent Office, European Office Action dated Nov. 2, 2018, issued in connection with European Application No. 18171206.8, 6 pages.
European Patent Office, European Office Action dated Feb. 4, 2019, issued in connection with European Application No. 17703876.7, 9 pages.
European Patent Office, European Office Action dated May 9, 2019, issued in connection with European Application No. 18171206.8, 7 pages.
European Patent Office, European Partial Search Report dated Jun. 7, 2019, issued in connection with European Application No. 19161826.3, 17 pages.
European Patent Office, European Search Report dated Jun. 13, 2019, issued in connection with European Application No. 18204450.3, 11 pages.
European Patent Office, European Search Report dated Sep. 13, 2019, issued in connection with European Application No. 19161826.3, 13 pages.
European Patent Office, European Search Report dated Jan. 18, 2018, issued in connection with European Patent Application No. 17185193.4, 9 pages.
European Patent Office, European Search Report dated Jul. 9, 2019, issued in connection with European Application No. 19168800.1, 12 pages.
European Patent Office, Extended European Search Report dated Jan. 5, 2017, issued in connection with European Patent Application No. 15765555.6, 8 pages.
European Patent Office, Extended European Search Report dated Jan. 25, 2017, issued in connection with European Application No. 15765548.1, 7 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 18, 2016, issued in connection with International Application No. PCT/US2016/043840, filed on Jul. 25, 2016, 14 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2015, issued in connection with International Application No. PCT/US2015/048942, filed on Sep. 8, 2015, 14 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2015, issued in connection with International Application No. PCT/US2015/048944, filed on Sep. 8, 2015, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2016, issued in connection with International Patent Application No. PCT/US2016/052266, filed on Sep. 16, 2016, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Jan. 24, 2017, issued in connection with International Application No. PCT/US2016/052264, filed on Sep. 16, 2016, 17 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 25, 2016, issued in connection with International Application No. PCT/US2016/043109, filed on Jul. 20, 2016, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Sep. 25, 2017, issued in connection with International Application No. PCT/US2017/042191, filed on Jul. 14, 2017, 16 pages.
International Searching Authority, International Search Report and Written Opinion dated Aug. 3, 2017, in connection with International Application No. PCT/US2017014596, 20 pages.
Japanese Patent Office, English Translation of Office Action dated May 8, 2018, issued in connection with Japanese Application No. 2017-513241, 4 pages.
Japanese Patent Office, Japanese Office Action dated Oct. 3, 2017, issued in connection with Japanese Application No. 2017-501082, 7 pages.
Japanese Patent Office, Non-Final Office Action and Translation dated Dec. 10, 2019, issued in connection with Japanese Patent Application No. 2018-213477, 8 pages.
Japanese Patent Office, Non-Final Office Action with Translation dated Apr. 25, 2017, issued in connection with Japanese Patent Application No. 2016-568888, 7 pages.
Japanese Patent Office, Non-Final Office Action with Translation dated Oct. 3, 2017, issued in connection with Japanese Patent Application No. 2017-501082, 3 pages.
Japanese Patent Office, Office Action dated Jun. 12, 2018, issued in connection with Japanese Application No. 2018-502729, 4 pages.
Japanese Patent Office, Office Action dated May 14, 2019, issued in connection with Japanese Patent Application No. 2018-500529, 8 pages.
Japanese Patent Office, Office Action dated Aug. 21, 2018, issued in connection with Japanese Application No. 2018-514418, 7 pages.
Japanese Patent Office, Office Action dated Jul. 24, 2018, issued in connection with Japanese Application No. 2018-514419, 5 pages.
Japanese Patent Office, Office Action dated Jun. 4, 2019, issued in connection with Japanese Patent Application No. 2018-112810, 4 pages.
Japanese Patent Office, Office Action dated May 8, 2018, issued in connection with Japanese Application No. 2017-513241, 8 pages.
Japanese Patent Office, Office Action with English Summary dated Jul. 18, 2017, issued in connection with Japanese Patent Application No. 2017-513171, 4 pages.
Japanese Patent Office, Translation of Office Action dated May 14, 2019, issued in connection with Japanese Patent Application No. 2018-500529, 5 pages.
Jo et al., “Synchronized One-to-many Media Streaming with Adaptive Playout Control,” Proceedings of SPIE, 2002, pp. 71-82, vol. 4861.
John Mark and Paul Hufnagel “What is 1451.4, what are its uses and how does it work?” IEEE Standards Association, The IEEE 1451.4 Standard for Smart Transducers, 14pages.
Jones, Stephen, “Dell Digital Audio Receiver: Digital upgrade for your analog stereo,” Analog Stereo, Jun. 24, 2000 retrieved Jun. 18, 2014, 2 pages.
“AuEQ for the iPhone,” Mar. 25, 2015, retrieved from the internet: URL:https://web.archive.org/web20150325152629/http://www.hotto.de/mobileapps/iphoneaueq.html [retrieved on Jun. 24, 2016], 6 pages.
Louderback, Jim, “Affordable Audio Receiver Furnishes Homes With MP3,” TechTV Vault. Jun. 28, 2000 retrieved Jul. 10, 2014, 2 pages.
Microsoft Corporation, “Using Microsoft Outlook 2003,” Cambridge College, 2003.
Motorola, “Simplefi, Wireless Digital Audio Receiver, Installation and User Guide,” Dec. 31, 2001, 111 pages.
Mulcahy, John, “Room EQ Wizard: Room Acoustics Software,” REW, 2014, retrieved Oct. 10, 2014, 4 pages.
Non-Final Action dated Jan. 29, 2016, issued in connection with U.S. Appl. No. 14/481,511, filed Sep. 9, 2014, 10 pages.
Non-Final Office Action dated Mar. 1, 2017, issued in connection with U.S. Appl. No. 15/344,069, filed Nov. 4, 2016, 20 pages.
Non-Final Office Action dated Nov. 1, 2017, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 15 pages.
Non-Final Office Action dated Jun. 2, 2014, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 14 pages.
Non-Final Office Action dated Jun. 2, 2017, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 18 pages.
Non-Final Office Action dated Nov. 2, 2017, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 12 pages.
Non-Final Office Action dated Oct. 2, 2017, issued in connection with U.S. Appl. No. 15/005,853, filed Jan. 25, 2016, 8 pages.
Non-Final Office Action dated Feb. 3, 2016, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 12 pages.
Non-Final Office Action dated Jul. 3, 2018, issued in connection with U.S. Appl. No. 15/909,327, filed Mar. 1, 2018, 30 pages.
Non-Final Office Action dated Jan. 4, 2017, issued in connection with U.S. Appl. No. 15/207,682, filed Jul. 12, 2016, 6 pages.
Non-Final Office Action dated Nov. 4, 2016, issued in connection with U.S. Appl. No. 14/826,856, filed Aug. 14, 2015, 10 pages.
Non-Final Office Action dated Sep. 4, 2019, issued in connection with U.S. Appl. No. 16/213,552, filed Dec. 7, 2018, 16 pages.
Non-Final Office Action dated Jul. 5, 2017, issued in connection with U.S. Appl. No. 14/481,522, filed Sep. 9, 2014, 8 pages.
Non-Final Office Action dated Jul. 6, 2016, issued in connection with U.S. Appl. No. 15/070,160, filed Mar. 15, 2016, 6 pages.
Non-Final Office Action dated Oct. 6, 2016, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 30 pages.
Non-Final Office Action dated Jun. 6, 2018, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 16 pages.
Non-Final Office Action dated Dec. 7, 2015, issued in connection with U.S. Appl. No. 14/921,762, filed Oct. 23, 2015, 5 pages.
Non-Final Office Action dated Jul. 7, 2016, issued in connection with U.S. Appl. No. 15/066,049, filed Mar. 10, 2016, 6 pages.
Non-Final Office Action dated Mar. 7, 2017, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 24 pages.
Non-Final Office Action dated Sep. 7, 2016, issued in connection with U.S. Appl. No. 14/826,873, filed Aug. 14, 2015, 12 pages.
Non-Final Office Action dated Jul. 8, 2016, issued in connection with U.S. Appl. No. 15/066,072, filed Mar. 10, 2016, 6 pages.
European Patent Office, Extended Search Report dated Apr. 26 2017, issued in connection with European Application No. 15765548.1, 10 pages.
European Patent Office, Office Action dated Nov. 12, 2018, issued in connection with European Application No. 17000460.0, 6 pages.
European Patent Office, Office Action dated Jun. 13, 2017, issued in connection with European patent application No. 17000484.0, 10 pages.
European Patent Office, Office Action dated Dec. 15, 2016, issued in connection with European Application No. 15766998.7, 7 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Nov. 15, 2018, issued in connection with European Application No. 16748186.0, 57 pages.
European Patent Office, Summons to Attend Oral Proceedings dated Sep. 24, 2019, issued in connection with European Application No. 17000460.0, 5 pages.
Ex Parte Quayle Office Action dated Apr. 15, 2019, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 7 pages.
Ex Parte Quayle Office Action dated Dec. 26, 2019, issued in connection with U.S. Appl. No. 16/542,418, filed Aug. 16, 2019, 7 pages.
Final Office Action dated Dec. 2, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 19 pages.
Final Office Action dated Apr. 3, 2017, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages.
Final Office Action dated Jul. 13, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 10 pages.
Final Office Action dated Jun. 13, 2017, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 22 pages.
Final Office Action dated Feb. 14, 2019, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 16 pages.
Final Office Action dated Feb. 14, 2019, issued in connection with U.S. Appl. No. 15/217,399, filed Jul. 22, 2016, 37 pages.
Final Office Action dated Oct. 14, 2016, issued in connection with U.S. Appl. No. 14/682,182, filed Apr. 9, 2015, 16 pages.
Final Office Action dated Oct. 17, 2016, issued in connection with U.S. Appl. No. 14/678,248, filed Apr. 3, 2015, 22 pages.
Final Office Action dated Apr. 18, 2017, issued in connection with U.S. Appl. No. 14/678,263, filed Apr. 3, 2015, 16 pages.
Final Office Action dated Apr. 18, 2018, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 8 pages.
Final Office Action dated Dec. 18, 2014, issued in connection with U.S. Appl. No. 13/340,126, filed Dec. 29, 2011, 12 pages.
Final Office Action dated Jan. 19, 2017, issued in connection with U.S. Appl. No. 14/940,779, filed Nov. 13, 2015, 15 pages.
Final Office Action dated Apr. 2, 2018, issued in connection with U.S. Appl. No. 15/166,241, filed May 26, 2016, 14 pages.
Final Office Action dated Oct. 21, 2016, issued in connection with U.S. Appl. No. 14/696,014, filed Apr. 24, 2015, 13 pages.
Final Office Action dated Jan. 25, 2018, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25, 2016, 17 pages.
Final Office Action dated Mar. 25, 2019, issued in connection with U.S. Appl. No. 15/856,791, filed Dec. 28, 2017, 11 pages.
Final Office Action dated Oct. 28, 2019, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 17 pages.
Final Office Action dated Apr. 3, 2018, issued in connection with U.S. Appl. No. 15/235,598, filed Aug. 12, 2016, 12 pages.
Final Office Action dated Feb. 5, 2018, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 21 pages.
Final Office Action dated Mar. 5, 2019, issued in connection with U.S. Appl. No. 15/056,553, filed Feb. 29, 2016, 9 pages.
Final Office Action dated Dec. 6, 2018, issued in connection with U.S. Appl. No. 15/806,126, filed Nov. 7, 2017, 18 pages.
Final Office Action dated Apr. 9, 2019, issued in connection with U.S. Appl. No. 15/229,693, filed Aug. 5, 2016, 33 pages.
First Action Interview Office Action dated Mar. 3, 2017, issued in connection with U.S. Appl. No. 14/726,921, filed Jun. 1, 2015, 9 pages.
First Action Interview Office Action dated Jul. 12, 2016, issued in connection with U.S. Appl. No. 14/481,514, filed Sep. 9, 2014, 10 pages.
First Action Interview Office Action dated Jun. 30, 2016, issued in connection with U.S. Appl. No. 14/481,505, filed Sep. 9, 2014, 9 pages.
First Action Interview Pilot Program Pre-Interview Communication dated Apr. 5, 2017, issued in connection with U.S. Appl. No. 14/793,190, filed Jul. 7, 2015, 4 pages.
First Action Interview Pilot Program Pre-Interview Communication dated Oct. 7, 2015, issued in connection with U.S. Appl. No. 14/216,306, filed Mar. 17, 2014, 5 pages.
First Action Interview Pilot Program Pre-Interview Communication dated Feb. 16, 2016, issued in connection with U.S. Appl. No. 14/681,465, filed Apr. 8, 2015, 5 pages.
Gonzalez et al., “Simultaneous Measurement of Multichannel Acoustic Systems,” J. Audio Eng. Soc., 2004, pp. 26-42, vol. 52, No. 1/2.
International Bureau, International Preliminary Report on Patentability, dated Sep. 24, 2015, issued in connection with International Application No. PCT/US2014/030560, filed on Mar. 17, 2014, 7 pages.
International Bureau, International Preliminary Report on Patentability, dated Sep. 29, 2016, issued in connection with International Application No. PCT/US2015/020993, filed on Mar. 17, 2015, 8 pages.
International Bureau, International Preliminary Report on Patentability, dated Sep. 29, 2016, issued in connection with International Application No. PCT/US2015/021000, filed on Mar. 17, 2015, 9 pages.
International Bureau, International Preliminary Report on Patentability, dated Aug. 9, 2018, issued in connection with International Application No. PCT/US2017/014596, filed on Jan. 23, 2017, 11 pages.
International Searching Authority, International Preliminary Report on Patentability dated Mar. 23, 2017, issued in connection with International Patent Application No. PCT/US2015/048944, filed on Sep. 8, 2015, 8 pages.
International Searching Authority, International Preliminary Report on Patentability dated Oct. 24, 2017, issued in connection with International Application No. PCT/US2016/028994 filed on Apr. 22, 2016, 7 pages.
International Searching Authority, International Search Report and Written Opinion dated Jul. 4, 2016, issued in connection with International Application No. PCT/US2016/028994, filed on Apr. 22, 2016, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Jul. 5, 2016, issued in connection with International Application No. PCT/US2016/028997, filed on Apr. 22, 2016, 13 pages.
International Searching Authority, International Search Report and Written Opinion dated Jun. 5, 2015, issued in connection with International Application No. PCT/US2015/021000, filed on Mar. 17, 2015, 12 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 12, 2016, issued in connection with International Application No. PCT/US2016/041179 filed on Jul. 6, 2016, 9 pages.
International Searching Authority, International Search Report and Written Opinion dated Jun. 16, 2015, issued in connection with International Application No. PCT/US2015/020993, filed on Mar. 17, 2015, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Nov. 18, 2015, issued in connection with International Application No. PCT/US2015/048954, filed on Sep. 8, 2015, 11 pages.
International Searching Authority, International Search Report and Written Opinion dated Oct. 18, 2016, issued in connection with International Application No. PCT/US2016/043116, filed on Jul. 20, 2016, 14 pages.

Related Publications (1)

	Number	Date	Country
	20200065059 A1	Feb 2020	US

Continuations (1)

	Number	Date	Country
Parent	15229693	Aug 2016	US
Child	16665415		US

Calibration of a playback device based on an estimated frequency response

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract