Wireless MIDI Headset

The wireless headset with a MIDI sound processor addresses MIDI audio delay issues by processing data in real time, improving performance timing.

JP7736679B2Active Publication Date: 2025-09-09QRS MUSIC TECH
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2022523664
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-10-23
Filing Date
2020-10-22
Publication Date
2025-09-09
Estimated Expiration
2040-10-22

AI Technical Summary

Technical Problem

Existing wireless headsets for MIDI instruments suffer from delays in audio output due to the use of Bluetooth or RF transmitters, affecting performance timing.

Method used

A wireless headset with an integrated MIDI sound processor that processes MIDI data in real time, reducing delay by converting and outputting audio directly on the headset via Bluetooth or network connections.

Benefits of technology

Significantly reduces the delay between playing a MIDI instrument and hearing the corresponding audio output, enhancing performance experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007736679000001
    Figure 0007736679000001
  • Figure 0007736679000002
    Figure 0007736679000002
  • Figure 0007736679000003
    Figure 0007736679000003
Patent Text Reader

Abstract

Described herein is a wireless headset configured to process a music interface protocol (e.g., a MIDI protocol) received wirelessly by a source device (e.g., via a Bluetooth connection or an Internet connection). The wireless headset includes first and second headset speakers and a wireless transceiver unit for receiving a stream of data over the wireless connection. The wireless transceiver unit includes a sound processing logic unit that converts the stream of data into a stream of data associated with the music interface protocol and outputs audio corresponding to the converted stream of data to the first and second headset speakers.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to a headset device that receives Musical Instrument Digital Interface (MIDI) data and / or audio over a wireless protocol for audio output. [Background technology]

[0002] Many electronic musical instruments, such as keyboards, synthesizers, and drum machines, implement the MIDI standard. When an individual plays a MIDI instrument, the instrument (e.g., via the instrument's MIDI controller) converts the individual's actions into MIDI data. More specifically, the instrument generates MIDI data that specifies musical instructions (e.g., musical notation, pitch, vibrato, and other characteristics).

[0003] A device such as a sound module or sequencer configured within or external to the MIDI instrument can then interpret the MIDI data to play sounds representing the individual's instrumental performance. Summary of the Invention [Problem to be solved by the invention]

[0004] Typically, MIDI instruments can be configured to output audio to an analog headset device (or speakers connected to the MIDI instrument) connected to the MIDI instrument via a cable or a combination of a radio frequency (RF) transmitter and receiver. Individuals may desire to wear a wireless headset while practicing a MIDI instrument for various reasons (e.g., to practice quietly from others). However, wireless headsets generally have several drawbacks. One such drawback is the cost and inconvenience of using an RF transmitter and receiver pair. In such cases, if a wireless protocol such as Bluetooth® is used, the wireless headset may introduce a delay between playing an instrument, such as pressing a key, and transmitting the corresponding MIDI data to the headset for audio output to the headset's speakers. As a result, an individual may hear a given output relatively later than when the corresponding key was pressed, which may affect the overall experience for the individual playing the MIDI instrument. For example, a relatively large delay may affect the time at which an individual hears the corresponding output from the MIDI instrument, thereby affecting aspects of performance such as timing. [Means for solving the problem]

[0005] One embodiment presented herein discloses a wireless headset configured with a MIDI sound processor for outputting MIDI data in relatively real time. The wireless headset device includes first and second headset speakers. The wireless headset device also includes a wireless transceiver unit having a sound processing logic unit. The wireless transceiver receives a stream of data via a wireless connection with a source device. The wireless transceiver is also for converting, by the sound processing logic unit, the stream of data into a stream of data associated with a music interface protocol. The wireless transceiver is also for outputting, by the sound processing logic unit, audio corresponding to the converted stream of data to the first and second headset speakers.

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

[0007] Yet another embodiment presented herein discloses a wireless headset having means for receiving a stream of data via a wireless connection with a source device. The wireless headset further includes means for converting the stream of data into a stream of data associated with a music interface protocol. The wireless headset also includes means for outputting audio corresponding to the converted stream of data to first and second headset speakers. [Brief explanation of the drawings]

[0008] [Figure 1] 1 illustrates a perspective view of at least one embodiment of an exemplary wireless headset configured with a MIDI sound engine to output MIDI data in relatively real time. [Figure 2] 2 illustrates at least one embodiment of an exemplary performance environment in which the wireless headset of FIG. 1 can operate. [Figure 3] 2 illustrates a flow diagram of at least one embodiment of a method for operating the wireless headset of FIG. 1. DETAILED DESCRIPTION OF THE INVENTION

[0009] The embodiments presented herein disclose a wireless headset having a sound processor configured to receive data formatted under a music interface protocol, such as MIDI (Music Instrument Digital Interface), from a source, for example, a MIDI instrument (e.g., a MIDI keyboard, synthesizer, drum kit, etc.). The data may be generated as a result of an individual playing the MIDI instrument. The source may transmit the MIDI data to the wireless headset via a wireless communication protocol, such as the Bluetooth protocol. The sound processor of the wireless headset converts the MIDI data into audio for output on the headset. Advantageously, by processing the MIDI data on the headset rather than through the MIDI instrument for output on the headset, the delay between an individual playing the MIDI instrument and the corresponding sound being output on the wireless headset is significantly reduced.

[0010] Further advantageously, sound processing of MIDI data via a wireless headset enables the wireless headset to process and output MIDI data received from a variety of sources and communication protocols. For example, in one embodiment, the wireless headset can receive MIDI data (e.g., time-stamped MIDI packet data) from a device over a network, such as the Internet, using a publish-subscribe messaging protocol. The wireless headset can then process audio data corresponding to the received MIDI data in relatively real time and output it to the source device transmitting the MIDI data over the network.

[0011] The following detailed description includes references to the accompanying drawings. In the drawings, like numerals generally identify like components unless context dictates otherwise. The exemplary embodiments described herein are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are contemplated herein.

[0012] 1 illustrates one embodiment of a wireless headset 100 configured to receive musical instrument protocol (e.g., MIDI protocol) data and process the data for audio output via the headset 100. Illustratively, the wireless headset 100 includes a headset speaker 104 and a wireless transceiver unit 102.

[0013] In one embodiment, the headset speakers 104 may represent traditional headphone speakers that an individual may wear in each ear. In another embodiment, each headset speaker 104 may be embodied as an earbud that an individual may insert into their ear. Furthermore, in some embodiments, the headset speakers 104 may be physically connected to one another via a band, wire, or other material. In other embodiments, each headset speaker 104 may be physically separate from one another. Also, in some embodiments, one or both of the headset speakers 104 may be physically connected to the wireless transceiver unit 104 via a band, wire, or other material. In other embodiments, the wireless transceiver unit may be located on or within one of the headset speakers 104.

[0014] In one embodiment, one of the headset speakers 104 can be designated as a master speaker relative to the other headset speaker 104. In such a case, the other headset speaker 104 is designated as a slave speaker. The headset speaker 104 designated as master can receive digital audio data from a source (e.g., the wireless transceiver unit 102) and transmit the digital audio data to the slave device such that both speakers 104 play the digital audio in sync.

[0015] The exemplary wireless transceiver unit 102 may be embodied as any device or circuit (e.g., a microcontroller, processor, or other processing or control circuit) capable of communicating with an external device (e.g., an electronic musical instrument configured with the MIDI protocol) via a wireless protocol, such as the Bluetooth wireless protocol. For example, the wireless transceiver unit 102 may use the Bluetooth protocol to connect to a MIDI instrument, such as an electronic keyboard, configured with wireless capabilities. If the MIDI instrument does not have built-in Bluetooth functionality, a Bluetooth adapter may be attached to the MIDI instrument (e.g., at the instrument's MIDI port) to connect and communicate with the wireless transceiver unit 102 via Bluetooth technology. The wireless transceiver unit 102 may also include other wireless communication devices or circuitry used to establish communications over a network, such as the Internet. Doing so enables the wireless transceiver unit 102 to receive data over the network, such as from an Internet-connected MIDI source device or a server transmitting MIDI data over the Internet. In other embodiments, the wireless headset 100 may include additional network communication components for establishing and communicating over a network.

[0016] As further described herein, the wireless transceiver unit 102 also includes sound processor circuitry for processing received data and transmitting an underlying audio output that is played through the headset speakers 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), where the underlying data stream includes MIDI data. The sound processor circuit converts the data stream into MIDI data, reads the MIDI data, and outputs corresponding audio from the headset speakers 104. By transmitting the MIDI data to the headset for sound processing using a wireless protocol such as the Bluetooth protocol, the wireless headset 100 can output audio with relatively less delay than if the MIDI data were processed by a MIDI instrument and sent to an external audio output device. The wireless transceiver unit 102 also includes network communications circuitry for connecting the wireless headset over a network, such as the Internet, to enable the wireless headset to receive the MIDI data stream wirelessly over the network.

[0017] It should be noted that wireless headset 100 may also include other components not shown in FIG. 1 . For example, wireless headset 100 may include a display panel, such as on headset speaker 104, one of wireless transceiver units 102, or as a separate physical component. The display panel may provide a user with information such as the remaining battery life of wireless headset 100, whether wireless headset 100 is connected to a device, and the type of device to which wireless headset 100 is connected. Additionally, wireless headset 100 may also include buttons and corresponding circuitry that map to functions of wireless headset 100, such as an on / off function, a pairing and connection function, a volume up / down function, an audio recording function, an audio upload function, etc.

[0018] 2 illustrates an exemplary environment 200 in which wireless headset 100 may operate, including a description of the components within wireless headset 100. As shown, environment 200 includes a MIMD source device 202 and wireless headset 100.

[0019] In one embodiment, MIDI source device 202 may be embodied as any device or software (e.g., a virtual machine instance) capable of generating and / or transmitting MIDI data. For example, MIDI source device 202 may 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, MIDI source device 202 may include a MIDI converter / transmitter 204, which may be embodied as any device or circuitry used to convert input data generated from the MIDI source device into data for wireless transmission and transmit the MIDI data wirelessly over a network.

[0020] For example, MIDI source device 202 can generate MIDI data from input by an individual (e.g., the individual pressing keys on a digital keyboard, the individual executing a play command on MIDI player software running on MIDI source device 202, etc.). The generated MIDI data can include event messages including corresponding notes, notations, pitch, velocity, vibrato, pan, tempo, etc. In communication with wireless headset 100, MIDI converter / transmitter 204 can convert this MIDI data to data for wireless transmission (e.g., via the Bluetooth protocol) and transmit the converted data to wireless headset 100. It should be noted that while FIG. 2 depicts MIDI converter / transmitter 204 as a single component, in practice MIDI converter / transmitter 204 can be embodied as separate components, such as separate MIDI converter circuitry and wireless transmitter circuitry.

[0021] As mentioned, the MIDI source device 202 can also be a computing device. The computing device may be capable of streaming MIDI data over a network (e.g., the Internet) to multiple wireless headsets over the network. This allows multiple headsets to play MIDI data relatively simultaneously from a single source. For example, to do so, the computing device can establish communication with the wireless headsets (e.g., its wireless transceiver unit 102) using a publish-subscribe protocol such as the Message Queuing Telemetry Transport (MQTT) protocol via a message broker such as Mosquitto's MQTT broker. The MIDI source device 202 can send MIDI data over a TCP / IP protocol client port using the publish-subscribe technique. The MIDI source device 202 can also send or receive MIDI data using a web client via the broker. The MIDI data transmitted over the network can include time-stamped MIDI packet data. The wireless transceiver unit 102 of the wireless headset 100 can subscribe to an MQTT topic related to the MIDI data. Once subscribed, wireless headset 100 receives the packets (eg, via wireless transceiver unit 102), processes the packets, and plays the MIDI data.

[0022] As shown, wireless headset 100 further includes a wireless receiver 206, a signal processor 205, an amplifier 208, an audio output 210, and a MIDI sound processing logic unit 212. In one embodiment, wireless receiver 206 may be embodied as some device or circuitry within wireless headset 100 (e.g., within wireless transceiver 102) configured to receive wireless transmissions from an external device, such as MIDI source device 202. For example, wireless receiver 206 may receive a wireless transmission of input data converted from MIDI data from MIDI converter / transmitter 204. Signal processor 207 may be embodied as some device or circuitry to evaluate data received at wireless receiver 206, for example, to determine whether the received data includes any MIDI data. If so, signal processor 207 may transmit the data for processing by MIDI sound processing logic unit 212.

[0023] MIDI sound processing logic unit 212 may be embodied as any device, software, firmware, or circuitry configured to convert wireless transmissions received from MIDI source device 202 for output as audio to wireless headset 100 (e.g., via headset speaker 104). For example, in one embodiment, MIDI sound 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, MIDI sound processing logic unit 212 may also include circuitry or logic for synchronizing MIDI data with digital audio. Each component may be embodied as any combination of devices, firmware, software, or circuits within MIDI sound processing logic unit 212. While each of these components is depicted separately within MIDI sound processing logic unit 212, those skilled in the art will recognize that each of the components may be embodied within wireless headset 100 in various configurations. For example, some components may be combined into one circuit (eg, audio output to amplifier logic 220 and amplifier to speaker logic 222).

[0024] Wireless MIDI-to-serial MIDI logic 214 is configured to evaluate the 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 that can be read for playback by a sound engine within wireless headset 100 (not shown). Serial MIDI-to-sound engine logic 216 converts the serial MIDI data into data readable by the sound engine, allowing event messages within the MIDI data to be interpreted by the sound engine. Sound engine-to-audio output logic 218 processes the MIDI data (e.g., determines the channel on which to play the sound, the volume of the sound, the velocity of the sound, etc.) to generate a given sound on audio output unit 210 of wireless headset 100, which, in one embodiment, is configured to send the sound (and other audio output) to amplifier 220. To do so, audio output-to-amplifier logic 220 can send audio output from audio output 210 to amplifier 208. The amplifier to speaker logic 222 can convert the audio for output on each of the headset speakers 104 .

[0025] Referring now to FIG. 3 , a method 300 for operating a wireless headset 100 will now be described. As shown, method 300 begins at block 302, in which wireless headset 100 receives a request to connect with a MIDI source device (e.g., MIDI source device 202) using a wireless protocol. For example, a user of wireless headset 100 may initiate a Bluetooth connection and pairing sequence with an electronic keyboard configured with the MIDI protocol, for example, via pressing a button on wireless headset 100. Wireless headset 100 may initiate the connection based on the request via logic executing internally. At block 304, wireless headset 100 determines whether the request is valid. For example, wireless headset 100 may determine whether a Bluetooth-enabled device is within network range and further determine whether the device is a device that supports the MIDI protocol. If the request is not valid, at block 306, wireless headset 100 may return an error (e.g., an audio message indicating that the connection was not successfully output through headset speaker 104).

[0026] However, if the request is valid and wireless headset 100 detects a compatible MIDI source device, wireless headset 100 may initiate a connection with the MIDI source device using a wireless protocol (e.g., Bluetooth) technology in block 308. Wireless headset 100 may determine whether the connection was successful in block 310. If not, wireless headset 312 may return an error (e.g., an audio message indicating that the connection was not successfully output through headset speaker 104) in block 312.

[0027] Of course, blocks 302-312 can be adapted for wireless connections to a network such as the Internet. For example, wireless headset 100 can connect to the Internet via a wireless access point (e.g., a network router) and initiate the flow of the aforementioned blocks with 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 such as MQTT. The device can establish an MQTT topic for MIDI data, and wireless headset 100 subscribes to the topic. The source device can send MIDI data packets that include a timestamp within them. The timestamp can be generated based on a monotonic clock rounded to the nearest microsecond. Wireless headset 100 can record a monotonic clock that is different from headset 100.

[0028] While connected, wireless headset 100 can process MIDI data for playback, for example, in relatively real time with minimal delay. For example, if the connected MIDI source device is an electronic keyboard, an individual can press a key on the electronic keyboard. In response, the MIDI source device can generate MIDI data and transmit it wirelessly over the connection to wireless headset 100 as a raw stream of data. MIDI data can also be simultaneously transmitted by the MIDI source device to other connected devices, such as a portable device that captures the MIDI data and automatically uploads the data to a cloud provider network.

[0029] In block 314, the wireless headset 100 receives a stream of data from a MIDI source device via a wireless connection. In block 316, the wireless headset 100 converts the raw data stream into MIDI data via its internal MIDI sound processing logic unit. Once converted, in block 318, the wireless headset 100 outputs the corresponding audio from the MIDI data via the headset speaker 104. If the wireless headset 100 is connected to a source device via a network, when the wireless headset 100 receives packets of the MIDI data stream, the wireless headset 100 can compare its monotonic clock with the timestamps in the received packets. The wireless headset 100 can build a playback buffer array with a determined difference, for example, by converting the remote playback time to local time and adding a specific delay. The wireless headset 100 can control playback using a timer loop with the buffer array. Furthermore, if the wireless headset 100 receives MIDI data corresponding to a received note too late to play it, it can remove it from the queue. The wireless headset 100 can then refresh the playback queue using the next received underlying note as the new timing-based note. The difference between the remote and local monotonic clocks is recorded for each note. Additionally, notes with delays that significantly deviate from the difference may increment a counter. After a specified threshold is exceeded, the wireless headset 100 can shift the delay at specified intervals (e.g., 1-millisecond intervals) until several notes fall within the specified difference.

[0030] In the foregoing description, numerous specific details, examples, and scenarios are set forth to provide a more complete understanding of the present disclosure. However, it will be understood that embodiments of the present disclosure can be practiced without such specific details. Furthermore, such examples and scenarios are provided for illustrative purposes only and are not intended to limit the disclosure in any way. Those skilled in the art should be able, with the included description, to implement the appropriate functionality without undue experimentation.

[0031] References herein to "one embodiment," etc., indicate that the described embodiment may include a particular configuration, structure, or characteristic. Such phrases do not necessarily refer to the same embodiment. Furthermore, if a particular configuration, structure, or characteristic is described in connection with one embodiment, achieving such configuration, structure, or characteristic in connection with other embodiments, whether or not explicitly shown, is believed to be within the knowledge of one skilled in the art.

[0032] Embodiments of the present disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments may also be implemented as instructions stored using one or more machine-readable media that may be read and executed by one or more processors. The machine-readable media may include any suitable form of volatile or non-volatile memory.

[0033] Modules, data structures, etc. defined herein are so defined for ease of discussion and are not intended to imply that 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 may be required by a particular design or implementation of a computing device.

[0034] The figures may show a particular arrangement or order of elements for ease of explanation. However, such a particular order or arrangement of elements does not imply that a particular order or sequence of processing or separation of processes is required in all embodiments. In general, schematic elements used to represent instruction blocks or modules can be implemented using machine-readable instructions in any suitable format, and each such instruction can be implemented using any suitable programming language, library, application programming interface (API), and / or other software development tool or framework. Similarly, schematic elements used to represent data or information can be implemented using any suitable electronic arrangement or data structure. Additionally, some connections, relationships, or associations between elements may be simplified or not shown in the figures so as not to obscure the present disclosure.

[0035] This disclosure is considered to be illustrative, not restrictive. All changes and modifications that are within the nature and spirit of this disclosure are desired to be protected. While certain aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art in view of the foregoing teachings.

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

[0037] While the forgoing is directed to embodiments of the present disclosure, other and further embodiments of the present disclosure may be devised without departing from the basic scope thereof, which scope is determined by the following claims.

Claims

1. first and second headset speakers; A monotonous clock, a wireless transceiver unit including a sound processing logic unit; 1. A wireless headset device comprising: The wireless transceiver unit receiving a stream of data via a wireless connection with a source device, the stream of data including one or more network packets, each packet including a timestamp and an event message, the stream of data being associated with a wireless music interface protocol, the event message including at least musical notes; comparing the monotonic clock to the timestamp for each network packet; converting, by the sound processing logic unit, the stream of data into a stream of data associated with a serial music interface protocol, the conversion including constructing a playout buffer array based on a comparison of the monotonic clock and the timestamp for each network packet; outputting audio corresponding to the converted stream of data to the first and second headset speakers by the sound processing logic unit and in accordance with the playback buffer array; It is intended for wireless headset devices.

2. The wireless headset device of claim 1 , wherein the stream of data associated with a music interface protocol includes a stream of data associated with a MIDI protocol.

3. The wireless headset device of claim 1 , wherein the wireless connection comprises a Bluetooth connection.

4. The wireless headset device of claim 1 , wherein the wireless connection includes an Internet connection.

5. The wireless headset device of claim 4 , wherein the wireless headset device communicates with the source device over the Internet connection using a publish-subscribe protocol.

6. 6. The wireless headset device of claim 5, wherein the wireless headset device communicates with the source device over an internet connection using the MQTT protocol.

7. A wireless headset device as described in claim 1, further comprising a plurality of buttons and respective circuits that map to one or more functions thereof.

8. receiving a stream of data by a wireless headset via a wireless connection with a source device, the wireless headset comprising a wireless headset device as recited in claim 1; converting, by the wireless headset, the stream of data to a stream of data associated with a music interface protocol; outputting, by the wireless headset, audio corresponding to the converted stream of data to the first and second headset speakers; A method comprising:

9. The method of claim 8 , wherein the stream of data associated with a music interface protocol comprises a stream of data associated with a MIDI protocol.

10. The method of claim 8 , wherein the wireless connection comprises a Bluetooth connection.

11. The method of claim 8 , wherein the wireless connection comprises an Internet connection.

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

13. The method of claim 12 , wherein the source device is connected to the wireless headset via an MQTT protocol.

14. The method of claim 8, further comprising a plurality of buttons and respective circuits that map to one or more functions thereof.

Citation Information

Patent Citations

  • Signal output device

    JP2014182277A

  • Musical performance information output control device, keyboard instrument, and control method

    JP2016008974A

  • Program, communication method, and server

    JP2017111614A