System Exclusive Protocol
K2vx System Exclusive Implementation
30-4
CHANGE = 08h
type(2) idno(2) newid(2) name(n)
Échanges the name and/or ID number of an existing object. If ÔnewidÕ is zero or ÔnewidÕ equals
ÔidnoÕ, the ID number is not changed. If ÔnewidÕ is a legal object id number for the objectÕs type
, then the existing object will be relocated in the database at the new ID number. This will cause
the deletion of any object which was previously assigned to the ÔnewidÕ. If the ÔnameÕ Þeld is
null, the name will not change. Otherwise, the name is changed to the (null-terminated) string
in the ÔnameÕ Þeld.
WRITE = 09h
type(2) idno(2) size(3) mode(1) name(n) form(1) data(n) xsum(1)
Éwrites an entire objectÕs data directly into the database. It functions like the message
sequence DEL followed by NEW followed by a LOAD of one complete object data structure. It
Þrst deletes any object already existing at the same type/ID. If no RAM object currently exists
there, a new one will be allocated and the data will be written into it. The object name will be
set if the ÔnameÕ string is non-null. The response to this message will either be a DACK or a
DNAK, as with the load message. The ÔoffsÕ Þeld of the response will be zero. The K2vx will
send a WRITE message whenever an object is dumped from the front-panel (using a ÒDumpÓ
soft-button), or in response to a READ message.
The ÔmodeÕ Þeld is used to determine how the ÔidnoÕ Þeld is interpreted.
If ÔmodeÕ = 0:
The ÔidnoÕ speciÞes the absolute ID number to write to, which must exist.(must be valid)
If ÔidnoÕ equals zero, write to the Þrst available ID number.
If ÔmodeÕ = 1
The object is written at the Þrst available ID number after what is speciÞed by ÔidnoÕ.
It doesnÕt matter if ÔidnoÕ is a legal ID number. Remember that for certain object types, the 100s
through 900s banks allow fewer than 100 objects to be stored (for example, the 100s bank will
store preset effects at IDs 100Ñ109 only). In this mode, if ÔidnoÕ was 313, the object would be
written to ID 400 if available.
READ = 0Ah
type(2) idno(2) form(1)
Érequests the K2vx to send a WRITE message for the given object. No response will be sent if
the object does not exist.
READBANK = 0Bh type(2) bank(1) form(1) ramonly(1)
Érequests the K2vx to send a WRITE message for multiple objects within one or all banks.
ÔtypeÕ and ÔbankÕ specify the group of objects to be returned in WRITE messages. The ÔtypeÕ
Þeld speciÞes a single object type, unless it is zero, in which case objects of all user types will be
returned (see object type table below). The ÔbankÕ Þeld speciÞes a single bank, 0-9, unless it is
set to 127, in which case objects from all banks will be returned.
ÔformÕ requests the format of the binary data in the WRITE messages. If ÔramonlyÕ is one, only
objects in RAM will be returned. If ÔramonlyÕ is zero, both RAM and ROM objects are returned.
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...