Musical Instrument Digital Interface

Description

Within 3GPP, Musical Instrument Digital Interface (MIDI) refers to the adaptation and transport of the industry-standard MIDI protocol over mobile networks for multimedia services. Unlike audio codecs that encode sound waves, MIDI transmits instructions—a series of messages that describe a musical performance, such as 'note on' (which note, on which channel, with what velocity), 'note off', pitch bend, control change (modulation, volume), and program change (selecting an instrument sound). These messages are consumed by a synthesizer or sound engine at the receiving end to generate audio. 3GPP has standardized specific profiles and codecs for MIDI content to ensure interoperability across devices and networks. Key specifications like 3GPP TS 26.114 define the MIDI media type for use in the Packet-switched Streaming Service (PSS) and Multimedia Messaging Service (MMS). The transport involves encapsulating the MIDI command stream within a structured audio format, often using the General MIDI (GM) or Scalable Polyphony MIDI (SP-MIDI) standards to ensure consistent playback across different device capabilities. SP-MIDI, for instance, allows content creators to specify how a complex MIDI sequence should be adapted (e.g., which notes to drop) when played on a device with limited polyphony (fewer simultaneous notes). For streaming, MIDI data is packetized within an RTP payload format (defined in IETF RFCs and referenced by 3GPP) and sent over the network. The receiving client's media player includes a MIDI renderer (software synthesizer) that interprets these packets and generates the corresponding audio in real-time. This architecture allows for highly efficient transmission of musical content, as a minutes-long, multi-instrument piece can be represented in a few kilobytes of MIDI data, compared to megabytes for equivalent PCM audio.

Purpose & Motivation

3GPP standardized MIDI transport to enable rich, interactive audio services on early 2.5G and 3G mobile networks, where bandwidth was severely limited and expensive. Sending high-quality polyphonic ringtones, game soundtracks, or interactive music applications as compressed PCM or MP3 audio was often impractical. MIDI provided a perfect solution: it offered high musical fidelity (dependent on the device's synthesizer quality) with extremely low data throughput, making it ideal for downloadable ringtones, music messaging, and streaming background music for games. It addressed the need for a scalable, device-adaptive audio format. The creation of profiles like SP-MIDI specifically solved the problem of device fragmentation—a single MIDI file could sound acceptable on both a high-end phone with a 64-voice synthesizer and a basic model with only 4-voice polyphony. This drove the commercial success of polyphonic ringtones. Furthermore, MIDI's event-based nature allowed for interactive control, enabling applications like real-time music tutoring or remote instrument control, which would be impossible with pre-rendered audio. Its inclusion in 3GPP standards was motivated by the desire to create a viable mobile music ecosystem before widespread high-speed data and efficient perceptual audio codecs became available.

Key Features

• Transmits musical performance commands, not audio waveforms, for extreme bandwidth efficiency
• Supports standard MIDI messages (note on/off, control change, program change)
• Utilizes profiles like General MIDI (GM) and Scalable Polyphony MIDI (SP-MIDI) for consistent playback
• Defined RTP payload formats for real-time streaming over IP networks
• Enables interactive and adaptive musical applications
• Used for services like downloadable polyphonic ringtones, music messaging, and game audio

Evolution Across Releases

Defining Specifications