Chapter 2: Individual Parameter-Access 4
Sysex-start $f0
TC ID $33
Device# xx
Card# xx
Packet-type $01 - Request
<Par #xxxx>
<Par #yyyy>
<Par #zzzz>
...
...
Sysex-end $f7
The M5000 replies with a Parameter Dump, as described next:
2.4 Setting Parameter Values
In a single parameter-dump, you can set as many or as few parameters as you like. In order to
minimize MIDI-traffic, you should set as many parameters as possible in a single dump.
Sysex-start $f0
TC ID $33
Device# xx
Card# xx
Packet-type $00 - Dump
<Par #xxxx>
<Par Value>
<Par #yyyy>
<Par Value>
<Par #zzzz>
<Par Value>
...
...
Sysex-end $f7
2.4.1 Truncation and Mutual Dependencies
If a parameter-value is out of range, it is truncated to fit. Please note, that some parameters (such as
cross-overs) have floating minimum and maximum values. This scheme follows a fairly simple logic,
although you must implement this yourself in order to track the correct value for the user; the M5000
has no way of telling you that a parameter-value has been truncated. These mutual dependencies are
described as necessary in conjunction with the parameter-listings in chapter 0 and 0.
2.4.2 Linked Parameters
Some parameters are linked to always contain the same value (a good example of this is the 0dBRef
parameter in the DYNAMIC1 algorithm). Generally, you shouldn’t display or manipulate more than
one of the linked parameters. With the 0dBRef example, simply choose one of the parameters as the
only one.
2.4.3 The Parameter-Queue
The M5000 places all parameters that need to be changed in a queue. Some parameters take a little
time to recalculate, while others change instantaneously. The parameters are extracted from the
queue as fast as possible.
To Next Page
Loading...
Need help?
General
