Suppression of noise caused by switching of audio source

Abstract

To provide a program, a method and a device for suppressing noise caused by switching of audio source.SOLUTION: A suppression method of noise caused by switching of audio source includes: receiving, while a speaker outputs audio from a first application, an instruction to output audio from a second application; muting audio output from the speaker in response to receiving the instruction; instructing an amplifier in communication with the speaker to associate a second channel with the second application; instructing the first application to deactivate audio transmission; instructing the amplifier to switch a speaker input from a first channel associated with the first application to the second channel; instructing the second application to activate audio transmission; and unmuting the audio output from the speaker.SELECTED DRAWING: Figure 3

Description

[Background technology]

[0001] An audio output device, such as a speaker or speaker system, installed in a vehicle is used by multiple applications. Some applications are non-flutter applications that generate a continuous audio stream from radio, pre-recorded physical media, the Internet, etc. Some applications are flutter applications that generate intermittent audio data related to navigation, warnings, etc. At any given time, multiple applications may be generating audio for output by the output device. At a particular time, the sound emitted from the audio output device may change from one application to another. [Brief explanation of the drawings]

[0002] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying figures. It should be noted that, according to standard industry practice, various features have not been drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or decreased for clarity of illustration.

[0003] [Figure 1] FIG. 1 is a schematic diagram of a system for suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention. [Figure 2] FIG. 2 is a schematic diagram of a head unit for suppressing noise caused by switching audio sources, in accordance with at least some embodiments of the present invention. [Figure 3] FIG. 3 is an operational flow for suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention. [Figure 4]FIG. 4 is a block diagram of a hardware configuration for suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0004] The following disclosure provides numerous different embodiments or examples for implementing different features of the provided subject matter. To simplify the disclosure, specific examples of components, values, operations, materials, arrangements, or the like are set forth below. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, or the like are contemplated. In addition, the disclosure may repeat reference numerals and / or characters in various examples. This repetition is for the purposes of simplicity and clarity and does not, in itself, dictate a relationship between the various embodiments and / or configurations described.

[0005] In some cases, digital noise is generated when the sound emitted from an audio output device is changed from one application to another. In some cases, the noise is caused by the current application continuing to output after the bit rate or other characteristics of the audio output have been changed. For example, if a navigation application attempts to provide a reminder to turn right over the sound of a radio application, the navigation application voice will become misleading.

[0006] In at least some embodiments described herein, the application manager mutes audio output in response to receiving an instruction to switch active audio applications, communicates with the current application and the new application to implement the switch, and then unmutes audio output.

[0007] In at least some embodiments, the application manager implementation provides low-latency noise suppression caused by audio source switching. In at least some embodiments, the head unit requires less than one second to perform the noise suppression caused by audio source switching, which reduces the required buffer capacity of the audio channel in the amplifier, which is typically less than one second. In at least some embodiments, the head unit implementation is faster than many amplifiers, particularly those that do not have sufficient computational resources to perform the noise suppression caused by audio source switching without exceeding their buffer limits.

[0008] In at least some embodiments, the head unit instructs the amplifier to reserve the second channel by associating it with the second application before instructing the first application to disable audio generation so that the amplifier does not detect the error. In at least some embodiments, reserving the second channel before instructing the first application to disable audio generation also gives the amplifier time to set aside resources such as channel buffers and establish any permissions for the second application while the head unit communicates with the application.

[0009] 1 is a schematic diagram of a system for suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention. The system includes a head unit 100, an amplifier 110, and a speaker 118.

[0010] The head unit 100 communicates with the amplifier 110. The head unit 101 includes a controller 102 and storage 104. In at least some embodiments, the head unit 100 utilizes the controller 102 and storage 104 to execute an application manager. In at least some embodiments, the head unit 100 also utilizes the controller 102 and storage 104 to execute a first application and a second application. In at least some embodiments, the head unit 100 is an in-dash media device for a vehicle. In at least some embodiments, the head unit 100 issues commands to the amplifier 110 to "mute," "change channel," etc. In at least some embodiments, the head unit 100 utilizes a channel identifier. In at least some embodiments, the head unit 100 communicates with other vehicle devices, such as an electronic control unit (ECU), through a network, such as a controller area network (CAN), Ethernet, or other wireless or wired network. In at least some embodiments, the head unit 100 communicates with an ECU that executes an arbitration manager. In at least some embodiments, controller 102 is a processor or programmable circuit, such as an ECU, that executes instructions to cause the processor or programmable processor to operate in accordance with the instructions, for example, to execute an application manager, a first application, and a second application. In at least some embodiments, storage 104 includes a volatile or non-volatile computer-readable medium capable of storing executable and non-executable data accessed by controller 102 during execution of instructions.

[0011] Amplifier 110 communicates with head unit 100 and speaker 118. Amplifier 110 includes channel 112, channel 114, and channel 116. In at least some embodiments, amplifier 110 outputs an audio signal to speaker 118. In at least some embodiments, channel 112, channel 114, and channel 116 are each configured to route audio data from an application to speaker 118. In at least some embodiments, channel 112, channel 114, and channel 116 are each associated with a path identifier, e.g., “radio,” “media player,” etc. In at least some embodiments, channel 112, channel 114, and channel 116 each have a preconfigured audio bit rate, sampling rate, buffer size, equalizer level, etc. In at least some embodiments, channel 112, channel 114, and channel 116 are each configured upon association with a path identifier. In at least some embodiments, each of channels 112, 114, and 116 is configured and associated with a path identifier by head unit 100. In at least some embodiments, amplifier 110 is configured to increase the amplitude of the audio signal before transmitting the audio signal to speaker 118. In at least some embodiments, amplifier 110 is configured to convert audio data received from head unit 100 into an audio signal before amplifying the audio signal. In at least some embodiments, amplifier 110 receives commands and audio transmissions over a digital interface.

[0012] The speaker 118 is in communication with the amplifier 110. In at least some embodiments, the speaker 118 receives an audio signal from the amplifier 110. In at least some embodiments, the speaker 118 is a transducer configured to convert an electrical signal into a compression wave. In at least some embodiments, the speaker 118 includes multiple transducers. In at least some embodiments, the speaker 118 includes multiple speakers, e.g., left and right speakers, front and rear speakers, etc.

[0013] 2 is an information flow relating to suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention. The information flow is between an arbitration manager 220, an application manager 222, a first application 224, and a second application 226.

[0014] In at least some embodiments, arbitration manager 220 is configured to determine audio priorities among applications executing in the vehicle. In at least some embodiments, application manager 222 is configured to facilitate and switch audio output from applications executing in the vehicle. In at least some embodiments, first application 224 is a flutter-free application configured to generate audio data from a music source, such as radio, pre-recorded physical media, the Internet, etc. In at least some embodiments, second application 226 is a flutter-free application configured to generate intermittent audio data related to navigation, warnings, etc. In at least some embodiments, first application 224 and second application 226 are any combination of flutter and flutter-free applications. In at least some embodiments, first application 224 and second application 226 are flutter applications. In at least some embodiments, first application 224 and second application 226 are flutter-free applications. In at least some embodiments, the application manager 222, the first application 224, and the second application 226 are executed by an ECU of the head unit, such as the controller 102 of the head unit 100 of FIG. 1. In at least some embodiments, the arbitration manager 220 is executed by an ECU that communicates with the head unit ECU. In at least some embodiments, the head unit ECU communicates with the ECU running the arbitration manager 220 over a CAN.

[0015] Prior to the information flow of FIG. 2, the application manager 222 has already configured the first channel of the amplifier to the first application 224 via a path identifier.

[0016] At S230, arbitration manager 222 sends an output request to application manager 222. In at least some embodiments, arbitration manager 222 sends an instruction to application manager 220 to output audio from the second application while the speaker outputs audio from the first application. In at least some embodiments, arbitration manager 220 sends the output request in response to determining that second application 226 has priority over first application 224. In at least some embodiments, arbitration manager 220 sends the output request in response to determining that second application 226 has absolute priority.

[0017] At S232, the application manager 222 sends a disable request to the first application 224. In at least some embodiments, the application manager 222 instructs the first application 224 to disable audio transmission. In at least some embodiments, the application manager 222 sends the disable request in response to muting the audio output.

[0018] At S233, the first application 224 sends a disable confirmation to the application manager 222. In at least some embodiments, the first application 224 approves the disable request. In at least some embodiments, the first application 224 sends the disable confirmation in response to disabling audio transmission to the amplifier.

[0019] At S235, the application manager 222 sends an enable request to the second application 226. In at least some embodiments, the application manager 222 instructs the second application to enable audio transmission. In at least some embodiments, the application manager 222 sends the enable request in response to switching the input to the speaker. In at least some embodiments, the second application 226 does not generate audio until instructed by the application manager 222.

[0020] At S236, the second application 226 sends an enable confirmation to the application manager 222. In at least some embodiments, the second application 226 approves the enable request. In at least some embodiments, the second application 226 sends the enable confirmation in response to enabling audio transmission to the amplifier.

[0021] 3 is an operational flow for suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention. The operational flow provides a method for suppressing noise caused by switching audio sources. In at least some embodiments, the method is performed by a controller of a head unit, such as controller 102 of FIG. 1 or controller 402 of FIG. 4.

[0022] At S340, the controller or a section thereof receives an instruction to output audio from the second application. In at least some embodiments, the controller receives an instruction to output audio from the second application while the speaker outputs audio from the first application. In at least some embodiments, the controller receives the instruction from an arbitration manager. In at least some embodiments, the controller receives the instruction from the ECU over the CAN. In at least some embodiments, the instruction identifies the first application. In at least some embodiments, the operational flow is triggered when the controller receives an instruction from the arbitration manager to switch audio from the first application to the second application.

[0023] At S341, the controller or a mute section thereof mutes the audio output. In at least some embodiments, the controller mutes the audio output in response to receiving a command. In at least some embodiments, the controller suppresses audio transmission from the first application. In at least some embodiments, the controller suppresses audio transmission to an amplifier. In at least some embodiments, the controller instructs the amplifier to set a speaker volume to zero. In at least some embodiments, the muting of the audio output includes at least one of suppressing audio transmission from the first application, suppressing audio transmission to the amplifier, or instructing the amplifier to set a speaker volume to zero.

[0024] At S343, the controller or its association section associates the second channel with the second application. In at least some embodiments, the controller instructs an amplifier in communication with the speaker to associate the second channel with the second application. In at least some embodiments, the second channel has at least one of an audio bitrate, a sampling rate, a buffer size, or an equalizer setting corresponding to the second application. In at least some embodiments, the controller instructs the amplifier to adjust the at least one of the audio bitrate, the sampling rate, the buffer size, or the equalizer setting to a predetermined level. In at least some embodiments, the instructions include an identifier of the second application and a predetermined level for each of the at least one of the audio bitrate, the sampling rate, the buffer size, or the equalizer setting. In at least some embodiments, the second channel is reserved but not selected for output to the speaker.

[0025] At S344, the controller or its instruction section instructs the first application to disable audio transmission. In at least some embodiments, the controller instructs the first application to disable audio transmission. In at least some embodiments, the controller instructs the amplifier to associate the second channel with the second application before instructing the first application to disable audio transmission. In at least some embodiments, the controller sends a disable request, such as disable request S232 of FIG. 2.

[0026] At S345, the controller or its switching section switches to a second channel. In at least some embodiments, the controller commands the amplifier to switch the speaker input from the first channel associated with the first application to the second channel. In at least some embodiments, the command identifies the second channel.

[0027] At S347, the controller or an instruction section thereof instructs the second application to enable audio transmission. In at least some embodiments, the controller instructs the second application to enable audio transmission. In at least some embodiments, the controller instructs the amplifier to switch to the second channel before instructing the second application to enable audio transmission. In at least some embodiments, the controller sends an enable request, such as enable request S235 of FIG. 2.

[0028] At S348, the controller or a section thereof determines whether the second application is sending audio data. In at least some embodiments, the controller detects whether audio data is being sent to the amplifier. In at least some embodiments, the controller determines whether the second application has queued audio data for the amplifier. In response to the controller determining that the second application is sending audio data, the operational flow proceeds to unmute at S349. In response to the controller determining that the second application is not sending audio data, the operational flow returns to the audio enable instruction at S347.

[0029] At S349, the controller or its unmute section unmutes the audio output. In at least some embodiments, the controller unmutes the audio output. In at least some embodiments, the unmute occurs in response to determining that the second application is transmitting audio data.

[0030] FIG. 4 is a block diagram of a hardware configuration for suppressing noise caused by switching audio sources, according to at least some embodiments of the present invention.

[0031] A preferred hardware configuration includes a head unit 400 that communicates with input devices 408, either directly or through a network 407, and with an ECU 419 through the network 407. In at least some embodiments, the head unit 400 is a computer or other computing device that receives input or commands from the input devices 408. In at least some embodiments, the head unit 400 is integrated into the input devices 408. In at least some embodiments, the head unit 400 is a computer system that executes computer-readable instructions to perform operations related to suppressing noise caused by switching audio sources.

[0032] The head unit 400 includes a controller 402, a storage unit 404, an input / output interface 406, and a communication interface 409. In at least some embodiments, the controller 402 includes a processor or programmable circuit that executes instructions to cause the processor or programmable circuit to perform operations in accordance with the instructions. In at least some embodiments, the controller 402 includes analog or digital programmable circuitry, or any combination thereof. In at least some embodiments, the controller 402 includes physically separate storage or circuitry that communicates through communications. In at least some embodiments, the storage unit 404 includes a non-volatile computer-readable medium capable of storing executable and non-executable data accessed by the controller 402 during execution of instructions. The communication interface 409 sends and receives data from a network 407. The input / output interface 406 connects to various input and output units, such as input devices 408 via parallel ports, serial ports, keyboard ports, mouse ports, monitor ports, and the like, to accept commands and present information. In some embodiments, the storage unit 404 is external to the head unit 400 .

[0033] The controller 402 includes a mute section 450, an association section 452, an instruction section 454, and a switching section 456. The storage unit 404 includes switching parameters 460, channel associations 462, and instruction parameters 464.

[0034] Mute section 450 is circuitry or instructions in controller 402 configured to mute audio output. In at least some embodiments, mute section 450 is configured to mute audio output in response to receiving an instruction. In at least some embodiments, mute section 450 utilizes information in storage unit 404, such as channel associations 462. In at least some embodiments, mute section 450 includes subsections for performing additional functions as described in the flowcharts above. In at least some embodiments, such subsections are referenced by names associated with the corresponding functions.

[0035] Association section 452 is circuitry or instructions in controller 402 configured to associate channels. In at least some embodiments, association section 452 is configured to instruct an amplifier in communication with the speaker to associate a second channel with a second application. In at least some embodiments, association section 452 utilizes information in storage unit 404, such as channel associations 462 and instruction parameters 464. In at least some embodiments, association section 452 includes subsections for performing additional functions as described in the flowcharts above. In at least some embodiments, such subsections are referenced by names associated with the corresponding functions.

[0036] Instruction section 454 is circuitry or instructions of controller 402 configured to issue instructions. In at least some embodiments, instruction section 454 is configured to instruct a first application to disable audio transmission and to instruct a second application to enable audio transmission. In at least some embodiments, association section 452 utilizes information in storage unit 404, such as instruction parameters 464. In at least some embodiments, instruction section 454 includes subsections for performing additional functions as described in the flowcharts above. In at least some embodiments, such subsections are referenced by names associated with the corresponding functions.

[0037] Switching section 456 is circuitry or instructions in controller 402 configured to switch audio channels. In at least some embodiments, switching section 456 is configured to instruct an amplifier to switch a speaker input from a first channel associated with a first application to a second channel. In at least some embodiments, switching section 456 utilizes information in storage unit 404, such as switching parameters 460. In at least some embodiments, instruction section 454 includes subsections for performing additional functions as described in the flowcharts above. In at least some embodiments, such subsections are referenced by names associated with the corresponding functions.

[0038] In at least some embodiments, the apparatus is a separate device capable of processing logical functions to perform the operations herein. In at least some embodiments, the controller and storage unit need not be entirely separate devices, and in some embodiments, share circuitry or one or more computer-readable media. In at least some embodiments, the storage unit includes a hard drive that stores both computer-executable instructions and data accessed by the controller, and the controller includes a central processing unit (CPU) and RAM combination, where the computer-executable instructions are copyable in whole or in part for execution by the CPU during performance of the operations herein.

[0039] In at least some embodiments where the device is a computer, programs installed on the computer can cause the computer to function as or perform operations associated with the device embodiments described herein, and in at least some embodiments, such programs are executable by a processor to cause the computer to perform specific operations associated with some or all of the blocks in the flowcharts and block diagrams described herein.

[0040] At least some embodiments are described with reference to flowcharts and block diagrams, where the blocks represent (1) steps in a process in which an operation is performed or (2) sections of a controller responsible for performing an operation. In at least some embodiments, particular steps and sections are implemented by dedicated circuitry, programmable circuitry provided with computer-readable instructions stored on a computer-readable medium, and / or a processor provided with computer-readable instructions (computer program) stored on a computer-readable medium. In at least some embodiments, dedicated circuitry includes digital and / or analog hardware circuitry, including integrated circuits (ICs) and / or discrete circuits. In at least some embodiments, programmable circuitry includes reconfigurable hardware circuitry, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), etc., comprising logical AND, OR, XOR, NAND, NOR, and other logic operations, flip-flops, registers, memory elements, etc.

[0041] In at least some embodiments, a computer-readable storage medium comprises a tangible device capable of holding and storing instructions for use by an instruction execution device. In some embodiments, a computer-readable storage medium includes, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as a punch card or a ridge-in-a-groove structure having instructions recorded thereon, and any suitable combination thereof. Computer-readable media as used herein should not be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted over wires.

[0042] In at least some embodiments, the computer-readable program instructions described herein can be downloaded to each computing / processing device from a computer-readable storage medium or can be downloaded to an external computer or external storage device over a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. In at least some embodiments, the network includes copper transmission cables, optical fiber transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. In at least some embodiments, a network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing / processing device.

[0043] In at least some embodiments, the computer-readable program instructions for performing the operations described above are either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, or the like, and traditional procedural programming languages ​​such as the "C" programming language or similar programming languages. In at least some embodiments, the computer-readable program instructions execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In at least some embodiments, in the latter scenario, the remote computer is connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or is connected to an external computer (e.g., over the Internet using an Internet Service Provider). In at least some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) executes computer-readable program instructions by utilizing state information in the computer-readable program instructions to individualize the electronic circuitry to perform aspects of the present invention.

[0044] Although embodiments of the present invention have been described, the scope of any claimed subject matter is not limited to the above-described embodiments. Those skilled in the art will understand that various modifications and improvements to the above-described embodiments are possible. Those skilled in the art will also understand from the claims that additional embodiments incorporating such modifications or improvements are within the scope of the present invention.

[0045] Unless an order is indicated by "before," "before," or the like, and unless output from a previous process is used in a later process, the operations, procedures, steps, and stages of each process performed by the apparatus, system, program, and method described in the claims, embodiments, or figures may be performed in any order. Even when a claim, embodiment, or figure describes a process flow using phrases such as "first" or "then," such description does not necessarily imply that the process must be performed in the order described.

[0046] In at least some embodiments, suppressing noise caused by switching audio sources is performed by receiving an instruction to output audio from a second application while a speaker outputs audio from a first application, and in response to receiving the instruction, muting the audio output from the speaker, instructing an amplifier in communication with the speaker to associate a second channel with the second application, instructing the first application to disable audio transmission, instructing the amplifier to switch the speaker input from the first channel associated with the first application to the second channel, instructing the second application to enable audio transmission, and unmuting the audio output from the speaker. In at least some embodiments, muting the audio output from the speaker includes at least one of suppressing audio transmission from the first application, suppressing audio transmission to the amplifier, or instructing the amplifier to set the speaker volume to zero. In at least some embodiments, the instruction to the first application to disable audio transmission occurs after the instruction to the amplifier to associate the second channel with the second application. In at least some embodiments, the unmuting occurs in response to determining that a second application is transmitting audio data. In at least some embodiments, the first application and the second application are any combination of flutter and flutter-free applications. In at least some embodiments, the amplifier receives the instructions and audio transmissions through a digital interface. In at least some embodiments, the second channel has at least one of an audio bit rate, a sampling rate, a buffer size, or an equalizer setting corresponding to the second application.

[0047] In at least some embodiments, suppression of noise caused by switching audio sources is performed by a device that includes a processor that executes instructions in accordance with the above operations, or a controller that includes circuitry configured to perform the above operations.

[0048] The foregoing outlines features of some embodiments so that those skilled in the art may more fully appreciate aspects of the present disclosure. Those skilled in the art should appreciate that this disclosure may readily be used as a basis for designing or modifying other processes and structures to carry out the same purposes and / or achieve the same advantages as the embodiments incorporated herein. Those skilled in the art should also appreciate that such equivalent structures do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations can be made therein without departing from the spirit and scope of the present disclosure.

Claims

1. 1. A computer program product for causing at least one processor to perform operations, said operations comprising: receiving an instruction to output audio from a second application while a speaker is outputting audio from a first application; muting audio output from the speaker in response to receiving the command; instructing an amplifier in communication with the speaker to associate a second channel with the second application; instructing the first application to disable audio transmission; instructing the amplifier to switch a speaker input from a first channel associated with the first application to the second channel; instructing the second application to enable audio transmission; unmuting the audio output from the speaker; a computer program comprising:

2. 2. The computer program product of claim 1, wherein the muting of the audio output from the speaker includes at least one of suppressing audio transmission from the first application, suppressing audio transmission to the amplifier, or instructing the amplifier to set a speaker volume to zero.

3. 3. The computer program product of claim 1, wherein the instruction to the first application to disable audio transmission occurs after the instruction to the amplifier to associate the second channel with the second application.

4. The computer program product of claim 1 or 2, wherein the unmuting occurs in response to determining that the second application is transmitting audio data.

5. The computer program product of claim 1 or 2, wherein the first application and the second application are any combination of flutter and non-flutter applications.

6. 3. A computer program according to claim 1 or 2, wherein the amplifier receives instructions and audio transmissions through a digital interface.

7. 3. The computer program product of claim 1, wherein the second channel has at least one of an audio bit rate, a sampling rate, a buffer size, or an equalizer setting corresponding to the second application.

8. 1. A processor-implemented method comprising: receiving an instruction to output audio from a second application while a speaker is outputting audio from a first application; muting audio output from the speaker in response to receiving the command; instructing an amplifier in communication with the speaker to associate a second channel with the second application; instructing the first application to disable audio transmission; instructing the amplifier to switch a speaker input from a first channel associated with the first application to the second channel; instructing the second application to enable audio transmission; unmuting the audio output from the speaker; A method comprising:

9. 9. The method of claim 8, wherein the muting of the audio output from the speaker includes at least one of suppressing audio transmission from the first application, suppressing audio transmission to the amplifier, or instructing the amplifier to set a speaker volume to zero.

10. 10. The method of claim 8 or 9, wherein the instruction to the first application to disable audio transmission occurs after the instruction to the amplifier to associate the second channel with the second application.

11. 10. The method of claim 8 or 9, wherein the unmuting occurs in response to determining that the second application is transmitting audio data.

12. The method of claim 8 or 9, wherein the first application and the second application are any combination of flutter and non-flutter applications.

13. 10. The method of claim 8 or 9, wherein the amplifier receives commands and audio transmissions through a digital interface.

14. 10. The method of claim 8 or 9, wherein the second channel has at least one of an audio bit rate, a sampling rate, a buffer size, or an equalizer setting corresponding to the second application.

15. 1. A device comprising a controller including circuitry configured to perform operations, the operations comprising: receiving an instruction to output audio from a second application while a speaker is outputting audio from a first application; muting audio output from the speaker in response to receiving the command; instructing an amplifier in communication with the speaker to associate a second channel with the second application; instructing the first application to disable audio transmission; instructing the amplifier to switch a speaker input from a first channel associated with the first application to the second channel; instructing the second application to enable audio transmission; unmuting the audio output from the speaker; Including, the device.

16. 16. The device of claim 15, wherein the muting of the audio output from the speaker includes at least one of suppressing audio transmission from the first application, suppressing audio transmission to the amplifier, or instructing the amplifier to set a speaker volume to zero.

17. 17. The device of claim 15 or 16, wherein the instruction to the first application to disable audio transmission occurs after the instruction to the amplifier to associate the second channel with the second application.

18. 17. The device of claim 15 or 16, wherein the unmuting occurs in response to determining that the second application is transmitting audio data.

19. 17. The device of claim 15 or 16, wherein the amplifier is configured to receive commands and audio transmissions over a digital interface.

20. 17. The device of claim 15 or 16, wherein the second channel has at least one of an audio bit rate, a sampling rate, a buffer size, or an equalizer setting corresponding to the second application.

Images