RFC 4695: RTP Payload Format for MIDI
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6295.
Current version: RFC 6295 — RTP Payload Format for MIDI
In plain English — editorial summary, not part of the RFC
This memo describes a Real-time Transport Protocol (RTP) payload format for the MIDI (Musical Instrument Digital Interface) command language. The format encodes all commands that may legally appear on a MIDI 1.0 DIN cable. The format is suitable for interactive applications (such as network musical performance) and content-delivery applications (such as file streaming). The format may be used over unicast and multicast UDP and TCP, and it defines tools for graceful recovery from packet loss. Stream behavior, including the MIDI rendering method, may be customized during session setup. The format also serves as a mode for the mpeg4-generic format, to support the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds Level 2, and Structured Audio. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4695
- Published
- November 2006
- Authors
- J. Lazzaro; J. Wawrzynek
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 169
- Also known as
- —
- Obsoleted by:
- RFC 6295
Topics
- asc
- content streaming
- DLS 2
- General MIDI
- MIDI
- MIDI file
- MIDI file streaming
- MIDI light control
- MIDI rendering
- MIDI ringtone
- MIDI streaming MIDI sequencer
- MIDI time code
- MIDI timecode
- MIDI Manufacturers Association
- MMA mpeg4-generic MPEG 4
- MPEG 4 Structured Audio
- MPEG 4 Synthetic Coding
- MTC
- musical notes
- network musical performance
- recovery journal
- Show Control
- sonification
- ringtone
- rtp-midi
- RTP
- RTP MIDI
- SMPTE time code
- SMPTE timecode
- Standard MIDI Files
- XMF
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4696An Implementation Guide for RTP MIDICurrent
November 2006
- RFC 4723Registration of Media Type audio/mobile-xmfCurrent
December 2006
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
- RFC 3952Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) SpeechCurrent
December 2004
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5691RTP Payload Format for Elementary Streams with MPEG Surround Multi-Channel AudioCurrent
October 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?