The PRIZM Sound Board User's Manual
Plecter Labs is in no way affiliated, associated, licensed or endorsed by Disney or Lucasfilm Ltd., Industrial Light
and Magic or any of their associates.All brands and trademarks listed are the exclusive property of their respective
Owners.
19
Parameters and fine tuning the saber
The configuration file includes a set of parameters dedicated to the sound section of
the controller and the gestural / motion detection (both being linked). A second set of
parameters handles the behavior of the high-power LED. Some parameters influence
both categories, since visual and sound effects are in tight relationship intrinsically. All
parameters are lowercase.
Certain parameters involve time / duration / delay. We tried to normalize
those parameters to a single unit: a multiple of 2ms. Unless otherwise
indicated, that’s what is used to define those timing parameters and it
matches the internal clock of the board.
Motion & Gesture detection parameters :
Motion recognition is processed using complex low latency DSP algorithms, however,
most of the parameters used for those are internally computed so the user only has to
setup a few thresholds & sensitivity level as high-level parameters.
The overall sensitivity of the board is controlled by the “i” parameter. If you want a
more “verbose” saber while you’re satisfied of the swing / clash discrimination, just
increase a little bit that parameter, turning it to 55 instead of the default 53 value.
Swings and clashes are separated using 3 thresholds. A swing motion must exceed
ls
(low swing) and must remain under
hs
(high swing). A clash must simply exceed
lc
(low clash).
It’s important to maintain a dead-zone between
hs
and
lc
to maximize the quality of
the motion detection.
Default parameters have been setup for you and usually, only the “i” parameter has to
be touched up.
However, some special cases can be considered:
The saber is not sensitive enough to the swing (placement in the hilt too close
to the spinning center, spinning style etc) : decrease parameter
ls
of one point
of two. Don’t decrease
ls
too much or undesired swing sounds will be
triggered.
When the saber cuts the air too fast, the swing is not triggered (it’s in the
dead-zone). Increase a little bit parameter
hs(
or reduce the speed of your
swings).
The saber often produces a clash sound when the user executes a swing:
parameter
hs
is probably too high and too close to parameter
lc
. If the clash
sensitivity is correct, decrease parameter
hs
.
The saber is not sensitive enough to clashes: decrease parameter
lc
.
The user wants the clash to happen
only
when blade is smacked very hard:
increase
lc
(keep it under 1023).
