Kurzweil KDFX, Руководство пользователя

Страница: 31 / 164

A Tour of KDFX
Building your own
2-15
A Note about KDFX in Setups
As we mentioned earlier, using Setups on a K2500R and a conventional MIDI keyboard
requires some special consideration. In order to play Setups, which normally require a multi-
zoned/multichannel keyboard like the K2500 or PC-88, the K2500R includes a parameter called
ÒLocal Keyboard ChannelÓ (
LocalKbdCh ), which is found on the MIDI:Receive page. If you
set this parameter to the transmitting channel of the keyboard, then the K2500 takes all
incoming MIDI data on that channel and treats it as if it was coming from a local keyboardÑ
that is, it plays all the Zones in the Setup.
However when you use this feature, be aware that many MIDI controller commands are
ÒremappedÓ by the SetupÕs parameters. See Chapter 4 for more information, and a list of the
MIDI controllers that are remapped.
Building your own
Now that weÕve walked you through a very complex studio, here are some hints on how to go
about building your own.
First, you want to decide whether you want the Studio to be static, or to be dynamic under
KDFX control from the K2500 keyboard and/or an external MIDI source, and/or to change
when the Program or Setup changes. If itÕs to be static, then
Effect mode must be set to Master.
If itÕs to change in any way in real time, the Effects mode must be Program, Setup, or Auto,
depending on how you want to approach it.
Then you need to look at how your Program outputs are arranged, so you can design the
Studio intelligently. If youÕre using internal Setups, look at the output assignments on the
various Zones, and change them so that sounds that need different effects are separated, and
those that can use the same effects are grouped. If youÕre using a MIDI sequencer, you might
want to use the ÒOutPairÓ parameter found on the
MIDI:Channels page (see page 10-9 in the
K2500 Performance Guide ), and arrange your sequence so that the routings of tracks to FX Buses
can be determined by their MIDI channel assignments.
Now set up your Studio, assigning FX Presets to the Program outputs/KDFX inputs. Many of
the ROM Studios follow a common organizational plan, which might be a good starting point
for your Studios:
¥
FXBus 1 contains a relatively simple reverb with a low Size requirement.
¥
FXBus 2 contains an effect which does not increase the ÒlengthÓ of the sound (that is, not
reverb or delay). Possibilities include chorus, ßange, phaser, distortion, shaper, pitcher,
enhancer, EQ, or EQ Morpher.
¥
FXBus 3 contains effects which take up lots of time, such as delays, delays with reverb, or
other ÒLeadÓ sounds.
¥
FXBus 4 is dry, and is used as a ÒbypassÓ bus going directly to the Aux FXBus. (ItÕs also
good to think this way if all of the PAUs have been used by the other Buses.)
¥
The Aux FXBus contains a larger reverb (Size: 2 or3), a compressor, or a graphic EQ. It can
often be used instead of an FXBus reverb, such as the one on FXBus1. If you use it in this
way (set the Aux Lvl on FXBus 1 to 0dB or higher), it frees up FX Bus 1 for use as an
Enhancer, Stereo Image, Flanger, etc.
Finally, set up your KDFX Mods in the Setup or Program you plan to use. If you are using a
sequencer, you might want to dedicate a Program
just to KDFX Mods, with no sound coming
from that program.