Liking cljdoc? Tell your friends :D

javax.sound.midi.SysexMessage

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:

0xF0: System Exclusive message (same as in MIDI wire protocol) 0xF7: Special System Exclusive message

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.

0xF0: System Exclusive message (same as in MIDI wire protocol) 0xF7: End of Exclusive (EOX)

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.

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:

0xF0: System Exclusive message (same as in MIDI wire protocol)
0xF7: Special System Exclusive message


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.

0xF0: System Exclusive message (same as in MIDI wire protocol)
0xF7: End of Exclusive (EOX)

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.
raw docstring

*-special-system-exclusiveclj

Static Constant.

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.

type: int

Static Constant.

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.

type: int
raw docstring

*-system-exclusiveclj

Static Constant.

Status byte for System Exclusive message (0xF0, or 240).

type: int

Static Constant.

Status byte for System Exclusive message (0xF0, or 240).

type: int
raw docstring

->sysex-messageclj

(->sysex-message)
(->sysex-message data length)
(->sysex-message status data length)

Constructor.

Constructs a new SysexMessage and sets the data for the message. The contents of the message can be changed by using one of the setMessage methods.

status - the status byte for the message; it must be a valid system exclusive status byte (0xF0 or 0xF7) - int data - the system exclusive message data (without the status byte) - byte[] length - the length of the valid message data in the array; it should be non-negative and less than or equal to data.length - int

throws: javax.sound.midi.InvalidMidiDataException - if the parameter values do not specify a valid MIDI meta message.

Constructor.

Constructs a new SysexMessage and sets the data for the message.
 The contents of the message can be changed by using one of
 the setMessage methods.

status - the status byte for the message; it must be a valid system exclusive status byte (0xF0 or 0xF7) - `int`
data - the system exclusive message data (without the status byte) - `byte[]`
length - the length of the valid message data in the array; it should be non-negative and less than or equal to data.length - `int`

throws: javax.sound.midi.InvalidMidiDataException - if the parameter values do not specify a valid MIDI meta message.
raw docstring

cloneclj

(clone this)

Creates a new object of the same class and with the same contents as this object.

returns: a clone of this instance - java.lang.Object

Creates a new object of the same class and with the same contents
 as this object.

returns: a clone of this instance - `java.lang.Object`
raw docstring

get-dataclj

(get-data this)

Obtains a copy of the data for the system exclusive message. The returned array of bytes does not include the status byte.

returns: array containing the system exclusive message data. - byte[]

Obtains a copy of the data for the system exclusive message.
 The returned array of bytes does not include the status byte.

returns: array containing the system exclusive message data. - `byte[]`
raw docstring

set-messageclj

(set-message this data length)
(set-message this status data length)

Sets the data for the system exclusive message.

status - the status byte for the message (0xF0 or 0xF7) - int data - the system exclusive message data - byte[] length - the length of the valid message data in the array - int

throws: javax.sound.midi.InvalidMidiDataException - if the status byte is invalid for a sysex message

Sets the data for the system exclusive message.

status - the status byte for the message (0xF0 or 0xF7) - `int`
data - the system exclusive message data - `byte[]`
length - the length of the valid message data in the array - `int`

throws: javax.sound.midi.InvalidMidiDataException - if the status byte is invalid for a sysex message
raw docstring

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close