Disk Mode
Saving Files
13-29
pressing "Open" on the Þle just saved (which should come up already highlighted). The
display of objects for the Þle will look like this:
Func:LOAD|||||Sel:0/2|||||||||||Index:|1
||||||||||||||||||||||||||||||||||||||||
||||||||||||||||||||||||||||||||||||||||
Table||||36|Names|||||||||||||||||||334|
Program|317|Steinwave|Piano|||||||||274|
||||||||||||||||||||||||||||||||||||||||
||||||
|
||||||
|
|||||
|
||||||
|
|||||
|
|||||||
Select
|
|Next|
|
Type|
|
Multi|
|
|OK||
|
Cancel|
The Name Table will always be the Þrst object in the list. You can verify the exact contents of
the name table by using the "View Name Table" shortcut (previously described in the Load
Object section); make sure the Name Table object is highlighted, and
press either the Left or
Right cursor button
on the front-panel (as if you were "auditioning "the Name Table object.)
You would then see the following informational display:
Name|Table|Contents|||||||||||||||||||||
Keymap||300|Steinwave|Piano|||||||||||||
Sample||300|StwaveG1||||||||||||||||||||
Sample||301|StwaveD2||||||||||||||||||||
Sample||302|StwaveB2||||||||||||||||||||
Sample||303|StwaveE3||||||||||||||||||||
Sample||304|StwaveB3||||||||||||||||||||
Sample||305|StwaveG4|||||||||||||||
|||||
|||||||||||||||||||||||||||||||||||
|OK||
The
Name Table Contents
display shows what would have been saved in the Þle had you
answered Yes to "Save dependent objects?" instead of answering by pressing Names. More
importantly, it allows you to see what objects will need to be already loaded in to the K2vx
before loading this Þle.
The object IDs shown in the table are the same numbers that those dependent objects used at
the time this Þle was saved. (The ID numbers are necessary in order for Relink-by-Name to
function, since they are the "link" between the higher level objects and the names of the
dependents.)
An important thing to notice about this particular Name Table is that the Sample names are not
needed by the K2vx for relinking purposes. In fact, the only information necessary for
relinking the dependent objects of this Þle is the Keymap object. The reason for this is that
when this Þle containing the program is loaded, all of these dependent objects should already
have been loaded, and the Keymap should already be correctly linked to the Samples.
Although the Samples' names are redundant from the K2vx's point of view, they are include for
free, so to speak, and you may Þnd them very helpful if you ever need to know exactly what
the dependents of this Þle were intended to be.
The Name Table Contents List is scrollable if there is object data past the 7 lines that Þt on the
screen.
Now that the two Þles STWAVE1.KRZ and STWAVE2.KRZ have been created using the Name
Table, they can be loaded back in and correctly relinked. The Þles can be loaded into any bank -
they do not need to go back into the bank they were originally in - since the STWAVE2.KRZ Þle
will search through all the banks to Þnd the objects by name in order to relink them. In fact, if
you were to immediately reload just the Þle containing the Program (STWAVE2.KRZ), into any
bank, you would Þnd that it was automatically relinked to the correct Keymap, since the
Keymaps and samples are currently in memory.
Summary of Contents for K2500RS
Page 12: ...Table of Contents TOC 12...
Page 16: ...Introduction How to use this manual 1 4...
Page 32: ...User Interface Basics The Panel Play Feature K2vxR 3 8...
Page 106: ...Effects Mode and the Effects Editor Configurations and Parameters 9 24...
Page 186: ...Song Mode Recording Multi timbral Sequences via MIDI 12 52...
Page 304: ...DSP Functions Hard Sync Functions 14 52...
Page 394: ...Programs Setups and Keymaps K2500 ROM Keymaps 21 12...
Page 402: ...LFOs LFO Shapes 23 4...
Page 406: ...Note Numbers and Intonation Tables List and Description of Intonation Tables 24 4...
Page 434: ...DSP Algorithms 26 14...
Page 450: ...MIDI and SCSI Sample Dumps SMDI Sample Transfers 29 8...
Page 464: ...Glossary 31 6...
Page 490: ...K2vx Program Farm VOX K25 Appendix A 22...
Page 494: ...K2vx Compatibility Converting programs from the K2vx to K2000 Appendix B 4...