SP MidiIANA Registered

MIME: audio/sp-midi
Extensions: —
{
  "full": "audio/sp-midi",
  "type": "audio",
  "subtype": "sp-midi",
  "extensions": [],
  "iana": {
    "template_url": "https://www.iana.org/assignments/media-types/audio/sp-midi",
    "type_name": "audio",
    "subtype_name": "sp-midi",
    "encoding_considerations": "sp-midi data is binary data and must be encoded for non-binary \n   transport; Base64 is suitable for Email.",
    "security_considerations": "Many synthetic audio compositions have associated intellectual \n   property rights.  It is conceivable that the rights owners of sp-\n   midi content will want to protect their rights by applying \n   security mechanisms that prohibit the rendering of the content \n   without a legally acquired license to do so.  These mechanisms \n   would be applied externally to the Content-Type defined here; sp-\n   midi content itself is not encrypted internally.  sp-midi streams \n   do not contain executable content.  sp-midi players are robust \n   against corrupted sp-midi content, because sp-midi players ignore \n   unidentified content.",
    "interoperability_considerations": "Scalable Polyphony MIDI (SP-MIDI) is a Musical Instrument Digital \n   Interface (MIDI) specification developed by MMA and AMEI.  SP-MIDI \n   is based on the MIDI 1.0 specification [n3], which standardizes a \n   protocol for the electronic transmission of music performance data \n   suitable for communication between a transmitter and receiver \n   using MIDI messages.  SP-MIDI data is stored in Standard MIDI \n   Files (SMF) [n3]. \n    \n   The SP-MIDI format [n1] provides a scalable representation of MIDI \n   content enabling broadly interoperable music applications.  SP-\n   MIDI files have encoded information about playback requirements \n   allowing SP-MIDI playback devices with different device \n   capabilities to play the same content according to the composer's \n   polyphony requirements and Channel priority order definitions.  \n   SP-MIDI player requirements are specified in separate SP-MIDI \n   profile specifications [n2] defining the supported MIDI messages \n   and device requirement.  All SP-MIDI profiles follow the \n   definitions of the SP-MIDI specification [n1]. \n    \n   MMA and AMEI have previously defined the General MIDI (GM) system \n   standards GM1 [i4] GM2 [i5], and GML [i6].  These specifications \n   are technically related to the SP-MIDI specification, but do not \n   support polyphony scalability.  Due to the differences between GM \n   and SP-MIDI systems, GM synthesizers do not support all SP-MIDI \n   content.  Likewise, not all SP-MIDI synthesizers support all GM \n   content.  Thus, a separate MIME definition is needed to \n   distinguish SP-MIDI from the informally used audio/midi content.",
    "additional_information": "Magic number(s):  \n     \n      First four bytes (1-4): \\115\\124\\150\\144,  \n      byte (24): \\360,  \n      byte (26): \\177,  \n      bytes (28-29): \\013\\001  \n \n   File extension(s): mid  \n \n   Macintosh File Type Code(s): Midi",
    "intended_usage": "common",
    "change_controller": "",
    "template_text": "[omitted]"
  }
}