Kurzweil K2600 Musician's Manual page 344

Disk Mode
Saving Files
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. Files containing dependent objects must be loaded Þrst.
2.
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 disks they are on or what disk directories they are in. By using
macro Þles in this way, you can avoid having to explicitly load multiple Þles and remember the
correct order each time.
You can also use the Multiple Object Selector (see page 13-36) to help in the process of
identifying dependent objects and parent objects that you want to place into separate Þles. For
example, 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 K2600, such that you now have all your favorite instruments in RAM. Then, you
make a bunch of songs using a combination of ROM programs and the RAM programs you
loaded.
The dependent object structure of the songs would look something like this:
Songs
Programs
Effects
Keymaps, Samples
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
the song objects, plus a name table. Once again, this is done by selecting the songs from the Save
Object dialog, and answering Names to ÒSave dependent objects?Ó The contents of this Þle can
then be displayed by pressing Open (as was done for the previous example).
Func:LOAD||||Sel:0/2|||||||||||Index:||||1
||||||||||||||||||||||||||||||||||||||||||
||||||||||||||||||||||||||||||||||||||||||
Table||||36|Names|||||||||||||||||||||700|
Song||||400|Wild|Jam||||||||||||||||12114|
Song||||400|Memphis|Groove||||||||||34002|
||||||||||||||||||||||||||||||||||||||||||
Select||Next|||Type|||Multi|||OK||||Cancel
13-34
Always use unique names for like objects types. (NOTE: In cases where duplicate names exist
in different banks, load the Þle(s) containing dependent objects, then load the Þle that
contains the name table into the same bank or to the one just before it. This will prevent
relinking conßicts.
400 Wild Jam
600 Drawbarz
231 Funky GTR
50 Studio Kit 1 (from ROM)
ROM Effects
Lots of 'em...
401 Memphis Groove
245 FendJazzBass
400 ObieWarble Pad