User's Manual

Table Of Contents

Bome MIDI Translator: User's Manual 10 Rules and Variables

Conditional Rule Operators:

== EQUALS (true example: IF 10 == 10 THEN)

!= DOES NOT EQUAL (true example: IF 10 != 45 THEN)

GREATER THAN OR EQUAL

(true example: IF 86 >= 45 THEN)

<= LESS THAN OR EQUAL TO (true example: IF 34 <= 34 THEN)

> GREATER THAN (true example: IF 10 > 4 THEN)

< LESS THAN (true example: IF 24 < 80 THEN)

10.3 Types of Variables

There are two main types of variables in Bome MIDI Translator: Local

variables and Global variables. Variables can be set either with incoming

actions or with rules.

The life time of a Local Variable is bound to an incoming event. A Global

variable, however, will retain it's value as long as the project in Bome MIDI

Translator is running.

10.3.1 Local Variables

Local Variables are defined by character combinations in the following

range:

oo-xx (example: pp, ss, ww, etc...).

Local variables retain their value as long as a given input event is being

processed. Once an incoming event processing is done, the local variable is

undefined. Because MIDI Translator can execute multiple incoming events

simultaneously, there are then multiple sets of the same local variable. Each

simultaneous translator will work on the local variable that is assigned to the

respective incoming event. So local variables are an easy way to ensure that

incoming events do not mess up processing of other simultaneous events

which use the same local variables.

Local variables are normally the most commonly used variables, and are

useful for holding temporary values. Local variables can be used in incoming

actions to pass, for example, a continuous controller value to the Rules

section of a Translator, where it can then be processed and resent to the

outgoing action.

Note that Local Variables are not pre-initialized: if you don't define them in

the Incoming Action, and you don't set them to a value in a Rule, a Local

Variable can have any (random) value.