10.6

Table Of Contents
1162Logic Pro User Guide
Lo7: Low 7bits of the value (LSB or Least Significant Bits)
Hi7: High 7bits of the value (MSB or Most Significant Bits)
For messages containing only a Lo7 placeholder, the value is treated as 7 bit. For
messages containing both a Lo7 and Hi7 placeholder, the value is treated as 14 bit.
The order of Lo7 and Hi7 is honored, and there may be constant bytes in between. This
allows you to define Control Change LSB and MSB portions. For example, B0 08 Hi7 B0
28 Lo7 indicates a 14-bit message.
Note: When you enter multiple MIDI messages, always enter each message completely,
being sure to repeat the status byte, even if it’s the same. It may help to write out the
message to ensure that the correct byte works, as you can’t know what status the
previously sent message had.
For messages containing neither Lo7 nor Hi7 placeholders, Logic Pro assumes an
incoming value of 1. This is typical for pressed or released buttons. Also see Multiply
field in Controller assignments Expert view Value parameters in Logic Pro.
Touch/Release field: Enter an integer value to use the incoming MIDI message for status
changes of the destination parameter from touched to released, or vice versa. A non-
zero value means touched; a value of 0 means released. The messages are shown and
edited in the same way as the Value Change field.
Note: The Touch/Release setting applies only to the Channel Strip assignment class and
to parameters that can be automated.
Controller assignments OSC Message Paths in Logic Pro
The parameters in this section let you edit the OSC paths used to communicate with OSC
devices. The OSC protocol allows for real time communication between software and
hardware over a network, or when using USB or other serial interfaces. The current OSC
implementation in Logic Pro supports UDP and IPv4 network connections only.
OSC Message Path parameters
Value field: Determine the message for sending the parameter value. Normally the value
is a normalized float, such as 0.0 to 1.0.
Note: There is an exception to the normalized value rule: feedback for global and
control surface group parameters is always sent non-normalized. As an example, the
current fader bank is sent as per its integer form, but in float format (0.0, 1.0, 2.0 and so
on).
Touch/Release field: Choose from the following values: 1.0 indicates touched and a
value of 0.0 indicates released.
Label field: Displays the parameter name.
Value String field: Displays the current parameter value.