Wireless MIDI headset

CN114946194BActive Publication Date: 2026-07-07QRS MUSIC TECH CO

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
QRS MUSIC TECH CO
Filing Date
2020-10-22
Publication Date
2026-07-07

AI Technical Summary

Technical Problem

Existing wireless headphones suffer from latency issues when receiving MIDI instrument data, which affects the performance experience.

Method used

The wireless headphone device is equipped with a wireless transceiver unit and a sound processing logic unit, which receives MIDI data via Bluetooth or network and converts it into audio output in real time, reducing latency.

Benefits of technology

It significantly reduces the latency between MIDI instrument playback and wireless headphone audio output, improving the real-time performance and experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114946194B_ABST
    Figure CN114946194B_ABST
Patent Text Reader

Abstract

This document describes a wireless headset configured to process a music interface protocol (e.g., Musical Instrument Digital Interface (MIDI) protocol) received wirelessly by a source device (e.g., via Bluetooth or Internet connection). The wireless headset includes a first headphone speaker and a second headphone speaker, and a wireless transceiver unit that receives data streams via a wireless connection. The wireless transceiver unit includes sound processing logic that converts the data stream into a data stream associated with the music interface protocol and outputs audio corresponding to the converted data stream to the first and second headphone speakers.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 924,872, filed October 23, 2019, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to a headphone device that receives Musical Instrument Digital Interface (MIDI) data and / or audio via a wireless protocol for audio output. Background Technology

[0004] Many electronic musical instruments (e.g., keyboards, synthesizers, and electronic drums) implement the MIDI standard. When a person plays a MIDI instrument, the instrument (e.g., via MIDI controllers on it) translates the person's movements into MIDI data. More specifically, the instrument generates MIDI data that specifies instructions for the music (e.g., clefs, pitches, vibrato, and other characteristics). Devices such as sound modules or sequencers, configured inside or outside the MIDI instrument, can then interpret the MIDI data to reproduce the sound representing the person playing the instrument.

[0005] Typically, MIDI instruments can be configured to output audio to an analog headphone device connected to it (or to speakers connected to the MIDI instrument) via a cable or a combination of radio frequency (RF) transmitters and receivers. For various reasons (e.g., practicing an instrument quietly relative to others), individuals may wish to wear wireless headphones while practicing on a MIDI instrument. However, wireless headphones generally have several drawbacks. One of these drawbacks includes the cost and inconvenience of using RF transmitters and receivers. In this case, if a wireless protocol such as Bluetooth is used, wireless headphones may encounter latency between the instrument playing (e.g., pressing a key) and the transmission of the corresponding MIDI data to the headphones for audio output to the headphone speakers. As a result, when a corresponding key is pressed, a person may hear the given output later, which can affect the overall experience of the person playing the MIDI instrument. For example, higher latency can affect the time it takes for a person to hear the corresponding output from the MIDI instrument, and thus affect performance (e.g., rhythm). Summary of the Invention

[0006] The embodiments presented herein disclose a wireless headset configured with a MIDI sound processor for relatively real-time output of MIDI data. The wireless headset device includes a first headphone speaker and a second headphone speaker. The wireless headset device also includes a wireless transceiver unit with sound processing logic. The wireless transceiver receives a data stream via a wireless connection to a source device. The wireless transceiver further converts the data stream into a data stream associated with a music interface protocol via the sound processing logic unit. The wireless transceiver further outputs audio corresponding to the converted data stream to the first headphone speaker and the second headphone speaker via the sound processing logic unit.

[0007] Another embodiment presented herein discloses a method. This method typically includes receiving a data stream by a wireless headset via a wireless connection to a source device. The wireless headset includes a first headphone speaker and a second headphone speaker. The method further includes converting the data stream into a data stream associated with a music interface protocol by the wireless headset. The method also includes outputting audio corresponding to the converted data stream to the first and second headphone speakers by the wireless headset.

[0008] Another embodiment presented herein discloses a wireless headset having means for receiving a data stream via a wireless connection to a source device. The wireless headset further includes means for converting the data stream into a data stream associated with a music interface protocol. The wireless headset also includes means for outputting audio corresponding to the converted data stream to a first headphone speaker and a second headphone speaker. Attached Figure Description

[0009] Figure 1 A perspective view of at least one embodiment of an example wireless headset configured with a MIDI sound engine to output MIDI data in relatively real time is shown;

[0010] Figure 2 It shows Figure 1 At least one embodiment of an example performance environment in which the wireless headphones can operate; and

[0011] Figure 3 The operation is shown Figure 1 A flowchart of at least one embodiment of a method for making wireless headphones. Detailed Implementation

[0012] The embodiments presented herein disclose a wireless headset with a sound processor configured to receive data formatted under a music interface protocol such as MIDI Instrument Digital Interface (MIDI) from a source such as a MIDI instrument (e.g., a MIDI keyboard, synthesizer, drum kit, etc.). Data can be generated as a result of a personal performance of the MIDI instrument. The source can transmit the MIDI data to the wireless headset via a wireless communication protocol (e.g., Bluetooth). The sound processor on the wireless headset converts the MIDI data into audio for output on the headset. Advantageously, this is done on the headset itself, rather than processing the MIDI data via the MIDI instrument for output on the headset, thus significantly reducing the latency between the playback of the personal MIDI instrument and the corresponding sound output on the wireless headset.

[0013] A further advantage is that the audio processing of MIDI data via the wireless headphones enables the wireless headphones to process and output MIDI data received from various sources and communication protocols. For example, in one embodiment, the wireless headphones can receive MIDI data (e.g., timestamped MIDI packet data) from a device via a network (such as the Internet) using a publish-subscribe messaging protocol. The wireless headphones can then process the audio data corresponding to the received MIDI data and output the audio data corresponding to the received MIDI data to the source device that sent the MIDI data relatively in real time via the network.

[0014] The following detailed description includes reference to the accompanying drawings. In the drawings, similar symbols generally identify similar parts unless the context otherwise requires. The exemplary embodiments described herein are not intended to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the scope of the subject matter set forth herein. It will be readily understood that aspects of this disclosure, as illustrated in the general description and drawings herein, can be arranged, substituted, combined, separated, and designed in a variety of different configurations, all of which are considered herein.

[0015] Figure 1 An embodiment of a wireless headset 100 is shown, which is configured to receive and process instrument protocol (e.g., MIDI protocol) data for audio output via the headset 100. Illustratively, the wireless headset 100 includes a headphone speaker 104 and a wireless transceiver unit 102.

[0016] In one embodiment, the headphone speaker 104 may represent a conventional binaural headphone speaker that an individual can wear on each ear. In another embodiment, each headphone speaker 104 may be implemented as an earbud-type headphone that an individual can insert into their ear. Furthermore, in some embodiments, the headphone speakers 104 may be physically connected to each other via straps, wires, or other materials. In other embodiments, each headphone speaker 104 may be physically separate from each other. Additionally, in some embodiments, one or both of the headphone speakers 104 may be physically connected to the wireless transceiver unit 102 via straps, wires, or other materials. In other embodiments, the wireless transceiver unit may be located on or within one of the headphone speakers 104.

[0017] In one embodiment, one headphone speaker 104 can be designated as the master speaker relative to the other headphone speaker 104. In this case, the other headphone speaker 104 is designated as the slave speaker. The headphone speaker 104 designated as the master device can receive digital audio data from a source (e.g., wireless transceiver unit 102) and transmit the digital audio data to the slave device, so that the two speakers 104 play the digital audio synchronously.

[0018] The illustrated wireless transceiver unit 102 can be implemented as any device or circuit (e.g., a microcontroller, processor, or other processing or control circuitry) capable of communicating with external devices (e.g., an electronic musical instrument configured with a MIDI protocol) via a wireless protocol (e.g., Bluetooth). For example, the wireless transceiver unit 102 can connect to a MIDI musical instrument (e.g., an electronic keyboard with wireless capabilities) using the Bluetooth protocol. If the MIDI instrument does not have built-in Bluetooth capability, a Bluetooth adapter can be attached to the MIDI instrument (e.g., at the instrument's MIDI port) to connect to and communicate with the wireless transceiver unit 102 via Bluetooth technology. Furthermore, the wireless transceiver unit 102 may include other wireless communication devices or circuitry for establishing communication over a network (e.g., the Internet). This allows the wireless transceiver unit 102 to receive data over a network, such as data received from a MIDI source instrument connected to the Internet or data received from a server that transmits MIDI data over the Internet. In other embodiments, the wireless headset 100 may include additional network communication components for establishing communication over a network.

[0019] Furthermore, as further described herein, the wireless transceiver unit 102 also includes sound processor circuitry to process the received data and transmit a reference audio output to be played through the headphone speaker 104. More specifically, the wireless transceiver unit 102 is configured to receive a raw data stream from a device (e.g., a MIDI instrument or a computing device streaming MIDI data), wherein the reference data stream includes MIDI data. The sound processor circuitry converts the data stream into MIDI data and reads the MIDI data to output corresponding audio from the headphone speaker 104. By using a wireless protocol such as Bluetooth to transmit MIDI data to the headphones for sound processing, the wireless headphones 100 can output audio with relatively lower latency compared to a scenario where MIDI data is processed at a MIDI instrument and transmitted to an external audio output device. The wireless transceiver unit 102 may also include network communication circuitry to connect the wireless headphones via a network (e.g., the Internet), enabling the wireless headphones to wirelessly receive MIDI data streams over the network.

[0020] Note that the wireless earphone 100 may also include Figure 1 Other components not shown. For example, the wireless headset 100 may include a display panel, such as one on the headset speaker 104 or the wireless transceiver unit 102, or a display panel as a separate physical component. The display panel may provide the user with information such as the remaining battery life of the wireless headset 100, whether the wireless headset 100 is connected to any device, and the type of device to which the wireless headset 100 is connected. Furthermore, the wireless headset 100 may also include buttons and corresponding circuitry for mapping each button to features of the wireless headset 100, such as on / off functions, pairing and connection functions, volume up / down functions, audio recording functions, and audio up / down functions.

[0021] Figure 2 An exemplary environment 200 in which a wireless headset 100 may operate is shown, including a description of components within the wireless headset 100. As shown, environment 200 includes a MIDI source device 202 and the wireless headset 100.

[0022] In one embodiment, the MIDI source device 202 can be implemented as any device or software (e.g., a virtual machine instance) capable of generating and / or transmitting MIDI data. For example, the MIDI source device 202 can be a desktop computer, an electronic musical instrument (e.g., a digital or acoustic keyboard, a synthesizer, a drum kit, etc.), etc. In one embodiment, the MIDI source device 202 may include a MIDI converter / transmitter 204, which can be implemented as any device or circuit for converting input data generated from the MIDI source device into data for wireless transmission and wirelessly transmitting the MIDI data over a network.

[0023] For example, MIDI source device 202 can generate MIDI data based on individual input (e.g., an individual pressing a key on a digital keyboard, an individual executing a playback command on MIDI player software running on MIDI source device 202, etc.). The generated MIDI data may include event messages, which include corresponding notes, clefs, pitches, tempos, vibrations, beats, rhythms, etc. When communicating with wireless headphones 100, MIDI converter / transmitter 204 can convert the MIDI data into data for wireless transmission (e.g., via Bluetooth protocol) and transmit the converted data to wireless headphones 100. Note that although... Figure 2 The MIDI converter / transmitter 204 is described as a single component, but in reality, the MIDI converter / transmitter 204 can be implemented as different components, such as a separate MIDI converter circuit and a wireless transmitter circuit.

[0024] As described above, the MIDI source device 202 can also be a computing device. The computing device can stream MIDI data over a network (e.g., the Internet) to multiple wireless headsets on the network. This allows multiple headsets to play back MIDI data from a single source relatively simultaneously. For example, the computing device can establish communication with the wireless headset (e.g., its wireless transceiver unit 102) via a message broker (e.g., the Mosquitto MQTT broker) using a publish-subscribe protocol (e.g., the Message Queuing Telemetry Transport (MQTT) protocol). The MIDI source device 202 can send MIDI data via a TCP / IP protocol client port using publish-subscribe technology. The MIDI source device 202 can also send or receive MIDI data via a web client through a broker. MIDI data sent over the network can include timestamped MIDI packet data. The wireless transceiver unit 102 of the wireless headset 100 can subscribe to MQTT topics associated with the MIDI data. Once subscribed, the wireless headset 100 receives packets (e.g., via the wireless transceiver unit 102), processes the packets, and plays back the MIDI data.

[0025] As shown in the figure, the wireless headset 100 also includes a wireless receiver 206, a signal processor 207, an amplifier 208, an audio output 210, and a MIDI sound processing logic unit 212. In one embodiment, the wireless receiver 206 may be implemented within the wireless headset 100 (e.g., within the wireless transceiver 102), and the wireless receiver 206 may be configured to receive wireless transmissions from an external device (e.g., a MIDI source device 202). For example, the wireless receiver 206 may receive wireless transmissions of input data converted from MIDI data from a MIDI converter / transmitter 204. The signal processor 207 may be implemented as any device or circuit that evaluates the data received at the wireless receiver 206 (e.g., determines whether the received data includes any MIDI data). If so, the signal processor 207 may transmit data for processing by the MIDI sound processing logic unit 212.

[0026] The MIDI audio processing logic unit 212 can be implemented as any device, software, firmware, or circuitry configured to convert wireless transmissions received from the MIDI source device 202 into MIDI data to be output as audio to the wireless headset 100 (e.g., via the headset speaker 104). For example, in one embodiment, the MIDI audio processing logic unit 212 includes wireless MIDI to serial MIDI logic 214, serial MIDI to sound engine logic 216, sound engine to audio output logic 218, audio output to amplifier logic 220, and amplifier to speaker logic 222. In one embodiment, the MIDI audio processing logic unit 212 may also include circuitry or logic for synchronizing MIDI data to digital audio. Each component can be implemented as any combination of devices, firmware, software, or circuitry within the MIDI audio processing logic unit 212. Although each of these components is described as independent of each other and within the MIDI audio processing logic unit 212, those skilled in the art will recognize that each of these components can be implemented in various configurations within the wireless headset 100. For example, some components may be combined into circuitry such as audio output to amplifier logic 220 and amplifier to speaker logic 222.

[0027] Wireless MIDI to Serial MIDI logic 214 is configured to evaluate wireless MIDI data processed by signal processor 207. Furthermore, wireless MIDI to Serial MIDI logic 214 is configured to convert the wireless MIDI data into serial MIDI data, which can be read by a sound engine (not shown) in the wireless headset 100 for playback. Serial MIDI to Sound Engine logic 216 converts the serial MIDI data into data readable by the sound engine, so that event messages in the MIDI data can be interpreted by the sound engine. Sound Engine to Audio Output logic 218 processes the MIDI data to generate a given sound (e.g., determining which channels play the sound, the volume of the sound, the speed of the sound, etc.) on the audio output unit 210 of the wireless headset 100. In this embodiment, sound engine to audio output logic 218 is configured to send the sound (and other audio outputs) to amplifier 220. In doing so, audio output to amplifier logic 220 can send audio output from audio output 210 to amplifier 208. Amplifier to Speaker logic 222 can convert the audio for output on the respective headphone speakers 104.

[0028] Now for reference Figure 3 This describes a method 300 for operating a wireless headset 100. As shown, method 300 begins in block 302, where the wireless headset 100 receives a request to connect to a MIDI source device (e.g., MIDI source device 202) using a wireless protocol. For example, a user of the wireless headset 100 can initiate a Bluetooth connection and pairing sequence with an electronic keyboard configured with the MIDI protocol (e.g., by pressing a button on the wireless headset 100). The wireless headset 100 can initiate the connection based on the request via logic running therein. In block 304, the wireless headset 100 determines whether the request is valid. For example, the wireless headset 100 can determine whether a Bluetooth-enabled device is within network range and further determine whether the device is a MIDI-enabled device. If the request is invalid, in block 306, the wireless headset 100 can return an error (e.g., outputting an audio message indicating a failed connection via the headset speaker 104).

[0029] However, if the request is valid and the wireless headset 100 detects a compatible MIDI source device, then in box 308, the wireless headset 100 can initiate a connection to the MIDI source device using a wireless protocol (e.g., Bluetooth) technology. In box 310, the wireless headset 100 determines whether the connection was successful. If unsuccessful, then in box 312, the wireless headset 312 can return an error (e.g., outputting an audio message indicating that the connection was unsuccessful via the headset speaker 104).

[0030] Of course, blocks 302 through 312 can be applied to wireless connections to a network (such as the Internet). For example, wireless headset 100 can connect to the Internet, for example, via a wireless access point (e.g., a network router), and initiate the processes described in the above blocks using a source device also connected to the Internet. In one embodiment, the source device can communicate with wireless headset 100 using a publish-subscribe protocol (e.g., MQTT). The device can create an MQTT topic for MIDI data, and wireless headset 100 can subscribe to that topic. The source device can send MIDI data packets that include timestamps. The timestamps can be generated based on a monotonic clock rounded to a given unit (e.g., the nearest microsecond). Wireless headset 100 can record a different monotonic clock than headset 100.

[0031] While connected, the wireless headset 100 can process MIDI data for playback (e.g., in near real-time with minimal latency). For example, if the connected MIDI source device is a keyboard, an individual can press a key on it. In response, the MIDI source device can generate MIDI data and wirelessly transmit the MIDI data as a raw data stream to the wireless headset 100 via the connection. MIDI data can also be simultaneously transmitted by the MIDI source device to other connected devices, such as portable devices that capture MIDI data and automatically upload it to a cloud operator's network.

[0032] In box 314, the wireless headset 100 receives a data stream from a MIDI source device via a wireless connection. In box 316, the wireless headset 100 converts the raw data stream into MIDI data via a MIDI sound processor logic unit therein. Once converted, in box 318, the wireless headset 100 outputs the corresponding audio from the MIDI data via the headset speaker 104. When the wireless headset 100 is connected to the source device via a network, when the wireless headset 100 receives packets of the MIDI data stream, the wireless headset 100 can compare its own monotonic clock with the timestamp in the received packets. The wireless headset 100 can use the determined difference to construct a playback buffer array, for example, by converting the remote playback time to local time and adding a specified delay. The wireless headset 100 can use a timer ring with the buffer array to control playback. Furthermore, if the wireless headset 100 receives MIDI data corresponding to a note that is received too late to play, it can remove it from the queue. Thereafter, the wireless headset 100 can refresh the playback queue using the next reference note received as the new timing reference note. The difference between the remote and local monotonic clocks is recorded for each note. Furthermore, notes with delays significantly different from this difference can increment the counter. After exceeding a specified threshold, the wireless headset 100 can move the delay at specified time intervals (e.g., a 1-millisecond interval) until multiple notes are within the specified difference range.

[0033] Numerous specific details, examples, and scenarios have been set forth in the foregoing description to provide a more thorough understanding of this disclosure. However, it should be understood that embodiments of this disclosure can be practiced without these specific details. Furthermore, such examples and scenarios are provided for illustrative purposes only and are not intended to limit this disclosure in any way. Those skilled in the art should be able to implement appropriate functionality without excessive experimentation based on the included description.

[0034] References to "embodiments" and similar terms in the specification indicate that the described embodiments may include specific features, structures, or characteristics. Such phrases do not necessarily refer to the same embodiment. Furthermore, when a specific feature, structure, or characteristic is described in connection with an embodiment, it is believed that, to the knowledge of those skilled in the art, such feature, structure, or characteristic can be implemented in conjunction with other embodiments, whether or not explicitly stated.

[0035] Embodiments of this disclosure can be implemented using hardware, firmware, software, or any combination thereof. Embodiments can also be implemented as instructions stored using one or more machine-readable media, which can be read and executed by one or more processors. Machine-readable media can include any suitable form of volatile or non-volatile memory.

[0036] For ease of discussion, the modules, data structures, etc., defined in this article are defined in this way, but this is not intended to imply any specific implementation details are required. For example, any of the described modules and / or data structures may be combined or divided into sub-modules, sub-processes, or other units of computer code or data as required by the specific design or implementation of the computing device.

[0037] In the accompanying drawings, a specific arrangement or order of elements may be shown for ease of description. However, such a specific order or arrangement of elements is not intended to imply that a particular processing order or sequence, or separation of processes, is required in all embodiments. Generally, illustrative elements representing instruction blocks or modules can be implemented using any suitable form of machine-readable instructions, and each such instruction can be implemented using any suitable programming language, library, application programming interface (API), and / or other software development tools or frameworks. Similarly, illustrative elements representing data or information can be implemented using any suitable electronic device or data structure. Furthermore, some connections, relationships, or associations between elements may be simplified or not shown in the drawings to avoid obscuring this disclosure.

[0038] This disclosure is intended to be exemplary and not restrictive. All variations and modifications within the spirit of this disclosure are intended to be protected. Although specific aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art in light of the foregoing teachings.

[0039] Additional examples of wireless headphones and their operating techniques are provided in the attached appendix.

[0040] While the foregoing describes embodiments of the present invention, other and further embodiments of the present invention may be designed without departing from the basic scope of the present invention, and the scope of the present invention is defined by the appended claims.

Claims

1. A wireless earphone device, comprising: First headphone speaker and second headphone speaker; Monotonic clock; A wireless transceiver unit including a sound processing logic unit, wherein the wireless transceiver is used for: A data stream is received via a wireless connection to a source device, the data stream comprising one or more network packets, each packet containing a timestamp and an event message, wherein the data stream is associated with a wireless music interface protocol, and wherein the event message comprises at least one note; For each network packet, the monotonic clock is compared with the timestamp; The sound processing logic unit converts the data stream into a data stream associated with the music interface protocol, wherein the conversion includes constructing a playback buffer array based on a comparison between the monotonic clock and the timestamp of each network data packet; and The sound processing logic unit outputs the audio corresponding to the converted data stream to the first headphone speaker and the second headphone speaker according to the playback buffer array.

2. The wireless earphone device according to claim 1, wherein, The data streams associated with the music interface protocol include data streams associated with the Musical Instrument Digital Interface (MIDI) protocol.

3. The wireless earphone device according to claim 1, wherein, The wireless connection includes a Bluetooth connection.

4. The wireless earphone device according to claim 1, wherein, The wireless connection includes an Internet connection.

5. The wireless earphone device according to claim 4, wherein, The wireless earphone device communicates with the source device using a publish-subscribe protocol via the Internet connection.

6. The wireless earphone device according to claim 5, wherein, The wireless earphone device communicates with the source device via the Internet connection using the Message Queuing Telemetry Transmission (MQTT) protocol.

7. The wireless earphone device according to claim 1, wherein, It also includes multiple buttons and corresponding circuitry mapped to one or more functions of the wireless headset device.

8. A method performed by a wireless headset, comprising: A data stream is received by a wireless headset via a wireless connection to a source device. The data stream includes one or more network packets, each packet containing a timestamp and an event message. The wireless headset includes a first headphone speaker and a second headphone speaker. The data stream is associated with a wireless music interface protocol. The event message includes at least one musical note. For each network packet, the monotonic clock is compared with the timestamp; The wireless headphones convert the data stream into a data stream associated with a music interface protocol, wherein the conversion includes constructing a playback buffer array based on a comparison of the monotonic clock and the timestamp for each network data packet; and The wireless earphones output audio corresponding to the converted data stream to the first earphone speaker and the second earphone speaker according to the playback buffer array.

9. The method according to claim 8, wherein, The data streams associated with the music interface protocol include data streams associated with the Musical Instrument Digital Interface (MIDI) protocol.

10. The method according to claim 8, wherein, The wireless connection includes a Bluetooth connection.

11. The method according to claim 8, wherein, The wireless connection includes an Internet connection.

12. The method according to claim 11, wherein, The source device is connected to the wireless earphone via a publish-subscribe protocol.

13. The method according to claim 12, wherein, The source device is connected to the wireless headset via the Message Queuing Telemetry Transmission (MQTT) protocol.

14. The method according to claim 8, wherein, The wireless headset also includes multiple buttons and corresponding circuitry mapped to one or more functions of the wireless headset.

15. A wireless earphone device, comprising: A means for receiving a data stream via a wireless connection to a source device, the data stream comprising one or more network packets, each packet containing a timestamp and an event message, wherein the data stream is associated with a wireless music interface protocol, and wherein the event message comprises at least one note; A means for comparing a monotonic clock with the timestamp for each network packet; A means for converting the data stream into a data stream associated with a music interface protocol, wherein the means for the conversion includes means for constructing a playback buffer array based on a comparison of the monotonic clock and the timestamp for each network data packet; and A means for outputting audio corresponding to the converted data stream to a first headphone speaker and a second headphone speaker according to the playback buffer array.

16. The wireless earphone device according to claim 15, wherein, The data streams associated with the music interface protocol include data streams associated with the Musical Instrument Digital Interface (MIDI) protocol.

17. The wireless earphone device according to claim 15, wherein, The wireless connection includes a Bluetooth connection.

18. The wireless earphone device according to claim 15, wherein, The wireless connection includes an Internet connection.

19. The wireless earphone device according to claim 18, wherein, The source device is connected to the wireless headset device via the Message Queuing Telemetry Transmission (MQTT) protocol.

20. The wireless earphone device according to claim 15, wherein, It also includes multiple buttons and corresponding circuitry mapped to one or more functions of the wireless headset device.