Patent Grant
10880664
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.
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 what he or she wants in any room that has a networked playback device. Additionally, using the controller, 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.
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:
The drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.
Examples described herein involve updating playback device configuration information based on data collected from playback device calibrations that have been performed. The updated configuration information may result in improved calibrations and sound quality in a given playback device, or perhaps across many playback devices. Other benefits are also possible.
For instance, calibration data may be aggregated by a computing device, such as a server, from the individual calibrations of a plurality of different playback devices located in different respective playback environments. The plurality of playback devices may be numerous, including hundreds of thousands or perhaps even millions of playback devices across the world.
The calibration data received by the computing device may include data associated with the calibration events of each playback device in the plurality of playback devices, such as the date and time of the calibration, the make and model of the calibrated playback device, and/or the target frequency response curve used in the calibration, among other things. The target frequency response curve for a given playback device may correspond to a frequency response that is considered a good-sounding, or pleasing to a typical listener. Thus, each calibration may aim to adjust the equalization settings of the given playback device to meet the target frequency response curve.
The computing device may receive and store the calibration data over time, as more playback devices are calibrated and recalibrated. Additionally, the computing device may receive playback device characteristic information from the plurality of playback devices. This may include information that is not necessarily related to a given calibration event, such as data regarding manual adjustments to a playback devices equalization (EQ) settings made by a user either before or after a calibration event. Other playback device characteristics may include data corresponding to associated user accounts (e.g., geography, age, gender, etc.) or playback history of the playback device and associated data (e.g., listening duration, audio quality, genres, favorites, media sources, etc.). Other possibilities also exist.
After receiving the data discussed above from the plurality of playback devices, the computing device may analyze the received calibration data in conjunction with the received playback device characteristic data to determine what correlations may exist within the data. This may present opportunities for the computing device to take actions based on the data that may improve future calibrations or otherwise improve the overall listening experience among the plurality of playback devices.
For instance, the computing device may determine from the data that a significant number of playback devices sharing one or more of the same playback device characteristics would likely benefit from the same update to the configuration information of the playback device. As one example, the data may indicate that, among a plurality of playback devices of the same model, a similar manual EQ adjustment was frequently performed following a calibration to the target frequency response curve. This may indicate that, for that model of playback device, the target frequency response curve may be improved.
Accordingly, the computing device may determine updated configuration information, including an updated target frequency response curve that incorporates the identified EQ adjustment. The computing device may then transmit the updated configuration information to the plurality of playback devices of that particular model. Each playback device may then use the updated target frequency response in a new calibration, resulting in an improved listening experience. In this way, some configuration updates may be crowd-sourced by identifying trends among calibration data and user behaviors across a large number of playback devices.
Additionally, the computing device may also use the plurality of playback devices to implement comparative testing of proposed configurations, such as a proposed target frequency response curve. For instance, the computing device may transmit two different target frequency response curves to two different populations of playback devices. The playback devices within each population may then be calibrated according to their respective response curve. The computing device may then receive calibration data and playback device characteristic data, including user behaviors that may indicate a level of satisfaction with each target frequency response curve. For instance, one response curve may lead to increased listening frequency and listening duration by users of the first population of playback devices. On the other hand the other response curve may lead to frequent recalibrations and manual EQ adjustments by users in the second population.
In some examples, the computing device may solicit feedback from users of the playback devices within each population, inquiring directly whether a new calibration is satisfying and/or an improvement over a previous calibration. Alternatively, the computing device may transmit both target frequency response curves to be tested to each playback device in the plurality of playback device. The users of each playback device may be presented with audio content played back according to a calibration resulting from the first response curve, and then according to a calibration resulting from the second response curve. The user may then indicate which calibration is preferred, via a control device, for example, and this data may be transmitted to the computing device.
In addition, the computing device may develop new categorizations within the plurality of playback devices for which particular calibration changes may be implemented. In some embodiments, a target frequency response curve may be applied based on trends drawn from the aggregated calibration and characteristic data, rather than being based on the model of the playback device, for instance. As one example, the computing device may determine that playback devices having a playback history and/or music sources indicating a preference for a particular genre of music tend to be similarly adjusted according toward a given EQ. Thus, the computing device may determine a target frequency response curve that corresponds to the given EQ, and may transmit it to playback devices associated with the same genre preference. Other examples are also possible.
The collection, storage, and transmission of data and information discussed may be carried out by a server communicating with a relatively large number of playback devices, as noted above. However, the same actions may be carried out within a single playback system, by one or more of the playback devices and control devices of the individual system, either temporarily or for an extended period of time. For example, calibration data may be aggregated for all playback device calibrations within a single playback system, and may be stored among one or more of the playback devices or other devices within the playback system. The aggregated calibration data may then be analyzed or transmitted to another computing device in communication with multiple playback systems. Other examples are also possible.
Additionally, the transmission of data and information are generally discussed as transmissions between the computing device and one or more playback devices. It should be understood that transmissions may also involve one or more other, intermediate playback devices and/or control devices which may relay the data and information from one device to another.
As indicated above, the examples involve updating playback device configuration information based on data collected from playback device calibrations that have been performed. In one aspect, a computing device is provided. The device includes a processor, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium that, when executed by the processor, cause the computing device to perform functions. The functions include transmitting playback device configuration information to a given playback device and receiving calibration data corresponding to each playback device of a plurality of playback devices. The functions also include receiving playback device characteristic data indicating at least one playback device characteristic for each playback device of the plurality of playback devices. The functions also include, based on at least the received calibration data and the received playback device characteristic data, determining updated playback device configuration information; and transmitting data indicating the updated playback device configuration information to the given playback device.
In another aspect, a method is provided. The method involves transmitting, by at least one computing device, playback device configuration information to a given playback device and receiving, by the at least one computing device, calibration data corresponding to each playback device of a plurality of playback devices. The method also involves receiving, by the at least one computing device, playback device characteristic data indicating at least one playback device characteristic for each playback device of the plurality of playback devices. The method also involves, based on at least the received calibration data and the received playback device characteristic data, determining updated playback device configuration information. The method also involves transmitting data indicating the updated playback device configuration information to the given playback device.
In yet another aspect, a playback device is provided. The device includes a processor, a microphone, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium that, when executed by the processor, cause the playback device to perform functions. The functions include determining configuration information for the playback device and transmitting calibration data to a computing device, where the calibration data comprises data indicating the configuration information. The functions also include transmitting data to the computing device indicating at least one playback device characteristic for the playback device. The functions also include receiving, from the computing device, data indicating updated configuration information and applying the updated configuration information when playing back audio content.
It will be understood by one of ordinary skill in the art that this disclosure includes numerous other embodiments. It will be understood by one of ordinary skill in the art that this disclosure includes numerous other examples. While some examples described herein may refer to functions performed by given actors such as “users” and/or other entities, it should be understood that this description is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.
While some examples described herein may refer to functions performed by given actors such as “users” and/or other entities, it should be understood that this is for purposes of explanation only. The claims should not be interpreted to require action by any such example actor unless explicitly required by the language of the claims themselves.
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
a. Example Playback Devices
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
The playback device 200 may also include one or more microphones 220. The microphone(s) 220 may be used to detect audio data in proximity to the playback device 200, such as voice commands for controlling the playback device 200. Further, the microphone(s) 220 may be used to capture and record audio playback data from the playback device 200, or from one or more other playback devices in proximity to the playback device 200, during a calibration procedure. Other examples and other uses for the microphone(s) 220 are also possible.
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
b. Example Playback Zone Configurations
Referring back to the media playback system 100 of
As shown in
In one example, one or more playback zones in the environment of
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
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 configured to store instructions 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.
The control device 300 may also include one or more microphones 310. The microphone(s) 310 may be used to detect audio data in proximity to the control device 300, such as voice commands for controlling the control device 300. Further, the microphone(s) 310 may be used to capture and record audio playback data from a playback device, such as the playback device 200 shown in
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
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
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
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
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.
As further discussed in the related application Ser. Nos. 14/481,505, 14/481,511, and 14/805,140, which are incorporated herein by reference, an example calibration of a playback device in a playback environment may generally involve the playback device playing back a first audio signal, which is detected and recorded by a microphone as a second audio signal. For instance, the playback device may be the playback device 200 shown in
The first audio signal may be a test or calibration tone having a particular spectral profile. Different test tones may be stored and used based on the particular configuration of the playback device 200, an anticipated genre of music to be played, the particular characteristics of the playback environment (e.g., room size), etc. After detecting the second audio signal, the control device 300 may, in some examples, send data indicating the second audio signal to a computing device. The computing device may be a server that determines, based on the data indicating the second audio signal, an audio processing algorithm for use by the playback device 200 in the playback environment, which may be transmitted back to the playback device 200.
The audio processing algorithm determined for the playback device 200 in a given calibration is based on several inputs. First, each calibration of the playback device 200 may generally aim to calibrate the playback device 200 according to a target frequency response curve. The target frequency response curve may correspond to a frequency response that is considered a good-sounding, or pleasing to a typical listener. The target frequency response curve may vary based on the model of playback device 200 (e.g., size), the orientation of the playback device 200 (e.g., vertical or horizontal), or other configurations states of the playback device 200 (e.g., bonded with another playback device). The computing device may store target frequency response curves in a database for each potential configuration, or they may be stored on the playback device 200, the controller device 300, or more than one of the above.
Further, the microphone that detects the first audio signal, whether it is the microphone 310 on the control device, the microphone 220 on the playback device 200, or a microphone on another playback device, has its own audio characteristics. For example, the response of microphone 310 may depend on the type and model of control device 300 used. The microphone response curve may also be stored in the database on the computing device, or elsewhere. With this information, the second audio signal that is detected by the microphone 310 may be normalized considering the known audio characteristics of the microphone 310. Other known adjustments to the second audio signal may also be applied. For instance, in some cases, the control device 300 may be configured to detect the presence of a protective case, and may obtain from the computing device information regarding the effects of the case on the microphone's audio characteristics. Again, this information may be stored in the database on the computing device. Other possibilities al so exist.
Additionally, the second audio signal detected by the microphone 310 will reflect a frequency response corresponding to the playback environment where the playback device is located. Unlike the configuration of the playback device 200, the target frequency response curve, microphone response curve, and other device-based inputs, which may be generally known, the frequency response of the playback environment may represent an unknown variable in each calibration. For instance, the frequency response of the playback environment may be based on the size of a given room, its construction materials, the furnishings of the room and their location with in the room, among other factors. Consequently, it may be determined empirically during the calibration using the microphone 310.
Based on at least some of the calibration inputs discussed above, the computing device may determine an audio processing algorithm that, when transmitted to and applied by the playback device 200 in the playback environment, will cause audio playback by the playback device 200 to approach or meet the target frequency response curve. More or fewer calibration inputs than those described above may be used. However, to obtain a playback device calibration that is specific to the playback environment, some calibration procedures may require a minimum amount of recorded spectral data from the playback environment for the computing device to determine an accurate response curve for the playback environment. For instance, some calibrations may require 45 seconds of recorded playback of the test tone, which may proceed through a designated series of spectral sweeps. Further, the calibration may require recorded spectral data from multiple locations in the playback environment, necessitating movement of the microphone about the environment by a user, for instance.
The computing device 610 may receive and store in the database additional information relating to each calibration event. The information may be transmitted by each of the playback devices that is calibrated, whether in playback environment 600 or elsewhere. Additionally or alternatively, the information may be transmitted by a control device involved in the calibration. For instance, a given playback device and/or control device may transmit information regarding the date and time of a given calibration, an identification of the playback device including the make, model, and serial number, which may further indicate the “age” of the playback device (since it was manufactured), the zone configuration of the playback device, such as a grouping or pairing state, the software version of the playback device, the hardware and software version of a given control device. Numerous other examples are also possible.
In addition, the computing device 610 may receive and store results from each calibration in the database. For example, the computing device may store the determined response curve for each playback environment in which a playback device is calibrated, including more specific information such as the approximate room size or the proximity of an obstructive object to the playback device, which may be detected by the microphone. Further, the computing device 601 may receive and store the audio processing algorithm that is implemented by each playback device as a result of each calibration. For instance, the computing device 601 may receive and store the specific filter coefficients that are applied by each playback device. As another example, the computing device 601 may receive and store a difference metric for each calibration, which may include an indication of how significantly the sound calibration of the playback device changed as a result of the calibration. The computing device 610 may also receive and store information regarding failed calibration attempts, including the reason for the failure, if known. Other examples are also possible.
In some embodiments, the computing device 610 may be a server that is maintained and operated by the company that sells the playback devices being calibrated, such as SONOS, Inc. Alternatively, a third party may maintain and operate the server on behalf of the playback device company. In other examples, a company may employ the methods described herein across multiple different types of speaker systems, which may include playback devices that are made and sold by various different companies. For example, the server might be operated by an audio content provider, or audio content curating service, among other possibilities.
The calibration information discussed above may be provided to the computing device 610 in a variety of ways. For example, the calibration data may be transmitted to the server directly in real time, during or immediately following each calibration that takes place. However, if there are a relatively large number of calibrations across many devices, this may create bandwidth issues at the computing device 610. Therefore, each playback device may locally store and update a calibration file containing the data discussed above. The calibration file may then be periodically requested (“pulled”) by the computing device 610, perhaps as part of a playback device diagnostic event or a software update. Alternatively, the calibration file may be transmitted (“pushed”) to the computing device 610 by the playback device as part of a diagnostic event or a software update. The calibration file might also be transmitted in response to a manual commend, such as a user input. Other examples are also possible.
In addition to receiving and storing the calibration data, the computing device 610, may also receive and store information from each playback device that is not necessarily related to an individual calibration event. For example, the computing device 610 may receive and store playback device characteristics such as user account(s) data associated with the playback device (e.g., geography, age, gender, etc.), playback history of the playback device and associated data (e.g., listening duration, audio quality, genres, favorites, media sources, etc.) and any manual settings present on the playback device at the time of calibration, such as a manually adjusted equalization (EQ). Other possibilities also exist.
Further, the computing device 610 may receive and store data that may indicate a level of listener satisfaction with each calibration. For instance, if two calibrations for the same device occur in relatively close proximity to each other, with few other variables changing, it may indicate that the listener was dissatisfied with the first calibration. As another example, the computing device may receive an indication that the audio response of the playback device has been manually adjusted following a calibration, which may again indicate that the calibration did not meet the listener's expectations.
On the other hand, the computing device 610 may receive data indicating an increase playback activity following a calibration. This may indicate increased listener satisfaction with the calibration. Further, if the computing device 610 does not receive any recalibration data, nor any data indicating a manual EQ change, it may imply that the user was satisfied. As another example, a survey inquiring whether the listener was satisfied with the calibration, or noticed an improvement, may be provided via an interface of the control device 602. Other measures for determining listener satisfaction with a given calibration also exist.
Finally, although the examples described herein may primarily involve the computing device 601 acting as a centralized server receiving and storing calibration information from numerous playback devices across numerous playback environments, it should be understood that the collection, storage, and transmission of calibration information discussed in all of the examples herein may be carried out within a single playback system, by one or more of the playback devices and controllers of the individual system, either temporarily or for an extended period of time. For example, calibration data may be aggregated for all playback device calibrations within a single playback system, and may be stored among one or more of the playback devices or other devices within the playback system. The aggregated calibration data may then be analyzed or transmitted to another computing device in communication with multiple playback systems. Other examples are also possible.
Additionally, the transmission of data and information noted throughout the examples herein are generally discussed as transmissions between the computing device 701 and one or more playback devices or control devices. It should be understood that transmissions may also involve one or more other, intermediate playback devices and/or control devices which may relay the data and information from one device to another.
a. Updating Playback Device Configuration Information Based on Calibration Data
As noted above, examples discussed herein involve updating playback device configuration information based on data collected from playback device calibrations that have been performed. The updated configuration information may result in improved calibrations and sound quality in a given playback device, or perhaps across many playback devices. Other benefits are also possible.
Methods 500 and 800 shown in
In addition, for the methods 500, 800, 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, for the methods 500, 900 and other processes and methods disclosed herein, each block in
At block 502 of the method 500, a computing device may transmit playback device configuration information to a given playback device. The computing device may be, for instance, the computing device 610 and the given playback device may be the playback device 604 shown in
At block 504, the computing device 610 may receive calibration data corresponding to each playback device of a plurality of playback devices. In particular, the computing device 610 may receive calibration data that corresponds to a respective calibration event associated with each respective playback device in the plurality of playback devices. In some cases, the plurality of playback devices from which the computing device 610 receives calibration data may include the given playback device 604. Further, the plurality of playback devices from which calibration data is received may include not only those playback devices 604 and 606 located in the playback environment 600, but in other playback environments as well. In some cases, the calibration data may be received from hundreds of thousands, perhaps even millions of playback devices located in playback environments around the world.
Along these lines,
The calibration data received by the computing device 701 may include any of the data discussed above that may be transmitted in association with a particular calibration event of a playback device, such as the date and time of the calibration, the make and model number of the calibrated playback device, the target frequency response curve used in the calibration, among other things. The computing device 701 may receive and store the calibration data over time, as more playback devices are calibrated and recalibrated.
In some cases, the computing device 701 may transmit a request for at least a portion of the calibration data from the plurality of playback devices. The computing device 701 may request only a portion of the total calibration data in order to minimize the required data transfer, which may be substantial over a large number of calibrated playback devices. For example, the computing device may request only the determined frequency response curves for the respective playback environment involved in each calibration, in order to analyze that specific aspect of the calibration data.
The computing device 701 may transmit the request for the calibration data to each playback device directly, or it may transmit requests at the media playback system level. Each media playback system, such as the media playback system shown in
At block 506, the computing device 701 may receive playback device characteristic data indicating at least one playback device characteristic for each playback device of the plurality of playback devices. For example, a given playback device characteristic may include a manually adjusted equalization (EQ) setting of the playback device, which may be adjusted by a user. Other playback device characteristics might include the geographic location of the playback device, playback history of the device, details regarding a user profile associated with the device (e.g., age, gender, etc.), among other possibilities.
In some cases, the computing device 701 may receive the both playback device characteristic data and calibration data for a given playback device at the same time, for example, within the same data transfer. Alternatively or additionally, the computing device 701 may receive two separately, in response to requests by the computing device 701, transmissions initiated by a given playback device, or any combination these. For example, playback device characteristic data relating to geography and user demographic data might be transmitted from the plurality of playback devices less frequently than calibration data, as it may be less subject to change over time. As another example, playback characteristic data regarding manually adjusted EQ settings might be received more frequently. For instance, this data may be requested by the computing device both before and after each calibration event, for reasons discussed below. Other examples are also possible.
After receiving the data discussed above from the plurality of playback devices, the computing device 701 may analyze the received calibration data in conjunction with the received playback device characteristic data to determine what correlations may exist within the data. Based on this information, the computing device 701 may take actions to improve future calibrations or otherwise improve the overall listening experience among the plurality of playback devices.
Accordingly, at block 508, based on at least the received calibration data and the received playback device characteristic data, the computing device 701 may determine updated playback device configuration information. For instance, the computing device 701 may determine that, among a plurality of PLAY: 3 model playback devices that used the same target frequency response for the calibration events recorded in the data set, a significant number of those playback devices were subject to a manual EQ adjustment following the calibration.
In some embodiments, the computing device 701 may average all of these manual EQ adjustments and use the determined average as the updated target frequency response for all PLAY: 3 model playback devices. Alternatively, the computing device 701 might analyze the EQ adjustments more specifically. For example, the computing device 701 may determine that among the manual EQ adjustments, a significant number increased the bass response by a certain amount. Based on this information, the computing device may update the target frequency response corresponding to the PLAY: 3 model of playback device to incorporate the increased bass response.
At block 510, the computing device 701 may transmit data indicating the updated playback device configuration information to the given playback device. For example, the given playback device 702 shown in
It is noteworthy that, in some cases, the basis for updating the playback device configuration information might not be apparent if the calibration data and playback device characteristic data of the given playback device 702 are considered in isolation. For instance, with reference to the example above, the given playback device 702 may be a PLAY: 3 model, but it might not have been manually adjusted to increase the bass response following its calibration event(s) recorded in the data set. Nonetheless, the given playback device 702 may be updated based on the data received by the computing device 701 regarding similar or identical playback devices. In this way, a crowd-sourced component for improved playback quality may be implemented, whereby users who do not want to take the time to adjust manual EQ settings, or who might not appreciate how such adjustments may improve in a playback device's frequency response, may benefit from other users who do.
In some cases, the computing device 701 may transmit updated configuration information to the given playback device 702 that may be applied immediately, without any additional calibration. For instance, the computing device 701 may determine an updated target frequency response for the given playback device 702, as noted above. Moreover, because the computing device 701 may have already received calibration data from the given playback device 702 for one or more previous calibrations, the computing device 701 may already have stored in a database the frequency response for the given playback environment 703, the zone configuration and grouping of the given playback device 702, among other calibration data.
Consequently, the computing device 701 may have the information necessary to identify an audio processing algorithm for the given playback device 702 based on the updated target frequency response, without the need for further calibration. Thus, the updated configuration information that is transmitted to the given playback device 702 may include the identified audio processing algorithm. This audio processing algorithm may be applied by the given playback device 702 automatically. In some cases, an indication might be provided to a user that a calibration improvement has been applied. The indication might be provided, for example, via an interface of a control device associated with the given playback device 702.
Alternatively, a user might be given an option to implement the updated configuration information. For instance, a user might be prompted via a control device with a message indicating that “Some other users prefer a higher bass than your current calibration—would you like to increase the bass?” The user may then select whether or not to do so.
As another example, the computing device 701 may determine the updated playback device configuration information based on a particular playback device characteristic. For example, the computing device 701 may determine further data that is correlated with the users who manually increased the bass response following a calibration, so as to define a plurality of playback devices that is more specific than just all PLAY: 3 model playback devices.
For instance, the computing device 701 may determine that the behavior discussed above of increasing the bass response is strongly correlated with playback devices having an associated user profile indicating a user age under 30 years old. Thus, the computing device 701 may transmit the updated playback device configuration information to the given playback device 702 based on the given playback device 702 having that particular playback device characteristic—an associated user profile indicating a user age under 30 years old.
In some embodiments, given the volume of calibrations that may be available for analysis by the computing device 701, it may be possible to test one or more target frequency response curves among the plurality of playback devices. For example, AB testing may be performed to obtain feedback regarding potential target frequency response curves. Accordingly, the computing device 701 may split the plurality of playback devices into two populations and then apply a first target frequency response curve to the playback devices in population A, and a second target frequency response curve to the playback devices in population B.
Feedback from this type of testing may be obtained in a variety of ways. As one example, the plurality of playback devices in each population be monitored such that, after a calibration event of a given playback device according to one of the “test” target frequency response curves, any subsequent manual adjustments to the EQ settings of the given playback device are recorded and analyzed. This type of passive, or “blind” testing between two populations may implicitly indicate that users preferred one response curve over the other, if users made substantially fewer subsequent EQ adjustments in population A, for example. Additionally or alternatively, this testing may provide implicit data suggesting how the target frequency response curves might be improved. For instance, if post-calibration adjustments to the playback devices in population B consistently indicate a user desire to decrease the bass response, it may indicate that the target frequency response curve used in population B has a bass response that is too high.
Further, it may be possible to control for some variables in the testing of target frequency response curves, such as differences between playback devices (e.g., different models, configurations, etc.) or differences in location (e.g., different playback environments). For instance, the computing device 701 may have access to the calibration data, including audio characteristic data, for each of these factors and more, as discussed above. Therefore, it may be able to normalize some of the feedback that is received regarding manual EQ adjustments.
Additionally, the blind AB testing discussed above may also be used to draw inferences about how a particular target frequency response curve influences other user behaviors, in addition to manual EQ adjustments. For example, the computing device 701 may collect data regarding a change in content preferences following a calibration to the particular target frequency response curve. This information might be used to provide suggestions to other uses who may have indicated satisfaction with the particular target frequency response curve, or a similar curve. For instance, a user might be prompted with a suggestion that “Other users like this calibration for listening to jazz music.” Other changes in user behaviors or listening habits may be monitored as well such as listening frequency, duration, volume, etc. Other examples are also possible.
Feedback may also be collected from this type of testing more directly. For example, after a new calibration is applied to a given playback device based on the particular target frequency response curve to be testing, users may be asked if they like the new calibration, and/or what could be done to improve it. Users might be surveyed, for instance, via an interface of an associated control device, which may transmit the results to the computing device 701. Then, the satisfaction levels and suggested improvements between the two populations may be compared. Other possibilities also exist.
As yet another example, the computing device 701 may initiate a more straight-forward variety of AB testing where a given user is presented with both target frequency response curves, and asked which one is preferred. For instance, a given playback device may be calibrated according to a first target frequency response curve, and may then play back a sample audio content. The given playback device may then be recalibrated according to a second target frequency response curve, and may then play back the sample audio content again. The user may be prompted to choose between the two via a control device, as discussed above.
Other types of information may be additionally or alternatively solicited from users regarding a newly implemented target frequency response curve. For instance, a user may be asked to rate how significant of a change he or she perceives the new calibration to have made. The user may be asked via a control device interface, “On a scale of 1 to 5, how big of an impact did the new calibration make?” Results from this type of inquiry across a population of tested playback devices may be used to inform users of the potential effect of a new calibration, if the particular target frequency response curve being tested is later transmitted more broadly. For example, a user might be informed that “Other users have found this new calibration to have a significant impact.” Numerous other examples are also possible.
In some embodiments, the computing device 701 may use the stored calibration data and playback device characteristic data to determine new categorizations of playback devices to which a target frequency response curve might be applied. For instance, the computing device 701 may determine that a certain manual EQ adjustment following calibration is correlated with a particular playback device characteristic. Thus, the computing device 701 may determine a target frequency response curve which incorporates the recurring manual EQ adjustment, and then apply it to playback devices having the correlated characteristic.
For instance, the data that is collected and stored by the computing device 701 may indicate that a significant number of playback devices are manually adjusted to increase the bass response following a calibration to a certain target frequency response curve. Further, the computing device 701 may also determine that this manual EQ adjustment is correlated with playback devices that have, as just one example, a playback history that indicates a strong preference for hip-hop music. Accordingly, the computing device 701 might determine updated configuration information that includes a target frequency response curve with higher bass response, and then transmit it to playback devices sharing the same characteristic of a hip-hop music preference.
Further, the computing device 701 may determine this type of categorization not only at the level of individual playback devices, but perhaps at a more specific level corresponding to different users of a the same playback device. For instance, more than one user account may be associated with a given playback device, and only one of those user accounts may exhibit the strong preference to hip-hop music noted above. Thus, the given playback device may receive the updated configuration information containing the updated target frequency response curve, but may only apply it when playing back audio content from the hip-hop-preferring user account. Other examples are also possible.
As another example, a playback device characteristic such as geography may be used in similar fashion. For instance, the data indicating a manually increased bass response may be correlated with playback devices located in a particular region of the United States, or a particular country or region of the world. Thus, the computing device 701 may determine that similar manual EQ adjustments are made by users in the southern United States, or in the country of Australia. Accordingly, the computing device 701 may assign an appropriately adjusted target frequency response curve to playback devices located that particular geography.
In some further embodiments, the computing device 701 might determine updated configuration data including a target frequency response curve for playback devices on a case-by-case basis, rather than using a broader categorization of playback devices to implement calibration changes.
For instance, the computing device 701 may determine from received data that a particular user of a given playback device has manually adjusted the EQ of the given playback device in the past to increase the bass response. In response, the computing device 701 may update the updated the playback device's target frequency response curve so as to carry forward the previously applied bass increase when the given playback device is calibrated. For example, the bass response in a particular frequency range may be increased by a certain percentage that corresponds to the previously applied manual EQ changes.
Similarly, the computing device 701 may determine from the data, as noted above, that a preference for hip-hop music is correlated with a manual bass increase of a certain amount at associated playback devices. Thus, if a given playback device to be calibrated transmits data to the computing device 701 indicating a preference for hip-hop music, the computing device 701 may adjust the target frequency response curve for the given playback device by increasing the bass response commensurate with the other similar bass increases found in the data set. Numerous other examples are also possible.
In some cases, the computing device 701 may receive data indicating that a user is performing manual EQ adjustments more often than might be considered typical, suggesting dissatisfaction with the user's listening experience. For instance, a user may adjust the manual EQ settings of a playback device more than a threshold amount, such as once a day or once a week. In response, the computing device 701 may provide a suggestion to the user, via a control device, for instance, that a calibration be initiated. During the calibration, the playback device 701 may incorporate the user's manual EQ changes into a target frequency response curve, if the adjustments reveal a consistent user preference. If issues persist, the user might be further prompted to provide feedback regarding why the calibration is not satisfactory.
Finally, although the examples described herein may primarily involve the computing device 701 acting as a centralized server receiving and storing calibration information from numerous playback devices across numerous playback environments, it should be understood that the collection, storage, and transmission of calibration information discussed in all of the examples herein may be carried out within a single playback system, by one or more of the playback devices and controllers of the individual system, either temporarily or for an extended period of time. For example, calibration data may be aggregated for all playback device calibrations within a single playback system, and may be stored among one or more of the playback devices or other devices within the playback system. The aggregated calibration data may then be analyzed or transmitted to another computing device in communication with multiple playback systems. Other examples are also possible.
Additionally, the transmission of data and information noted throughout the examples herein are generally discussed as transmissions between the computing device 701 and one or more playback devices or control devices. It should be understood that transmissions may also involve one or more other, intermediate playback devices and/or control devices which may relay the data and information from one device to another.
b. Receiving Playback Device Configuration Updates Based on Calibration Data
Similar to the above, examples that involve updating playback device configuration information based on data collected from playback device calibrations that have been performed may be discussed form the perspective of the playback device to be calibrated.
At block 802 of the method 800, a playback device may determine configuration information for the playback device. The playback device may be, for instance, the playback device 702 shown in
At block 804, the playback device 702 may transmit calibration data to the computing device 701. The calibration data may include the configuration information, as well as other data related to the calibration event of the playback device 701. For example, the calibration data may include the make and model, zone configuration, and hardware and software version of the playback device 702, among other possibilities.
In some embodiments, the playback device 702 may receive, from the computing device 701, a request for the calibration data. Additionally or alternatively, the playback device 702 may transmit the calibration data each time a calibration is performed, and/or on a periodic schedule, such as once every week or once every month. As discussed in previous examples, the calibration data may be transmitted to the computing device 701 as a calibration file in a way that allows the computing device 701 to manage what may be relatively large amounts of data.
At block 806, the playback device 702 may transmit data to the computing device 701 indicating at last one playback device characteristic for the playback device 702. The characteristic data may include data corresponding to the user accounts associated with the playback device 702, a playback history, or any manual equalization (“EQ”) adjustments that may be applied to the playback device 702, among other examples previously discussed. Further, the playback device characteristic data may be transmitted in conjunction with the calibration data, or it may be transmitted separately, as noted above.
At block 808, the playback device 702 may receive, from the computing device 701, data indicating updated configuration information. As discussed above, the updated configuration information may be determined by the computing device 701 based on calibration data received from a plurality of other playback devices, corresponding to previously performed calibrations.
The updated configuration information may include, for instance, an updated target frequency response curve to be used in a calibration of the playback device 702. Additionally or alternatively, the updated configuration information may include an updated audio processing algorithm, which may be applied by the playback device 702 without the need for further calibration. Other examples are also possible.
Further, the updated configuration information may be based, in part, on a particular playback device characteristic of the playback device 702 that was transmitted to the computing device 701. For example, the playback device 702 may transmit data to the computing device 702 indicating that the playback device 702 has been previously adjusted to manually increase the bass response, or has a playback history indicating a preference for hip-hop music, or both. Thus, the updated configuration information received from the computing device 701 may include an updated target frequency response curve that includes a higher bass response based on one or both of these characteristics. Other possibilities exist, as mentioned in previous examples.
At block 810, the playback device 702 may apply the updated configuration information when playing back audio content. For instance, the playback device 701 may apply an updated target frequency response curve in a subsequent calibration, resulting in a new calibration that may be applied for the play back of audio content. Other examples are also possible.
Finally, as noted throughout, it should be understood that the collection, storage, and transmission of calibration information discussed in all of the examples herein may be carried out within a single playback system, by one or more of the playback devices and controllers of the individual system, either temporarily or for an extended period of time. For example, calibration data may be aggregated for all playback device calibrations within a single playback system, and may be stored among one or more of the playback devices or other devices within the playback system. The aggregated calibration data may then be analyzed or transmitted to another computing device in communication with multiple playback systems. Other examples are also possible.
Additionally, the transmission of data and information noted throughout the examples herein are generally discussed as transmissions between the playback device 702 and the computing device 701. It should be understood that transmissions may also involve one or more other, intermediate playback devices and/or control devices, such as the control device 300, which may relay the data and information from one device to another.
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.
As indicated above, the examples involve updating playback device configuration information based on data collected from playback device calibrations that have been performed. In one aspect, a computing device is provided. The device includes a processor, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium that, when executed by the processor, cause the computing device to perform functions. The functions include transmitting playback device configuration information to a given playback device and receiving calibration data corresponding to each playback device of a plurality of playback devices. The functions also include receiving playback device characteristic data indicating at least one playback device characteristic for each playback device of the plurality of playback devices. The functions also include, based on at least the received calibration data and the received playback device characteristic data, determining updated playback device configuration information; and transmitting data indicating the updated playback device configuration information to the given playback device.
In another aspect, a method is provided. The method involves transmitting, by at least one computing device, playback device configuration information to a given playback device and receiving, by the at least one computing device, calibration data corresponding to each playback device of a plurality of playback devices. The method also involves receiving, by the at least one computing device, playback device characteristic data indicating at least one playback device characteristic for each playback device of the plurality of playback devices. The method also involves, based on at least the received calibration data and the received playback device characteristic data, determining updated playback device configuration information. The method also involves transmitting data indicating the updated playback device configuration information to the given playback device.
In yet another aspect, a playback device is provided. The device includes a processor, a microphone, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium that, when executed by the processor, cause the playback device to perform functions. The functions include determining configuration information for the playback device and transmitting calibration data to a computing device, where the calibration data comprises data indicating the configuration information. The functions also include transmitting data to the computing device indicating at least one playback device characteristic for the playback device. The functions also include receiving, from the computing device, data indicating updated configuration information and applying the updated configuration information when playing back audio content.
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.
The present application is a continuation of U.S. application Ser. No. 15/859,311 filed Dec. 29, 2017, which is a continuation of U.S. application Ser. No. 15/088,994 filed Apr. 1, 2016, the disclosures of which are explicitly incorporated by reference herein in their entirety. The present application also incorporates by reference U.S. patent application Ser. No. 14/481,505, filed on Sep. 9, 2014, for “Audio Processing Algorithms;” U.S. patent application Ser. No. 14/481,511, filed on Sep. 9, 2014, for “Playback Device Calibration;” U.S. patent application Ser. No. 14/805,140, filed on Jul. 21, 2015, for “Hybrid Test Tone for Space-Averaged Room Audio Calibration Using a Moving Microphone;” and U.S. patent application Ser. No. 15/089,004, filed on Apr. 1, 2016, for “Playback Device Calibration Based on Representative Spectral Characteristics.”
| 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 et al. | 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 et al. | 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 |
| 8995688 | Chemtob et al. | Mar 2015 | B1 |
| 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 |
| 9729984 | Tan 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 | Jan 2018 | B2 |
| 9864574 | Hartung et al. | Jan 2018 | B2 |
| 9910634 | Sheen et al. | Mar 2018 | B2 |
| 9913056 | Master 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 |
| 10402154 | Hartung et al. | Sep 2019 | B2 |
| 10405116 | Jarvis | Sep 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 et al. | 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 |
| 20040114771 | Vaughan et al. | Jun 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 et al. | 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 et al. | 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 et al. | 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 |
| 20110293123 | Neumeyer et al. | Dec 2011 | A1 |
| 20120032928 | Alberth et al. | Feb 2012 | A1 |
| 20120051558 | Kim et al. | Mar 2012 | A1 |
| 20120057724 | Rabinowitz et al. | 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 |
| 20120184335 | Kim 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 |
| 20130019193 | Rhee 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 et al. | Jun 2013 | A1 |
| 20130170647 | Reilly et al. | Jul 2013 | A1 |
| 20130179535 | Baalu 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 et al. | Jan 2014 | A1 |
| 20140003626 | Holman et al. | Jan 2014 | A1 |
| 20140003635 | Mohammad et al. | Jan 2014 | A1 |
| 20140006587 | Kusano | 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 et al. | Mar 2014 | A1 |
| 20140086423 | Domingo 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 |
| 20140364056 | Belk 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 et al. | 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 |
| 20150286360 | Wachter | 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 |
| 20160014511 | Sheen 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 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 et al. | Jul 2016 | A1 |
| 20160239255 | Chavez et al. | Aug 2016 | A1 |
| 20160254696 | Plumb et al. | Sep 2016 | A1 |
| 20160260140 | Shirley et al. | Sep 2016 | A1 |
| 20160309276 | Ridihalgh et al. | Oct 2016 | A1 |
| 20160330562 | Crockett | Nov 2016 | A1 |
| 20160353018 | Anderson et al. | Dec 2016 | A1 |
| 20160366517 | Chandran et al. | Dec 2016 | A1 |
| 20170069338 | Elliot et al. | Mar 2017 | A1 |
| 20170083279 | Sheen et al. | 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 et al. | Oct 2017 | A1 |
| 20170311108 | Patel et al. | Oct 2017 | A1 |
| 20170374482 | McPherson et al. | Dec 2017 | A1 |
| 20180122378 | Mixter et al. | May 2018 | A1 |
| 20190037328 | McPherson et al. | Jan 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 1447624 | Oct 2003 | CN |
| 1984507 | Jun 2007 | CN |
| 101366177 | Feb 2009 | CN |
| 101491116 | Jul 2009 | CN |
| 101681219 | Mar 2010 | CN |
| 102318325 | Jan 2012 | CN |
| 102893633 | Jan 2013 | CN |
| 103491397 | Jan 2014 | CN |
| 103988523 | Aug 2014 | CN |
| 104284291 | Jan 2015 | 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 |
| 2874413 | May 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 |
| H10307592 | Nov 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 |
| 2006340285 | Dec 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 |
| 2013247456 | Dec 2013 | 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 |
| Entry |
|---|
| 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. 7, 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 Search Report dated Jan. 25, 2017, issued in connection with European Application No. 15765548.1, 7 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. 14, 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. |
| 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 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 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 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 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 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 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 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 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 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 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 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 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 Jul. 20, 2016, 14 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 Jul. 25, 2016, 14 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. |
| U.S. Appl. No. 60/490,768, filed Jul. 28, 2003, entitled “Method for synchronizing audio playback between multiple networked devices,” 13 pages. |
| U.S. Appl. No. 60/825,407, filed Sep. 12, 2006, entitled “Controlling and manipulating groupings in a multi-zone music or media system,” 82 pages. |
| UPnP; “Universal Plug and Play Device Architecture,” Jun. 8, 2000; version 1.0; Microsoft Corporation; pp. 1-54. |
| 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 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. |
| 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 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. |
| 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. |
| International Searching Authority, International Search Report and Written Opinion dated Nov. 23, 2015, issued in connection with International Application No. PCT/US2015/048942, filed 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 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 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 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 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 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 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. |
| 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. |
| 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. 7, 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. 1, 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. |
| Advisory Action dated Jun. 3, 2020, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 3 pages. |
| Chinese Patent Office, First Office Action and Translation dated Jun. 29, 2020, issued in connection with Chinese Application No. 201780057093.3, 11 pages. |
| Chinese Patent Office, First Office Action and Translation dated Aug. 4, 2020, issued in connection with Chinese Application No. 201910395715.4, 22 pages. |
| Chinese Patent Office, Office Action dated Nov. 14, 2019, issued in connection with Chinese Application No. 201680040086.8, 9 pages. |
| Chinese Patent Office, Second Office Action dated May 6, 2020, issued in connection with Chinese Application No. 201680040086.8, 3 pages. |
| European Patent Office, European Extended Search Report dated Mar. 16, 2020, issued in connection with European Application No. 19209551.1, 7 pages. |
| European Patent Office, European Extended Search Report dated Mar. 25, 2020, issued in connection with European Application No. 19215348.4, 10 pages. |
| European Patent Office, European Office Action dated Aug. 19, 2020, issued in connection with European Application No. 17754501.9, 6 pages. |
| European Patent Office, European Office Action daed Jan. 3, 2020, issued in connection with European Application No. 17703876.7, 8 pages. |
| European Patent Office, European Office Action dated Jul. 9, 2020, issued in connection with European Application No. 19167365.6, 4 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 Mar. 3, 2020, issued in connection with U.S. Appl. No. 16/115,525, filed Aug. 28, 2018, 13 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, Office Action and Translation dated Jun. 12, 2020, issued in connection with Japanese Patent Application No. 2019-056360, 6 pages. |
| Japanese Patent Office, Office Action dated Feb. 4, 2020, issued in connection with Japanese Patent Application No. 2018-500529, 6 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 Mar. 12, 2020, issued in connection with U.S. Appl. No. 16/796,496, filed Feb. 20, 2020, 13 pages. |
| Non-Final Office Action dated Mar. 13, 2020, issued in connection with U.S. Appl. No. 15/005,496, filed Jan. 25. 2016, 20 pages. |
| Non-Final Office Action dated Aug. 18, 2020, issued in connection with U.S. Appl. No. 16/827,143, filed Mar. 23, 2020, 8 pages. |
| Non-Final Office Action dated Feb. 19, 2020, issued in connection with U.S. Appl. No. 16/665,415, filed Oct. 28, 2019, 53 pages. |
| Non-Final Office Action dated Jun. 19, 2020, issued in connection with U.S. Appl. No. 16/403,077, filed May 3, 2019, 6 pages. |
| Non-Final Office Action dated Jun. 22, 2020, issued in connection with U.S. Appl. No. 16/555,832, filed Aug. 29, 2019, 15 pages. |
| Non-Final Office Action dated Mar. 4, 2020, issued in connection with U.S. Appl. No. 15/966,534, filed Apr. 30, 2018, 11 pages. |
| Non-Final Office Action dated Jul. 6, 2020, issued in connection with U.S. Appl. No. 16/812,618, filed Mar. 9, 2020, 15 pages. |
| Notice of Allowance dated Jun. 10, 2020, issued in connection with U.S. Appl. No. 16/713,858, filed Dec. 13, 2019, 8 pages. |
| Notice of Allowance dated Apr. 13, 2020, issued in connection with U.S. Appl. No. 16/181,865, filed Nov. 6, 2018, 10 pages. |
| Notice of Allowance dated Jul. 14, 2020, issued in connection with U.S. Appl. No. 16/556,297, filed Aug. 30, 2019, 11 pages. |
| Notice of Allowance dated Jul. 16, 2020, issued in connection with U.S. Appl. No. 16/530,324, filed Aug. 2, 2019, 9 pages. |
| Notice of Allowance dated Mar. 2, 2020, issued in connection with U.S. Appl. No. 16/213,552, filed Dec. 7, 2018, 9 pages. |
| Notice of Allowance dated Mar. 23, 2020, issued in connection with U.S. Appl. No. 16/542,418, filed Aug. 16, 2019, 5 pages. |
| Notice of Allowance dated Jul. 24, 2020, issued in connection with U.S. Appl. No. 16/665,415, filed Oct. 28, 2019, 12 pages. |
| Notice of Allowance dated Mar. 31, 2020, issued in connection with U.S. Appl. No. 16/538,629, filed Aug. 12, 2019, 9 pages. |
| Notice of Allowance dated Feb. 4, 2020, issued in connection with U.S. Appl. No. 16/416,619, filed May 20, 2019, 7 pages. |
| Notice of Allowance dated Aug. 6, 2020, issued in connection with U.S. Appl. No. 16/564,684, filed Sep. 9, 2019, 8 pages. |
| Notice of Allowance dated Jun. 8, 2020, issued in connection with U.S. Appl. No. 16/658,896, filed Oct. 21, 2019, 8 pages. |
| Notice of Allowance dated Apr. 9, 2020, issued in connection with U.S. Appl. No. 16/416,593, filed May 20, 2019, 9 pages. |
| Notice of Allowance dated Jun. 9, 2020, issued in connection with U.S. Appl. No. 15/966,534, filed Apr. 30, 2018, 16 pages. |
| Yamaha DME Designer 3.0 Owner's Manual; Copyright 2008, 501 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190387337 A1 | Dec 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15859311 | Dec 2017 | US |
| Child | 16555846 | US | |
| Parent | 15088994 | Apr 2016 | US |
| Child | 15859311 | US |
