Specifications

converter 1.5

2000 - 2005 urr Sound Technologies Inc.
79
lfo midi conversion settings
game/mouse/lfo parameters : lfo parameters : midi conversion settings
[ F4 – F7 – F6 – F5/F6/F7… ]
lfo byte position
Selects which databyte of the chosen midi message the converted value is placed in. For example, to
convert the value from the sine lfo generator to control the pitch wheel, the generated message would
consist of one statusbyte and 2 databytes as follows: the statusbyte (indicating a pitch wheel message
on midi channel X), followed by the first databyte representing the LSB component of the pitch wheel
message (unused in this case since we can only provide an 8-bit value, therefore should be set to a
value of zero), followed by the second databyte representing the MSB value for pitch wheel. Hence you
would type 2 or scroll the parameter until it says “databyte #2” (to indicate that the value taken from the
lfo generator should be placed in the 2
nd
databyte of the midi message). Since the statusbyte is not
considered a data byte, this parameter should be read in terms of databyte number, not byte number in
the cumulative message packet (i.e. 2 instead of 3). Possible databyte position values are either 1 or 2;
if set to zero (or “unused in msg”), the converted byte is not added to the midi message to be
transmitted (in this way, a fixed midi message will be generated every time the lfo generates a byte).
Note that not all midi messages use both, or any, data bytes; channel aftertouch, program change, and
song select only use the first databyte (for aftertouch amount, program change number and song
number respectively), while system realtime messages such as midi clock simply use the statusbyte. As
converter automatically enforces these midi definitions, setting this byte position parameter to 2 when
the message type only supports one data byte results in the converted value not being a part of the
generated midi message.
lfo statusbyte
Determines the midi message type (and channel) to use for the lfo conversion value. Possible values are
between 128 and 255. Note that certain midi message types are not allowed, simply because they are
either undefined (such as 253 or 245), or are complex multi-byte messages such as 240 (system
exclusive) or 241 (midi time code quarter frame).
lfo 1
st
databyte value
Sets a fixed value for the first databyte of a midi message. The
conversion byte position
parameter
overrides this value if it is set to place the conversion result in the 1
st
databyte position.
lfo 2
nd
databyte value
Sets a fixed value for the second databyte of a midi message. The
conversion byte position
parameter overrides this value if it is set to place the conversion result in the 2
nd
databyte position.
lfo tempo subdivision
Specifies the note length of a half-cycle of the lfo wave. In other words, if the square wave lfo is set to a
¼ note subdivision, the waveform if high (maximum amplitude) for 1 quarter note length, and then low
(minimum amplitude) for the next quarter note, and so on. Triplet values are supported.
lfo key retrigger
Determines whether the lfo wave is returned to the beginning of its waveform cycle when a (post midi
input processor, if enabled) note on message (on the same midi channel as the lfo is programmed to
transmit on) is received via the midi input. This allows for quick resynchronization of the lfo cycle, and
fun changes to the rhythmic placement of the lfo in relation to whatever song is being worked with. This
does not affect the lfo if it is not transmitting its own midi message (is only used as a modulator).