Save This Page
Home » openjdk-7 » javax.sound » midi » [javadoc | source]
javax.sound.midi
public class: SysexMessage [javadoc | source]
java.lang.Object
   javax.sound.midi.MidiMessage
      javax.sound.midi.SysexMessage

All Implemented Interfaces:
    Cloneable

A SysexMessage object represents a MIDI system exclusive message.

When a system exclusive message is read from a MIDI file, it always has a defined length. Data from a system exclusive message from a MIDI file should be stored in the data array of a SysexMessage as follows: the system exclusive message status byte (0xF0 or 0xF7), all message data bytes, and finally the end-of-exclusive flag (0xF7). The length reported by the SysexMessage object is therefore the length of the system exclusive data plus two: one byte for the status byte and one for the end-of-exclusive flag.

As dictated by the Standard MIDI Files specification, two status byte values are legal for a SysexMessage read from a MIDI file:

When Java Sound is used to handle system exclusive data that is being received using MIDI wire protocol, it should place the data in one or more SysexMessages. In this case, the length of the system exclusive data is not known in advance; the end of the system exclusive data is marked by an end-of-exclusive flag (0xF7) in the MIDI wire byte stream.

The first SysexMessage object containing data for a particular system exclusive message should have the status value 0xF0. If this message contains all the system exclusive data for the message, it should end with the status byte 0xF7 (EOX). Otherwise, additional system exclusive data should be sent in one or more SysexMessages with a status value of 0xF7. The SysexMessage containing the last of the data for the system exclusive message should end with the value 0xF7 (EOX) to mark the end of the system exclusive message.

If system exclusive data from SysexMessages objects is being transmitted using MIDI wire protocol, only the initial 0xF0 status byte, the system exclusive data itself, and the final 0xF7 (EOX) byte should be propagated; any 0xF7 status bytes used to indicate that a SysexMessage contains continuing system exclusive data should not be propagated via MIDI wire protocol.

Field Summary
public static final  int SYSTEM_EXCLUSIVE    Status byte for System Exclusive message (0xF0, or 240).
    Also see:
    MidiMessage#getStatus
 
public static final  int SPECIAL_SYSTEM_EXCLUSIVE    Status byte for Special System Exclusive message (0xF7, or 247), which is used in MIDI files. It has the same value as END_OF_EXCLUSIVE, which is used in the real-time "MIDI wire" protocol.
    Also see:
    MidiMessage#getStatus
 
Fields inherited from javax.sound.midi.MidiMessage:
data,  length
Constructor:
 public SysexMessage() 
 protected SysexMessage(byte[] data) 
Method from javax.sound.midi.SysexMessage Summary:
clone,   getData,   setMessage,   setMessage
Methods from javax.sound.midi.MidiMessage:
clone,   getLength,   getMessage,   getStatus,   setMessage
Methods from java.lang.Object:
clone,   equals,   finalize,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from javax.sound.midi.SysexMessage Detail:
 public Object clone() 
    Creates a new object of the same class and with the same contents as this object.
 public byte[] getData() 
    Obtains a copy of the data for the system exclusive message. The returned array of bytes does not include the status byte.
 public  void setMessage(byte[] data,
    int length) throws InvalidMidiDataException 
    Sets the data for the system exclusive message. The first byte of the data array must be a valid system exclusive status byte (0xF0 or 0xF7).
 public  void setMessage(int status,
    byte[] data,
    int length) throws InvalidMidiDataException 
    Sets the data for the system exclusive message.