Kurzweil K2661, Справочник музыканта

Страница: 67 / 500

System Exclusive Protocol
K2661 System Exclusive Implementation
7-5
returned (see object type table below). The
bank
fi eld speci fi 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.
The responses, a stream of complete WRITE messages, will come out in order of object type,
while objects of a given type are in order by ID number, from lowest to highest. If no objects are
found that match the speci
fi cations, no WRITE messages will be returned. After the last WRITE
message, an ENDOFBANK message (de fi ned below) is sent to indicate the completion of the
bank dump.
The K2661 will insert a small delay (50ms) between WRITE messages that it issues in response to
a READBANK message.
A bank dump can be sent in its entirety to another K2661, which will add all of the objects
contained in the dump to its own object database. Important: If the K2661 receives a large bank
dump for a bank or banks that already contain objects, errors may result unless the sender waits
for the DACK message before sending the next object’s WRITE message. One way to avoid
transmission errors such as this is to make sure that the bank being dumped is clear in the K2661
before sending the dump, so that the K2661 will not miss parts of the dump while its CPU is
busy deleting already existing objects. This can be done using the DELBANK message (de
fi ned
below). If the destination bank in the K2661 is clear, it is not necessary to wait for the DACK
before sending. Even if the sender chooses not to wait for the DACK before sending the next
message, it may be necessary to preserve the 50ms delay between the WRITE messages.
Due to the large amount of incoming data during a bank dump containing many objects, the
receiving K2661 may have a more sluggish response to front-panel use and keyboard playing
during the data transfer. This is normal behavior and the machine will become fully responsive
as soon as the dump is
fi nished.
DIRBANK = 0Ch type(2) bank(1) ramonly(1)
This is similar to the READBANK message. The DIRBANK message requests an INFO message
(containing object size, name, and memory information) be returned for each object meeting the
speci
fi cations in the
type
and
bank
fi elds. Following the last INFO response will be an
ENDOFBANK message.
ENDOFBANK = 0Dh type(2) bank(1)
This message is returned after the last WRITE or INFO response to a READBANK or DIRBANK
message. If no objects matched the speci
fi cations in one of these messages, ENDOFBANK will
be the only response.
DELBANK = 0Eh type(2) bank(1)
This message will cause banks of objects (of one or all types) to be deleted from RAM. The
type
and
bank
speci fi cations are the same as for the READBANK message. The deletion will take
place with no con fi rmation. Speci fi cally, the sender of this message could just as easily delete
every RAM object from the K2661 (for example,
type
= 0 and
bank
= 127) as it could delete all
studios from bank 7 (for example,
type
= 113,
bank
= 7.)
MOVEBANK = 0Fh type(2) bank(1) newbank(1)
This message is used to move entire banks of RAM objects from one bank to another. A speci fi c
object type may be selected with the
type
fi eld. Otherwise, if the
type
fi eld is unspeci fi ed (0), all
object types in the bank will be moved. The
bank
and
newbank
fi elds must be between 0 and 9.
The acknowledgement is an ENDOFBANK message, with the
bank
fi eld equal to the new bank