Specifications

converter 1.5

2000 - 2005 urr Sound Technologies Inc.
50
audio midi data settings
audio parameters : midi conversion settings : midi data settings : main/filter channels
[ F3 – F7 – F5 – F5/F6/F7 ]
When programming an audio channel to generate a midi note on message, the particular note can be
‘auditioned’ by pressing the [Tab] key while the menu cursor is hovering over one of the channel’s midi
data parameters. This is particularly useful when programming drum triggering.
converted byte position
Selects which databyte of the chosen midi message the converted value is placed in. For example, to
use a channel of audio input 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 converted from the
audio input signal 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 message will be generated when the audio is above the gate threshold).
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.
statusbyte
Determines the midi message type (and channel) to use for the audio conversion value. Possible values
are between 128 and 255.
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.
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.
convert mode
Selects the mode in which to perform audio to midi conversion for the particular channel. In continuous
controller mode, audio amplitude is tracked to provide time varying continuous controller values. In
trigger mode, the audio is monitored to generate a midi message when the audio’s amplitude exceeds
the gate’s threshold, with a respective counter-message generated when the audio falls back below the
gate’s threshold. Typically, trigger mode conversion is used to generate note on / note off messages
from such sources as percussion sounds, etc.