4-18
Disk Mode Enhancements in Version 3
Load Function Dialog Changes
Fill Ignore the object ID numbers stored in the file. Try to use consecutive numbering
from the beginning of the selected bank. If an ID number is already in use,
increment the ID number until a free slot is found.
Cancel Cancel the mode selection, and go back to choosing a bank. Scrolling to a
different bank value will have the same effect as Cancel.
Typically, you will always want to just use the Fill method. Append, Merge, and Overwrt try to
preserve the numbers stored with the objects in the file, but this should only really be necessary
if you depend on program numbers or effect numbers to be at a certain MIDI program change
number. OvFill is like Fill except the selected bank (or Everything) is cleared out before loading.
Overwrt and OvFill operate in different ways after a selected bank has been filled up for a given
object type (for example, after you have loaded in more than 100 programs into a bank).
Overwrt will begin continue to preserve the objectIDs stored in the file, and will individually
overwrite objects in the bank following the just filled bank. OvFill will not overwrite any
further objects past the end of the selected bank; it instead skips over object IDs that are in use.
Because of this difference, it can sometimes be faster to load in a file using OvFill rather than
Overwrt. However, this only applies if the objects to be loaded would extend past the end of a
selected bank.
Note that when loading into a specific bank (as opposed to loading as
Everything), the object
ID's in the file are used as follows: The “bank” digit is ignored, and the remainder of the number
is used when the K2000 re-banks the object ID into the bank that you specify. For instance, if you
save Program 453 into a file, and load it back into the 300s bank, the K2000 will use the number
53 when deciding upon a new object ID. If the 300s bank was previously empty, and the load
mode is Append, then the Program will end up with ID 353.
For loading as Everything, the ID number for an object stored in a file is taken literally, and
not re-banked (except if Fill or OvFill mode is chosen, in which case the K2000 will use ID
numbers starting from 200).
Here is an example that compares all of the above load modes.
EXAMPLE: Starting with the following objects already stored in the K2000 internal RAM:
Program|200|Existing|Prog1
Program|204|Existing|Prog2
Program|205|Existing|Prog3
Program|210|Existing|Prog4
Program|211|Existing|Prog5
Suppose you were to load file containing the following objects into the 200s bank:
Program|405|Electric|Piano|
Program|406|Stereo|EPiano||
Program|409|Weird|Piano||||
Program|410|Wild|Funk|Piano
To Next Page
Loading...
Need help?
General
