Controller with adjustable features

Abstract

A controller is disclosed that allows for adjustment of various features of the controller. The controller may include one or more speakers for outputting sound or audio content. A user can touch one or more of the speakers with their fingers to adjust characteristics of the audio content and / or adjust audio settings. For example, a user can touch a speaker with their finger to change the volume (e.g., increase or decrease) or mute the sound. In some cases, the speaker may be located on the controller body of the handheld controller for convenient and quick access by the user.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a PCT application which claims priority to co-pending, commonly owned U.S. Provisional Patent Application No. 62 / 977,046, entitled "CONTROLLER WITH ADJUSTABLE FEATURES", filed February 14, 2020, which claims priority to U.S. Provisional Patent Application No. 17 / 174,216, entitled "CONTROLLER WITH ADJUSTABLE FEATURES", filed February 11, 2021, each of which is incorporated by reference in its entirety herein. [Background technology]

[0002] Handheld controllers are used in an array of architectures to provide input to local or remote computing devices, for example. For example, handheld controllers are utilized in the gaming industry to allow players to interact with personal computing devices running gaming applications, game consoles, game servers, or the handheld controller itself, etc. While current handheld controllers offer a range of functionality, further technological improvements can enhance the user experience that these controllers provide. [Brief description of the drawings]

[0003] The detailed description is now described with reference to the accompanying drawings, in which the leftmost digit(s) of a reference number identifies the figure in which the reference number first appears, and the same or similar reference numbers in different drawings indicate similar or identical items.

[0004] [Figure 1] 1 illustrates a front perspective view of an exemplary handheld controller that partially includes one or more speakers, where a user operating the handheld controller can adjust characteristics of audio content being output by the speakers by touching the speakers with a finger.

[0005] [Diagram 2] 1 illustrates an exemplary technique for detecting finger contact on a speaker of a handheld controller.

[0006] [Diagram 3] 1 illustrates another example technique for detecting finger contact on a speaker of a handheld controller and / or detecting finger gestures and gesture directionality on the speaker.

[0007] [Figure 4] 1 illustrates another exemplary technique for detecting finger contact on a speaker of a handheld controller.

[0008] [Diagram 5] 1 illustrates another exemplary technique for detecting finger contact on a speaker of a handheld controller.

[0009] [Figure 6] 1 illustrates an example process for adjusting audio characteristics of audio content being output from a speaker based at least in part on sensor data.

[0010] [Figure 7] 1 illustrates an example process for adjusting a volume of audio content being output from a speaker based at least in part on sensor data.

[0011] [Figure 8] 1 illustrates an example process for adjusting audio characteristics of audio content being output from a speaker using high frequency audio (HFA) tones.

[0012] [Figure 9]1 shows a front perspective view of an exemplary handheld controller partially including a display screen and one or more front controls having touch sensors for detecting the presence and location of a user operating the handheld controller. The controller may also include a mechanism for adjusting the sensitivity of the one or more front controls. The adjustment feature may provide a more versatile and / or versatile handheld controller.

[0013] [Figure 10] 10 illustrates a rear view of an example handheld controller, such as the handheld controller of FIG. 9, partially including one or more rear controls.

[0014] [Figure 11] 10 illustrates a rear view of an example handheld controller, such as the handheld controller of FIG. 9, partially including one or more receptacles for receiving add-on components. The add-on components can improve the ergonomics of the handheld controller and / or provide different functionality.

[0015] [Figure 12] 10 illustrates a rear view of an example handheld controller, such as the handheld controller of FIG. 9, partially including one or more receptacles for receiving one or more add-on components.

[0016] [Figure 13] 10 illustrates a rear view of an example handheld controller, such as the handheld controller of FIG. 9, partially including one or more rear controls at least partially operable through a first rear cover. The first rear cover may be interchangeable with other rear covers to provide different functionality to the handheld controller.

[0017] [Figure 14]14 illustrates a rear view of the handheld controller of FIG. 13 partially including a second rear cover. The second rear cover may be interchangeable with the first rear cover of FIG. 13 to simplify certain controls and / or functions of the handheld controller.

[0018] [Figure 15] 14 illustrates a rear view of the handheld controller of FIG. 13 partially including a third rear cover to provide extended features to the controller. The third rear cover may be interchangeable with the first rear cover of FIG. 13 and / or the second rear cover of FIG. 14 to provide different functionality to the handheld controller.

[0019] [Figure 16A] 16A shows a front perspective view of the handheld controller of FIG. 9 partially including a knob for adjusting the sensitivity of one or more front controls. In FIG. 16A, the knob is shown in a first position corresponding to a first sensitivity of the one or more front controls.

[0020] [Figure 16B] 16A shows a front perspective view of the handheld controller of FIG. 9 partially including a knob for adjusting the sensitivity of one or more front controls. In FIG. 16B, the knob is shown in a second position corresponding to a second sensitivity of the one or more front controls.

[0021] [Figure 17A] FIG. 1 shows a first perspective view of a dial mechanism for adjusting the sensitivity of one or more front controls.

[0022] [Figure 17B] 17B shows a second perspective view of the dial mechanism of FIG. 17A for adjusting the sensitivity of one or more front controls.

[0023] [Figure 18] 1 illustrates selected functional components of an exemplary handheld controller. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] As discussed above, handheld controllers are used in a variety of environments and include a variety of functions, however, some conventional handheld controllers include a static configuration despite the fact that different users may have different configuration needs, grips, and / or preferences.

[0025] Described herein are handheld controllers having various controls for, among other things, engaging in video game play via a running video game application and / or controlling other types of applications and / or programs. In some cases, the handheld controller may include controls for controlling a game or application running on the handheld controller itself (e.g., a standalone handheld gaming system that is substantially self-contained on the controller). In some cases, the handheld controller may include controls for controlling a remote device (e.g., a television, an audio system, a personal computing device, a game console, etc.). The handheld controller may include one or more controls, including one or more front controls on the front of the housing of the handheld controller. These front controls may include one or more joysticks, directional pads (D-pads), track pads, track balls, buttons, or other controls controllable, for example, by the thumbs of a user of the handheld controller.

[0026] Additionally or alternatively, the handheld controller may include one or more top controls present on a top surface of the housing of the handheld controller. These top controls may be referred to as "triggers" or "bumpers," etc., and may be controllable by one or more fingers of a user, such as a middle finger or index finger. In some cases, the handheld controller includes one or more top controls operable by one or more fingers of a user's left hand and / or one or more fingers of a user's right hand. Additionally, the handheld controller may include one or more rear controls. In some cases, the rear controls may include one or more controls operable by a user's left hand and / or a user's right hand.

[0027] The handheld controllers described herein allow for different configurations depending on the needs of different applications (e.g., game titles) and users, etc. Thus, the techniques described herein allow for dynamically configurable handheld controllers that remedy some of the current deficiencies of conventional handheld controllers, as discussed above.

[0028] In some cases, the handheld controller may include one or more speakers for outputting sound or audio content. The audio content may be associated with a running game or application. The speakers may be located on the front, sides, top, bottom, and / or back of the handheld controller. A user may touch one or more of the speakers with a finger to adjust characteristics of the audio content and / or adjust audio settings. For example, a user may touch a speaker with his or her finger to change (e.g., increase or decrease) the volume or mute the sound. In some cases, the speakers may be located on the controller body of the handheld controller for convenient and quick access by the user. For example, a first speaker may be located on the front of the controller body on or in the left side, left half, or left handle of the handheld controller, while a second speaker may be located on the front of the controller body on or in the right side, right half, or right handle of the handheld controller. In some cases, the user's left thumb can easily access the first speaker and can touch the speaker with the left thumb to increase, decrease, and / or mute the volume while the left hand is holding the controller. Additionally or alternatively, the user's right thumb can easily access the second speaker and can touch the speaker with the right thumb to increase, decrease, or mute the volume while the right hand is holding the controller. In some cases, touching the first speaker can decrease the volume while touching the second speaker can increase the volume (or vice versa). As another example, touching the first speaker and the second speaker simultaneously (or substantially simultaneously) can mute / unmute the volume. As yet another example, the user can swipe in a particular direction (e.g., up, down, left, or right) on the speaker to adjust the characteristics of the audio content being output by the speaker.

[0029] In some examples, one or more sensors can be used to detect or sense finger contact on the speaker, and possibly pressure on the speaker and / or gestures on the speaker (e.g., swipe gestures). Thus, characteristics (e.g., volume) of audio content being output by the speaker can be adjusted based at least in part on sensor data received from the sensors. Various exemplary types of sensors for detecting or sensing finger contact on the speaker are described herein, including, but not limited to, inductive sensors, capacitive sensors, impedance sensors, and / or microphones.

[0030] An exemplary controller system may include a processor and a controller, the controller including a controller body, a speaker disposed on the controller body, and a sensor associated with the speaker and configured to detect finger contact on the speaker. The controller system may further include logic configured to receive data from the sensor indicating that a finger is contacting the speaker, and to adjust characteristics of audio content being output by the speaker based at least in part on the data. Allowing control of audio characteristics via user interaction with the speaker disposed on the controller may provide a user with an intuitive and convenient way to adjust audio characteristics while operating the controller. For example, a user may conveniently maintain attention on a video game being played while adjusting the volume or muting or unmuting sound by touching a speaker disposed near other controls being used to play the video game.

[0031] The present disclosure provides a general understanding of the principles of structure, function, manufacture, and use of the systems and methods disclosed herein. One or more examples of the present disclosure are illustrated in the accompanying drawings. Those skilled in the art will understand that the systems and methods specifically described herein and illustrated in the accompanying drawings are non-limiting embodiments. Features described or described in connection with one embodiment, including between the systems and methods, can be combined with features of other embodiments. Such modifications and variations are intended to be included within the scope of the appended claims.

[0032] 1 illustrates a front view of an exemplary controller 100, according to one embodiment of the disclosure. The controller 100 may be considered handheld if it is operated by a user's hand, regardless of whether the entire controller 100 is supported by or within the user's hand. However, in accordance with various embodiments described herein, the terms "device," "handheld device," "handheld gaming device," "handheld console," "handheld gaming console," "controller," and "handheld controller" may be used interchangeably herein to describe any device, such as the controller 100.

[0033] The controller 100 may include a controller body 102 having a front surface 104. The controller body 102 may further include a rear surface (or rear), a top surface (or top edge or top), a bottom surface (or bottom edge or bottom), a left surface (or left edge or left), and a right surface (or right edge or right). Thus, the controller body 102 may be a rectangular parallelepiped. The front surface 104 and the rear surface may be relatively large surfaces compared to the top surface, the bottom surface, the left surface, and the right surface.

[0034] As shown in FIG. 1, the front surface 104 of the controller body 102 may include a number of controls configured to receive user input. Touch data generated by the controls may be used to detect the presence, location, and / or gestures of a user's fingers operating the controller 100. In some cases, the front surface 104 of the controller body 102 may include one or more front controls, in some cases controllable by one or more thumbs of a user operating the controller 100. Although not shown in FIG. 1, the handheld controller 100 may further include one or more top surface controls present on the top surface (or top edge) of the controller body 102. These top surface controls may include, but are not limited to, triggers or bumpers, and the like, and the top surface controls may be controllable by one or more fingers of a user, such as a middle finger or index finger. Additionally or alternatively, the handheld controller 100 may include one or more rear surface controls present on the rear surface of the controller body 102 and operable by fingers of a user's left and / or right hand. Additionally or alternatively, the handheld controller 100 may include one or more left and / or right side controls present on respective left and right sides of the controller body 102 .

[0035] The front controls may include one or more trackpads, trackballs, joysticks, buttons, or directional pads (D-pads), etc., as described in more detail below. For example, the front surface 104 may include a left joystick 106, a left trackpad 108, and / or a left D-pad 110 controllable by a user's left thumb. In some embodiments, the front surface 104 may include additional left buttons controllable by the left thumb, such as button 112 and button 114. The front surface 104 may also include a right joystick 116, a right trackpad 118, and / or one or more right buttons 120(1)-(4) (e.g., an X button, a Y button, an A button, and a B button) controllable by a user's right thumb. In some embodiments, the front surface 104 may include additional right buttons controllable by the right thumb, such as button 122 and button 124. However, front 104 may include other controls, such as tilt buttons, triggers, knobs, wheels, and / or trackballs, and the controls may be configured to receive input from any combination of a user's thumbs and / or fingers. In some cases, the trigger may be a multi-directional trigger configured to be pushed away from controller 100 and pulled towards handheld controller 100.

[0036] In some embodiments, the track pads 108 and 118 are quadrilateral-shaped track pads. For example, the track pads 108 and 118 may be generally square-shaped track pads. Furthermore, the quadrilateral-shaped track pads 108 and 118 may have rounded corners. Furthermore, as shown in FIG. 1, the straight side edges of each track pad 108 and 118 are aligned (e.g., parallel) with the side (e.g., left and right) edges of the display 126 at the center of the controller body 102 on the front surface 104 of the controller body 102. Compared to a circular track pad, the quadrilateral-shaped track pads 108 and 118 provide extra space in the corners that can be accessed by the user's fingers (e.g., thumbs). Thus, the quadrilateral-shaped track pads 108 and 118 may be more ergonomic than a circular track pad due to the extra area provided by the track pads 108 and 118. For example, the quadrilateral shape of track pads 108 and 118 may give a user the ability to re-orient their hands on controller 100 and still use their thumbs to access track pads 108 and 118. Additionally or alternatively, a user may choose to grip controller body 102 in a slightly different manner, such that the corners of a track pad (e.g., track pads 108 and 118) are used as are the north, south, east, and west portions of the track pad (e.g., as in a diamond shaped track pad).

[0037] Additionally, the controller 100 may include one or more speakers disposed on the controller body 102 that are configured to output audio content or sounds. For example, a video game or another application running on the controller 100 may include audio content that is output during execution of the application (e.g., during gameplay). The speakers may also output other sounds, such as audible notifications.

[0038] 1 illustrates a pair of speakers disposed on the front face 104 of the controller body, the pair including a first (left) speaker 128 and a second (right) speaker 130. The left speaker 128 is shown as being located on the front face 104 and in the left half 132 (or left side) of the front face 104, while the right speaker 130 is shown as being located on the front face 104 and in the right half 134 (or right side) of the front face 104. In some cases, the left speaker 128 and the right speaker 130 may be located on or adjacent to the handle of the controller 100. For example, the left speaker 128 may be located adjacent to or on a left handle 136 of the controller 100 configured to be grasped and / or held by a user's left hand, while the right speaker 130 may be located adjacent to or on a right handle 138 of the controller 100 configured to be grasped and / or held by a user's right hand. In some cases, the left speaker 128 may be located in a location accessible to a user's left thumb while the left hand is holding the controller 100 by the left handle 136, and the right speaker 130 may be located in a location accessible to a user's right thumb while the right hand is holding the controller 100 by the right handle 138. In some examples, the speakers 128, 130 are located on the front surface 104 closer to a bottom end 140 of the controller body 102 than to a top end 142 of the controller body 102.

[0039] 1 shows particular shapes and locations of the speakers 128, 130, the speakers 128, 130 may be located elsewhere on the controller body 102 (e.g., on other portions on the front surface 104, on other surfaces such as the rear, top, bottom, etc.). The speakers 128, 130 may further include different shapes (e.g., spherical, rectangular, elliptical, etc.). Additionally, the controller 100 may include a single speaker or three or more speakers.

[0040] A user may touch a speaker (e.g., the first speaker 128 and / or the second speaker 130) to control or otherwise adjust audio characteristics or features of the audio content being output by the speakers 128, 130. For example, the user's left thumb may touch the first speaker 128 to disable, enable, and / or adjust certain audio features, while the user's right thumb may touch the right speaker 130 to disable, enable, and / or adjust certain audio features. In some cases, a user may touch one or both of the first speaker 128 or the second speaker 130 to mute / unmute the audio. In some cases, a user can touch the first speaker 128 and the second speaker 130 substantially simultaneously (e.g., touch the first speaker 128 and then touch the second speaker 130 within a threshold period, such as within one second or milliseconds, or vice versa) to mute or unmute the audio. In some cases, a user can touch the second speaker 130 to increase the volume and / or touch the first speaker 128 to decrease the volume (or vice versa). In some examples, a user can swipe up or right on the speaker 128 or 130 to increase the volume and / or swipe down or left on the speaker 128 or 130 to decrease the volume. These are examples of interactions (e.g., gestures) that are intuitive to a user.

[0041] In some examples, sensors associated with the speakers 128, 130 may be configured to detect finger contact on the speakers 128, 130 to determine whether audio characteristics should be adjusted. Additionally or alternatively, one or more of the speakers 128, 130 may be depressible to cause activation of a switch (e.g., a switch located directly below the speaker 128, 130), thereby allowing the speaker 128, 130 to be pressed like a button. The sensor configured to detect finger contact on the speaker 128, 130 may be any suitable type of sensor, examples of which are described in more detail below. In general, the sensor may be configured to sense the proximity of a finger to the speaker 128, 130. Thus, the sensor may be a proximity sensor (e.g., a touch sensor). Additionally or alternatively, the sensor may be a pressure sensor configured to detect a press and / or an amount of press force on the speaker 128, 130.

[0042] FIG. 2 illustrates an example technique for detecting finger contact on a speaker 200 of a handheld controller. The speaker 200 depicted in FIG. 2 may be a schematic representation of either or both of the speakers of the handheld controller 100 described herein, such as the first speaker 128 or the second speaker 130. The speaker 200 may include a speaker coil 202 (sometimes referred to herein as a “voice coil 202”). During operation of the speaker 200, an electric current may flow through the speaker coil 202 to move a diaphragm, frame, suspension, or the like, thereby producing sound. A sensor 204 may be coupled to the speaker coil 202 and configured to detect or sense a change in an electrical parameter associated with the speaker coil 202 based at least in part on a finger 206 moving in proximity to the speaker coil 202. For example, the sensor 204 may represent an inductive sensor configured to provide inductance data to a processor of a controller system disclosed herein, the inductance data indicating a change in inductance associated with the speaker coil 202 based on the finger 206 moving in proximity to the speaker coil 202. In some embodiments, the sensor 204 may be part of or represent an amplifier (e.g., a smart amplifier) ​​of the speaker 200. A smart amplifier may be configured utilizing modeling and / or algorithms to produce a robust, rich sound while mitigating damage to the speaker 200. Such a smart amplifier may include or otherwise utilize the sensor 204 to determine a change in inductance caused by the finger 206 moving toward or away from the speaker coil 202 of the speaker 200, which may be determined when an audio waveform is driven from the speaker 200. In this manner, the change in inductance can be used to determine whether a finger 206 is in contact with the speaker 200 (eg, by determining whether the value of inductance meets a threshold inductance).

[0043] Alternatively, the sensor 204 may be omitted from the system, and the speaker coil 202 may be configured to function as an inductive sensor (or "pickup") without the use of a separate sensor to detect inductance chance. In such a configuration, the speaker coil 202 itself may be configured to detect or sense a change in inductance based at least in part on the movement of a finger 206 in proximity to the speaker coil 202. A processor of a controller system disclosed herein may be coupled to the speaker coil 202 to receive an indication of this change in inductance sensed by the speaker coil 202 based on the movement of a finger 206 in proximity to the speaker coil 202, and to adjust an audio characteristic (e.g., volume) in response to the change in inductance.

[0044] As another example, the sensor 204 may represent a capacitance sensor configured to provide capacitance data to a processor of a controller system disclosed herein, the capacitance data indicative of a change in capacitance associated with the speaker coil 202 based on the finger 206 moving in proximity to the speaker coil 202. That is, the sensor 204 may be configured to determine a change in capacitance caused by the finger 206 moving toward or away from the speaker coil 202 of the speaker 200, which may be determined when an audio waveform is driven from the speaker 200. In this manner, the change in capacitance may be utilized to determine whether the finger 206 is in contact with the speaker 200 (e.g., by determining whether the capacitance value meets a threshold capacitance).

[0045] 3 illustrates another exemplary technique for detecting finger contact on a speaker 300 of a handheld controller and / or detecting finger gestures and gesture directionality on the speaker 300. The speaker 300 depicted in FIG. 3 may be a schematic representation of either or both of the speakers of the handheld controller 100 described herein, such as the first speaker 128 or the second speaker 130. The speaker 300 may include a touch sensor 302 disposed in or on the speaker 300. For example, the touch sensor 302 may represent a capacitance array, much like a trackpad touch sensor, attached to a cover of the speaker 300. The touch sensor 302 may be configured to sense or determine the presence, location, and / or gesture of a finger 304 touching the speaker 300. For example, the touch sensor 302 can detect or sense whether a finger 304 is touching the surface of the speaker 300 based on a capacitance value meeting (e.g., meeting or exceeding a threshold, strictly exceeding a threshold). Although a capacitance type sensor is described, the touch sensor 302 can include, but is not limited to, a resistive sensor, an infrared sensor, a touch sensor that utilizes acoustic sound waves to detect the proximity of the finger 304, and / or another sensor for detecting the presence, location, and / or position of an object proximate to the speaker 300, such as the finger 304. In an implementation utilizing capacitance-based sensing, the touch sensor 302 can include electrodes (e.g., transmitter and receiver electrodes of a trans-capacitive type sensor) and a voltage can be applied to the electrodes such that the electrodes are configured to measure a change in capacitance at the electrodes, which can be converted into sensor data in the form of a capacitance value indicative of the proximity of the object to the sensor 302. For example, the capacitance change at the electrodes of a capacitance-based touch sensor can be affected by an object (such as a finger) proximate to the electrodes.Additionally, logic in the controller system may be configured to analyze touch data generated by the touch sensor 302 to identify a gesture of the finger 304 on the speaker 300 (e.g., a swipe gesture), such as the finger 304 moving in a particular direction at a particular speed, as well as the direction of the gesture (e.g., relative up, down, left, right within a fixed reference plane, such as the XY plane shown in FIG. 1). The processor may then adjust audio characteristics (e.g., volume) of the audio content based on the gesture (e.g., based on the direction of the swipe gesture).

[0046] FIG. 4 illustrates an example technique for detecting finger contact on a speaker 400 of a handheld controller. The speaker 400 depicted in FIG. 4 may be a schematic representation of either or both of the speakers of the handheld controller 100 described herein, such as the first speaker 128 or the second speaker 130. The speaker 400 may include leads 402, such as leads of a speaker coil (or voice coil) of the speaker 400. A sensor 404 may be coupled to the leads 402 and configured to detect or sense a change in electrical impedance between the speaker's leads 402 based at least in part on a finger 406 moving in proximity to the speaker. For example, the sensor 404 may represent an impedance sensor configured to provide impedance data to a processor of a controller system disclosed herein, the impedance data indicative of a change in impedance between a pair of leads 402 of the speaker 400 based on a finger 406 moving in proximity to the speaker 400. That is, when the finger 406 covers the speaker 400 by touching it, thus muffling the sound 408 being output from the speaker 400, the acoustic impedance of the speaker 400 may change, which in turn may alter the electrical impedance between the speaker's leads 402. In some implementations, the impedance sensor 404 may be part of or represent an amplifier (e.g., a smart amplifier) ​​of the speaker 400, which may be configured to determine the change in impedance between the speaker's leads 402 caused by the finger 406 moving closer to or farther away from the speaker 400, and thereby muffling or un-muffling the sound 408 being output from the speaker 400, which may be determined when an audio waveform is driven from the speaker 400. In this manner, the change in electrical impedance can be used to determine whether a finger 406 is in contact with the speaker 400 (e.g., by determining whether the impedance value meets a threshold impedance).

[0047] FIG. 5 illustrates an exemplary technique for detecting finger contact on a speaker 500 of a handheld controller. The speaker 500 depicted in FIG. 5 may be a schematic representation of either or both of the speakers of the handheld controller 100 described herein, such as the first speaker 128 or the second speaker 130. The speaker 500 may be configured to output one or more tones 502 at frequencies inaudible to the human ear. As such, such tones 502 may be referred to herein as "high frequency audio (HFA) 502," "high frequency sound 502," or "ultrasonic communication 502." The frequency at which the tones 502 are output using HFA may be greater than a threshold frequency (e.g., greater than about 20 kilohertz (kHz)). In this manner, a human in the vicinity of the speaker 500 (or the controller 100 including the speaker 500) outputting the tones 502 cannot hear the tones. The controller 100 may further include a microphone 504 configured to detect the broadcast tones 502, such as by generating audio data indicative of the HFA tones 502. The series of tones 502 may be output on a periodic basis (e.g., every few milliseconds or seconds, etc.), such that the tones 502 are periodically broadcast from the speaker 500 for use in detecting finger contact. If a finger 506 covers the speaker 500 by touching it, thus muffling the tones 502 being output from the speaker 500, the tones 502 may not be indicated in the audio data generated by the microphone 504. In other words, the microphone 504 may not be able to detect (or "hear") the tone 502 when the finger 506 is muffling the tone 502 being output by the speaker 500, and in this scenario, the audio data generated by the microphone 504 can be used to determine whether the finger 506 is in contact with the speaker 500 (e.g., by determining whether the amplitude of a tone indicated in the audio data above a threshold frequency does not meet the threshold amplitude).

[0048] The processes described herein are illustrated as a collection of blocks in logic flow diagrams that represent sequences of operations, some or all of which may be implemented in hardware (which may be referred to herein as "logic"), software, firmware, or combinations thereof. In the context of software, the blocks may represent computer-executable instructions stored on one or more computer-readable media that, when executed by one or more processors, programs the processors to perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform a particular function or implement a particular data type. The order in which the blocks are described should not be construed as limiting unless otherwise stated. Any number of the described blocks may be combined in any order and / or in parallel to implement a process, or alternative processes, and not all blocks need to be executed.

[0049] 6 shows an example process 600 for adjusting audio characteristics of audio content being output from a speaker based at least in part on sensor data. In some cases, process 600 may be performed by controller 100 and / or a remote device communicatively coupled to controller 100.

[0050] At 602, a processor of a controller system disclosed herein may receive data from a sensor associated with a speaker disposed on the controller body 102 of the controller 100, such as speaker 128 or speaker 130. The sensor from which data is received at block 602 may be any of the sensors described herein, such as a sensor configured to detect finger contact on the associated speaker. Examples of such sensors, such as inductive or capacitive sensor 204, touch sensor 302, impedance sensor 404, and / or microphone 504, are described above with reference to FIGS. 2-5. The data received from the sensor at block 602 may indicate that a finger is touching the speaker. If a remote device is the device making this determination, the controller 100 may transmit the sensor data to the remote device, which may process the provided sensor data to detect a finger touching the speaker.

[0051] At 604, the processor may adjust characteristics of audio content or sounds being output by the speakers based at least in part on the data received at block 602. For example, if the sensor data received at block 602 indicates that a finger is touching the second (right) speaker 130 (located on the front face 104 of the controller body 102 in the right half 134 of the front face 104), the processor may increase the volume of audio content or sounds being output by the first (left) speaker 128 and the second (right) speaker 130. As another example, if the sensor data received at block 602 indicates that a finger is touching the first (left) speaker 128 (located on the front face 104 of the controller body 102 in the left half 132 of the front face 104), the processor may decrease the volume of audio content or sounds being output by the first (left) speaker 128 and the second (right) speaker 130. Thus, an intuitive interaction may be provided by touching the right speaker 130 to increase the volume and / or the left speaker 128 to decrease the volume. As another example, if the sensor data received at block 602 indicates that a finger swipe gesture has been made on the first (left) speaker 128 and / or the second (right) speaker 130, and if the sensor data indicates that the direction of the swipe gesture is in an upward direction (e.g., the positive Y direction in FIG. 1) or a rightward direction (e.g., the positive X direction in FIG. 1), the processor may increase the volume of the audio content or sound being output by the first (left) speaker 128 and the second (right) speaker 130. A swipe gesture in the opposite direction (e.g., a downward or leftward swipe gesture) may decrease the volume. Other examples include touching both speakers 128 and 130 substantially simultaneously to mute or unmute their audio content, sound, or volume. These are merely examples, and any suitable algorithm may be used to adjust the characteristics of the audio content or sound being output by speakers 128, 130 in block 604.As indicated by the return arrow from block 604 to block 602, process 600 may be repeated when additional sensor data is received indicating various types of finger contact with the speaker. For example, a user may adjust the volume up or down, mute or unmute the audio, as needed during gameplay of a video game.

[0052] 7 shows an example process 700 for adjusting a volume of audio content being output from a speaker based at least in part on sensor data. In some cases, process 700 may be performed by controller 100 and / or a remote device communicatively coupled to controller 100.

[0053] At 702, data may be received from a sensor associated with a speaker located within a particular half (e.g., left half 132 or right half 134) of the front face 104 of the controller body 102 of the controller 100. For example, sensor data may be received at block 702 from a sensor associated with the first (left) speaker 128 or from a sensor associated with the second (right) speaker 130 depicted in FIG.

[0054] At 704, a determination may be made based at least in part on the sensor data received at block 702 whether a finger is in contact with the associated speaker. As indicated by block 706, this determination may be made by detecting a change in an electrical parameter that the sensor is configured to sense. For example, the sensor may be an inductive sensor configured to detect a change in inductance based on a finger moving in proximity to the speaker coil 202 of the speaker, as described herein. As another example, the sensor may be a capacitive sensor configured to detect a change in capacitance based on a finger moving in proximity to the speaker coil 202 of the speaker. As yet another example, the sensor may be an impedance sensor configured to detect a change in impedance between a pair of leads 402 of the speaker. If a finger contact is not detected at block 704, process 700 may follow a "no" route from block 704 to block 702, where additional sensor data may be received and the determination at block 704 may be repeated. If a finger contact is detected at block 704 , process 700 may follow a “Yes” route from block 704 to block 708 .

[0055] At 708, a determination may be made whether to increase or decrease the volume of audio content or sounds being output by the speaker of the controller 100 based at least in part on the sensor data received at block 702. As indicated by block 710, this determination may be made by determining that a particular gesture has been made by a finger contacting the speaker, such as a swipe gesture and / or the direction of the gesture. For example, if the direction of the swipe gesture (e.g., as detected by the touch sensor 302 associated with the speaker) is in an upward or rightward direction in the XY plane shown in FIG. 1, the processor of the controller system may determine to increase the volume, and if the direction of the swipe gesture is in the opposite direction (e.g., downward or leftward), the processor may determine to decrease the volume. As another example, at block 712, the processor may determine that the received sensor data is associated with a particular speaker or a particular half of the front surface 104 of the controller body 102. For example, if the sensor data indicates that a finger is touching the second (right) speaker 130, the processor may decide to increase the volume, while if the sensor data indicates that a finger is touching the first (left) speaker 128, the processor may decide to decrease the volume.

[0056] If it is determined at block 708 to increase the volume, process 700 may follow an "up" route from block 708 to block 714, where the volume of the audio content or sound is increased. In some embodiments, this may involve increasing the volume setting to the next highest increment. The user may, in some embodiments, touch the speaker and maintain contact to continue to increase the volume at block 714. If it is determined at block 708 to decrease the volume, process 700 may follow a "down" route from block 708 to block 716, where the volume of the audio content or sound is decreased. Again, the user may, in some embodiments, touch the speaker and maintain contact to continue to decrease the volume at block 716.

[0057] 8 shows an example process 800 for adjusting audio characteristics of audio content being output from a speaker using high frequency audio (HFA) tones. In some cases, process 800 may be performed by controller 100 and / or a remote device communicatively coupled to controller 100.

[0058] At 802, the speakers of the controller 100 can output one or more tones (e.g., HFA tones) at frequencies inaudible to the human ear, as described herein. The tones can be output from one speaker or multiple speakers. When the tones are output from multiple speakers, each speaker can be configured to output a tone at a different frequency. For example, the first (left) speaker 128 can be configured to output a first tone at a first frequency above about 20 kHz, and the second (right) speaker 130 can be configured to output a second tone at a second frequency above about 20 kHz.

[0059] At 804, a processor of a controller system disclosed herein may receive audio generated by a microphone 504 of the controller 100. For example, the microphone 504 may capture sounds in the vicinity of the controller 100 and generate audio data, and if HFA tones are being emitted by a speaker of the controller 100, the audio data may indicate these high frequencies. In some embodiments, the microphone 504 is associated with a particular speaker (e.g., a first microphone is associated with the first speaker 128, a second microphone is associated with the second speaker 130, etc.) and configured to detect tones of a particular frequency being emitted by the associated speaker. In other embodiments, a single microphone or a microphone array may be configured to capture any sound in the environment of the controller 100, including ambient noise, audio content emitted by the speaker of the controller 100, and HFA tones emitted by one or more of the speakers of the controller 100. In some embodiments, the filter may remove background / ambient noise and / or audio content associated with video games from the audio data to isolate the HFA tones.

[0060] At 806, a determination may be made of whether a finger is in contact with the speaker based at least in part on the audio data generated by the microphone 504. For example, if a finger is muffling the HFA tone 502 being output by the first (left) speaker 128, audio content in that high frequency range may not be present in the audio data generated by the microphone 504 or may be at least below a threshold amplitude in the audio data, which may indicate a finger is in contact with the first (left) speaker 128. Similar techniques may be used to detect finger contact with the second (right) speaker 130, or any other speaker of the controller 100. If a finger contact is not detected at block 806, the process 800 may follow the "no" route from block 806 to block 802 and continue to output the HFA tone and utilize the tone to determine finger contact.

[0061] If finger contact is detected at block 806, process 800 may follow the "Yes" route from block 806 to block 808, where the processor may adjust the characteristics of the audio content or sounds being output by the speakers based at least in part on the audio data generated by the microphone 504. For example, if the audio data generated by the microphone indicates that a finger is contacting the second (right) speaker 130 (and thus muffling the sounds being output), the processor may increase the volume of the audio content or sounds being output by the first (left) speaker 128 and the second (right) speaker 130. As another example, if the audio data generated by the microphone indicates that a finger is contacting the first (left) speaker 128 (and thus muffling the sounds being output), the processor may decrease the volume of the audio content or sounds being output by the first (left) speaker 128 and the second (right) speaker 130. Other examples include touching both speakers 128 and 130 substantially simultaneously (thus muffling the sound being output) to mute or unmute their audio content, sounds, or volumes. These are merely examples, and any suitable algorithm may be used to adjust the characteristics of the audio content or sounds being output by speakers 128, 130 in block 808.

[0062] FIG. 9 illustrates an exemplary controller 900 having a controller body 902 including a front surface 904. As shown, the front surface 904 of the controller body 902 may include multiple controls, including a front control configured to receive input via a user's thumb. For example, the controller 900 may include a left joystick 906, a left trackpad 908, a left D-pad 910 in the form of four separate buttons, a right joystick 912, a right trackpad 914, and right buttons 916 (e.g., X, Y, A, B). The controller 100 may also include additional controls or features similar to the controller 100. Additionally, the controller 900 may include a left handle 918 and a right handle 920 configured to be gripped by a user's hands.

[0063] In some examples, depending on the game or application, the user may desire different sensations to increase the user's comfort and / or may desire a particular gameplay experience. Additionally, the user may desire particular features or functions of the handheld controller. For example, a first game application may be best played using a first control, while a second game application may be best played using a second control. Here, the user may select which controls are available depending on the currently running game application. In this sense, the controls or particular features of the handheld controller may be interchangeable based on the user's preferences and / or application. In some cases, the handheld controller may be dynamically configured depending on which user is currently operating the handheld controller. Additionally, in each of these cases, the handheld controller or the remote system may determine the configuration of the handheld controller and which controls are currently being operated. This information may be provided to the system running the current application, which may then make changes based on the configuration of the handheld controller.

[0064] In some cases, one or more of the front controls may be depressible. For example, the trackpads (e.g., left trackpad 908 and / or right trackpad 914) may be depressible to allow detection of a pressing force and / or to activate a button-like actuation of the trackpad. However, in some cases, a user may prefer to adjust the sensitivity associated with a trackpad press or to adjust the amount of force required to press the trackpad to activate a button-like action. In some cases, the controller 900 may include a protrusion, lever, or knob 922 for adjusting the sensitivity of one or more of the front controls, such as the right trackpad 914. As shown in FIG. 9, the knob 922 may protrude through a front cover of the controller 900 or may protrude on the front portion 904. The knob 922 may be manipulated or otherwise actuated by the user to adjust the sensitivity of the right trackpad 914. For example, the knob 922 may be slid or repositioned within a slot or channel 924 on the front portion 904. Knob 922 can be slid within or between the ends of channel 924 to adjust the sensitivity of the right track pad 914 .

[0065] As discussed herein and shown in later figures, the knob 922 may be operably coupled to a rotary dial mechanism disposed with the controller body 902. This rotary dial mechanism allows the amount of force required to depress the right track pad 914 and engage one or more switches disposed below the right track pad 914 to be adjusted. The knob 922 may also be disposed adjacent to the right track pad 914. However, the knob 922 may be located at other locations on the controller 900 or may protrude through other surfaces of the controller 900 for the user to navigate. Additionally or alternatively, instead of sliding the knob 922 back and forth to change the sensitivity, the user may press a button that activates a motor and changes the sensitivity of the track pad. Additionally, while FIG. 9 illustrates certain front controls that include a knob 922 or that the knob 922 is operable to change the sensitivity of certain front controls, other front controls may include a corresponding knob (or other feature) for adjusting the associated sensitivity.

[0066] 10 shows a rear 1000 of a controller body 1002 of a controller 1004, which may represent the rear of the controller 100 or the controller 900. FIG. 10 also shows a top 1006 of the controller 1004, which may represent the controller 100 or 900, or the top of the controller 100 or 900.

[0067] The upper portion 1006 may include one or more left triggers and / or one or more right triggers. In some cases, the one or more left triggers and / or one or more right triggers may each be located along an upper edge of the controller body 1002. The one or more left triggers and / or one or more right triggers may be controlled by a user's index finger during normal operation while the controller 1004 is held by the user. The upper portion 1006 may additionally or alternatively include a depressible button (or other additional input control) that may be controllable by the user's finger. In some cases, the upper portion 1006 may include a touch sensor for detecting the presence, position, and / or gesture of a finger on the control. Additionally, the upper portion 1006 may include a receiver, such as a wired communication interface (e.g., a port, plug, jack, etc.), for communicatively coupling the controller 1004 to an external device (e.g., a charger, a game console, a display, a computing device, etc.).

[0068] The rear portion 1000 of the controller body 1002 may also include one or more left controls 1008 and / or one or more right controls 1010 that may be conveniently manipulated by a user's index or middle fingers during normal operation while the controller 1004 is held in a user's hand. The one or more left controls 1008 and / or one or more right controls 1010 may be touch-sensitive to identify the presence, position, and / or gesture of one or more fingers on the controls.

[0069] In addition to providing different controls, the handheld controller can support different interchangeable accessories. For example, the portions of the handheld controller that are gripped or held in the user's hand can be replaced or interchanged to provide different sensations and / or comfort levels. These grips may be of various sizes, shapes, and / or contours to fit in the hand and be gripped by the user. For example, a small grip may be used by a user with a small hand size, while a large grip may be used by a user with a large hand size. In some cases, the grips (or handles) may be coupled in or to a receiver located at the rear and / or side of the handheld controller. Different grips may be removably coupled to or within the receiver. Grips may also provide the user with additional surfaces to hold or hold while manipulating the handheld controller. For example, the grips may include different degrees of contours and protrusions, and depending on the application or user preference, the user can select a corresponding grip.

[0070] In some cases, the handheld controller may include a cavity or compartment located on the rear of the handheld controller. The compartment may include controls (e.g., buttons) that are operable via a cover disposed over the compartment. When attached, the cover may hide the compartment. Buttons may be disposed within the compartment, and the buttons (or other sensors / switches) may be operable by pressing a portion of the cover. For example, applying pressure to the cover may engage one or more buttons.

[0071] FIG. 11 shows a rear 1100 of a controller body 1102 of a controller 1104, which may represent the rear of the controller 100 or the rear of the controller 900. The rear 1100 of the controller body 1102 may include a receptacle 1106 for receiving one or more accessories, which couples the accessory to the rear of the controller body 1102. As shown, the receptacle 1106 may include a recess, pocket, or compartment disposed on, in, and / or within the controller body 1102. In some cases, the receptacle 1106 may include a sidewall disposed below a surface of the rear 1100 for fastening or coupling the accessory to the controller body 1102. Stated another way, the receptacle 1106 may include a sidewall that is recessed below a surface of the rear 1100 of the controller body 1102. By recessing the receptacle 1106 in this manner, the accessory can be secured to or within the controller body 1102, preventing the accessory from translating or otherwise shifting during use.

[0072] In some cases, the receptacles 1106 may be located on the left and right handle portions of the controller body 1102, which are configured to be grasped or held in the hands of a user, respectively. Here, for example, the receptacles 1106 may receive accessories that are grasped or held by a user. In other cases, the receptacles 1106 may receive accessories that are controlled by the fingers of the user's left and right hands. For example, FIG. 11 shows that the receptacles 1106 may be located on the left handle portion of the controller 1104. As discussed herein, the accessories may be coupled to the controller body 1102, and the user's left hand may hold or otherwise utilize the accessories. However, in some cases, the controller 1104 may be operable without accessories attached to the controller body 1102. In this sense, the accessories may increase functionality and provide certain features to the controller 1104.

[0073] One or more accessories may, in some cases, be removably coupled to the rear 1100 of the controller body 1102 in the receptacle 1106 and may be interchangeable with one another. For example, different accessories may couple to the controller body 1102 depending on the user, the user's preferences, and / or the application. In some cases, the accessories may provide various grips or provide surfaces and / or areas of the controller 1104 that the user grasps or holds while manipulating the controller 1104. In some cases, the user may swap out accessories based on the current application (e.g., game title) the user is playing, based on the user's comfort, and / or for any other reason.

[0074] FIG. 11 illustrates a number of accessories 1108 that may be coupled to the controller body 1102. In some cases, a user of the controller 1104 may interchange any of the accessories 1108 that couple to the controller body 1102 to change the functionality, appearance, or feel of the controller 1104. For example, the different accessories may include different sizes, textures, shapes, heights, and the like. In one embodiment, the different accessories have different heights, shapes (e.g., convex, concave, flat, and the like). For example, the first accessory 1108(1) may represent a first grip configured to couple to the controller body 1102. The second accessory 1108(2) may represent a second grip configured to couple to the controller body 1102. Comparatively, the first accessory 1108(1) and the second accessory 1108(2) may represent grips of different sizes or shapes having different contours and shapes. For example, the first accessory 1108(1) may be used by a user with larger hands, while the second accessory 1108(2) may be used by a user with smaller hands. In either case, both the first accessory 1108(1) and the second accessory 1108(2) may provide a portion of the controller 1104 that is grasped by the user (e.g., a left grip held by the user) or may function as a portion of the controller 1104.

[0075] The accessory 1108 may also include a third accessory 1108(3) and / or a fourth accessory 1108(4). The third accessory 1108(3) represents a grip (or handle) having a button 1110 operable by a user. A user may actuate the button 1110 to cause a corresponding action to be performed within a game and / or application. The fourth accessory 1108(4) may represent an extended battery pack for providing extended battery life to the controller 1104. Additionally, the accessory 1108 may include touch-sensitive controls for identifying the presence, position, and / or gesture of one or more fingers on the controls.

[0076] In some cases, the grip or other accessory may magnetically couple to the rear and / or sides of the handheld controller. In this manner, the grips may be easily interchangeable with one another. However, other attachment mechanisms (e.g., snap-fit, slots, hooks, etc.) can be used. Additionally, the grip may also include one or more controls (e.g., buttons). In such cases, the receiver and grip may include corresponding connectors for transferring touch data, input data, and / or selection data to the handheld controller. For example, the grip may include buttons for controlling aspects of a game or application. In addition to coupling the grip to the handheld controller via an attachment mechanism, for example, a connector on the grip may communicatively couple to a connector of the handheld controller to provide data (e.g., indicative of button presses) to the handheld controller.

[0077] Regardless of the type of accessory or associated features of the accessory 1108, the accessory 1108 may be removably coupled to the controller body 1102 to add grip, functionality, and / or features to the controller 1104. In some cases, the accessory 1108 may couple to the controller body 1102 through engagement between an attachment feature on the controller body 1102 and an attachment feature on the accessory 1108. For example, the bottom or other surface of the receptacle 1106 may include a first magnetic element (e.g., a first magnet) that is complementary to engage with a second magnetic element (e.g., a second magnet) on the accessory 1108. For example, the bottom of the receptacle 1106 may include a magnetic element that engages with a magnetic element located on the bottom surface of the accessory 1108. The engagement or attraction between the first magnetic element and the second magnetic element may ensure retention of the accessory 1108 within the receptacle 1106 and / or the controller body 1102. However, the force of engagement between the first magnetic element and the second magnetic element can be overcome via the user applying a greater amount of force. In this manner, the user can interchange or replace accessories 1108 attached to the controller body 1102.

[0078] However, the accessory 1108 and the controller body 1102 may couple to one another using mechanisms other than magnetic elements. For example, the accessory 1108 may include tabs that engage with hooks on the controller body 1102. Additional attachment mechanisms may include snap fits, hook and loop, pressure fits, and / or mechanical fasteners. Additionally, in some cases, the accessory 1108 may include a flange or lip that engages or abuts a sidewall of the receptacle 1106 to further couple or secure the accessory 1108 within the receptacle 1106 or to the controller body 1102.

[0079] Additionally, the controller body 1102 may include connectors for communicatively coupling the functionality of the accessory 1108 to the controller 1104 (or vice versa). In some cases, the connectors may be located within the receptacle 1106 and may receive or couple to a corresponding connector of the accessory 1108. For example, if the controller 1104 includes a third accessory 1108(3) or a fourth accessory 1108(4), power from a battery may be communicated to the controller via the connectors and data indicative of button presses may be communicated to the controller 1104 via the connectors. In some cases, the connectors may represent prong connectors that are complementary to engage with each other and couple the functionality of the sensor, button, and / or accessory to the controller 1104. In some embodiments, the accessory 1108 may wirelessly transmit and receive data to and from a corresponding transceiver of the controller 1104.

[0080] 11 shows a particular location, size, or configuration of the receptacle 1106, the receptacle 1106 may be located elsewhere on the controller body 1102. In some cases, more than two receptacles 1106 and more than two accessories 1108 may be coupled to the controller body 1102. Additionally, while the above discussion shows a single accessory being received at the receptacle 1106, the receptacle 1106 may be configured to receive multiple accessories. For example, a first accessory may couple within the receptacle 1106 and engage a first magnetic element of the magnetic elements, while a second accessory may couple within the receptacle 1106 and engage a second magnetic element of the magnetic elements. The interchangeability of the accessories 1108 allows a user to customize the controller 1104 to the user's preferences depending on the user's desired functionality (or feel). In some cases, the controller 1104 and / or a communicatively coupled system may determine which accessories 1108 are coupled to the controller body 1102 for use in determining the capabilities of the controller 1104 and / or characteristics of the controller 1104 (e.g., tags, RFID, magnets, etc.). For example, after identifying the accessories currently coupled to the controller 1104, the controller 1104 and / or a system communicatively coupled to the controller 1104 may relay the identity of the controls of an application being executed by the system. The system may then take this information into account to determine one or more parameters of the application (e.g., calibration and conversion factors associated with control movements). In another example, an application (e.g., a game) may enable different movement / control selections based on which controls are currently coupled to the receiver.

[0081] 12 illustrates a rear view of the controller 1104 showing a first accessory 1108(1) coupled to the controller body 1102 and within the receptacle 1106. When coupled, the accessory 1108(1) can be secured to the controller 1104 and operable by a user. Additionally, when coupled, the rear 1100 of the controller 1104 can have a smooth, continuous surface for the user. As shown, the user can grasp the accessory 1108(1) to hold or otherwise grasp the controller 1104 in the user's hand.

[0082] In some cases, the cover may be interchangeable with other covers depending on the game, application, and / or user preferences. Different covers may provide additional features to the handheld controller and / or simplify certain features of the handheld controller. For example, a user may couple a cover that simplifies the controls in the compartment. In some cases, the cover may include portions that cannot be pressed and do not activate or engage buttons located in the cover. Additionally, interchangeable covers may include electronics such as batteries and haptic feedback mechanisms. Here, for example, if a user desires increased battery life, the user may couple a cover that houses a battery for the handheld controller. For example, if a user desires to receive haptic feedback during a racing game, the user may couple a cover that houses a haptic actuator. In such a case, the cover may include electronics and a connector for coupling the electronics of the cover to the handheld controller. For example, the connector of the cover may mate with the connector of the compartment.

[0083] 13-15 show a rear portion 1300 of a controller body 1302 of a controller 1304 including various rear covers attached to the controller body 1302. In some cases, the rear portion 1300 may represent the rear portion of the controller 100 or the rear portion of the controller 900. The rear portion 1300 of the controller body 1302 includes a receiver for receiving different types of rear covers. Thus, different covers may be configured to mount, couple, or attach to the rear portion 1300. In some cases, the rear covers may be coupled to the rear portion 1300 via latching mechanisms, magnets, fasteners, and / or any combination thereof. Additionally, the controller 1304 may be configured to obtain data indicating which rear cover is currently coupled to the controller 1304. The controller 1304 or another system may then use this data to make this determination, which may then be used by an application being operated via the controller 1304.

[0084] Beginning with FIG. 13, a first cover 1306 is shown attached to a controller body 1302. The first cover 1306 may include four buttons, two buttons on the left hand side, such as a first control 1308 and a second control 1310, and two buttons on the right hand side, such as a first control 1312 and a second control 1314. In some cases, when the controller 1304 is held by a user, the buttons located on the left hand side may be operated or controlled by the user's left fingers (e.g., ring finger, middle finger, index finger), while the buttons located on the right hand side may be operated or controlled by the user's right fingers (e.g., ring finger, middle finger, index finger). A dividing line on the first cover 1306 may separate the controls such that the controls are separately addressable. For example, a user may hold the controller 1304 via a left handle 1316 and a right handle 1318. In this position, the user can press the button.

[0085] The left and right buttons of the controller body 1302 may be individually depressible to engage or activate switches disposed within compartments of the controller 1304. The individual buttons, or respective portions of the first cover 1306, may engage respective switches 1320 within the compartments. For example, the switches 1320 shown in dashed lines may be disposed within compartments that are beneath the first cover 1306 when the first cover 1306 is attached to the controller body 1302. In some cases, the switches 1320 may include tactile or mechanical switches configured to sense or detect a press and / or may include force sensing resistors (FSRs) having a transducer with an electrical resistance that changes based on the applied force it experiences.

[0086] Removing the first cover 1306 may allow access to a compartment that may, in some cases, include a battery and a switch 1320. Thus, by pressing the control, the control itself, or a portion of the control, such as a protrusion, may engage a switch to cause a particular action to be performed. Additionally, although FIG. 13 shows the first cover 1306 to include four buttons, i.e., two buttons located on each side, the first cover may include any number of buttons and / or the buttons may be located elsewhere. In such a case, the controller 1304 may include a corresponding number of switches installed and located below the buttons.

[0087] FIG. 14 illustrates a second cover 1400 attached to the controller body 1302. In comparison to the first cover 1306, the second cover 1400 may not include any button that can or is configured to depress the switch 1320. For example, the switch 1320 is still shown in FIG. 14 and within the controller body 1302 to indicate its presence under the second cover 1400. However, the second cover 1400 may not include a button or a portion of the second cover 1400 may not be depressable to engage the switch 1320. In some cases, a user may replace the first cover 1306 with the second cover 1400 based on the current application (e.g., game title) the user is playing, based on the user's comfort, and / or for any other reason.

[0088] Given that the second cover 1400 does not include features that engage with the switch 1320, the second cover 1400 can be said to disable, simplify, or disable the switch 1320 in the compartment. That is, the controller 1304 may still include the switch 1320 in the compartment, but coupling the second cover 1400 to the controller body 1302 can prevent the switch 1320 from being activated. In some cases, a user can replace the second cover 1400 with the first cover 1306 if a game or application does not require input from the buttons on the back cover and / or if the user does not wish to utilize the buttons on the back cover.

[0089] Further, in some cases, when the second cover 1400 is coupled to the controller, the switch 1320 is not operable and therefore the switch 1320 may be deactivated (e.g., refrain from providing power to electronics associated with the switch 1320) to conserve or reduce power. In other words, based on the rear cover being coupled to the controller body 1302, the controller may be configured to sense certain inputs and / or simplify certain functions accordingly.

[0090] FIG. 15 shows a third cover 1500 attached to the controller body 1302. In some cases, the third cover 1500 may include buttons operable by the left and right hands of the user. In some cases, the user may replace the third cover 1500 with the first cover 1306 or the second cover 1400 based on the current application (e.g., game title) the user is playing, based on the user's comfort, and / or for any other reason. Additionally, the third cover 1500 may include additional electronics to provide additional features and / or functionality to the controller. For example, the third cover 1500 may include a haptic actuator to provide vibration feedback to the user. Additionally or alternatively, the third cover 1500 may include a battery to charge the controller 1304 or extend battery life. However, the third cover 1500 may include additional electronic components operable by the user and / or that increase the functionality of the controller 1304.

[0091] In such a case, the third cover 1500 may include a connector for communicatively coupling with the controller 1304. For example, the connector of the third cover 1500 may connect with a connector disposed within a compartment of the controller 1304 to provide data, transmit power, and enable functionality of the third cover 1500 (or vice versa).

[0092] In some cases, the controls of the handheld controller can be adjusted to increase and / or decrease the sensitivity of the controls. In some cases, the controls can be completely disabled such that the sensitivity of the controls is zero (or substantially zero). For example, the handheld controller can include a front control such as a trackpad. The trackpad can include a touch sensor for detecting or determining a presence, location, and / or gesture provided by a user. The trackpad may also be pressable (e.g., clickable). In some cases, a user can adjust the sensitivity of the trackpad to detect a press. Stated differently, a user can adjust the amount of force a user needs to press a control to press the trackpad. In this way, the sensitivity required to press the trackpad or to press a switch under the trackpad can be adjusted according to the game, application, and / or user preferences.

[0093] In some cases, mechanical features may control or be used to control the sensitivity of the trackpad to detect presses. For example, a knob on a handheld controller may be slidable, twistable, rotatable, or otherwise actuable to adjust the sensitivity. In some cases, the knob may be coupled to a rotary dial mechanism that couples to a rotary dial mechanism located under the trackpad (or within the housing of the controller). The rotary dial mechanism may change the amount of force required by the user to press the trackpad. For example, by rotating the dial, the placement of the support arm on the circular frame may be altered, which in turn adjusts the ease or difficulty of pressing the trackpad. For example, in a first position, the knob may allow the trackpad to be easily pressed with little force. In a second position, the knob may disable or effectively disable the depressable nature of the trackpad. In the second position, or when the trackpad is harder to press, the user may be required to apply a greater amount of force to press the trackpad compared to when the trackpad is easily depressable (e.g., in the first position). In some cases, the first and second positions may be considered extremes or limits of a range of sensitivity, however, the knob may be adjusted to one or more intermediate positions between the first and second positions to modify the sensitivity required to press the trackpad.

[0094] Although conventional handheld controllers include selectable controls, combining controls having switches with touch sensing capabilities (and their associated sensitivity) to identify control selections can increase the amount and richness of gestures that can be interpreted on the handheld controller. Furthermore, these gestures can enhance the operation of a game or other application being controlled by the handheld controller. Adjusting the sensitivity of the controls and substituting certain controls for one another can further increase the richness.

[0095] 16A and 16B show the knob 922 of the controller 900 in different positions to adjust the sensitivity of a control, such as the right track pad 914. As introduced and discussed above with respect to FIG. 9, the knob 922 may slide within a channel 924 to adjust or change the sensitivity of the right track pad 914. For example, the right track pad 914 may be depressible, and by moving the knob 922 within the channel 924, the amount of force required to depress the right track pad 914 and engage one or more switches can be adjusted. As discussed in detail herein, the knob 922 may interact with one or more features, such as a radial dial mechanism located under the right track pad 914 to adjust the sensitivity.

[0096] In FIG. 16A , the knob 922 is disposed at a first location 1600 in the channel 924. The first location 1600 may correspond to a first sensitivity (e.g., how hard the user needs to press) at which the right track pad 914 can be pressed. For example, the first location 1600 is shown to be at a left-most location in the channel 924 (i.e., the knob 922 cannot move any further to the left). In some cases, the first location 1600 may represent a first extreme of sensitivity. For example, when the knob 922 is at the first location 1600, the sensitivity may be at a maximum sensitivity and the right track pad 914 can be easily pressed with a small amount of force. Thus, the right track pad 914 may be sensitive to being pressed by the user.

[0097] In FIG. 16B, the knob 922 is disposed in a second location 1602 in the channel 924. The second location 1602 may correspond to a second sensitivity at which the right track pad 914 can be pressed. For example, the second location 1602 is shown to be at a right-most location in the channel 924 (i.e., the knob cannot move any further to the right). In some cases, the second location 1602 may represent a second extreme of sensitivity. For example, when the knob 922 is in the second location 1602, the sensitivity may be at a minimum sensitivity and the right track pad 914 may need to be pressed with a larger amount of force. In such a case, the user may need to apply a larger amount of force to the right track pad 914 to press the right track pad 914 than when the knob 922 is in the first location 1600. The right-most position may also represent a scenario in which the right trackpad 914 cannot be pressed down, thus simplifying or disabling the pressable nature of the right trackpad 914. Regardless of the sensitivity or position of the knob 922, the right trackpad 914 may still be able to detect touch input. In some cases, the sensitivity with which the right trackpad 914 is pressable may not affect the sensitivity of the right trackpad 914 to detect touch input.

[0098] In some cases, the front portion 904 of the controller 900 may include a visual indicator that indicates the sensitivity of the right track pad 914. For example, a visual indicator such as a less sign ("-") may be located adjacent to a left-hand side of the channel 924 and a visual indicator such as a plus sign ("+") may be located adjacent to a sign on the right-hand side of the channel 924. Such an indicator may indicate to a user how to decrease or increase the sensitivity of the right track pad 914.

[0099] 16A and 16B show adjusting the sensitivity of the right track pad 914, other controls of the controller 900 (or controller 100) can be adjusted in a similar manner. For example, the sensitivity of the left track pad 908 being pressed can be adjusted. Additionally, instead of the controller 900 including a knob 922 for adjusting sensitivity, other mechanisms such as buttons, screws, pins, motors, or levers can be used to adjust the sensitivity of the controls. Additionally, instead of the knob 922 sliding within a channel 924 to adjust sensitivity, the knob 922 can be located elsewhere on the controller body 902 and / or embodied within a different slider, channel, track for adjusting sensitivity.

[0100] The knob 922 may also be adjustable anywhere along the channel 924 to configure the right track pad 914 to a particular sensitivity. That is, although Figures 16A and 16B show the knob 922 located at the outer extremes of the channel 924, the knob 922 may be located at any intermediate position within the channel 924, and the right track pad 914 may have a sensitivity corresponding to the intermediate position. Thus, the sensitivity of the right track pad 914 (or other control) may be adjusted in increments.

[0101] 17A and 17B show perspective views of a rotary dial mechanism 1700. The rotary dial mechanism 1700 may be operably coupled to a knob 922 to adjust the sensitivity of a control, such as the right track pad 914. As shown, the rotary dial mechanism 1700 may include a frame 1702 having a top surface 1704, a dial 1706, and a channel 1708 within which an arm 1710 of the dial 1706 is configured for steering. The top surface 1704 may be coupled to the bottom of the right track pad 914 or to the bottom of a touch sensor of the right track pad 914. Thus, the top surface 1704 may be disposed vertically below the right track pad 914. In some cases, the right track pad 914 and / or the rotary dial mechanism 1700 may be integrated or combined as a single component within the controller or controller body. Combining controls having switches with touch-sensing capabilities to identify control selections can increase the amount and richness of gestures that can be interpreted on a handheld controller, which in turn can enhance the operation of a game or other application being controlled by the controller.

[0102] As discussed above with respect to FIGS. 16A and 16B, the dial 1706 operably couples to the knob 922. For example, an end of the knob 922 disposed within the controller body 902 can be attached or attached to the dial 1706, such as an arm 1710 of the dial 1706. The dial 1706 can be configured to rotate and steer the knob 922, as discussed above with respect to FIGS. 16A and 16B, causing the dial 1706 to rotate within the rotary dial mechanism 1700. For example, the dial 1706 can rotate about a central axis or hub. As the dial 1706 rotates, the arms 1710 can each move within the channel 1708. For example, the rotary dial 1706 can include three arms 1710, each disposed within a respective channel 1708.

[0103] Each of the arms 1710 may have a limited range of motion vertically within the channel 1708. For example, at both ends of the channel 1708, the arms 1710 may be prevented from rotating or moving further via side or end walls. However, as the arms 1710 slide or rotate in a first direction within the channel 1708, the distance between the arms 1710 and the top and bottom surfaces of the channel 1708 may become less (e.g., the channel 1708 may shrink or contract). The arms 1710 may then contact and be constrained between the top and bottom surfaces of the channel 924. Constraining the arms 1710 within the channel 1708 may reduce the amount that the right track pad 914 is configured to be depressible, which in turn may reduce the sensitivity of the right track pad. In such a case, it may be more difficult to make the right track pad 914 depressible to engage one or more switches. A spring or other biasing member may provide the mechanical action for the depressible nature of the right track pad 914 .

[0104] Conversely, by moving the arm in a second, opposite direction, it is released from the top and bottom surfaces of the channel 1708 and the right track pad 914 can be easily depressed. That is, because the arm 1710 of the dial 1706 may no longer be constrained between the top and bottom surfaces of the channel 1708, the arm 1710 may be depressed vertically, which in turn may depress the right track pad 914. However, the arm 1710 may be positioned elsewhere in the channel to modify or incrementally adjust the sensitivity with which the right track pad 914 can be depressed.

[0105] Collectively, each of the arms 1710 may be positioned within a respective channel 1708 to engage a respective top and bottom surface of the channel 1708. In this manner, the amount of force required to depress the right track pad may be uniform across the surface of the right track pad 914 or at various locations on the top of the right track pad 914. Additionally, while FIGS. 17A and 17B show the dial 1706 having three arms, the dial 1706 may include less than three or more than three arms 1710 for engaging the respective channels. Additionally, one or more functional structures within the controller may be able to provide tactile or mechanical motion to the right track pad 914 or rotary dial mechanism 1700 to enable the right track pad 914 to be depressed.

[0106] FIG. 18 illustrates exemplary computing components of a controller 1800, such as the controller 100 or 900. As shown, the handheld controller 1800 includes one or more input / output (I / O) devices 1802, such as the controls described above (e.g., joystick, trackpad, trigger, etc.), and potentially any other type of input or output device. For example, the I / O device 1802 may include one or more microphones for receiving audio input, such as user voice input. In some implementations, one or more cameras or other types of sensors (e.g., inertial measurement units (IMUs)) may function as input devices for receiving gestural input, such as movements of the controller 1800. In some embodiments, additional input devices may be provided in the form of a keyboard, keypad, mouse, touch screen, joystick, control buttons, etc. The input devices may further include control mechanisms, such as basic volume control buttons for increasing / decreasing the volume, as well as power and reset buttons.

[0107] Output devices, on the other hand, may include displays, light emitting elements (e.g., LEDs), vibrators that create tactile sensations, speakers (e.g., headphones), etc. There may also be simple light emitting elements (e.g., LEDs) to indicate a state, such as when the power is on. Although several examples are provided, the handheld controller may additionally or alternatively include any other type of output device.

[0108] In some cases, output by one or more output devices may be based on input received by one or more of the input devices. For example, a control may select to output a haptic response by a vibrator located adjacent (e.g., directly below) the control or at any other location. In some cases, the output may vary based at least in part on characteristics of a touch input on a touch sensor, such as a touch sensor associated with the control. For example, a touch input at a first location on the touch sensor may result in a first haptic output, while a touch input at a second location on the touch sensor may result in a second haptic output. Additionally, a particular gesture on the touch sensor may result in a particular haptic output (or other type of output). For example, a swipe gesture on the control may result in a first type of haptic output, while a tap on the control (detected by the touch sensor) may result in a second type of haptic output, while pressing down on the control may result in a third type of haptic output.

[0109] Additionally, controller 1800 may include one or more communications interfaces 1804 to facilitate wireless connection to a network and / or one or more remote systems and / or devices 1805 (e.g., host computing devices running applications, game consoles, etc.). Communications interface 1804 may implement one or more of a variety of wireless technologies, such as Wi-Fi, Bluetooth, radio frequency (RF), etc. It should be appreciated that controller 1800 may further include physical ports to facilitate wired connections to plug-in network devices that communicate with the network, connected peripheral devices, or other wireless networks.

[0110] In the illustrated implementation, the handheld controller 1800 further includes one or more processors 1806 and computer-readable media 1808. In some implementations, the processor 1806 may include a central processing unit (CPU), a graphics processing unit (GPU), both a CPU and a GPU, a microprocessor, a digital signal processor, or other processing units or components known in the art. Alternatively or additionally, what is functionally described herein may be implemented, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like. In addition, each of the processors 1806 may have its own local memory that may also store program modules, program data, and / or one or more operating systems.

[0111] The computer readable medium 1808 may include removable and non-removable media implemented in any method or technology for storing information, such as volatile and non-volatile memory, computer readable instructions, data structures, program modules, or other data. Such memory may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other medium that may be used to store the desired information and that may be accessed by a computing device. The computer readable medium 1808 may be implemented as a computer readable storage medium ("CRSM"), which may be any available physical medium accessible by the processor 1806 to execute instructions stored on the computer readable medium 1808. In one basic implementation, the CRSM may include random access memory ("RAM") and flash memory. In other implementations, the CRSM may include, but is not limited to, read-only memory ("ROM"), electrically erasable programmable read-only memory ("EEPROM"), or any other tangible medium that can be used to store the desired information and that can be accessed by the processor 1806.

[0112] Some modules, such as instruction and data storage, may be stored in the computer readable medium 1808 and configured to execute on the processor 1806. Some exemplary functional modules are illustrated as being stored in the computer readable medium 1808 and executed on the processor 1806, although the same functions may alternatively be implemented in hardware, firmware, or as a system on a chip (SOC).

[0113] The operating system module 1810 may be configured to manage hardware within the controller 1800 for the benefit of the other modules and to be coupled to the controller 1800. Additionally, the computer-readable medium 1808 may store a network communication module 1812 that enables the controller 1800 to communicate with one or more other devices 1805, such as a personal computing device, game console, or remote server, that runs an application (e.g., a game application) via the communication interface 1804. The computer-readable medium 1808 may further include a game session database 1814 for storing data associated with a game (or other application) executing on the handheld controller or on a computing device to which the handheld controller 1800 couples. The computer-readable medium 1808 may also include a device record database 1816 that stores data associated with a device to which the controller 1800 couples, such as a personal computing device, game console, or remote server. The computer-readable medium 1808 may further store game control instructions 1818 for configuring the controller 1800 to function as a game controller, and general purpose control instructions 1820 for configuring the controller 1800 to function as a controller for other non-gaming devices.

[0114] In some cases, some or all of the components (software) shown in FIG. 18 may be implemented on another computing device 1805 that is part of a controller system 1807 that includes the controller. In such cases, the processes and / or functions described herein may be implemented by the other computing device 1805 and / or the controller 1800. As an example, the controller 1800 may couple to a host PC or console, computing device / server in the same environment, and provide the device 1805 with data indicative of accessories to couple to the controller. For example, the controller 1800 may transmit data indicative of or identifying accessories coupled to the controller 1800. Such data may be used by the computing device 1805 during a gameplay experience or may be used by the computing device when determining how to interpret data received from the controller 1800 (e.g., which button is being pressed, what pressing the button means, etc.). The computing device 1805 may determine which accessories to couple to the controller based on this data. In another example, the computing device 1805 may interpret data received from the controller 1800 and receive data indicative of an adjusted sensitivity of the controls for use in performing one or more actions. However, although several scenarios have been described, the controller 1800 and the computing device 1805 may be communicatively coupled to each other to transmit and receive data such that the controller 1800, the computing device 1805, and / or other devices of the controller system 1807 can perform the operations and processes described herein.

[0115] Example clauses 1. A controller comprising: a controller body including a rear portion; a first receptacle disposed on the rear portion of the controller body, the first receptacle configured to receive a first grip, the first receptacle including a first attachment mechanism configured to engage a second attachment mechanism of the first grip to couple the first grip to the controller body; and a second receptacle disposed on the rear of the controller body, the second receptacle configured to receive a second grip, the second receptacle including a third attachment mechanism configured to engage a fourth attachment mechanism of the second grip to couple the second grip to the controller body. 2. The controller described in clause 1, wherein the controller body further includes a left handle portion and a right handle portion, the first receptacle being positioned adjacent to the left handle portion and the second receptacle being positioned adjacent to the right handle portion. 3. The controller of clause 1, wherein the first attachment mechanism includes a first magnetic element, the second attachment mechanism includes a second magnetic element engageable with the first magnetic element, the third attachment mechanism includes a third magnetic element, and the fourth attachment mechanism includes a fourth magnetic element engageable with the third magnetic element. 4. The controller of clause 1, wherein at least one of: the first grip is one of a first plurality of grips, the first plurality of grips each differing in at least one of contour, shape, or size, and each of the first plurality of grips configured to be received within a first receptacle; and the second grip is one of a second plurality of grips, the second plurality of grips each differing in at least one of contour, shape, or size, and each of the second plurality of grips configured to be received within a second receptacle. 5. The controller of clause 1, wherein at least one of the first grip includes one or more first buttons or the second grip includes one or more second buttons. 6. The controller of clause 1, wherein the first receptacle includes a first connector that communicatively couples to a second connector of the first grip, and the second receptacle includes a third connector that communicatively couples to a fourth connector of the second grip. 7. The controller of clause 1, wherein at least one of the first receptacle is recessed into the rear of the controller body or the second receptacle is recessed into the rear of the controller body. 8. A controller comprising: a controller body including a rear portion; a compartment disposed within the rear portion of the controller body; one or more switches disposed within the compartment; and a cover configured to couple to the rear portion of the controller body, wherein the cover is disposed over the compartment when coupled to the rear portion, and wherein the cover is interchangeable with one or more additional covers to change functionality of the controller. 9. The controller of clause 8, wherein the cover includes one or more actuatable areas that, when depressed, engage one or more switches. 10. The controller of clause 8, wherein the one or more switches include at least one of a tactile switch or a force sensing resistor. 11. The controller of clause 8, wherein the cover is configured to couple to a rear of the controller body between the left and right handle portions of the controller body. 12. The controller of clause 8, wherein the controller body includes a first attachment mechanism and the cover includes a second attachment mechanism, and engagement between the first attachment mechanism and the second attachment mechanism connects the cover to the controller body. 13. The controller of clause 8, wherein the one or more additional covers include at least one of a first cover that prevents the one or more switches from being engaged when the cover is pressed, or a second cover that includes at least one of a battery or a tactile actuator. 14. A controller system including one or more processors; and a controller, the controller including a controller body, a track pad configured to provide touch data indicative of touch input to the one or more processors, a switch at least partially beneath the track pad and configured to provide selection data indicative of a press on the track pad to the one or more processors, and a rotary dial mechanism disposed at least partially beneath the track pad and configured to adjust an amount of press force required for the switch to detect a press. 15. A controller system as described in clause 14, wherein the track pad is located on the front of the controller body. 16. The controller system of clause 14, wherein the rotary dial mechanism includes a frame having one or more channels, a central dial, and one or more arms extending from the central dial and positioned within the one or more channels. 17. The controller system of clause 16, wherein each of the one or more channels includes a first end and a second end, and each of the one or more arms moves within a corresponding one of the channels between the first end and the second end to adjust the amount of force required for the switch to detect a press. 18. The controller system of clause 16, further comprising a channel disposed through a front cover of the controller body, and a knob disposed within the channel and operably coupled to the rotary dial mechanism, the knob being movable within the channel to adjust the amount of force required for the switch to detect a press. 19. The controller system of clause 14, wherein the amount of force is adjustable between a first amount of force required for the switch to detect the press and a second amount of force required for the switch to detect the press. 20. A controller comprising: a controller body having a front surface; and a speaker present on the front surface of the controller body, the speaker being operable to change audio characteristics of a running application. 21. The controller of clause 20, wherein the speaker is a first speaker and the controller further includes a second speaker present on a front surface of the controller body, the second speaker operable to change audio characteristics of a running application or additional audio characteristics. 22. The controller of clause 21, wherein the first speaker is located on a first side of the controller body and the second speaker is located on a second side of the controller body. 23. The controller of clause 20, wherein the controller further includes a control portion present on a front surface of the controller body, the control portion configured to provide touch data indicative of touch input to one or more processors, the touch data modifying additional audio characteristics of a running application. 24. The controller of clause 23, further including a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to perform acts including determining that touch data is received within a threshold amount of time of detecting activation of the speaker, and altering an audio characteristic based at least in part on the determination. 25. The controller of clause 23, wherein the speaker is operable by a first thumb of a user and the control is operable by a second thumb of the user. 26. The controller of clause 20, wherein the audio characteristics include at least one of increasing volume, decreasing volume, muting volume, or unmuting volume.

[0116] Unless otherwise specified, all numerical values ​​expressing quantities, properties, conditions, and the like used in the specification and claims should be understood in all instances to be modified by the term "about". Accordingly, unless indicated to the contrary, the numerical parameters set forth in this specification and the appended claims are approximations that may vary depending on the desired properties sought to be obtained by the present disclosure. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should be construed in light of at least the number of reported significant digits and by applying ordinary rounding techniques. Where further clarity is needed, the term "about" has the meaning reasonably regarded by one of ordinary skill in the art, and when used in conjunction with a stated numerical value or range, means somewhat greater than or somewhat less than the stated value or range, i.e., within ±20% of the stated value, ±19% of the stated value, ±18% of the stated value, ±17% of the stated value, ±16% of the stated value, ±15% of the stated value, ±14% of the stated value, ±13% of the stated value, ±12% of the stated value, ±11% of the stated value, ±10% of the stated value, ±9% of the stated value, ±8% of the stated value, ±7% of the stated value, ±6% of the stated value, ±5% of the stated value, ±4% of the stated value, ±3% of the stated value, ±2% of the stated value, or ±1% of the stated value.

[0117] Although various examples and embodiments are described individually herein, the examples and embodiments can be combined, rearranged, and modified to arrive at other variations within the scope of the present disclosure. Moreover, while the present subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims. The invention as originally claimed in the present application is set forth below. [Appendix 1] 1. A controller system comprising: one or more processors; A controller, A controller body having a front surface; a first speaker disposed on the front surface and within a left half of the front surface; a first sensor associated with the first speaker and configured to detect a finger contact on the first speaker; a second speaker disposed on the front surface and within a right half of the front surface; and a controller comprising a second sensor associated with the second speaker and configured to detect a finger contact on the second speaker; and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving data from at least one of the first sensor or the second sensor indicating that a finger is in contact with at least one of the first speaker or the second speaker; and and a controller system that performs actions including adjusting a volume of audio content being output by the first speaker and the second speaker based at least in part on the data. [Appendix 2] the data is received from the second sensor; said adjusting the volume includes increasing the volume; or the data is received from the first sensor; 2. The controller system of claim 1, wherein the adjusting of the volume includes at least one of decreasing the volume. [Appendix 3] the first sensor comprises a first capacitance sensor disposed in or on the first speaker; the second sensor comprises a second capacitive sensor disposed in or on the second speaker; 2. The controller system of claim 1, wherein the data includes capacitance data based on the finger contacting the at least one of the first speaker or the second speaker. [Appendix 4] the action being based at least in part on the capacitance data; said finger swipe gesture; and determining a direction of the swipe gesture; 4. The controller system of claim 3, wherein adjusting the volume includes increasing or decreasing the volume based at least in part on a direction of the swipe gesture. [Appendix 5] The first sensor comprises: a first speaker coil of the first speaker; or at least one of a first inductive sensor coupled to the first speaker coil; The second sensor comprises: a second speaker coil of the second speaker; or at least one of the second inductive sensors coupled to the second speaker coil; 2. The controller system of claim 1, wherein the data includes inductance data, the inductance data indicating a change in inductance based on the finger being moved in proximity to at least one of the first speaker coil or the second speaker coil. [Appendix 6] the first speaker includes a first speaker coil; the second speaker includes a second speaker coil; the first sensor comprises a first capacitance sensor; the second sensor comprises a second capacitive sensor; 2. The controller system of claim 1, wherein the data includes capacitance data, the capacitance data indicating a change in capacitance based on the finger being moved in proximity to at least one of the first speaker coil or the second speaker coil. [Appendix 7] the first sensor comprises a first impedance sensor; the second sensor comprises a second impedance sensor; 2. The controller system of claim 1, wherein the data includes impedance data, the impedance data indicating a change in impedance between a pair of leads of the at least one of the first speaker or the second speaker based on the finger muffling the audio content being output by the at least one of the first speaker or the second speaker. [Appendix 8] the first sensor comprises a first microphone; the second sensor comprises a second microphone; The act outputting, by the first speaker, one or more first tones at a frequency inaudible to the human ear; outputting, by the second speaker, one or more second tones at the frequency or a different frequency inaudible to the human ear; 2. The controller system of claim 1, wherein the data includes audio data generated by at least one of the first microphone or the second microphone, and the audio data indicates that the finger is muffling at least one of the one or more first tones or the one or more second tones being output by the at least one of the first speaker or the second speaker. [Appendix 9] 1. A method comprising: receiving, by a processor, data from a sensor associated with a speaker disposed on a controller body of the controller, the data indicating a finger is in contact with the speaker; and adjusting, by the processor, a characteristic of audio content being output by the speaker based at least in part on the data. [Appendix 10] said adjusting said characteristic of said audio content further comprising: increasing the volume of the audio content; decreasing the volume; muting the volume; or 10. The method of claim 9, further comprising at least one of: unmuting the volume. [Appendix 11] the sensor comprises a capacitance sensor disposed in or on the speaker; the data includes capacitance data based on the finger touching the speaker; the method further comprising determining a direction of the finger swipe gesture based at least in part on the capacitance data; 10. The method of claim 9, wherein adjusting the characteristic of the audio content includes increasing or decreasing a volume of the audio content based at least in part on a direction of the swipe gesture. [Appendix 12] the speaker is a first speaker of a pair of speakers disposed on a front surface of the controller body, the first speaker being disposed within a right half of the front surface; 10. The method of claim 9, wherein adjusting the characteristic of the audio content includes increasing a volume of the audio content. [Appendix 13] the sensor comprises a microphone; the method further comprising outputting, by the speaker, one or more tones at frequencies inaudible to the human ear; 10. The method of claim 9, wherein the data includes audio data generated by the microphone, the audio data indicating the finger is muffling the one or more tones being output by the speaker. [Appendix 14] 1. A controller system comprising: one or more processors; A controller, Controller body, A speaker disposed on the controller body; and a controller comprising a sensor associated with the speaker and configured to detect a finger contact on the speaker; and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving data from the sensor indicating a finger is in contact with the speaker; and adjusting a characteristic of audio content being output by the speaker based at least in part on the data. [Appendix 15] The sensor, a speaker coil of the speaker; or at least one of the inductive sensors coupled to the speaker coil; 15. The controller system of claim 14, wherein the data includes inductance data, the inductance data indicating a change in inductance based on the finger being moved in proximity to the speaker coil. [Appendix 16] the speaker includes a speaker coil; the sensor comprises a capacitance sensor; 15. The controller system of claim 14, wherein the data includes capacitance data, the capacitance data indicating a change in capacitance based on the finger being moved in proximity to the speaker coil. [Appendix 17] the sensor comprises an impedance sensor; 15. The controller system of claim 14, wherein the data includes impedance data, the impedance data indicating a change in impedance between a pair of reeds of the speaker based on the finger muffling the audio content being output by the speaker. [Appendix 18] the sensor comprises a microphone; the acts further include outputting, by the speaker, one or more tones at frequencies inaudible to the human ear; 15. The controller system of claim 14, wherein the data includes audio data generated by the microphone, the audio data indicating the finger is muffling the one or more tones being output by the speaker. [Appendix 19] the speakers include a first speaker disposed on a front surface of the controller body and within a left half of the front surface; the sensor comprises a first sensor; The controller: a second speaker disposed on the front surface and within a right half of the front surface; and a second sensor associated with the second speaker and configured to detect a finger contact on the second speaker; 15. The controller system of claim 14, wherein adjusting the characteristic of the audio content includes reducing a volume of the audio content. [Appendix 20] the sensor comprises a capacitance sensor disposed in or on the speaker; the data includes capacitance data based on the finger touching the speaker; the acts further include determining a direction of the finger swipe gesture based at least in part on the capacitance data; 15. The controller system of claim 14, wherein adjusting the characteristic of the audio content includes increasing or decreasing a volume of the audio content based at least in part on the direction of the swipe gesture.

Claims

1. 1. A controller system comprising: one or more processors; A controller, a controller body having a front surface; a first speaker disposed on the front surface and within a left half of the front surface; a first sensor associated with the first speaker and configured to detect a finger contact on the first speaker, the first sensor comprising at least one of a first speaker coil of the first speaker or a first inductive sensor coupled to the first speaker coil; a second speaker disposed on the front surface and within a right half of the front surface; and a controller comprising: a second sensor associated with the second speaker and configured to detect a finger contact on the second speaker, the second sensor comprising at least one of a second speaker coil of the second speaker or a second inductive sensor coupled to the second speaker coil; and and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving inductance data from at least one of the first sensor or the second sensor indicative of a change in inductance based on a finger moving in proximity to at least one of the first speaker coil or the second speaker coil; and adjusting a volume of audio content being output by the first speaker and the second speaker based at least in part on the inductance data; Here, the finger contact on the first speaker is a left finger contact; the finger contact on the second speaker is a right finger contact, and and when the left finger and the right finger contact the first speaker and the second speaker, respectively, substantially simultaneously, adjusting the volume includes muting or unmuting a volume of the audio content being output by the first speaker and the second speaker.

2. the inductance data is received from the second sensor; said adjusting the volume includes increasing the volume; or the inductance data is received from the first sensor; The controller system of claim 1 , wherein the adjusting of the volume comprises at least one of: decreasing the volume.

3. 1. A method comprising: receiving, by a processor, inductance data from a sensor associated with a speaker disposed on a controller body of the controller, the sensor comprising at least one of a speaker coil of the speaker or an inductive sensor in communication with the speaker coil, and the inductance data indicative of a change in inductance based on a finger moving in proximity to the speaker coil; and causing the processor to adjust a characteristic of audio content being output by the speaker based at least in part on the inductance data and a gesture by the finger contacting the speaker.

4. said adjusting said characteristic of said audio content further comprising: increasing the volume of the audio content; decreasing the volume; muting the volume; or The method of claim 3 , further comprising at least one of: unmuting the volume.

5. the speaker is a first speaker of a pair of speakers disposed on a front surface of the controller body, the first speaker being disposed within a right half of the front surface; The method of claim 3 , wherein the adjusting the characteristic of the audio content comprises increasing a volume of the audio content.

6. 1. A controller system comprising: one or more processors; A controller, Controller body, A speaker disposed on the controller body; and a controller comprising a sensor associated with the speaker and configured to detect a finger contact on the speaker, the sensor comprising at least one of a speaker coil of the speaker or an inductive sensor coupled to the speaker coil; and a non-transitory computer-readable medium storing instructions that, when executed by the one or more processors, cause the one or more processors to: receiving inductance data from the sensor indicative of a change in inductance based on a finger moving in proximity to the speaker coil; and adjusting characteristics of audio content being output by the speaker based at least in part on the inductance data and a gesture by the finger contacting the speaker.

7. the speakers include a first speaker disposed on a front surface of the controller body and within a left half of the front surface; the sensor comprises a first sensor; The controller: a second speaker disposed on the front surface and within a right half of the front surface; and a second sensor associated with the second speaker and configured to detect a finger contact on the second speaker; The controller system of claim 6 , wherein the adjusting the characteristic of the audio content comprises decreasing a volume of the audio content.

8. The second speaker includes: The controller system of claim 7 comprising at least one of a second speaker coil of the second speaker or a second inductive sensor coupled to the second speaker coil.

9. the speakers include a first speaker disposed on a front surface of the controller body and within a right half of the front surface; The sensor comprises a first sensor; The controller: a second speaker disposed on a front surface of the controller body and within a left half of the front surface; a second sensor associated with the second speaker and configured to detect a finger contact on the second speaker; The controller system of claim 6 , wherein causing the characteristic of the audio content to be adjusted comprises increasing a volume of the audio content.

10. The second sensor includes: a second speaker coil of the second speaker; or The controller system of claim 9 comprising at least one second inductive sensor coupled to the second speaker coil.

11. Adjusting the characteristic of the audio content includes: increasing the volume of the audio content; decreasing the volume; muting the volume; or The controller system of claim 6 , further comprising at least one of: unmuting the volume.

12. The controller system of claim 6 , wherein the inductive sensor is part of an amplifier of the speaker.

13. The acts further comprise determining, based at least in part on the inductance data, that a value of inductance detected by the sensor meets a threshold; and The controller system of claim 6 , wherein adjusting the characteristic of the audio content is based on the value of the inductance satisfying the threshold.

14. The speaker comprises a first speaker; The sensor comprises a first sensor; the inductance data is first inductance data, the finger is an index finger, The controller: a second speaker disposed on the controller body; a second sensor associated with the second speaker and configured to detect a finger contact on the second speaker, the second sensor comprising at least one of a second speaker coil of the second speaker or a second inductive sensor coupled to the second speaker coil; receiving second inductance data from the second sensor indicating a change in inductance based on a middle finger moving in proximity to the second speaker coil; The said act is determining, based at least in part on the first inductance data and the second inductance data, that the index finger contacts the first speaker substantially simultaneously with the middle finger contacting the second speaker; The controller system of claim 6 , wherein causing the characteristic of the audio content to be adjusted comprises at least one of muting or unmuting a volume of the audio content.

15. the speakers are a pair of first speakers disposed on a front surface of the controller body, the first speaker being disposed within a left half of the front surface; The method of claim 3 , wherein causing the characteristic of the audio content to be adjusted comprises decreasing a volume of the audio content.

16. The method of claim 3 , wherein the inductive sensor is part of an amplifier of the speaker.

17. determining, based at least in part on the inductance data, that a value of inductance detected by the sensor meets a threshold; The method of claim 3 , wherein adjusting the characteristic of the audio content is based on the value of the inductance satisfying the threshold.

18. The speaker comprises a first speaker; The sensor comprises a first sensor; the inductance data is first inductance data, the finger is an index finger, The method comprises: receiving, by a processor, second inductance data from a second sensor associated with a second speaker disposed on the controller body, the second sensor comprising at least one of a second speaker coil of the second speaker or a second inductive sensor in communication with the second speaker coil, and the second inductance data indicative of a change in inductance based on a middle finger being moved in proximity to the second speaker coil; and determining, by the processor, based at least in part on the first inductance data and the second inductance data, that the index finger contacts the first speaker substantially simultaneously with the middle finger contacting the second speaker. The method of claim 3 , wherein causing the characteristic of the audio content to be adjusted comprises at least one of muting or unmuting a volume of the audio content.

19. the first inductive sensor is part of a first amplifier of the first speaker; or The controller system of claim 1 , wherein the second inductive sensor is at least one of: a second amplifier of the second speaker.

20. The acts further include determining, based at least in part on the inductance data, that a value of inductance detected by at least one of the first sensor and the second sensor meets a threshold value; and The controller system of claim 1 , wherein the adjustment of the volume is based on the value of the inductance satisfying the threshold.

Images