Patent Grant
11941319
This relates generally to audio output systems, including but not limited to systems for selecting audio output modes on audio output devices that are in communication with electronic devices, optionally via user interfaces displayed on the electronic devices.
Audio output devices, including wearable audio output devices such as headphones, earbuds, and earphones, are widely used to provide audio outputs to a user.
But conventional methods for playing audio on wearable audio output devices are limited in the types of audio output modes in which the wearable audio output devices can output audio. For example, conventionally-used audio output modes, such as stereo and mono audio output modes, provide audio with respect to a frame of reference that is tied to the audio output devices, which can make the listening experience less immersive and less realistic than the listening experience provided when outputting audio using a spatial audio output mode, which simulates a more realistic listening experience in which audio seems to come from sources of sound in a separate frame of reference, such as the physical environment surrounding the user. Furthermore, an audio output device (e.g., a wearable audio output device) that supports a spatial audio output mode, in which the positioning of simulated sources of sound is independent of movement of the audio output devices or the user, enables the realistic and immersive aspects of a public listening experience while also providing the non-intrusiveness of a private listening experience. Moreover, conventional methods of selecting an active audio output mode for an audio output device fail to audibly and visually illustrate the differences between different available types of audio modes. Conventional methods of selecting audio output modes also fail to save audio output settings that have been selected for a particular context (e.g., for a respective application, for a respective set of audio output device, for a respective user, etc.) for future use, requiring a user to select the same settings again at a later time. In addition, conventional methods take longer and require more user interaction than necessary, which results in increased user mistakes and, more generally, wasted energy. These latter considerations are particularly important in battery-operated devices.
Accordingly, there is a need for audio output devices and associated electronic devices with improved methods and interfaces for selecting between different audio output modes for a set of one or more wearable audio output devices, and for providing feedback to aid a user in making such a selection. Such methods and interfaces optionally complement or replace conventional methods for selecting audio output modes. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated systems and devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices in communication with a set of one or more wearable audio output devices are reduced or eliminated by the disclosed devices. In some embodiments, the electronic device is a desktop computer. In some embodiments, the electronic device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the electronic device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the electronic device has a touchpad. In some embodiments, the electronic device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the electronic device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music/audio playing, note taking, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device that is in communication with one or more display devices, one or more input devices, and a set of one or more wearable audio output devices. The method includes displaying, via one or more display devices, a user interface for determining whether or not to enable a respective audio output mode for the set of one or more wearable audio output devices for a respective type of audio content. The method includes, while displaying the user interface, concurrently outputting, via the set of one or more wearable audio output devices, first audio using a first audio output mode while displaying in the user interface, via the one or more display devices, a first visual indication that the first audio output mode is being used for the first audio. The method includes, while displaying the user interface and outputting the first audio using the first audio output mode, receiving, via the one or more input devices, a request to switch to using a second audio output mode. The method includes, in response to the electronic device receiving the request to switch to using the second audio output mode, concurrently outputting, via the set of one or more wearable audio output devices, second audio using the second audio output mode while displaying in the user interface, via the one or more display devices, a second visual indication that the second audio output mode is being used for the second audio. The second visual indication is different from the first visual indication. The method includes, while concurrently outputting the second audio using the second audio output mode and displaying the second visual indication that the second audio output mode is being used, detecting, via the one or more input devices, an input directed to the user interface. The method includes, in response to detecting the input directed to the user interface, selecting, based on the input, one of the first audio output mode or the second audio output mode as an active audio output mode for the respective type of audio content.
In accordance with some embodiments, a method is performed at an electronic device that is in communication with one or more display devices and one or more input devices. The method includes, while displaying, via the one or more display devices, a first user interface of the electronic device, the electronic device receives, via the one or more input devices, a sequence of one or more inputs that corresponds to a request to display an audio settings user interface. The method includes, in response to the electronic device receiving the sequence of one or more inputs, displaying, via the one or more display devices, the audio settings user interface. The audio settings user interface includes a first user interface element that is activatable to change whether a first audio output mode of one or more audio output devices that are in communication with the electronic device is enabled. Displaying the audio settings user interface includes: in accordance with a determination that the first audio output mode is enabled and that the electronic device is causing respective audio that is configured for output using the first audio output mode to be output using the first audio output mode via one or more audio output devices that are in communication with the electronic device, displaying the first user interface element concurrently with a first visual indication that the first audio output mode is being used; and, in accordance with a determination that the first audio output mode is enabled and that the electronic device is not causing respective audio to be output using the first audio output mode via one or more audio output devices that are in communication with the electronic device, displaying the first user interface element without displaying the first visual indication that the first audio output mode is being used.
In accordance with some embodiments, a method of playing audio is performed at a computer system that is in communication with a display generation component, one or more input devices, and a set of one or more audio output devices. The method includes, while a first application is causing output of audio information to the set of one or more audio output devices, causing output of the audio information from the first application to the set of one or more audio output devices in accordance with a first audio output mode previously selected for the first application using a system audio output setting control. The method includes, after causing output of audio information from the first application via the set of one or more audio output devices in accordance with the first audio output mode, receiving a request to play audio from a second application different from the first application. The method includes, in response to receiving the request to play audio from the second application, causing output of audio information from the second application to the set of one or more audio output devices, which includes: in accordance with a determination that a second audio output mode, different from the first audio output mode, was previously selected for the second application using the system audio output setting control, causing output of the audio information from the second application via the set of one or more audio output devices in accordance with the second audio output mode.
In accordance with some embodiments an electronic device (or, as alternatively used herein, a computer system) includes or is in communication with one or more display devices, one or more input devices, one or more audio output devices, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more tactile output generators, one or more processors, and memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which, when executed by an electronic device as described herein cause the electronic device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device as described herein includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device as described herein includes means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device as described herein includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices that include or are in communication with one or more display devices, one or more input devices, one or more audio output devices, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more tactile output generators are provided with improved methods and interfaces for selecting audio output modes of the one or more audio output devices, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for selecting audio output modes.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
As noted above, audio output devices such as wearable audio output devices are widely used to provide audio outputs to a user. Many electronic devices that include or are in communication with audio output devices fail to provide a quick way of selecting between audio output modes, fail to save previously selected audio output settings, and/or fail to provide sufficient feedback to aid a user in selecting a desired audio output mode. The methods, systems, and user interfaces/interactions described herein improve in multiple ways how audio output modes are selected. For example, embodiments disclosed herein describe improved ways of demonstrating different available audio output modes and of enabling and disabling specific audio output modes.
The processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual, audio, and/or haptic feedback to the user, reducing the number of inputs needed to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes or is in communication with one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick. In some embodiments, the touch-sensitive surface and/or the other aforementioned physical user-interface devices are replaced by or supplemented by a voice recognition device or subsystem for receiving orally delivered user inputs, and/or a user gaze determination device or subsystem that determines a location (e.g., in a user interface, or in a two or three dimensional environment) or sequence of locations at which a user is gazing or focusing.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. Using tactile outputs to provide haptic feedback to a user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, a tactile output pattern specifies characteristics of a tactile output, such as the amplitude of the tactile output, the shape of a movement waveform of the tactile output, the frequency of the tactile output, and/or the duration of the tactile output.
When tactile outputs with different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate tactile outputs), the tactile outputs may invoke different haptic sensations in a user holding or touching the device. While the sensation of the user is based on the user's perception of the tactile output, most users will be able to identify changes in waveform, frequency, and amplitude of tactile outputs generated by the device. Thus, the waveform, frequency and amplitude can be adjusted to indicate to the user that different operations have been performed. As such, tactile outputs with tactile output patterns that are designed, selected, and/or engineered to simulate characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behaviors (e.g., oscillation, displacement, acceleration, rotation, expansion, etc.); and/or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface that includes graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and/or a combination of any of the above) will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, tactile outputs are, optionally, generated to correspond to feedback that is unrelated to a simulated physical characteristic, such as an input threshold or a selection of an object. Such tactile outputs will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device.
In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue for the occurrence of an event of interest in a user interface or behind the scenes in a device. Examples of the events of interest include activation of an affordance (e.g., a real or virtual button, or toggle switch) provided on the device or in a user interface, success or failure of a requested operation, reaching or crossing a boundary in a user interface, entry into a new state, switching of input focus between objects, activation of a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, tactile outputs are provided to serve as a warning or an alert for an impending event or outcome that would occur unless a redirection or interruption input is timely detected. Tactile outputs are also used in other contexts to enrich the user experience, improve the accessibility of the device to users with visual or motor difficulties or other accessibility needs, and/or improve efficiency and functionality of the user interface and/or the device. Tactile outputs are optionally accompanied with audio outputs and/or visible user interface changes, which further enhance a user's experience when the user interacts with a user interface and/or the device, and facilitate better conveyance of information regarding the state of the user interface and/or the device, and which reduce input errors and increase the efficiency of the user's operation of the device.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In some embodiments, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (e.g., touchpad 355 discussed below with reference to
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.
The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensity of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).
Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have a criteria that is met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by haptic feedback controller 161) to produce tactile outputs using tactile output generator(s) 167 at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video and music player module 152. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204 (sometimes called home button 204), push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensities of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (
Each of the above-identified elements in
In some embodiments, wearable audio output device 301 includes audio I/O logic 312, which determines the positioning or placement of wearable audio output device 301 relative to a user's ear based on information received from placement sensor(s) 304, and, in some embodiments, audio I/O logic 312 controls the resulting conditional outputting of audio. In some embodiments, wearable audio output device 301 includes a wireless interface 315 for communication with one or more multifunction devices, such as device 100 (
In some embodiments, wearable audio output device 301 includes one or more microphones 302 for receiving audio input. In some embodiments, microphone(s) 302 detect speech from a user wearing wearable audio output device 301 and/or ambient noise around wearable audio output device 301. In some embodiments, as described in more detail herein with reference to
In some embodiments, wearable audio output device 301 includes one or more input devices 308. In some embodiments where wearable audio output device 301 includes multiple (e.g., a pair) of wearable audio output components (e.g., earphones, earbuds, or earcups), each component includes one or more respective input devices. In some embodiments, input device(s) 308 includes a pressure-sensitive (e.g., intensity-sensitive) input device, which in some embodiments is located within a portion of wearable audio output device 301, sometimes called a “stem,” that physically extends from a portion of wearable audio output device 301 that is configured to be inserted in a user's ear (e.g., stem 305 as shown in
In some embodiments, ambient sound waveform 322 is compared to attenuated ambient sound waveform 324 (e.g., by wearable audio output device 301 or a component of wearable audio output device 301, such as audio I/O logic 312, or by an electronic device that is in communication with wearable audio output device 301) to determine the passive attenuation provided by wearable audio output device 301. In some embodiments, the amount of passive attenuation provided by wearable audio output device 301 is taken into account when providing the antiphase audio signal to cancel ambient sound from the surrounding physical environment. For example, antiphase audio signal waveform 326-2 is configured to cancel attenuated ambient sound waveform 324 rather than unattenuated ambient sound waveform 322.
In some embodiments, wearable audio output device 301 is configured to operate in one of a plurality of available audio output modes, such as an active noise control audio output mode, an active pass-through audio output mode, and a bypass audio output mode (also sometimes called a noise control off audio output mode). In the active noise control mode (also called “ANC”), wearable audio output device 301 outputs one or more audio-cancelling audio components (e.g., one or more antiphase audio signals, also called “audio-cancellation audio components”) to at least partially cancel ambient sound from the surrounding physical environment that would otherwise be perceivable to the user. In the active pass-through audio output mode, wearable audio output device 301 outputs one or more pass-through audio components (e.g., plays at least a portion of the ambient sound from outside the user's ear, received by microphone 302-1, for example) so that the user can hear a greater amount of ambient sound from the surrounding physical environment than would otherwise be perceivable to the user (e.g., a greater amount of ambient sound than would be audible with the passive attenuation of wearable audio output device 301 placed in the user's ear). In the bypass mode, active noise management is turned off, such that wearable audio output device 301 outputs neither any audio-cancelling audio components nor any pass-through audio components (e.g., such that any amount of ambient sound that the user perceives is due to physical attenuation by wearable audio output device 301).
In some embodiments, wearable audio output device 301b represents a set of headphones with on-ear earcups to be worn on a user's ears, or over-ear earcups to be worn over a user's ears, rather than one or more earbuds to be worn in the user's ears. In some such embodiments, the earcups act as the physical barriers that block at least some ambient sound from the surrounding physical environment from reaching the user's ear. At least one of the earcups includes microphones 302-1 and 302-2 to detect, respectively, ambient sound in the physical environment (corresponding to ambient sound in region 316, represented by waveform 322 in
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on characteristics of the input, such as the duration of the input or the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental recognition of deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria. Alternatively, in some embodiments, for some light press inputs, the duration of the input exceeding a first threshold amount of time (e.g., since the input was detected) triggers a first response; and in some embodiments, for some deep press inputs, the duration of the input exceeding a second threshold amount of time (e.g., since the input was detected), greater than the first threshold amount of time, triggers a second response different from the first response.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. No. 14/399,606 and Ser. No. 14/624,296, which are incorporated by reference herein in their entireties.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device (e.g., portable multifunction device 100 (
A spatial audio output mode is a mode that allows audio that is output from the earbuds 502 to sound as though the audio is coming from one or more locations (e.g., one or more sources of sound) in a frame of reference, such as a physical environment (e.g., a surround sound effect), where the positioning of the one or more simulated or perceived sources of sound is independent of movement of earbuds 502 relative to the frame of reference. Typically, the one or more perceived sound sources, when fixed, are fixed relative to the frame of reference, and, when moving, move relative to the frame of reference. For example, where the frame of reference is a physical environment, the one or more perceived sound sources have respective spatial locations in the physical environment. As earbuds 502 move about the physical environment, the audio output from earbuds 502 is adjusted so that the audio continues to sound as though it is coming from the one or more perceived sound sources at the respective spatial locations in the physical environment. Where the one or more perceived sound sources are moving sources that move through a sequence of spatial locations about the physical environment, the audio output from earbuds 502 is adjusted so that the audio continues to sound as though it is coming from the one or more perceived sound sources at the sequence of spatial locations in the physical environment. Such adjustment for moving sound sources also takes into account any movement of earbuds 502 relative to the physical environment (e.g., if earbuds 502 move relative to the physical environment along an analogous path as the moving source of sound so as to maintain a constant spatial relationship with the source of sound, the audio would be output so that the sound does not appear to move relative to earbuds 502).
In some embodiments, the frame of reference for the spatial audio effect is fixed to an electronic device, such as device 100, that is outputting audio via earbuds 502 (e.g., the sound follows the device), and is referred to herein as the “follow device” feature. For example, locations of the simulated sources of the audio in a physical environment move corresponding to movement of device 100 in the physical environment. This feature may be useful when the user is traveling in a vehicle or other mode of transportation, or walking, or the like and the device is moving along with the user, so the audio moves along with the device and the user in the vehicle, or in situations where the device is moving relative to the audio output device(s) and is associated with visual content playing on the device, so that the simulated sources of sound are located at virtual locations that correspond to the location of the device as it moves around the physical environment. When the follow device feature is not enabled, the audio output does not follow the movement of device 100. For example, spatial audio is positioned relative to a frame of reference that is not fixed to device 100 (e.g., such that the spatial audio is not moved based on movement of device 100 even as device 100 moves relative to the frame of reference), and non-spatial stereo or mono audio is positioned relative to the position of the earbuds, and is not moved based on device 100 being moved.
In
Audio settings user interface 610 in
To aid in understanding the circumstances associated with how audio settings user interface 610 is presented in
As described below, method 700 provides on an electronic device an improved user interface for demonstrating different audio output modes for outputting audio content of a particular type via a set of one or more wearable audio output devices (e.g., on-ear or over-ear headphones, or a pair of earbuds or earphones), to illustrate the operation of the different audio output modes and help the user understand how outputting audio using one audio output mode differs from outputting audio using another audio output mode prior to selecting a respective mode as the active audio output mode for the particular type of audio content. Demonstrating different audio output modes for a particular type of audio content, particularly during a setup process for the set of one or more wearable audio output devices, helps the user to quickly choose between different audio output modes with less trial and error during later use of the electronic device and set of one or more wearable audio output devices. Providing to the user improved feedback, or an improved audio mode selection user interface, and reducing the number of inputs needed to use different control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
The electronic device displays (704), via the one or more display devices, a user interface for determining whether or not to enable a respective audio output mode (e.g., whether or not to enable spatial audio) for the set of one or more wearable audio output devices for a respective type of audio content (e.g., the user interfaces shown in
In some embodiments, while displaying the user interface, the electronic device concurrently outputs (706), via the set of one or more wearable audio output devices, first audio using a first audio output mode while displaying in the user interface, via the one or more display devices, a first visual indication that the first audio output mode is being used for the first audio (e.g., stereo audio simulation 538 in
In some embodiments, while displaying the user interface and outputting the first audio using the first audio output mode, the electronic device receives (708), via the one or more input devices, a request to switch to using a second audio output mode. In some embodiments, when the first audio output mode is a spatial audio output mode, the second audio output mode is a non-spatial audio output mode (e.g., the request to switch to using the second audio output mode is an input on stereo audio user interface element 536 in
In some embodiments, in response to receiving the request to switch to using the second audio output mode, the electronic device concurrently outputs (710), via the set of one or more wearable audio output devices, second audio using the second audio output mode while displaying in the user interface, via the one or more display devices, a second visual indication that the second audio output mode is being used for the second audio. In some embodiments, the second visual indication is different from the first visual indication. For example, where the first audio output mode is a stereo audio output mode, and the second audio output mode is a spatial audio output mode, the second visual indication may be a spatial audio simulation, such as spatial audio simulation 546 in
In some embodiments, while concurrently outputting the second audio using the second audio output mode and displaying the second visual indication that the second audio output mode is being used, the electronic device detects (712), via the one or more input devices, an input (e.g., input 550 over “Use Spatial Audio” button 540 in
In some embodiments, in response to detecting the input directed to the user interface, the electronic device selects (714), based on the input, one of the first audio output mode or the second audio output mode as an active audio output mode for the respective type of audio content (e.g., when the device is causing an audio output device to output the respective type of audio content). For example, in response to detecting input 550 in
In some embodiments, the first audio output mode is (716) a non-spatial audio output mode (e.g., as illustrated in
In some embodiments, for the spatial audio output mode, audio signal processing is performed to compute and adjust audio signals for output so that a user (e.g., an average user) will perceive the sound of the audio output to be coming from one or more simulated locations in the frame of reference (e.g., not limited to a location within the user's head). In some embodiments, the audio signal processing of the audio signals is performed by the electronic device, by the one or more wearable audio output devices, or by a combination of the electronic device and the one or more wearable audio output devices (e.g., in part by the electronic device and in part by the one or more wearable audio output devices).
In some embodiments, a non-spatial audio output mode is an audio output mode where audio of the set of one or more wearable audio output devices is not adjusted as the set of one or more wearable audio output devices is moved relative to the frame of reference (e.g., relative to a physical environment or relative to a displayed user interface corresponding to the one or more sources of sound, such as the display of a device or a projected user interface) (e.g., resulting in not maintaining the one or more sources of sound in a substantially fixed position relative to the frame of reference).
Demonstrating different audio output modes for a particular type of audio content, such as demonstrating spatial and non-spatial audio output modes for spatial audio content, by allowing the user to easily switch between the different audio output modes helps the user to quickly choose between the different audio output modes with less trial and error during later use of the electronic device and set of one or more wearable audio output devices. Providing to the user improved feedback, or an improved audio mode selection user interface, and reducing the number of inputs needed to use different control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the first audio output mode is (718) a spatial audio output mode (e.g., as illustrated in
Demonstrating different audio output modes for a particular type of audio content, such as demonstrating spatial and non-spatial audio output modes for spatial audio content, by allowing the user to easily switch between the different audio output modes helps the user to quickly choose between the different audio output modes with less trial and error during later use of the electronic device and set of one or more wearable audio output devices. Providing to the user improved feedback, or an improved audio mode selection user interface, and reducing the number of inputs needed to use different control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the user interface includes (720) a user interface element (e.g., button 542 in
Displaying, in the same user interface for demonstrating audio being output in different audio output modes, a user interface element to select a particular audio output mode as the active audio output mode for a particular type of audio content allows the user to quickly enable a desired audio output mode after listening to one or more audio output mode demonstrations. Reducing the number of inputs needed to perform an operation enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the user interface includes (722) a user interface element (e.g., button 540 in
Displaying, in the same user interface for demonstrating audio being output in different audio output modes, a user interface element to select a particular audio output mode as the active audio output mode for a particular type of audio content allows the user to quickly enable a desired audio output mode after listening to one or more audio output mode demonstrations. Reducing the number of inputs needed to perform an operation enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the first visual indication includes (724) a first animation associated with the first audio output mode, and the second visual indication includes a second animation, different from the first animation, associated with the second audio output mode (e.g., where the first audio output mode is the stereo audio output mode and the second audio output mode is the spatial audio output mode, the first visual indication includes stereo audio simulation 538 in
Displaying different animations on the electronic device while demonstrating different audio output modes provides the user with visual feedback illustrating the operation of the different audio output modes, to help the user understand how audio is output by the set of one or more wearable audio output devices in the different audio output modes. Providing to the user improved feedback, or an improved audio mode selection user interface, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the respective audio output mode is (726) a spatial audio output mode. In some embodiments, a respective animation of the first animation and the second animation that corresponds to the spatial audio output mode includes moving a representation of a user while maintaining a representation of an audio output displayed in the user interface (e.g., while the representation of the first audio output continues to be displayed at the first location and the representation of the second audio output continues to be displayed at the second location, without moving). For example, the transition from
Displaying an animation that includes movement of a representation of a user relative to a non-moving representation of an audio output provides the user with visual feedback illustrating the operation of a spatial audio output mode, to help the user understand how audio is output by the set of one or more wearable audio output devices in the spatial audio output mode. Providing to the user improved feedback, or an improved audio mode selection user interface, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the respective audio output mode is (728) a spatial audio output mode. In some embodiments, a respective animation of the first animation and the second animation that corresponds to a non-spatial audio output mode includes concurrently moving a representation of a user and a representation of a first audio output displayed with a first predefined spatial relationship to the representation of the user in accordance with the movement of the representation of the user (e.g., such that the predefined spatial relationship between the representation of the first audio output and the representation of the user is maintained). For example, the transition from
Displaying an animation that includes movement of a representation of a user concurrently with corresponding movement of a representation of an audio output that maintains a respective spatial relationship between the representation of the audio outputs and the representation of the user provides the user with visual feedback illustrating the operation of a non-spatial (e.g., stereo) audio output mode, to help the user understand how audio is output by the set of one or more wearable audio output devices in the non-spatial audio output mode. Providing to the user improved feedback, or an improved audio mode selection user interface, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the second audio is a continuation of the first audio, with the second audio rendered using the second audio output mode where the first audio is rendered using the first audio output mode (730) (e.g., optionally, in
Using the same audio (e.g., different portions of the same audio) to demonstrate different audio output modes, by rendering a first portion of the audio using one audio output mode and a second portion of the same audio using another audio output mode, or by rendering the audio using one audio output mode and repeating the same audio again rendered in the other audio output mode, ensures that the user is provided with aural feedback illustrating the operation of the different audio output modes in a manner that better enables comparison between how audio is output using the different audio output modes, to help the user understand how the audio output modes operate and differ. Providing to the user improved feedback, or an improved audio mode selection user interface, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, outputting the first audio using the first audio output mode includes (732) rendering respective audio for output using the first audio output mode. In some embodiments, outputting the second audio using the second audio output mode includes rendering the respective audio (e.g., the same respective audio content used for the first audio output mode) for output using the second audio output mode (e.g., optionally, the audio used for the stereo audio demo in
Using the same respective audio to demonstrate different audio output modes, by rendering the respective audio using the different audio output modes, ensures that the user is provided with aural feedback illustrating the operation of the different audio output modes in a manner that better enables comparison between how audio is output using the different audio output modes, to help the user understand how the audio output modes operate and differ. Providing to the user improved feedback, or an improved audio mode selection user interface, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the respective audio includes a moving source of sound (734). In some embodiments when rendering audio from a moving source of sound for output via a set of one or more wearable audio output devices using a spatial audio output mode, where the source of sound moves relative to a frame of reference, the audio output via the set of one or more wearable audio output devices is adjusted according to both movement of the moving source of sound and movement of the set of one or more wearable audio output devices relative to a frame of reference, so as to maintain the audio as coming from the moving source of sound (e.g., the spatial relationship between the moving source of sound and the frame of reference is preserved). In one example, a source of sound that moves past the user is output at a first simulated location represented by speaker representation 546-5 and later at a second simulated location represented by speaker representation 546-2 in
In some embodiments when rendering audio from a moving source of sound for output using a non-spatial stereo audio output mode, the audio output via the set of one or more wearable audio output devices is adjusted according to movement of the moving source of sound but not according to movement of the set of one or more wearable audio output devices relative to the frame of reference (e.g., the spatial relationship between the moving source of sound and the frame of reference is not preserved, and instead the movement of the moving source of sound is presented as being relative to the set of one or more wearable audio output devices). In one example, a source of sound that moves past the user is output at a first simulated location represented by speaker representation 538-2 in
Stated another way, the respective audio is to be output to sound as though the respective audio is coming from a plurality of different locations at different times (e.g., audio that is associated with a sequence of different locations, and that is to be output to sound as though the respective audio is moving relative to the user and/or the set of one or more wearable audio output devices). In some embodiments outputting the respective audio using a spatial audio output mode includes outputting the respective audio to sound as though, at a first time, the respective audio is coming from a first simulated location in the frame of reference (e.g., a first location in a physical environment), and, at a second time, the respective audio is coming from a second simulated location in the frame of reference (e.g., a second location in the physical environment), independently of movement of the set of one or more wearable audio output devices. In some embodiments outputting the respective audio using a non-spatial audio output mode includes outputting the respective audio to sound as though, at the first time, the respective audio is coming from a first location with a first predefined spatial relationship to the set of one or more wearable audio output devices, and, at the second time, the respective audio is coming from a second location with a second predefined spatial relationship to the set of one or more wearable audio output devices.
Demonstrating different audio output modes by using the same respective audio that is to be output to sound as though the respective audio is coming from a moving source of sound (e.g., moving over time relative to the user and/or the set of one or more wearable audio output devices) provides the user with aural feedback, or aural demonstrations, illustrating the operation of the different audio output modes in a manner that better enables comparison between how audio is output using the different audio output modes, to help the user understand how the audio output modes operate and differ. Providing to the user improved feedback, or an improved audio mode selection user interface that includes aural demonstrations of user-selectable audio output modes, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the set of one or more wearable audio output devices includes (736) a first wearable audio output component and a second wearable audio output component (e.g., a pair of earbuds or earcups). In some embodiments, prior to displaying the user interface, in accordance with a determination that at least one of the first wearable audio output component or the second wearable audio output component is not in a respective position relative to an ear of a user (e.g., the respective position is an in-ear, on-ear, or over-the-ear position) (e.g., the first and second wearable audio output components are not both in the respective position relative to different ears of the user), the electronic device presents a notification (e.g., displaying a visual notification via the one or more display devices or outputting an audible notification via one or more of the audio output devices) prompting the user to place the first wearable audio output component in the respective position relative to a first ear of the user and the second wearable audio output component in the respective position relative to a second ear of the user (e.g., notification 530 in
In some embodiments, the notification is displayed in response to activation of a respective user interface element on a previously-displayed user interface (e.g., button 514 in
Prompting the user to place both wearable audio output components in the respective position relative to (e.g., in, on, or over) the ears of a user before playing audio to demonstrate one or more audio output modes improves the conditions under which the demonstration is performed, particular for audio output modes that require the use of multiple audio output components for outputting audio, which improves the user's perception of the demonstration and reduces the need to repeat the demonstration. In embodiments where the prompt ceases to be displayed in response to detecting placement of both wearable audio output components in the respective position relative to the user's ears, doing so enables the audio output mode demonstration process to proceed without requiring the user to provide an input to explicitly dismiss the prompt and advance the demonstration process. Reducing the number of inputs needed to perform an operation, as well as in some embodiments performing the operation (e.g., automatically) when a set of conditions has been met without requiring further user input, enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the user interface (e.g., as shown in 5E, optionally part of a sequence of user interfaces including the user interface shown in
Displaying the user interface for demonstrating audio in response to establishing communication with a particular set of one or more wearable audio output devices for a first (e.g., initial) time provides the user with quick access to setup options for the set of one or more wearable audio output devices when setup is needed or most relevant (e.g., without prompting the user about the setup options every time the electronic device establishes communication with the set of one or more wearable audio output devices). Performing an operation (e.g., automatically) when a set of conditions has been met without requiring further user input enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the user interface (e.g., as shown in 5E, optionally part of a sequence of user interfaces including the user interface shown in
Displaying the user interface for demonstrating audio in response to establishing communication with a particular set of one or more wearable audio output devices for a first (e.g., initial) time since a most recent electronic device software update provides the user with quick access to setup options for the set of one or more wearable audio output devices when setup is needed or most relevant (e.g., without prompting the user about the setup options every time the electronic device establishes communication with the set of one or more wearable audio output devices). Performing an operation (e.g., automatically) when a set of conditions has been met without requiring further user input enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, prior to displaying the user interface, the electronic device displays (742) a settings user interface (e.g., as shown in
Providing access to the user interface for demonstrating audio output modes in response to an input selecting a corresponding option in a settings user interface helps the user to more quickly understand the different options for audio output mode prior to selecting, in the settings user interface, whether to enable a respective mode as the active audio output mode. Providing to the user improved feedback, or an improved audio mode selection user interface, and/or improved access to an audio mode selection user interface, and reducing the number of inputs needed to use different control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
It should be understood that the particular order in which the operations in
As described below, method 800 provides on an electronic device an audio settings user interface for indicating a current audio output mode of one or more connected audio output devices and for enabling and disabling available audio output modes. The user interface includes a user interface element that is associated with a particular audio output mode of the one or more audio output devices and whose appearance is varied, while the particular audio output mode is enabled, to indicate whether audio is in fact being output using the particular enabled audio output mode, thus providing a user with visual feedback about how audio is currently being output via the one or more audio output devices. The user interface element is also activatable to change whether the particular audio output mode is enabled, thereby providing the user with quick access to control over the audio output mode without requiring the user to navigate through complex settings menu hierarchies. Providing improved feedback to the user and reducing the number of inputs needed to access additional control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
While displaying, via the one or more display devices, a first user interface of the electronic device, the electronic device receives (804), via the one or more input devices, a sequence of one or more inputs that corresponds to a request to display an audio settings user interface (e.g., in response to swipe gesture 602 in
In some embodiments, in response to receiving the sequence of one or more inputs, the electronic device displays (806), via the one or more display devices, the audio settings user interface, wherein the audio settings user interface includes a first user interface element that is activatable to change whether a first audio output mode (e.g., a spatial audio output mode) of one or more audio output devices that are in communication with the electronic device is enabled, and displaying the audio settings user interface includes (e.g., as shown in
In some embodiments, displaying the audio settings user interface includes, in accordance with a determination that the first audio output mode is enabled and that the electronic device is causing respective audio that is configured for output using the first audio output mode to be output using the first audio output mode via one or more audio output devices that are in communication with the electronic device (808) (e.g., outputting the respective audio to sound as though the respective audio is coming from one or more simulated locations in a frame of reference, such as a physical environment, independently of a location of the one or more audio output devices in the frame of reference, including, for a fixed source of sound, adjusting output of the respective audio as the one or more audio output devices are moved relative to the frame of reference, so as to maintain the simulated source of sound in a substantially fixed position (or in substantially fixed respective positions) relative to the frame of reference, and/or for a moving source of sound, adjusting output of the respective audio so as to move the simulated location of the source of sound relative to the frame of reference independently of a position of the set of one or more audio output devices relative to the frame of reference), displaying the first user interface element concurrently with a first visual indication that the first audio output mode is being used (e.g., in
In some embodiments, displaying the audio settings user interface includes, in accordance with a determination that the first audio output mode is enabled and that the electronic device is not causing respective audio to be output using the first audio output mode via one or more audio output devices that are in communication with the electronic device (810) (e.g., the respective audio is not being output (e.g., playback has not been initiated or is paused), or audio that is being output is not configured for output using the first audio output mode), displaying the first user interface element without displaying the first visual indication that the first audio output mode is being used (e.g., in
In some embodiments, the first visual indication that the first audio output mode is being used is (812) an appearance of the first user interface element (e.g., the first user interface element has a first appearance when audio is being output with the first audio output mode and a second appearance when audio is not being output with the first audio output mode). For example, spatial audio toggle 618 in
Displaying a visual indication as to whether audio is in fact being output using a particular enabled audio output mode provides the user with visual feedback about how audio is currently being output via one or more connected audio output devices. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, while displaying the first user interface element concurrently with the first visual indication that the first audio output mode is being used, the appearance of the first user interface element includes (814) a respective animation (e.g., spatial audio toggle 618 in the enabled state in
Displaying an audio output mode user interface element with different appearances, such as animated versus not animated, to indicate whether audio is in fact being output using a particular enabled audio output mode provides the user with visual feedback about how audio is currently being output via one or more connected audio output devices. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, displaying the audio settings user interface includes (816), in accordance with a determination that the first audio output mode is not enabled, displaying the first user interface element and displaying a visual indication that the first audio output mode is not enabled (e.g., without regard to whether or not audio is currently being output that could be output with the first audio output mode). In some embodiments, the visual indication that the first audio output mode is not enabled is a change in appearance of the first user interface element. For example, in
Displaying a visual indication as to whether a particular audio output mode (e.g., a spatial audio output mode) is enabled or disabled provides the user with visual feedback about whether outputting audio using the particular audio output mode is currently permitted. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the visual indication that the first audio output mode is not enabled is (818) an appearance of the first user interface element that is different from one or more appearances of the first user interface element that are displayed while the first audio output mode is enabled (e.g.,
Displaying an audio output mode user interface element with different appearances based on whether a particular audio output mode (e.g., a spatial audio output mode) is enabled or disabled (e.g., further differentiated from the appearance(s) of the user interface element based on whether audio is currently being output using the particular audio output mode while the particular audio output mode is enabled), provides the user with visual feedback about whether outputting audio using the particular audio output mode is currently permitted. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the appearance of the first user interface element while the first audio output mode is not enabled is (820) different from (e.g., visually deemphasized relative to) the one or more appearances of the first user interface element that are displayed while the first audio output mode is enabled in color, fill, and/or shading (e.g.,
Displaying an audio output mode user interface element with different color, fill, and/or shading based on whether a particular audio output mode (e.g., a spatial audio output mode) is enabled or disabled provides the user with intuitive visual feedback about whether outputting audio using the particular audio output mode is currently permitted. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the audio settings user interface includes (822) a second user interface element indicating a first ambient sound control mode in which the one or more audio output devices are operating (e.g., mode control 616 shown in
Displaying a user interface element indicating an ambient sound control mode in which one or more connected audio output devices are currently operating provides the user with visual feedback about how audio is currently being output. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the electronic device detects (824) a user input that corresponds to activation of the second user interface element. In some embodiments, in response to the electronic device detecting the user input that corresponds to the activation of the second user interface element (e.g., input 624 in
Providing an expanded set of selectable options for available ambient sound control mode of one or more connected audio output devices in response to an input activating a user interface element that indicates the current ambient sound control mode provides the user with quick access to additional audio output mode options without requiring the user to navigate through complex settings menu hierarchies and without displaying the expanded set of options when not needed. Reducing the number of inputs needed to access additional control options and providing such control options without cluttering the user interface with additional displayed controls enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, in accordance with the determination that the first audio output mode is enabled and that the electronic device is not causing respective audio to be output using the first audio output mode via one or more audio output devices that are in communication with the electronic device, while outputting second respective audio that is not configured for output using the first audio output mode, the electronic device outputs (826) the second respective audio using a second audio output mode (e.g., a non-spatial audio output mode such as a stereo audio output mode) that is different from the first audio output mode (e.g., even though the first audio output mode is enabled). For example, in
Switching audio output mode from a first audio output mode to a different audio output mode in accordance with a determination that the audio that is to be output is not configured for output using the first audio output mode avoids outputting audio in a manner that is not compatible with current conditions for audio output (e.g., due to the type of audio that is to be output). Performing an operation (e.g., automatically) when a set of conditions has been met enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the one or more audio output devices include a first wearable audio output component configured to be placed in a respective position relative to a first ear of a user (e.g., the respective position is an in-ear, on-ear, or over-the-ear position) and a second wearable audio output component configured to be placed in the respective position relative to a second ear of the user (e.g., distinct wearable audio output components, such as earbuds or earcups, configured to be worn in, on, or over different ears of a user). In some embodiments, the electronic device causes (828) the respective audio to be output using the first audio output mode is performed in accordance with a determination that the first wearable audio output component is in the respective position relative to a first ear of a user and that the second wearable audio output component is in the respective position relative to a second ear of the user. In some embodiments, the electronic device displays the first user interface element with the first appearance in accordance with the determination that the first wearable audio output component and the second wearable audio output component are in the respective position relative to the user's ears, respectively. In some embodiments, while the first audio output mode is enabled, and while the electronic device is causing the respective audio that is configured for output using the first audio output mode to be output via the one or more audio output devices: in accordance with a determination that the first wearable audio output component or the second wearable audio output component is not in the respective position relative to a respective ear of the user, the electronic device causes the respective audio to be output via the one or more audio output devices using a third audio output mode (e.g., a mono audio output mode) that is different from the first audio output mode (e.g.,
Switching audio output mode from a first audio output mode to a different audio output mode in response to at least one wearable audio output component being removed from the respective position relative to an ear of the user avoids outputting audio in a manner that is not compatible with current conditions for audio output and that may use more power than necessary (e.g., due to the user not being able to perceive audio output from both wearable audio output components as intended for the first audio output mode). Performing an operation (e.g., automatically) when a set of conditions has been met enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the electronic device detects (830) an input activating the first user interface element to change whether the first audio output mode is enabled. In some embodiments, in response to the electronic device detecting the input activating the first user interface element: the electronic device displays an indication whether the first audio output mode is enabled (e.g., in combination with enabling or disabling the first audio output mode) (e.g., textual indication 621 in
Displaying an indication whether the first audio output mode is enabled (and optionally indicating what types of audio will be output using the first audio output mode) in response to activation of the first user interface element (e.g., to toggle whether the first audio output mode is enabled) provides the user with visual feedback indicating a current mode of audio output. Providing improved feedback to the user enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the electronic device automatically ceases (832) to display the indication whether the first audio output mode is enabled after occurrence of a predetermined condition (e.g., after a predetermined amount of time has elapsed since the first audio output mode was enabled, after a predetermined amount of time has elapsed since the first audio output mode was disabled, after a predetermined amount of time has elapsed since audio using the first audio output mode started to be output via one or more audio output devices in communication with the electronic device, after a predetermined amount of time has elapsed since audio using the first audio output mode ceased to be output via one or more audio output devices in communication with the electronic device, and/or after a predetermined amount of time has elapsed since the audio settings user interface was displayed). For example, the transition from
Automatically ceasing to display an indication whether the first audio output mode is enabled (and optionally what types of audio will be output using the first audio output mode) after a predetermined condition has occurred, such as a predetermined amount of time elapsing since a respective event associated with the first audio output mode or audio settings user interface occurred, provides the visual feedback indicating the current mode of audio output for an amount of time sufficient for the user to perceive the feedback but not for longer than necessary. Providing improved feedback to the user without cluttering the user interface with additional displayed elements enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the first settings user interface includes (834) a third user interface element for adjusting a volume of audio output via the one or more audio output devices (e.g., expanded volume control slider 612 in
Displaying a user interface element for adjusting audio output volume for audio that is output via one or more connected audio output devices provides the user with quick access to additional audio output control options without requiring the user to navigate through complex settings menu hierarchies. Reducing the number of inputs needed to access additional control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, while the first audio output mode is enabled, and while causing the respective audio that is configured for output using the first audio output mode to be output using the first audio output mode: in accordance with a determination that an electronic device tracking audio output mode is enabled, the electronic device outputs (836) the respective audio using the first audio output mode includes modifying output of the respective audio based on a current location of the electronic device as the electronic device is moved in a physical environment relative to the one or more audio output devices that are outputting the respective audio (e.g., the respective audio continues to follow the location of the electronic device even if the pose of the one or more audio output devices changes, as described herein with reference to the “follow device” feature, for example in the discussions of
Providing an electronic device tracking audio output mode that outputs audio to sound as though the audio is moving with the electronic device as the electronic device moves relative to one or more connected audio output devices improves accessibility by providing aural feedback to the user about the current location of the electronic device, thus helping users (e.g., particularly visually-impaired users) interact with the electronic device. Because a user might only need to interact with a user interface element to enable such an audio output mode once, displaying such user interface element in a different, second settings user interface (e.g., a more comprehensive settings user interface) from the audio settings user interface simplifies the audio settings user interface to controls that a user is likely to access more frequently. Improving accessibility and providing additional control options without cluttering the user interface with infrequently-used displayed controls enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, the electronic device detects (838) a user input directed to the first user interface element. In some embodiments, in response to the electronic device detecting the user input directed to the first user interface element, and in accordance with a determination that the user input directed to the first user interface element is detected while the first audio output mode is enabled, the electronic device disables the first audio output mode (e.g., in response to input 620 on spatial audio toggle 618 in
Displaying in an audio settings user interface an audio output mode user interface element to enable or disable the first audio output mode (e.g., a spatial audio output mode) provides a user with quick access to control over audio output mode without requiring the user to navigate through complex settings menu hierarchies. Reducing the number of inputs needed to access additional control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, in response to receiving the sequence of one or more inputs at the electronic device, the audio settings user interface includes (840) the first user interface element in accordance with a determination that the one or more audio output devices that are in communication with the electronic device are capable of outputting audio using the first audio output mode (e.g., the one or more audio output devices support spatial audio output) (e.g., spatial audio toggle 618 is displayed in audio settings user interface 610 in
Conditionally displaying user interface elements, which indicate and are activatable to change respective audio output modes in which one or more audio output devices in communication with an electronic device are operating, based on whether the one or more connected audio output devices support such audio output modes provides visual feedback to the user as to which audio output modes are supported and provides the user with quick access to control options over such audio output modes when relevant. Forgoing displaying a user interface element indicating a respective audio output mode that is not supported by the one or more connected audio output devices avoids misleading the user into believing that the audio output mode is available and can be controlled. Providing improved feedback to the user about available control options, reducing the number of inputs needed to access available and relevant control options, and providing such control options without cluttering the user interface with unavailable and thus irrelevant control options enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
In some embodiments, audio that is configured for output using the first audio output mode includes (842) one or more of: audio associated with television content (e.g., videos or video clips of television content such as television shows), audio associated with movie content (e.g., movies or movie clips or trailers), audio associated with video calls (sometimes called video conferences), sounds associated with (e.g., generated by) an operating system of the electronic device, audio associated with a virtual assistant (e.g., a software module or application, executing on the electronic device, that assists a user with performing tasks or operations on the electronic device in response to voice and/or text inputs recognized as requests to perform such tasks or operations), and audio associated with notifications on the electronic device (e.g., to alert a user of notifications received at or generated by the electronic device). In some embodiments audio that is configured for output using the first audio output mode includes audio for videos, more generally. In some embodiments, audio that is configured for output using the first audio output mode includes audio associated with multiparty telephone calls in which users of three or more electronic devices are participating. In some circumstances, one or more (e.g., a subset) of the aforementioned types of audio is not included among the types of audio that are configured for output using the first audio output mode. For example, textual indication 623 in
Outputting one or more different types of audio that are configured for output using a particular audio output mode (e.g., a spatial audio output mode) when playback of the audio is requested while the particular audio output mode is enabled, and conversely using a different audio output mode to output one or more types of audio that are not configured for output using the particular audio output mode, improves how audio is presented to the user based on the properties of the requested audio without requiring the user to explicitly request playback using a specific audio output mode. Performing an operation (e.g., automatically, without further user input) when a set of conditions has been met without requiring further user input enhances the operability of the devices and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the devices), which, additionally, reduces power usage and improves battery life of the devices by enabling the user to use the devices more quickly and efficiently.
It should be understood that the particular order in which the operations in
Bandwidth meter 946 in
However, because streaming bandwidth for the movie is below the threshold bandwidth Bth, spatial audio content is not being output even though spatial audio is enabled. Instead, audio is output as spatialized stereo audio (e.g., by applying an algorithm to two-channel stereo audio content to upscale the stereo audio content, and outputting the upscaled audio content spatially, as spatialized stereo audio content, which is herein described further with reference to operation 1030 of method 1000). In some embodiments, as illustrated by
In contrast to the example shown in
Similarly, spatialized stereo global toggle 984, while in a disabled state as shown in
Similarly, while spatialized stereo audio global toggle 984 is set to the enabled state, a list of applications on device 100 (e.g., that support spatialized stereo audio) is displayed, with a respective toggle for each application in the list for enabling the use of spatialized stereo audio by the respective corresponding application. In the example shown in
As described below, method 1000 enables a user to control the audio output mode used for a respective application independently of the audio output mode that is set for other applications, and uses the same selected audio output mode again later for the same respective application, even if different audio output modes are used with other applications, for example in between uses of the respective application. Saving and reusing a previously selected audio output mode for a respective application avoids requiring the user to select that audio output mode again when resuming use of the respective application. Reducing the number of inputs needed to perform an operation enhances the operability of the system and makes the user-device interface more efficient (e.g., by helping the user to achieve an intended outcome and reducing user mistakes when operating/interacting with the system), which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.
While a first application is causing output of audio information (e.g., corresponding to first media being played by the first application) to the set of one or more audio output devices, the computer system causes (1002) output of the audio information from the first application to the set of one or more audio output devices in accordance with a first audio output mode previously selected for the first application using a system audio output setting control (e.g., in
After (e.g., while) causing output of audio information from the first application via the set of one or more audio output devices in accordance with the first audio output mode, the computer system receives (1004) a request to play audio from a second application different from the first application (e.g., a request to play second media using the second application) (e.g., in
In response to receiving the request to play audio from the second application, the computer system causes (1006) output of (second) audio information from the second application to the set of one or more audio output devices (e.g., in
Causing output of the audio information from the second application to the set of one or more audio output devices includes: in accordance with a determination that a second audio output mode, different from the first audio output mode, was previously selected for the second application using the system audio output setting control (1008), causing output of the (second) audio information from the second application via the set of one or more audio output devices in accordance with the second audio output mode (e.g., and changing an audio output mode for the set of one or more audio output devices from the first audio output mode to the second audio output mode) (e.g., in
In some embodiments, causing, in response to receiving the request to play audio from the second application, output of the audio information from the second application to the set of one or more audio output devices includes: in accordance with a determination that the first audio output mode was previously selected for the second application using the system audio output setting control (1010), causing output of the (second) audio information from the second application via the set of one or more audio output devices in accordance with the first audio output mode (e.g., and maintaining use of the first audio output mode for the set of one or more audio output devices) (e.g., if the user were to switch to the movie application without performing the changes, shown in
In some embodiments, an audio output mode for the first application, previously selected for the first application using the system audio output setting control, is (1012) the first audio output mode (e.g., spatial audio output mode). In some such embodiments, while executing the first application (e.g., optionally, or in some circumstances, while delivering audio information from the first application to the set of one or more audio output devices), using the system audio output setting control, the computer system changes (e.g., in response to one or more user inputs) the audio output mode for the first application from the first audio output mode to the second audio output mode (e.g., non-spatial audio output mode) (e.g., and saving the changed audio output mode for future audio output by the first application). In some such embodiments, after changing the audio output mode for the first application to the second audio output mode, while the first application is delivering audio information to the set of one or more audio output devices, the computer system causes output of the audio information from the first application via the set of one or more audio output devices in accordance with the second audio output mode (e.g., instead of delivering the audio information from the first application to the set of one or more audio output devices in accordance with the first audio output mode) (e.g., in
In some embodiments, the computer system saves (1014) the changed audio output mode for the first application (e.g., as a saved audio output mode setting for the first application) for future audio output by the first application (e.g., after execution of the first application ends, and is then resumed at a later time, audio information is output from the first application to the set of one or more audio output devices in accordance with the (saved) audio output mode). In some embodiments, after the audio output mode for a respective application (e.g., the first application) is changed (e.g., from the first audio output mode to the second audio output mode), and after ceasing to cause output of audio information from the respective application via the set of one or more audio output devices in accordance with the changed (e.g., second) audio output mode, a subsequent request for the respective application to cause output of audio information is received, and, in response to the subsequent request, output of audio information from the respective application is performed in accordance with the changed audio output mode for the respective application. For example, after the audio output mode settings used for the music application are changed in
In some embodiments, an audio output mode for the second application, previously selected for the second application using the system audio output setting control, is (1016) the second audio output mode (e.g., a non-spatial audio output mode such as a stereo mode). In some such embodiments, while executing the second application (e.g., optionally, or in some circumstances, while delivering audio information from the second application to the set of one or more audio output devices), using the system audio output setting control, the computer system changes (e.g., in response to one or more a user inputs) the audio output mode for the second application from the second audio output mode to the first audio output mode (e.g., and saves the changed audio output mode for future audio output by the second application). In some such embodiments, after changing the audio output mode for the second application to the first audio output mode, while the second application is delivering audio information to the set of one or more audio output devices, the computer system causes output of the audio information from the second application via the set of one or more audio output devices in accordance with the first audio output mode (e.g., instead of delivering the audio information from the second application to the set of one or more audio output devices in accordance with the second audio output mode). For example, if the audio output mode settings for the movie application were changed, the newly selected audio output mode settings would be used to output movie audio. Outputting audio in accordance with a newly selected audio output mode for a respective application and saving that selected audio output mode for the respective application avoids requiring the user to select that audio output mode again when resuming use of the respective application later, which reduces the number of inputs needed to perform the operation.
In some embodiments, the computer system saves (1018) the changed audio output mode for the second application (e.g., as a saved audio output mode setting for the second application) for future audio output by the second application (e.g., after execution of the second application ends, and is then resumed at a later time, audio information is output from the second application to the set of one or more audio output devices in accordance with the (saved) audio output mode). For example, if the audio output mode settings for the movie application were changed, the newly selected audio output mode settings would be saved for future audio output by the movie application. Saving a selected audio output mode for a respective application and reusing the same selected audio output mode later for the respective application avoids requiring the user to select that audio output mode again when resuming use of the respective application, which reduces the number of inputs needed to perform the operation.
In some embodiments, the first audio output mode is (1020) a spatial audio output mode, and the second audio output mode is the spatial audio output mode or a non-spatial audio output mode. In some embodiments, a spatial audio output mode is an audio output mode where audio is output at simulated spatial locations in a 3D environment, independent of the audio output device locations and orientations. In some embodiments, a spatial audio output mode is an audio output mode where audio of the set of one or more audio output devices is adjusted as the set of one or more audio output devices is moved relative to a frame of reference (e.g., the set of one or more audio output devices are moved relative to a three-dimensional environment, such as a physical environment in which the set of one or more audio output devices are located, or moved relative to a displayed user interface, or the displayed user interface is moved relative to the set of one or more audio output devices), so as to position (e.g., a simulated location of, or one or more respective simulated locations of) one or more sources of sound in the frame of reference independently of a position of the set of one or more audio output devices relative to the frame of reference (e.g., for a fixed source of sound, adjust the audio output of the set of one or more audio output devices so as to maintain the simulated location of the fixed source of sound (e.g., of the audio being output) in a substantially fixed position (or in substantially fixed respective positions) relative to the frame of reference, independent of a position of the set of one or more audio output devices relative to the frame of reference; or for a moving source of sound, adjust the audio output of the set of one or more audio output devices so as to move the simulated location of the source of sound relative to the frame of reference independently of a position of the set of one or more audio output devices relative to the frame of reference). In some embodiments, for the spatial audio output mode, audio signal processing is performed to compute and adjust audio signals for output so that a user (e.g., an average user) will perceive the sound of the audio output to be coming from one or more simulated locations in the frame of reference (e.g., not limited to a location within the user's head). In some embodiments, the audio signal processing of the audio signals is performed by the computer system, by the set of one or more audio output devices, or by a combination of the computer system and the set of one or more audio output devices (e.g., in part by the computer system and in part by the set of one or more audio output devices).
In some embodiments, a non-spatial audio output mode is an audio output mode where audio of the set of one or more audio output devices is not adjusted as the set of one or more audio output devices is moved relative to the frame of reference (e.g., resulting in not maintaining the one or more sources of sound in a substantially fixed position relative to the frame of reference (e.g., relative to a three-dimensional environment or relative to a displayed user interface corresponding to the one or more sources of sound, such as the display of a device or a projected user interface)).
Using the same selected audio output mode again later for a respective application avoids requiring the user to select that audio output mode again when resuming use of the respective application. For example, saving and reusing a spatial audio output mode for a respective application is beneficial particularly if the spatial audio output mode is commonly used for the respective application; analogously, saving and reusing a non-spatial audio output mode for a respective application is beneficial particularly if the non-spatial audio output mode is commonly used for the respective application, which reduces the number of inputs needed to perform the operation.
In some embodiments, an audio output mode of the first application is (1022) configured, by default, to be the spatial audio output mode (e.g., when the first application is executed for the first time on the computer system, the default audio output mode is a spatial audio output mode, for example based on the type of the first application or based on the specific identity of the first application). Configuring the spatial audio output mode as the default audio output mode for a respective application avoids requiring the user to select that audio output mode for the respective application, which is beneficial particularly if the spatial audio output mode is a commonly used or most appropriate audio output mode for the respective application, which reduces the number of inputs needed to perform the operation.
In some embodiments, an audio output mode of the second application is (1024) configured, by default, to be the non-spatial audio output mode (e.g., when the second application is executed for the first time on the computer system, the default audio output mode for the second application is a non-spatial audio output mode, for example based on the type of the second application (e.g., screen reader applications for converting text to speech) or based on the specific identity of the second application). Configuring the non-spatial audio output mode as the default audio output mode for a respective application avoids requiring the user to select that audio output mode for the respective application, which is beneficial particularly if the non-spatial audio output mode is a commonly used or most appropriate audio output mode for the respective application, which reduces the number of inputs needed to perform the operation.
In some embodiments, an audio output mode of the first application is (1026) configured, by default, in accordance with a user preference of (e.g., selected by or for) a user of the computer system (e.g., if a user dislikes spatial audio, and saves a corresponding preference setting (e.g., saved within a settings user interface for the computer system), then the audio output mode for the first application is set by default to a non-spatial audio output mode; in some embodiments, if the user expresses no preference with respect to spatial audio, or has a preference for spatial audio, then the audio output mode for the first application is set by default to a spatial audio output mode). Configuring the default audio output mode for applications based on a previously determined user preference or selection avoids requiring the user to select that audio output mode for each application individually or each time the user uses a respective application, which reduces the number of inputs needed to perform the operation.
In some embodiments, an audio output mode of the first application is (1028) configured, by default, by the first application (e.g., by the first application itself, for example by setting the audio output mode via an application programming interface (API)). Allowing a respective application to configure its own default audio output mode avoids requiring the user to select that audio output mode for the respective application and has the added benefit that the respective application (or application developer) may be better able to determine the most appropriate mode to use by default for outputting audio, which reduces the number of inputs needed to perform the operation and enables one or more operations to be performed automatically.
In some embodiments, while an audio output mode of the first application is a spatial audio output mode (1030): in accordance with a determination that the computer system is receiving streaming content at a reduced bandwidth, less than a threshold bandwidth, the computer system causes output of audio information by the first application, from the streaming content to the set of one or more audio output devices, as spatialized stereo audio information (e.g., at simulated spatial locations not specified by the streaming content) (e.g., the threshold bandwidth is, or corresponds to, the minimum bandwidth required to provide spatial audio information to the headphones (one or more audio output devices) so that spatial audio can be generated by the headphones); and, in accordance with a determination that the computer system is receiving streaming content at a bandwidth of at least the threshold bandwidth, the computer system causes output of audio information by the first application, from the streaming content to the set of one or more audio output devices, as spatial audio information (e.g., with different audio sources within the streaming content being output at different simulated spatial locations specified by the streaming content). As used herein, “spatial audio” refers to audio content that includes three or more audio channels (e.g., more than merely left and right channels as in stereo audio) rendered to simulate virtual speakers placed around a user's head. As used herein, “spatialized stereo audio” refers to two-channel stereo audio content that is put through an upscaling algorithm and output spatially even though the underlying stereo audio content does not have more than two channels. While the spatial audio output mode is selected, outputting audio as spatialized stereo audio rather than spatial audio while streaming bandwidth is below a threshold bandwidth (e.g., when initially beginning to stream content as illustrated by
In some embodiments, the computer system makes (1032) a determination (e.g., an initial determination, prior to beginning playback) of whether the computer system is receiving streaming content at a bandwidth of at least the threshold bandwidth while buffering the streaming content (e.g., as playback quality may be initially reduced to avoid noticeable transitions in audio quality during playback; further, the streaming content source may initially transmit the streaming content at a lower bandwidth and then increase the bandwidth as it determines that higher bandwidth transmission is available) (e.g., as illustrated by
In some embodiments, after causing output of audio information by the first application, from the streaming content to the set of one or more audio output devices, as spatial audio information: in accordance with a determination that the computer system is receiving the streaming content at a reduced bandwidth, less than the threshold bandwidth (e.g., that the bandwidth at which the computer system receives the streaming content decreases below the threshold bandwidth), the computer system transitions (1034) to causing output of audio information by the first application, from the streaming content to the set of one or more audio output devices, as spatialized stereo audio information (e.g., as illustrated by
In some embodiments, after causing output of audio information by the first application, from the streaming content to the set of one or more audio output devices, as spatialized stereo audio information: in accordance with a determination that the computer system is receiving the streaming content at or above the threshold bandwidth (e.g., that the bandwidth at which the computer system receives the streaming content increases to or above the threshold bandwidth), the computer system transitions (1036) to causing output of audio information by the first application, from the streaming content to the set of one or more audio output devices, as spatial audio information (e.g., as illustrated by
In some embodiments, or in some circumstances, the first audio output mode is (1038) a spatialized stereo audio output mode (e.g., as defined herein with reference to operation 1030). Using the same selected audio output mode again later for a respective application avoids requiring the user to select that audio output mode again when resuming use of the respective application. For example, saving and reusing a spatialized stereo audio output mode for a respective application is beneficial particularly if the spatialized stereo audio output mode is commonly used for the respective application, which reduces the number of inputs needed to perform the operation.
In some embodiments, the first audio output mode is (1040) an active noise cancelling mode, which reduces audio components corresponding to ambient sound from a physical environment, or a transparency audio mode (e.g., sometimes called a pass-through audio mode) that outputs audio components selected so as to increase audio-pass through of ambient sound from the physical environment. For example,
In some embodiments, the computer system displays (1042) a system control user interface that includes the system audio output setting control and at least one additional system control (e.g., settings user interface 908,
In some embodiments, the system audio output setting control in the system control user interface indicates (1044) whether the audio information from the first application (and/or the second application) includes spatial audio information (e.g., in some embodiments the spatial audio information includes an indication of a spatial audio type, such as spatialized stereo, or a specific brand or identifier of spatial audio) (e.g., in
In some embodiments, the system audio output setting control in the system control user interface identifies (1046) an application (e.g., the first application or second application) causing output of audio information to the set of one or more audio output devices (e.g., icon 924 in
In some embodiments, in accordance with a determination that a current audio output mode of the computer system is a spatial audio output mode and that the computer system is causing output of audio information that includes spatial audio content (1048), the computer system displays the system audio output setting control with a first appearance (e.g., an appearance corresponding to or indicating that spatial audio content is being output, such as the appearance of spatial audio toggle 920 in
In some embodiments, the set of one or more audio output devices comprises (1050) a first set of one or more audio output devices or a second set of one or more audio output devices. In some such embodiments, while using the first set of one or more audio output devices, the computer system saves, using the system audio output setting control, a first respective audio output mode for the first application; and, while using the second set of one or more audio output devices, the computer system saves, using the system audio output setting control, a second respective audio output mode for the first application. In some such embodiments, in accordance with a determination that the first set of one or more audio output devices is in use, the computer system causes output of the audio information from the first application to the first set of one or more audio output devices in accordance with the first respective audio output mode saved for the first application while using the first set of one or more audio output devices (e.g., in
In some embodiments, the first set of one or more audio output devices and the second set of one or more audio output devices are (1052) associated with a same user account (e.g., earbuds 502 being used to output audio in
In some embodiments, while displaying a settings user interface, the computer system detects (1054) an input directed to a first respective user interface element for enabling or disabling a spatial audio output mode with respect to all applications (or in some embodiments a plurality of applications), installed on the computer system, capable of causing output of audio information in accordance with the spatial audio output mode (e.g., a user can globally disable the use of a spatial audio output mode). In some such embodiments, in response to the input directed to the first respective user interface element: in accordance with a determination that the input corresponds to a request to disable spatial audio (e.g., an input directed to the first respective user interface element while the first respective user interface element indicates that the spatial audio output mode is enabled) (e.g., for one or more, or a plurality, or any, or all, applications installed on the computer system and capable of causing output of audio information in accordance with the spatial audio output mode), the computer system disables the spatial audio output mode with respect to all applications, installed on the computer system, capable of causing output of audio information in accordance with the spatial audio output mode; and, in accordance with a determination that input corresponds to a request to enable spatial audio (e.g., an input directed to the first respective user interface element while the first respective user interface element indicates that the spatial audio output mode is disabled) (e.g., for one or more, or a plurality, or any, or all, applications installed on the computer system and capable of causing output of audio information in accordance with the spatial audio output mode), the computer system makes the spatial audio output mode available to all applications, installed on the computer system, capable of causing output of audio information in accordance with the spatial audio output mode. For example, as described herein with reference to
In some embodiments, the computer system displays (1056) a settings user interface that concurrently displays: a first set of one or more controls for enabling or disabling use of a spatial audio output mode for the first application; and a second set of one or more controls for enabling or disabling use of the spatial audio output mode for the second application (e.g., a toggle or other dual-state affordance is displayed in conjunction with an identifier for each concurrently listed application). In some such embodiments, while displaying the settings user interface, the computer system receives an input. In some such embodiments, in accordance with a determination that the input is directed to the first set of one or more controls: in accordance with a determination that the input corresponds to a request to disable spatial audio for the first application (e.g., an input directed to the first set of one or more controls while use of the spatial audio output mode is enabled for the first application), the computer system disables use of the spatial audio output mode for the first application (e.g., making the spatial audio output mode unavailable to the first application); and, in accordance with a determination that the input corresponds to a request to enable spatial audio for the first application (e.g., an input directed to the first set of one or more controls while use of the spatial audio output mode is disabled for the first application), the computer system enables use of the spatial audio output mode for the first application (e.g., making the spatial audio output mode available to the first application). In some such embodiments, in accordance with a determination that the input is directed to the second set of one or more controls: in accordance with a determination that the input corresponds to a request to disable spatial audio for the second application (e.g., an input directed to the second set of one or more controls while use of the spatial audio output mode is enabled for the second application), the computer system disables use of the spatial audio output mode for the second application (e.g., making the spatial audio output mode unavailable to the second application); and, in accordance with a determination that the input corresponds to a request to enable spatial audio for the second application (e.g., an input directed to the second set of one or more controls while use of the spatial audio output mode is disabled for the second application), the computer system enables use of the spatial audio output mode for the second application (e.g., making the spatial audio output mode available to the second application). For example, as described herein with reference to
In some embodiments, while displaying a settings user interface, the computer system detects (1058) an input directed to a second respective user interface element for enabling or disabling a spatialized stereo audio output mode with respect to a plurality of (e.g., all) applications, installed on the computer system, capable of causing output of audio information in accordance with the spatialized stereo audio output mode (e.g., a user can globally disable the use of a spatialized stereo audio output mode, for example using a toggle or other dual-state affordance). In some such embodiments, in response to the input directed to the second respective user interface element: in accordance with a determination that the input corresponds to a request to disable spatialized stereo audio (e.g., an input directed to the second respective user interface element while the second respective user interface element indicates that the spatialized stereo audio output mode is enabled) (e.g., for one or more, or a plurality, or any, or all, applications installed on the computer system and capable of causing output of audio information in accordance with the spatialized stereo audio output mode), the computer system disables the spatialized stereo audio output mode with respect to all applications, installed on the computer system, capable of causing output of audio information in accordance with the spatialized stereo audio output mode; and, in accordance with a determination that the input corresponds to a request to enable spatialized stereo audio (e.g., an input directed to the second respective user interface element while the second respective user interface element indicates that the spatialized stereo audio output mode is disabled) (e.g., for one or more, or a plurality, or any, or all, applications installed on the computer system and capable of causing output of audio information in accordance with the spatialized stereo audio output mode), the computer system makes the spatialized stereo audio output mode available to all applications, installed on the computer system, capable of causing output of audio information in accordance with the spatialized stereo audio output mode. For example, as described herein with reference to
In some embodiments, the computer system displays (1060) a settings user interface that concurrently displays: a first user interface element for enabling or disabling use of a spatialized stereo audio output mode for the first application; and a second user interface element for enabling or disabling use of the spatialized stereo audio output mode for the second application (e.g., a toggle or other dual-state affordance is displayed in conjunction with an identifier for each concurrently listed application). In some such embodiments, while displaying the settings user interface, the computer system receives an input. In some such embodiments, in accordance with a determination that the input is directed to the first user interface element: in accordance with a determination that the input corresponds to a request to disable spatialized stereo audio for the first application (e.g., an input directed to the first user interface element while use of the spatialized stereo audio output mode is enabled for the first application), the computer system disables use of the spatialized stereo audio output mode for the first application; and, in accordance with a determination that the input corresponds to a request to enable spatialized stereo audio for the first application (e.g., an input directed to the first user interface element while use of the spatialized stereo audio output mode is disabled for the first application), the computer system enables use of the spatialized stereo audio output mode for the first application (e.g., making the spatialized stereo audio output mode available to the first application). In some such embodiments, in accordance with a determination that the input is directed to the second user interface element: in accordance with a determination that the input corresponds to a request to disable spatialized stereo audio for the second application (e.g., an input directed to the second user interface element while use of the spatialized stereo audio output mode is enabled for the second application), the computer system disables use of the spatialized stereo audio output mode for the second application; and, in accordance with a determination that the input corresponds to a request to enable spatialized stereo audio for the second application (e.g., an input directed to the second user interface element while use of the spatialized stereo audio output mode is disabled for the second application), the computer system enables use of the spatialized stereo audio output mode for the second application (e.g., making the spatialized stereo audio output mode available to the second application). For example, as described herein with reference to
It should be understood that the particular order in which the operations in
In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten or described as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met. A person having ordinary skill in the art would also understand that, similar to a method with contingent steps, a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application claims priority to U.S. Provisional Patent Application No. 63/197,481, filed Jun. 6, 2021, and U.S. Provisional Patent Application No. 63/054,194, filed Jul. 20, 2020, each of which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5003607 | Reed | Mar 1991 | A |
| 8126399 | Lee | Feb 2012 | B1 |
| 8290537 | Lee et al. | Oct 2012 | B2 |
| 8831238 | Rashid et al. | Sep 2014 | B2 |
| 8971546 | Millington et al. | Mar 2015 | B2 |
| 9148717 | Shaffer | Sep 2015 | B2 |
| 9210498 | Shaffer | Dec 2015 | B1 |
| 9342354 | Banda | May 2016 | B2 |
| 9385546 | Wakayama et al. | Jul 2016 | B2 |
| 9398367 | Scott et al. | Jul 2016 | B1 |
| 9729958 | Jaques et al. | Aug 2017 | B2 |
| 9807491 | Kim | Oct 2017 | B2 |
| 9894452 | Termeulen et al. | Feb 2018 | B1 |
| 9936297 | Dennis | Apr 2018 | B2 |
| 9949015 | Minoo et al. | Apr 2018 | B1 |
| 10042595 | Behzadi et al. | Aug 2018 | B2 |
| 10045111 | Bonner et al. | Aug 2018 | B1 |
| 10133358 | Chen et al. | Nov 2018 | B1 |
| 10136214 | Smus et al. | Nov 2018 | B2 |
| 10142577 | Laird | Nov 2018 | B1 |
| 10157037 | Patel et al. | Dec 2018 | B2 |
| 10165347 | Pantfoerder et al. | Dec 2018 | B2 |
| 10200780 | Steiner | Feb 2019 | B2 |
| 10405165 | Llami et al. | Sep 2019 | B2 |
| 10423381 | Utsuki et al. | Sep 2019 | B2 |
| 10560773 | Roadley-Battin et al. | Feb 2020 | B1 |
| 10628105 | Behzadi et al. | Apr 2020 | B2 |
| 10735554 | Jorgovanovic | Aug 2020 | B1 |
| 10873798 | Jackson et al. | Dec 2020 | B1 |
| 10951043 | Behzadi et al. | Mar 2021 | B2 |
| 11006201 | Kumar et al. | May 2021 | B2 |
| 11018516 | Cho et al. | May 2021 | B2 |
| 11089398 | Venkatraman et al. | Aug 2021 | B1 |
| 11115746 | Morrison et al. | Sep 2021 | B1 |
| 11204733 | Behzadi et al. | Dec 2021 | B2 |
| 11211819 | Ng et al. | Dec 2021 | B2 |
| 11228625 | Libin | Jan 2022 | B1 |
| 11240583 | DeMaio | Feb 2022 | B1 |
| 11258280 | Li | Feb 2022 | B2 |
| 11269575 | Behzadi et al. | Mar 2022 | B2 |
| 11688382 | Hull et al. | Jun 2023 | B2 |
| 20030202341 | McClanahan | Oct 2003 | A1 |
| 20030223604 | Nakagawa | Dec 2003 | A1 |
| 20060135218 | Son et al. | Jun 2006 | A1 |
| 20060166718 | Seshadri et al. | Jul 2006 | A1 |
| 20060193487 | Mok et al. | Aug 2006 | A1 |
| 20060200358 | Ohnemus et al. | Sep 2006 | A1 |
| 20070206829 | Weinans et al. | Sep 2007 | A1 |
| 20070213092 | Geelen | Sep 2007 | A1 |
| 20070300063 | Adams et al. | Dec 2007 | A1 |
| 20080065720 | Brodersen et al. | Mar 2008 | A1 |
| 20080076489 | Rosener et al. | Mar 2008 | A1 |
| 20080152160 | Chew et al. | Jun 2008 | A1 |
| 20080166968 | Tang et al. | Jul 2008 | A1 |
| 20080226094 | Rutschman | Sep 2008 | A1 |
| 20080248748 | Sangster et al. | Oct 2008 | A1 |
| 20080280655 | Ozaki | Nov 2008 | A1 |
| 20090081999 | Khasawneh et al. | Mar 2009 | A1 |
| 20090170431 | Pering et al. | Jul 2009 | A1 |
| 20090280871 | Hofer et al. | Nov 2009 | A1 |
| 20100041333 | Ungari et al. | Feb 2010 | A1 |
| 20100074451 | Usher et al. | Mar 2010 | A1 |
| 20100309284 | Samadani et al. | Dec 2010 | A1 |
| 20100310087 | Ishida | Dec 2010 | A1 |
| 20100320961 | Castillo et al. | Dec 2010 | A1 |
| 20110116643 | Tiscareno et al. | May 2011 | A1 |
| 20110159959 | Mallinson et al. | Jun 2011 | A1 |
| 20110222701 | Donaldson et al. | Sep 2011 | A1 |
| 20110286615 | Olodort et al. | Nov 2011 | A1 |
| 20120096188 | Cohen et al. | Apr 2012 | A1 |
| 20120144473 | Wyld | Jun 2012 | A1 |
| 20120215366 | Redmond et al. | Aug 2012 | A1 |
| 20120262537 | Baker et al. | Oct 2012 | A1 |
| 20120289157 | Palin et al. | Nov 2012 | A1 |
| 20120317194 | Tian | Dec 2012 | A1 |
| 20130121494 | Johnston | May 2013 | A1 |
| 20130154917 | Adermann et al. | Jun 2013 | A1 |
| 20130182867 | Knowles | Jul 2013 | A1 |
| 20130311694 | Bhamidipati et al. | Nov 2013 | A1 |
| 20140016803 | Puskarich | Jan 2014 | A1 |
| 20140037104 | Seo et al. | Feb 2014 | A1 |
| 20140126733 | Gauger, Jr. et al. | May 2014 | A1 |
| 20140126734 | Gauger, Jr. et al. | May 2014 | A1 |
| 20140152235 | Huang et al. | Jun 2014 | A1 |
| 20140247948 | Goldstein | Sep 2014 | A1 |
| 20140270200 | Usher et al. | Sep 2014 | A1 |
| 20140341399 | Dusse et al. | Nov 2014 | A1 |
| 20150054458 | Yoon et al. | Feb 2015 | A1 |
| 20150102879 | Jacobs et al. | Apr 2015 | A1 |
| 20150200558 | Castillo et al. | Jul 2015 | A1 |
| 20150230022 | Sakai et al. | Aug 2015 | A1 |
| 20150245126 | Shaffer | Aug 2015 | A1 |
| 20150245127 | Shaffer | Aug 2015 | A1 |
| 20150281830 | Gauger, Jr. et al. | Oct 2015 | A1 |
| 20150294662 | Ibrahim | Oct 2015 | A1 |
| 20150310846 | Andersen et al. | Oct 2015 | A1 |
| 20150319554 | Blanche et al. | Nov 2015 | A1 |
| 20150331940 | Manning | Nov 2015 | A1 |
| 20150351143 | Seymour et al. | Dec 2015 | A1 |
| 20160007140 | Yae et al. | Jan 2016 | A1 |
| 20160014492 | McCarthy et al. | Jan 2016 | A1 |
| 20160029114 | Chen | Jan 2016 | A1 |
| 20160071409 | Suomela et al. | Mar 2016 | A1 |
| 20160072936 | Kim et al. | Mar 2016 | A1 |
| 20160073249 | Moore et al. | Mar 2016 | A1 |
| 20160077843 | Jakoboski et al. | Mar 2016 | A1 |
| 20160094934 | Yang et al. | Mar 2016 | A1 |
| 20160109931 | Kobayashi | Apr 2016 | A1 |
| 20160119708 | Rodzevski et al. | Apr 2016 | A1 |
| 20160134141 | Jentz et al. | May 2016 | A1 |
| 20160165381 | Kapoor et al. | Jun 2016 | A1 |
| 20160180806 | Sharp et al. | Jun 2016 | A1 |
| 20160219358 | Shaffer et al. | Jul 2016 | A1 |
| 20160241972 | Gobeli et al. | Aug 2016 | A1 |
| 20160291666 | Hosoya et al. | Oct 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160351183 | Gauger, Jr. et al. | Dec 2016 | A1 |
| 20170013345 | Kumar et al. | Jan 2017 | A1 |
| 20170048613 | Smus et al. | Feb 2017 | A1 |
| 20170108906 | Chandra et al. | Apr 2017 | A1 |
| 20170134845 | Milam et al. | May 2017 | A1 |
| 20170180840 | Yamkovoy | Jun 2017 | A1 |
| 20170192746 | Jeong | Jul 2017 | A1 |
| 20170193974 | Gadonniex et al. | Jul 2017 | A1 |
| 20170195466 | Chen | Jul 2017 | A1 |
| 20170214994 | Gadonniex et al. | Jul 2017 | A1 |
| 20170245039 | Chen | Aug 2017 | A1 |
| 20170251295 | Pergament et al. | Aug 2017 | A1 |
| 20170256978 | Sauterel et al. | Sep 2017 | A1 |
| 20170293577 | Gomzin et al. | Oct 2017 | A1 |
| 20170318374 | Dolenc et al. | Nov 2017 | A1 |
| 20170339483 | Ergezer et al. | Nov 2017 | A1 |
| 20180014973 | Echeverri et al. | Jan 2018 | A1 |
| 20180048960 | Jeffrey et al. | Feb 2018 | A1 |
| 20180067712 | Behzadi et al. | Mar 2018 | A1 |
| 20180081453 | Ely | Mar 2018 | A1 |
| 20180088897 | Mathur | Mar 2018 | A1 |
| 20180114518 | Scanlan et al. | Apr 2018 | A1 |
| 20180132088 | Lee | May 2018 | A1 |
| 20180152781 | Boyer et al. | May 2018 | A1 |
| 20180206022 | Hsieh | Jul 2018 | A1 |
| 20180206025 | Rule et al. | Jul 2018 | A1 |
| 20180242085 | Dohmen et al. | Aug 2018 | A1 |
| 20180249266 | Termeulen et al. | Aug 2018 | A1 |
| 20180277123 | Boesen et al. | Sep 2018 | A1 |
| 20180279063 | Sun et al. | Sep 2018 | A1 |
| 20180286428 | Seider | Oct 2018 | A1 |
| 20180295439 | Garrett | Oct 2018 | A1 |
| 20180295455 | Eichfeld et al. | Oct 2018 | A1 |
| 20180301134 | Le et al. | Oct 2018 | A1 |
| 20180341448 | Behzadi et al. | Nov 2018 | A1 |
| 20180376528 | Lee et al. | Dec 2018 | A1 |
| 20190007780 | Sheaffer | Jan 2019 | A1 |
| 20190052951 | Kofman et al. | Feb 2019 | A1 |
| 20190075385 | Lee et al. | Mar 2019 | A1 |
| 20190081499 | Sun et al. | Mar 2019 | A1 |
| 20190124432 | Champy | Apr 2019 | A1 |
| 20190155487 | Zhao et al. | May 2019 | A1 |
| 20190179604 | Alexander et al. | Jun 2019 | A1 |
| 20190215611 | Lou et al. | Jul 2019 | A1 |
| 20190278556 | Usher et al. | Sep 2019 | A1 |
| 20190305591 | Ng et al. | Oct 2019 | A1 |
| 20190313178 | Mutlu et al. | Oct 2019 | A1 |
| 20190320282 | Moeller | Oct 2019 | A1 |
| 20190339825 | Anzures et al. | Nov 2019 | A1 |
| 20190341050 | Diamant et al. | Nov 2019 | A1 |
| 20190361666 | Oide | Nov 2019 | A1 |
| 20190394607 | Laaksonen et al. | Dec 2019 | A1 |
| 20200007989 | Gong et al. | Jan 2020 | A1 |
| 20200014792 | Lyren et al. | Jan 2020 | A1 |
| 20200067340 | Batra et al. | Feb 2020 | A1 |
| 20200120384 | Armaly | Apr 2020 | A1 |
| 20200150740 | Zhang et al. | May 2020 | A1 |
| 20200169101 | Li | May 2020 | A1 |
| 20200213705 | Ding et al. | Jul 2020 | A1 |
| 20200213799 | Lyren | Jul 2020 | A1 |
| 20200218486 | Behzadi et al. | Jul 2020 | A1 |
| 20200275223 | Usher et al. | Aug 2020 | A1 |
| 20200367006 | Beckhardt | Nov 2020 | A1 |
| 20210014610 | Carrigan et al. | Jan 2021 | A1 |
| 20210014611 | Carrigan et al. | Jan 2021 | A1 |
| 20210014612 | Carrigan | Jan 2021 | A1 |
| 20210014613 | Carrigan et al. | Jan 2021 | A1 |
| 20210126470 | Banerjee et al. | Apr 2021 | A1 |
| 20210210967 | Xiongbin | Jul 2021 | A1 |
| 20210218595 | Liu et al. | Jul 2021 | A1 |
| 20210255816 | Behzadi et al. | Aug 2021 | A1 |
| 20210258419 | Lyren et al. | Aug 2021 | A1 |
| 20210281943 | Lehnert | Sep 2021 | A1 |
| 20210329367 | Fletcher et al. | Oct 2021 | A1 |
| 20210376880 | Carrigan et al. | Dec 2021 | A1 |
| 20210377663 | Carrigan et al. | Dec 2021 | A1 |
| 20210391739 | Venkatraman et al. | Dec 2021 | A1 |
| 20220078864 | Yang et al. | Mar 2022 | A1 |
| 20220103963 | Satongar et al. | Mar 2022 | A1 |
| 20220107771 | Behzadi et al. | Apr 2022 | A1 |
| 20220256275 | Bang et al. | Aug 2022 | A1 |
| 20220374197 | Carrigan | Nov 2022 | A1 |
| 20230007398 | Carrigan | Jan 2023 | A1 |
| 20230020542 | Satongar et al. | Jan 2023 | A1 |
| 20230246671 | Carrigan et al. | Aug 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 102439972 | May 2012 | CN |
| 104054323 | Sep 2014 | CN |
| 104365173 | Feb 2015 | CN |
| 106291121 | Jan 2017 | CN |
| 2190213 | May 2010 | EP |
| 3188495 | Jul 2017 | EP |
| 3001695 | Jul 2018 | EP |
| 3456299 | Mar 2019 | EP |
| 3599777 | Jan 2020 | EP |
| 3664092 | Jun 2020 | EP |
| 2009-532937 | Sep 2009 | JP |
| 2011-521504 | Jul 2011 | JP |
| 2013-051626 | Mar 2013 | JP |
| 2016-076202 | May 2016 | JP |
| 2017126873 | Jul 2017 | JP |
| 2014-0018701 | Feb 2014 | KR |
| 2015-0021803 | Mar 2015 | KR |
| 101518010 | May 2015 | KR |
| 2016-0098522 | Aug 2016 | KR |
| 2016-0103779 | Sep 2016 | KR |
| 2017-0138588 | Dec 2017 | KR |
| 2019-0013880 | Feb 2019 | KR |
| WO 2008000304 | Jan 2008 | WO |
| WO 2012170446 | Dec 2012 | WO |
| WO 2013030736 | Mar 2013 | WO |
| WO 2013064747 | May 2013 | WO |
| WO 2015006950 | Jan 2015 | WO |
| WO 2015185123 | Dec 2015 | WO |
| WO 2016036541 | Mar 2016 | WO |
| WO 2016063143 | Apr 2016 | WO |
| WO 2016066483 | May 2016 | WO |
| WO 2019053993 | Mar 2019 | WO |
| WO 2020204611 | Oct 2020 | WO |
| WO-2021122076 | Jun 2021 | WO |
| WO 2021136671 | Jul 2021 | WO |
| WO 2022031260 | Feb 2022 | WO |
| Entry |
|---|
| 3GPP, “3rd Generation Partnership project; Technical Specification Group Services and System Aspects; Release 16”, ftp://ftp.3gpp.org/specs/archive/26_series/26.928/26928-110.zip 26928-110-rm.doc, Oct. 29, 2019, 4 pages. |
| Aguilera et al., “Spatial Audio for Audioconferencing in Mobile Devices: Investigating the Importance of Virtual Mobility and Private Communication and Optimizations”, https://www.aes.og/e-lib=18138, 4 pages. |
| Office Action, dated Mar. 29, 2022, received from Chinese Patent Application No. 202011538744.0, which corresponds with U.S. Appl. No. 16/056,328, 1 page. |
| Notice of Allowance, dated Mar. 11, 2022, received in Japanese Patent Application No. 2019-207313, which corresponds with U.S. Appl. No. 16/056,328, 2 pages. |
| Patent, dated Mar. 25, 2022, received in Japanese Patent Application No. 2019-207313, which corresponds with U.S. Appl. No. 16/056,328, 3 pages. |
| Patent, dated Feb. 17, 2022, 2022, received in Australian Patent Application No. 2020-239693, which corresponds with U.S. Appl. No. 16/920,303, 3 pages. |
| Office Action, dated Feb. 21, 2022, received in Indian Patent Application No. 202017041564, which corresponds with U.S. Appl. No. 16/920,303, 6 pages. |
| Office Action, dated Apr. 13, 2022, received in Korean Patent Application No. 2020-7027641, which corresponds with U.S. Appl. No. 16/920,303, 7 pages. |
| Final Office Action, dated Jun. 2, 2022, received in U.S. Appl. No. 17/023,265, 19 pages. |
| Patent, dated Mar. 31, 2022, received in Australian Patent Application No. 2021201777, which corresponds with U.S. Appl. No. 16/824,506, 3 pages. |
| Notice of Allowance, dated Mar. 21, 2022, received in U.S. Appl. No. 17/031,637, 7 pages. |
| Notice of Allowance, dated Apr. 26, 2022, received in Danish Patent Application No. 2020-70718, which corresponds with U.S. Appl. No. 17/028,936, 2 pages. |
| Office Action, dated May 25, 2022, received in U.S. Appl. No. 17/028,943, 5 pages. |
| Patent, dated Mar. 21, 2022, received in Danish Patent Application No. 2020-70719, which corresponds with U.S. Appl. No. 17/028,936, 5 pages. |
| Intent to Grant, dated May 5, 2022, received in Danish Patent Application No. 202070720, which corresponds with U.S. Appl. No. 17/028,947, 2 pages. |
| Final Office Action, dated Feb. 10, 2022, received in Korean Patent Application No. 2021-7022726, which corresponds with U.S. Appl. No. 17/306,898, 4 pages. |
| Office Action, dated Jun. 8, 2022, received in Korean Patent Application No. 2022-7016117, which corresponds with U.S. Appl. No. 17/553,018, 5 pages. |
| Invitation to Pay Additional Fees, dated Mar. 9, 2022, received in International Patent Application No. PCT/US2021/052052, which corresponds with U.S. Appl. No. 17/483,741, 23 pages. |
| International Search Report and Written Opinion, dated May 3, 2022, received in International Patent Application No. PCT/US2021/052052, which corresponds with U.S. Appl. No. 17/483,741, 54 pages. |
| Office Action, dated Aug. 12, 2022, received in Japanese Patent Application No. 2020-550113, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Notice of Allowance, dated Aug. 29, 2022, received in U.S. Appl. No. 17/483,741, 42 pages. |
| Office Action, dated Oct. 7, 2022, received in Australian Patent Application No. 2021245251, which corresponds with U.S. Appl. No. 17/028,936, 3 pages. |
| Patent, dated Aug. 11, 2022, received in Danish Patent Application No. 2020-70718, which corresponds with U.S. Appl. No. 17/028,936, 3 pages. |
| Notice of Allowance, dated Jul. 28, 2022, received in Danish Patent Application No. 202070720, which corresponds with U.S. Appl. No. 17/028,947, 2 pages. |
| Patent, dated Oct. 6, 2022, received in Danish Patent Application No. 202070720, which corresponds with U.S. Appl. No. 17/028,947, 5 pages. |
| Office Action, dated Sep. 1, 2022, received in U.S. Appl. No. 17/023,274, 16 pages. |
| Extended European Search Report, dated Jul. 29, 2022, received in European Patent Application No. 22161118.9, which corresponds with U.S. Appl. No. 17/028,943, 8 pages. |
| Office Action, dated Jun. 29, 2022, received in Chinese Patent Application No. 202011544171.2, which corresponds with U.S. Appl. No. 16/824,506, 5 pages. |
| Notice of Allowance, dated Jun. 29, 2022, received in U.S. Appl. No. 17/028,943, 7 pages. |
| Office Action, dated Jun. 24, 2021, received in U.S. Appl. No. 16/920,303, 5 pages. |
| Office Action, dated Dec. 21, 2020, received in Danish Patent Application No. 2020-70630, which corresponds with U.S. Appl. No. 16/920,303, 8 pages. |
| Intention to Grant, Action, dated Mar. 3, 2021, received in Danish Patent Application No. 2020-70630, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Notice of Allowance, dated Jun. 10, 2021, received in Danish Patent Application No. 2020-70630, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Office Action, dated Jan. 1, 2021, received in U.S. Appl. No. 17/028,936, 16 pages. |
| Final Office Action, dated Apr. 9, 2021, received in U.S. Appl. No. 17/028,936, 17 pages. |
| Notice of Allowance, dated Aug. 20, 2021, received in U.S. Appl. No. 17/028,936, 7 pages. |
| Office Action, dated Jan. 29, 2021, received in Danish Patent Application No. 2020-70718, which corresponds with U.S. Appl. No. 17/028,936, 7 pages. |
| Office Action, dated Jan. 29, 2021, received in Danish Patent Application No. 2020-70719, which corresponds with U.S. Appl. No. 17/028,936, 7 pages. |
| Intention to Grant, dated Aug. 27, 2021, received in Danish Patent Application No. 2020-70719, which corresponds with U.S. Appl. No. 17/028,936, 2 pages. |
| Office Action, dated Dec. 24, 2020, received in U.S. Appl. No. 17/028,947, 10 pages. |
| Final Office Action, dated Mar. 17, 2021, received in U.S. Appl. No. 17/028,947, 8 pages. |
| Office Action, dated Feb. 2, 2021, received in Danish Patent Application No. 202070720, which corresponds with U.S. Appl. No. 17/028,947, 3 pages. |
| Invitation to Pay Additional Fees, dated Oct. 8, 2020, received in International Patent Application No. PCT/2020/041074, which corresponds with U.S. Appl. No. 16/920,303, 24 pages. |
| International Search Report and Written Opinion, dated Dec. 3, 2020, received in International Patent Application No. PCT/US2020/041074, which corresponds with U.S. Appl. No. 16/920,303, 28 pages. |
| Samsung Electronics America, Inc., “Gear Icon X SM-R150”, User Manual, https://static.bhphtovideo.com/lit_files/268655.pdf, Aug. 6, 2016, 43 pages. |
| Office Action, dated Feb. 27, 2017, received in U.S. Appl. No. 15/271,114, 18 pages. |
| Final Office Action, dated Nov. 9, 2017, received in U.S. Appl. No. 15/271,114, 18 pages. |
| Notice of Allowance, dated Apr. 10, 2018, received in U.S. Appl. No. 15/271,114, 10 pages. |
| Innovation Patent, dated Aug. 16, 2017, received in Australian Patent Application No. 2017101032, which corresponds with U.S. Appl. No. 15/271,114, 4 pages. |
| Office Action, dated Nov. 6, 2017, received in Australian Patent Application No. 2017101032, which corresponds with U.S. Appl. No. 15/271,114, 5 pages. |
| Certificate of Exam, dated May 1, 2018, received in Australian Patent Application No. 2017101032, which corresponds with U.S. Appl. No. 15/271,114, 1 page. |
| Notice of Acceptance, dated Feb. 19, 2019, received in Australian Patent Application No. 2017324072, which corresponds with U.S. Appl. No. 15/271,114, 3 pages. |
| Certificate of Grant, dated Jun. 13, 2019, received in Australian Patent Application No. 2017324072, which corresponds with U.S. Appl. No. 15/271,114, 1 page. |
| Office Action, dated Sep. 25, 2019, received in Chinese Patent Application No. 201710741130.4, which corresponds with U.S. Appl. No. 15/271,114, 5 pages. |
| Office Action, dated Jun. 18, 2020, received in Chinese Patent Application No. 201710741130.4, which corresponds with U.S. Appl. No. 15/271,114, 10 pages. |
| Notice of Allowance, dated Nov. 27, 2020, received in Chinese Patent Application No. 201710741130.4, which corresponds with U.S. Appl. No. 15/271,114, 3 pages. |
| Patent, dated Jan. 22, 2021, received in Chinese Patent Application No. 201710741130.4, which corresponds with U.S. Appl. No. 15/271,114, 6 pages. |
| Office Action, dated Dec. 16, 2016, received in Danish Patent Application No. 201670727, which corresponds with U.S. Appl. No. 15/271,114, 7 pages. |
| Office Action, dated May 29, 2017, received in Danish Patent Application No. 201670727, which corresponds with U.S. Appl. No. 15/271,114, 6 pages. |
| Office Action, dated Dec. 13, 2017, received in Danish Patent Application No. 201670727, which corresponds with U.S. Appl. No. 15/271,114, 6 pages. |
| Office Action, dated Aug. 16, 2019, received in European Patent Application No. 17746593.7, which corresponds with U.S. Appl. No. 15/271,114, 6 pages. |
| Office Action, dated Jul. 5, 2019, received in Japanese Patent Application No. 2019-506652, which corresponds with U.S. Appl. No. 15/271,114, 4 pages. |
| Notice of Allowance, dated Oct. 18, 2019, received in Japanese Patent Application No. 2019-506652, which corresponds with U.S. Appl. No. 15/271,114, 5 pages. |
| Patent, dated Nov. 22, 2019, received in Japanese Patent Application No. 2019-506652, which corresponds with U.S. Appl. No. 15/271,114, 3 pages. |
| Office Action, dated Jun. 17, 2019, received in Korean Patent Application No. 2019-7004211, which corresponds with U.S. Appl. No. 15/271,114, 3 pages. |
| Notice of Allowance, dated Sep. 17, 2019, received in Korean Patent Application No. 2019-7004211, which corresponds with U.S. Appl. No. 15/271,114, 4 pages. |
| Patent, dated Dec. 4, 2019, received in Korean Patent Application No. 2019-7004211, which corresponds with U.S. Appl. No. 15/271,114, 4 pages. |
| Office Action, dated Oct. 3, 2019, received in U.S. Appl. No. 16/056,328, 11 pages. |
| Notice of Allowance, dated Jan. 15, 2020, received in U.S. Appl. No. 16/056,328, 7 pages. |
| Notice of Allowance, dated Feb. 22, 2021, received in Australian Patent Application No. 2019203626, which corresponds with U.S. Appl. No. 16/056,328, 3 pages. |
| Certificate of Grant, dated Jun. 24, 2021, received in Australian Patent Application No. 2019203626, which corresponds with U.S. Appl. No. 16/056,328, 3 pages. |
| Office Action, dated Jul. 2, 2021, received from Chinese Patent Application No. 202011538744.0, which corresponds with U.S. Appl. No. 16/056,328, 4 pages. |
| Office Action, dated Dec. 30, 2021, received from Chinese Patent Application No. 202011538744.0, which corresponds with U.S. Appl. No. 16/056,328, 2 pages. |
| Office Action, dated Jan. 12, 2021, received in Japanese Patent Application No. 2019-207313, which corresponds with U.S. Appl. No. 16/056,328, 5 pages. |
| Office Action, dated Oct. 18, 2021, received in Japanese Patent Application No. 2019-207313, which corresponds with U.S. Appl. No. 16/056,328, 2 pages. |
| Office Action, dated Apr. 6, 2020, received in Korean Patent Application No. 2019-7035730, which corresponds with U.S. Appl. No. 16/056,328, 2 pages. |
| Notice of Allowance, dated Jun. 23, 2020, received in Korean Patent Application No. 2019-7035730, which corresponds with U.S. Appl. No. 16/056,328, 2 pages. |
| Patent, dated Sep. 14, 2020, received in Korean Patent Application No. 2019-7035730, which corresponds with U.S. Appl. No. 16/056,328, 3 pages. |
| Office Action, dated Jan. 7, 2022, received in Japanese Patent Application No. 2020-550113, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Office Action, dated Sep. 4, 2020, received in U.S. Appl. No. 16/824,506, 17 pages. |
| Final Office Action, dated Mar. 22, 2021, received in U.S. Appl. No. 16/824,506, 22 pages. |
| Office Action, dated Aug. 5, 2021, received in U.S. Appl. No. 16/824,506, 20 pages. |
| Notice of Allowance, dated Oct. 18, 2021, received in U.S. Appl. No. 16/824,506, 9 pages. |
| Intent to Grant, dated Sep. 29, 2021, received in Australian Patent Application No. 2021201777, which corresponds with U.S. Appl. No. 16/824,506, 3 pages. |
| Notice of Acceptance, dated Nov. 29, 2021, received in Australian Australian Patent Application No. 2021201777, which corresponds with U.S. Appl. No. 16/824,506, 3 pages. |
| Office Action, dated Jun. 9, 2021, received in Chinese Patent Application No. 202011544171.2, which corresponds with U.S. Appl. No. 16/824,506, 1 page. |
| Office Action, dated Nov. 11, 2021, received in Chinese Patent Application No. 202011544171.2, which corresponds with U.S. Appl. No. 16/824,506. (English translation is provided.) 5 pages. |
| Notice of Allowance, dated May 24, 2021, received in Korean Patent Application No. 2020-7026460, which corresponds with U.S. Appl. No. 16/824,506, 2 pages. |
| Notice of Allowance, dated Feb. 1, 2022, received in U.S. Appl. No. 17/031,637, 26 pages. |
| Intention to Grant, dated Jan. 7, 2022, received in Danish Patent Application No. 2020-70718, which corresponds with U.S. Appl. No. 17/028,936, 2 pages. |
| Notice of Allowance, dated Oct. 29, 2021, received in U.S. Appl. No. 17/306,898, 5 pages. |
| Office Action, dated Aug. 20, 2021, received in Korean Patent Application No. 2021-7022726, which corresponds with U.S. Appl. No. 17/306,898, 5 pages. |
| International Search Report and Written Opinion, dated Oct. 17, 2017, received in International Patent Application No. PCT/US2017/043047, which corresponds with U.S. Appl. No. 15/271,114, 12 pages. |
| International Search Report and Written Opinion, dated Sep. 8, 2021, received in International Patent Application No. PCT/US2021/033200, which corresponds with U.S. Appl. No. 17/023,265, 17 pages. |
| International Search Report and Written Opinion, dated Jan. 11, 2022, received in International Patent Application No. US/2021/042402, which corresponds with U.S. Appl. No. 17/031,637, 22 pages. |
| Anonymous, “RX-V3800AV Receiver Owner's Manual”, Yamaha Music Manuals, Dec. 31, 2007, pp. 35, 36, 44-50. |
| Office Action, dated Sep. 14, 2021, received in U.S. Appl. No. 16/920,303, 7 pages. |
| Office Action, dated Sep. 10, 2021, received in Australian Patent Application No. 2020-239693, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Notice of Allowance, dated Oct. 15, 2021, received in Australian Patent Application No. 2020-239693, which corresponds with U.S. Appl. No. 16/920,303, 3 pages. |
| Patent, dated Oct. 14, 2021, received in Danish Patent Application No. 2020-70630, which corresponds with U.S. Appl. No. 16/920,303, 6 pages. |
| Notice of Allowance, dated Sep. 29, 2021, received in U.S. Appl. No. 17/028,936, 7 pages. |
| Office Action, dated Oct. 22, 2021, received in Danish Patent Application No. 2020-70718, which corresponds with U.S. Appl. No. 17/028,936, 4 pages. |
| Notice of Allowance, dated Dec. 16, 2021, received in Danish Patent Application No. 2020-70719, which corresponds with U.S. Appl. No. 17/028,936, 2 pages. |
| Office Action, dated Sep. 27, 2021, received in U.S. Appl. No. 17/028,947, 10 pages. |
| Notice of Allowance, dated Dec. 13, 2021, received in U.S. Appl. No. 17/028,947, 5 pages. |
| Office Action, dated Nov. 4, 2021, received in Danish Patent Application No. 202070720, which corresponds with U.S. Appl. No. 17/028,947, 3 pages. |
| Invitation to Pay Additional Fees, dated Nov. 18, 2021, received in International Patent Application No. PCT/2021/042402, which corresponds with U.S. Appl. No. 17/031,637, 22 pages. |
| Office Action, dated Jan. 19, 2023, received from Chinese Patent Application No. 202011538744.0, which corresponds with U.S. Appl. No. 16/056,328, 1 page. |
| Patent, dated Dec. 8, 2022, received in Japanese Patent Application No. 2020-550113, which corresponds with U.S. Appl. No. 16/920,303, 3 pages. |
| Notice of Allowance, dated Mar. 21, 2023, received in U.S. Appl. No. 17/023,265, 9 pages. |
| Office Action, dated Jan. 18, 2023, received in Australian Patent Application No. 2021245251, which corresponds with U.S. Appl. No. 17/028,936, 3 pages. |
| Intent to Grant, dated Feb. 1, 2023, received from European Patent Application No. 22161118.9, which corresponds with U.S. Appl. No. 17/028,936, 8 pages. |
| Notice of Allowance, dated Mar. 9, 2023, received in U.S. Appl. No. 17/023,274, 10 pages. |
| Office Action, dated Mar. 3, 2023, received in Japanese Patent Application No. 2022-018022, which corresponds with U.S. Appl. No. 17/306,898, 6 pages. |
| Office Action, dated Apr. 17, 2023, received in U.S. Appl. No. 17/898,735, 16 pages. |
| Notice of Allowance, dated Nov. 14, 2022, received in Japanese Patent Application No. 2020-550113, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Office Action, dated Nov. 24, 2021, received in U.S. Appl. No. 17/023,265, 16 pages. |
| Notice of Allowance, dated Nov. 17, 2022, received in U.S. Appl. No. 17/023,265, 10 pages. |
| Office Action, dated Aug. 5, 2021, received in U.S. Appl. No. 17/306,898, 6 pages. |
| Office Action, dated Dec. 8, 2022, received in Korean Patent Application No. 2022-7016117, which corresponds with U.S. Appl. No. 17/553,018, 5 pages. |
| Office Action, dated Jun. 23, 2022, received in U.S. Appl. No. 17/553,018, 17 pages. |
| Patent, dated Jun. 13, 2023, received from Chinese Patent Application No. 202011538744.0, which corresponds with U.S. Appl. No. 16/056,328, 6 pages. |
| Notice of Allowance, dated May 24, 2023, received in Korean Patent Application No. 2020-7027641, which corresponds with U.S. Appl. No. 16/920,303, 2 pages. |
| Decision to Grant, dated Jun. 22, 2023, received from European Patent Application No. 22161118.9, which corresponds with U.S. Appl. No. 17/028,936, 3 pages. |
| Patent, dated Jul. 19, 2023. received in European Patent Application No. 23175376.5, which corresponds with U.S. Appl. No. 17/028,936, 3 pages. |
| Notice of Allowance, dated Sep. 8, 2023, received in Japanese Patent Application No. 2022-018022, which corresponds with U.S. Appl. No. 17/306,898, 1 page. |
| Final Office Action, dated Sep. 19, 2023, received in U.S. Appl. No. 17/898,735, 15 pages. |
| European Search Report, dated Sep. 1, 2023, received in European Patent Application No. 23175376.5, 16 pages. |
| Office Action, dated Oct. 10, 2023, received in European Patent Application No. 20745450.5, which corresponds with U.S. Appl. No. 16/920,303, 9 pages. |
| Office Action, dated Oct. 13, 2023, received in U.S. Appl. No. 17/947,042, 29 pages. |
| Patent, dated Oct. 5, 2023, received in Japanese Patent Application No. 2022-018022, which corresponds with U.S. Appl. No. 17/306,898, 4 pages. |
| Final Office Action, dated Oct. 17, 2023, received in Korean Patent Application No. 2022-7016117, which corresponds with U.S. Appl. No. 17/553,018, 4 pages. |
| Final Office Action, dated Jan. 16, 2024, received in U.S. Appl. No. 17/553,018, 17 pages. |
| Office Action, dated Jan. 8, 2024, received in U.S. Appl. No. 17/898,735, 16 pages. |
| Invitation to Pay Additional Fees, dated Dec. 13, 2023, received in International Patent Application No. PCT/US2023/032012, which corresponds with U.S. Appl. No. 18/241,778, 13 pages. |
| Patent, dated Nov. 28, 2023, received in Chinese Patent Application No. 202011544171.2, which corresponds with U.S. Appl. No. 16/824,506, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220019403 A1 | Jan 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63197481 | Jun 2021 | US | |
| 63054194 | Jul 2020 | US |
