JLCooper FaderMaster Pro - Manual (Page 52)

Fader Null
An important concept in automation is the idea of “Nulling” a
fader. It is easiest to explain by an illustration.
Say that FaderMaster Pro is connected to a sequencer and
controlling MIDI controlled VCAs.
You start recording on the sequencer, and then you enable a
fader on FaderMaster Pro by pressing the button above the
fader. Then you perform a fade in, slowly bringing the fader
up. Now the fader on FaderMaster Pro is at the top of its throw.
Rewind the sequence, and begin to play it back. If your
sequencer features on screen moving faders, you will see the
fader jump immediately down to its minimum position, and
then slowly climb back up as your fade in plays back. But
suppose you stop the sequencer right away, and you don’t let
the fader move play back.
The picture of the fader on the computer is still near the
bottom
of its travel or throw.
Since we haven’t touched the FaderMaster Pro, the real fader
is still at the top of its throw.
The two faders, which are supposed to represent one audio
channel, are now in two different positions.
This doesn’t represent any problem whatsoever, until you
consider editing, that is, re-writing the fader move. If you were
to simply punch into record on the sequencer, and enable and
move the fader, you would have a radical jump in level.
The whole idea of Nulls and Enables is to prevent jumps in
level which would otherwise occur every time you tried to
punch in and correct fader moves consisting of MIDI controller
data.
52