User guide

952 Chapter 38 Working in the Environment
Go to Marker, Screenset, or Project
Choosing New > Fader > Special > Go to Marker creates a fader which allows you to
enter a marker number (Meta event 51).
The playhead moves instantly to the chosen marker number. Markers are numbered
sequentially, throughout the project, even if you have renamed them (from the default
numbers assigned when each marker was created).
Choosing New > Fader > Special > Goto Screenset creates a Screenset fader (Meta
event 49), allowing you to switch to the screenset number chosen with the fader.
Meta event 50 has no effect within Logic Express, but you can use it to switch between
songs on an external hardware sequencer.
Meta event 52 allows you to interrupt playback at any position.
Note: To make the most efficient use of these faders, we recommend that you limit the
value range to suit your particular circumstances. As an example, to limit the faders to
the number of screensets, projects, or markers you’re actually using.
SysEx Faders
The SysEx fader type is slightly different to other fader types. It allows you to create a
list of MIDI events that will be sent whenever the fader is moved or remote controlled.
You can enter the messages that you want to send in a window that resembles the
Event List. The positions of events in the list only control the order in which they are
sent—they are not sent at specific times, nor with any delay between them.
The SysEx fader type is primarily designed to send MIDI System Exclusive (SysEx)
messages—messages that are exclusive to individual manufacturers’ MIDI devices.
There are a number of features in the SysEx fader window (see below) that facilitate the
creation of SysEx messages.
Note: SysEx faders can actually be used for any kind of MIDI event, making them handy
for sending ordered batches of messages, such as mixer or control panel snapshots—
with one click of the mouse.
You can also specify SysEx as an Input definition, but this has limited usefulness
because the incoming message (presumably SysEx) must be very short, in order to be
recognized. This is a side-effect of the fact that SysEx messages can be of any length,
and Logic Express must break them into small packets, to avoid interrupting other MIDI
activities.