Specifications
converter 1.5
2000 - 2005 urr Sound Technologies Inc.
91
I just booted up converter, and when I transmit midi messages from the external midi controller,
converter appears to be receiving a corrupted midi stream (and/or the undefined data and data
code display in the system status wedge flashes and shows data codes which are ‘invalid’)
This means that converter hasn’t received a statusbyte yet from the midi input port, because the device
sending the midi stream to converter is in running status mode and is assuming converter caught the
initial statusbyte for the midi stream, which it hasn’t (because it wasn’t running or connected at that
point). Without an initial statusbyte to tell converter what the data stream represents, converter will be
unable to interpret and process the midi data. For example, if a midi controller was on and had been
used (keys pressed or modulation wheel moved) before converter was loaded or connected to via the
midi ports, converter missed the initial statusbyte that the controller had already transmitted to define its
midi stream. This situation will happen more often with consumer midi controllers which only transmit a
running status of note on messages without using the note off midi message to turn off voices (instead,
note on velocity 0). To resend a statusbyte from the midi controller, either move the modulation or
pitchbend wheel, press a patch select button, or (with more limited midi devices) turn off / turn on your
midi controller.
When I program the midi processor to convert or transform a midi message, nothing happens!
Make sure that:
•
converter is operating in a mode which enables midi input (see ‘software configuration’ for
more information)
•
the midi processor is enabled ( in the realtime engine settings menu – [Alt]-[E] )
•
the # of operations parameter in the program setting menu for your midi processor program is
set to the number of operations you’ve programmed, and not zero (which would mean none of
the operations are performed)
•
the # of byte checks and/or # of transforms parameter in the operation settings menu for the
operation(s) you have programmed is set to the number of byte checks / transforms you are
using for the operation, and not zero (which would mean none of the byte checks / transforms
are performed)
When I use the ‘do not xmit’ operand in the midi processor, the message still gets transmitted!
See the last two points from the above question, concerning the # of operations in the program settings
menu etc.
When I use unprocessed echo option in operation settings, I get stuck notes!
With note on and note off messages, it is important to have the proper number of note off messages to
accompany the number of note on messages generated by converter; it is also important that the note
off messages match the same note # and octave as the note on messages. The midi message texbox
is a useful tool to see what midi messages are actually being transmitted, and therefore catch any
programming errors. When unprocessed echo is used for an operation processing a note on message,
the resulting output stream will contain two note on messages (even if they are for the same note # and
octave). It is important, therefore, that two accompanying note off messages are transmitted to ensure
that both notes are actually turned off. This can be done by using another operation to process note off
messages with the unprocessed echo option turned on as well (thereby creating the second note off
message).