Disk Mode
Saving Files
13-30
Furthermore, you could edit the program and create more variations of it that reference the
"Steinwave Piano" keymap, add ROM layers, and/or effects programs if desired, and resave all
of the programs (and any effects) to the same or a new Þle (remember to press Names when
you are asked "Save dependent objects?". ) You never have to resave the Þle STWAVE1.KRZ
that contains the keymap and samples, if all you have done is edited the programs or added
more of them. This can be a tremendous time-saver.
If the Keymap and Sample Þles are found on a CD-ROM disk, then using Relink-by-Name is
not only a time-saver, but a disk space saver as well. If you like the samples and keymaps from
a CD-ROM Þle, there is no need to duplicate the sample data on your own writable hard drive.
Instead, all you have to do is save a program Þle in the above manner, and then make sure the
CD-ROM Þle is loaded Þrst before you load the program Þle.
If you needed to add some sample data to the Þle (for instance, you want to add a root to the
keymap or process and reloop a sample from the CD-ROM), you can do this by explicitly
selecting the new sample data and the keymap for saving along with the program and the
Name Table. Then, the new sample would not be listed in the Name Table (it would be in the
same Þle as the Name Table), and the Keymap would be relinked to all of the samples by name
instead of the program being relinked to the keymap (as before). What you put in the different
Þles is up to you, and there is no limit to where you can break up the objects in one Þle or
another. The main thing to be aware of are the two rules for Relink-by-name mentioned above:
1. Always use unique names for like objects types. (NOTE: In cases where duplicate names
do exist in different banks, load the Þle that contains the name table into a bank equal to or
preceding the bank in which the Þle with dependent objects was loaded.)
2. Files containing dependent objects must be loaded Þrst.
As you will see later, you can create a Macro Þle that will automatically load both of the Þles in
the correct order, no matter what drives they are on or what disk directories they are in. By
using Macro Þles in this way, you can avoid having to explicitly load 2 Þles and remember the
correct order each time.
You can also use the Multiple Object Selector (described in the next section) to help in the
process of identifying dependent objects and parent objects that you want to place into
separate Þles. For instance you could easily select all dependent Keymaps and Samples of any
group of programs, to create a "dependents" Þle. Then, you could quickly select the programs
and any other objects that you wanted to be relinked later on, and save them in another Þle.
Here is another practical example using Songs (sequences). Suppose you have loaded several
Þles into your machine, such that you now have all your favorite instruments on-board in the
K2vx's RAM. Then, you make a bunch of songs using a combination of ROM programs and the
RAM programs you loaded in.
The dependent object structure of the songs would look something like this:
Songs: Song 400 Wild Jam ,Song 401 Memphis Groove
Programs: Program 600 Drawbarz Program 245 FendJazzBass
Program 231 Funky GTR Program 400 ObieWarble Pad
Program 103 3 Layer Kit (from ROM)
Effects: ROM effects
Keymaps, Samples: Lots of them...
In this case you might want to save all of the songs in one Þle, and be able to automatically
relink the dependent programs used by the song tracks. All of the programs are presumably
already saved in separate Þles. The only Þle that needs to be created is one that contains all of
To Next Page
Loading...