16
LexiconPCM 90 MIDI Implementation Details
0x13 Patch Assignment Dump
This bidirectional dump contains the state of a particular patch in the currently running effect.
Byte # Byte Value Description Notes
1 F0 SysEx ID
2 06 Lexicon ID
3 08 PCM 90 ID
4 0iii iiii Device ID
5 0x13 PatchAssign
6 0n PatchID (0-9)
7-8 0000 iiii Patch Source.
Nibble-ized with less
significant part first. See Appendix A: Patch Sources by Index.
9 0iii iiii Patch Destination. The patchable parameter offset. A value of 0x7F indicates
that the patch is to be disconnected. All other values in the
packet remain valid.
10 0n Point Count (0-8). Only the ‘n’ following point values is meaningful. Remainder
should be set to 0. A point count of 0 is an alternate way to
indicate a disconnected path.
Patch Point Packet: This point packet is repeated 8 times...
11 0iii iiii Point Position (0-127) Positions should be in ascending order and may not be
duplicated.
12 0000 iiii Point Value LS nibble. The point value is independent of the specific parameter
range. The range of point value is from 0 (minimum) to
0x0400 (maximum). This format is used so that a new patch
destination can be selected while maintaining the contour of
the patch table. Any values above 0x0400 will be clipped to
0x0400.
13 0000 iiii Point Value next nibble
14 0000 iiii Point Value next nibble
15 0000 iiii Point Value MS nibble.
16 000i iiii Tempo value Numerator
(1-24) Out-of-range values will be clipped and will cause a message
to be printed on the front panel.
17 000i iiii Tempo value
Denominator (1-24) Out-of-range values will be clipped.
7 more 7-byte point packets...
67 0xF7 End of SysEx
If this message is improperly built, for example, if points are out of range or are not defined in ascending
order, the PCM 90 will attempt to correct the data. The message: “Bad patch data was corrected” will be
displayed
To Next Page
Loading...
