Bome Software

Midi Translator Manual: Incoming Triggers
>Home
>Products
 >Restorator
 >ReNovator
 >Midi Translator
 >- Classic
 >- Pro
 >- Author
 >- Player
 >- Compare
 >Download
 >Purchase
 >Screenshots
 >Manual
 >Usage Examples
 >Presets
 >Forums
 >Mailing List
 >Testimonials
 >Mouse Keyboard
 >SendSX
 >CS1x-Edit
 >Delphi components
 >Tools
 >More products
>Forums
>Search
>About
>Contact me

Translators Overview
Help Contents
Translators Outgoing

Contents

Summary
Translator Options
Incoming Triggers
Outgoing Actions


Incoming Triggers

Incoming Trigger actions are events that Bomes MIDI Translator can detect and act on. Bomes MIDI Translator can recognize five different types of incoming actions.

  1. MIDI Message

    2. MIDI Messages are defined as hexidecimal values in Bomes MIDI Translator. The hex values are broken up into three parts, the first being the associated MIDI channel, the second being the controller number, and the third being the controller CC value. The most simple way of defining a new MIDI incoming action is to use the 'capture midi' feature (covered in the Quick Start guide) to capture the incoming MIDI information while you are pressing a keyboard key, turning a knob or otherwise. If you need to assign multiple values to a single translator, variables can be used.

    translator incoming - midi action


    Local variables are automatically defined in incoming MIDI message actions if the 'capture midi' checkbox is enabled and multiple values of any one control are detected. Varibles are covered more completely in the Rules section. You can use local variables (defined as double-letter pairs such as 'oo' and 'xx' in the rules section to modify the incoming values to fit your needs. You can also use global variables (defined as variables beginning with the letters 'g' or 'h') to pass variables back and forth between translators.

    Bome's MIDI Translator's online help system includes a useful HEX<->DECIMAL translator that will assist in making proper MIDI assignments.

    The following are some sample incoming MIDI string examples, along with description. For further instructions on Using Variables go to Using Rules and Variables.

Incoming Action String

MIDI Detected
BF 6F oo
Channel: 16, Controller: 111, Value: ANY
BA ww 7F
Channel: 11, Controller: ANY, Value: 127
B4 xx pp
Channel: 5, Controller: ANY, Value: ANY
B4 4E ga
Channel: 5, Controller: 78, Value: Global Variable 'A'

  1. Keystroke

    2. Keystroke-based incoming translator actions are defined by single keys and can be separted either by complete keypress cycles (down and up) or by individual 'Key Down' or 'Key Up' events. Having seperate key 'Up' and 'Down' events lets the user define separate translators that occur when a key is pressed down (for example, to enable an audio effect), and when the key is released (disable previously activated effect).
    translator incoming - key action


  2. Timer

    3. Incoming Timer actions are events that will trigger multiple times automatically depending on the Timer settings. Incoming Timer actions must be tied to an already-existing Outoing Timer Action in order to work properly. Defining Incoming Timer actions is very simple - the only option is the selection of which Timer to use. Most of the Timer options are defined in the Outgoing Timer Action screen, which is covered in the Outgoing Actions section below.
    translator incoming - timer action


  3. Preset Change

    4. Preset change incoming actions are actions that are activated when the preset is changed through some means. Preset Change Actions are useful for "one-off" type of actions that only occur once at the very beginning of the preset change. These actions are often 'reset' actions that could either redefine global variables or reset controllers to default values.
    translator incoming - preset change action


  4. Special

    5. Special Actions are actions that occur in response to program events. 'Startup' actions are best defined with Special actions such as when the project file is loaded. Certain actions that need to take place first before any other actions, and only once are best defined by using Special actions, such as Full-Screening your application and perhaps enabling recording.
    translator incoming - special action


[back to top]


Translators Overview
Help Contents
Translators Outgoing
 
(c) 1997-2008 by Bome Software
Last modified on February 8th 2008