One of the things to keep in mind while reading this document is that
this protocol is intended to interface with "embedded" systems. As such,
ROM space required for the implementation of the protocol is expected to
be minimal. Small low cost systems cannot afford to tie up large portions
of ROM space for external control alone, so, while this protocol provides
"universal" or (generic) access to the system, it is, in some ways, terse.
The connected controller is expected to understand the standard
functionality of the protocol.
I should point out that this system has been, largely, implemented in
the MPX 1 system. In fact, the protocol was developed in response to the
complexity of the MPX 1. I say "largely" because, as of this writing, the
full potential of the protocol has not been implemented in the MPX 1. The
standard audio and system parameter controls and effect loading have been
implemented successfully but some of the more advanced capabilities were
not exploited.