Kurzweil K2500RS, Руководство музыканта

Страница: 435 / 530

Memory Upgrades and Other Options
Program RAM vs. Sample RAM
27-1
Chapter 27
Memory Upgrades and Other Options
Program RAM vs. Sample RAM
If youÕre creating a lot of your own programs, and using samples loaded from disk, there are a
few things you should be aware of to avoid perplexity. First of all, thereÕs an important
distinction between what we call Sample RAM and what we call Program RAM. Sample RAM
refers to any SIMMs you may have had installed in your K2vx. This RAM is reserved
exclusively for sample storage; nothing else is stored there. Sample RAM is volatile; that is,
when you power down your K2vx, the data stored there will ÒevaporateÓ almost immediately.
ThatÕs why you have to load RAM samples every time you power up.
The amount of sample RAM in your K2vx is indicated in the center of the top line of the Disk
mode page. If the center of the displayÕs top line is blank when youÕre on this page, it means
that there is no sample RAM installed in your K2vx (or that the K2vx isnÕt recognizing it, in
which case you should see your dealer or service center).
Program RAM is where all the other RAM objects you create (programs, setups, QA banks,
songs, keymaps, etc.) are stored. The K2vx comes from the factory with approximately 240K of
available Program RAM. The amount of free Program RAM is indicated at the right side of the
top line of the display in Song mode and Disk mode. You can add a Program RAM (P/RAM)
option to increase your total available Program RAM to about 1250K. Ask your dealer.
Program RAM is battery-backed, so anything thatÕs stored there will be preserved even when
you power down (as long as your batteries have enough juice). Fresh alkaline batteries will last
up to two years, so youÕll have very few worries about losing your RAM program information.
Nonetheless, we recommend that you back up your programs, songs, etc. by saving them to
disk. This offers insurance in case the RAM becomes corrupted. This is unlikely, but still a
possibility.
If you create a program that uses a disk-loaded sample, the program information (number of
layers, keymap assignment, output group, algorithm, etc.) is stored in Program RAM. All RAM
samples associated with the program are stored in Sample RAM. This means that when you
power down, the RAM samples associated with your programs will disappear. The program
information, however, will remain in Program RAM indeÞnitely. When you power up again,
your RAM programs will still appear in the display as you scroll through the program list, but
they wonÕt play if they use RAM samples, because the RAM samples are lost when you power
down.
Viewing RAM Objects
If youÕre a heavy Disk mode user, youÕll often be faced with the decision to overwrite, merge, or
append objects when you load Þles from disk. If youÕre loading into a memory bank thatÕs
nearly full, this can be a tricky call, because if you decide to merge or append, there may not be
enough open slots in the memory bank to accommodate the objects you load. In this case, the
extra objects will be loaded into the next-higher memory bank.
Things get even trickier if you save dependent objects when you save to disk. (A dependent
object is any object thatÕs associated with another object stored in a different memory bankÑfor
example, a RAM sample with ID 301 thatÕs used in a program with ID 200. See the discussion of
dependent objects in Chapter 13 in the
Performance Guide .) If you load a Þle that contains a
number of dependent objects, some of them may be loaded into a higher memory bank than