Access Virus User Manual - SoundProgramming.Net
Access Virus User Manual - SoundProgramming.Net
Access Virus User Manual - SoundProgramming.Net
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ACCESS VIRUS OS4 221<br />
Problems Related to Parameter Control<br />
PROBLEMS RELATED TO<br />
PARAMETER CONTROL<br />
If you enjoy experimenting with<br />
recording parameter changes,<br />
sooner or later, you will run into<br />
the following problem: When controller<br />
sequences are recorded to a<br />
sequencer, the last recorded value<br />
remains valid until another value is<br />
sent for this controller. For example,<br />
if you gradually open a filter<br />
for a sound in the middle of the<br />
song and record this parameter<br />
change, the filter will stay open<br />
until the end of the song if you not<br />
close it manually or close it via controllers.<br />
Moreover, when you start<br />
the song from the top, you’ll again<br />
hear the sound with the filter open<br />
because the <strong>Virus</strong> hasn’t received a<br />
command at the beginning of the<br />
song to close the filter. Not until<br />
the song arrives at the position<br />
where the recorded event begins<br />
does the <strong>Virus</strong> receive the first controller<br />
value for the filter. If, on the<br />
other hand, the song is started<br />
with the stored and unedited version<br />
of the filter sound, everything<br />
will be fine: The filter is closed and<br />
won’t be opened until the recorded<br />
event tells the <strong>Virus</strong> to do just that.<br />
If you understand this connection<br />
between recorded parameter<br />
changes and the current parameter<br />
status of the <strong>Virus</strong>, you’ll find it<br />
easy to come up with solutions for<br />
these kinds of problems. Sticking<br />
with our example, you could send<br />
a controller value to the <strong>Virus</strong> that<br />
closes the filter again in a suitable<br />
position within the song, for<br />
instance, at some point after the<br />
filter opens or at the beginning of<br />
the song. However, this procedure<br />
can become tedious rather quickly<br />
if you have recorded many parameter<br />
changes – after all, what<br />
you’re actually doing is literally<br />
copying the original values of different<br />
parameter in order to enter<br />
them into the sequencer. You could<br />
of course simply activate the<br />
sound at the beginning of the song<br />
via a program change message,<br />
which resets the parameters to<br />
their original stored values. What<br />
if, however, you change or replace<br />
the sound in the <strong>Virus</strong> at some<br />
point? The program change message<br />
in the song would call up the<br />
wrong sound. The more reliable<br />
and certainly more elegant solution<br />
would be to store the sound(s)<br />
in the song. The <strong>Virus</strong> then receives<br />
all settings for sounds at the