JUCE
Static Public Member Functions | Static Public Attributes | List of all members
MPEMessages Class Reference

This helper class contains the necessary helper functions to generate MIDI messages that are exclusive to MPE, such as defining MPE zones and setting per-note and master pitchbend ranges. More...

Static Public Member Functions

static MidiBuffer addZone (MPEZone zone)
 Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will define a new MPE zone. More...
 
static MidiBuffer perNotePitchbendRange (MPEZone zone)
 Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will change the per-note pitchbend range of an existing MPE zone. More...
 
static MidiBuffer masterPitchbendRange (MPEZone zone)
 Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will change the master pitchbend range of an existing MPE zone. More...
 
static MidiBuffer clearAllZones ()
 Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will erase all currently defined MPE zones. More...
 
static MidiBuffer setZoneLayout (const MPEZoneLayout &layout)
 Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will reset the whole MPE zone layout of the device to the laoyut passed in. More...
 

Static Public Attributes

static const int zoneLayoutMessagesRpnNumber = 6
 The RPN number used for MPE zone layout messages. More...
 

Detailed Description

This helper class contains the necessary helper functions to generate MIDI messages that are exclusive to MPE, such as defining MPE zones and setting per-note and master pitchbend ranges.

You can then send them to your MPE device using MidiOutput::sendBlockOfMessagesNow.

All other MPE messages like per-note pitchbend, pressure, and third dimension, are ordinary MIDI messages that should be created using the MidiMessage class instead. You just need to take care to send them to the appropriate per-note MIDI channel.

Note: if you are working with an MPEZoneLayout object inside your app, you should not use the message sequences provided here. Instead, you should change the zone layout programmatically with the member functions provided in the MPEZoneLayout class itself. You should also make sure that the Expressive MIDI zone layout of your C++ code and of the MPE device are kept in sync.

See also
MidiMessage, MPEZoneLayout, MPEZone

Member Function Documentation

static MidiBuffer MPEMessages::addZone ( MPEZone  zone)
static

Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will define a new MPE zone.

static MidiBuffer MPEMessages::perNotePitchbendRange ( MPEZone  zone)
static

Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will change the per-note pitchbend range of an existing MPE zone.

static MidiBuffer MPEMessages::masterPitchbendRange ( MPEZone  zone)
static

Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will change the master pitchbend range of an existing MPE zone.

static MidiBuffer MPEMessages::clearAllZones ( )
static

Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will erase all currently defined MPE zones.

static MidiBuffer MPEMessages::setZoneLayout ( const MPEZoneLayout layout)
static

Returns the sequence of MIDI messages that, if sent to an Expressive MIDI device, will reset the whole MPE zone layout of the device to the laoyut passed in.

This will first clear all currently defined MPE zones, then add all zones contained in the passed-in zone layout, and set their per-note and master pitchbend ranges to their current values.

Member Data Documentation

const int MPEMessages::zoneLayoutMessagesRpnNumber = 6
static

The RPN number used for MPE zone layout messages.

Note: This number can change in later versions of MPE.

Pitchbend range messages (both per-note and master) are instead sent on RPN 0 as in standard MIDI 1.0.


The documentation for this class was generated from the following file: