RTP Payload Format for MIDI
draft-ietf-avt-rfc4695-bis-10
Document | Type |
Replaced Internet-Draft
(payload WG)
Expired & archived
|
|
---|---|---|---|
Authors | John Lazzaro , John Wawrzynek | ||
Last updated | 2011-02-01 (Latest revision 2011-01-24) | ||
Replaced by | draft-ietf-payload-rfc4695-bis | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-payload-rfc4695-bis | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)