Event Processors

Event Processors can manipulate and analyse incoming Midi, but also create Midi events based on incoming Midi.
Prominent Event Processors are Arpeggiator and Chorder; you can find a complete summary here.
Using Lua, you can even design your own Event Processors, in this case called Script Processors.
There are already many Script processor examples included in Falcon, but also some available on the Internet.
UVI Soundware partly uses Script Processors, and graphics not included in Falcon.

Basics

Event Processors are working in a serial way.
Example:

• Load two Arpeggiators, both on the same hierarchy level.
• The first one will modify an incoming note into some rhythmically played notes.
• The second one will then do the same for each of the notes the first Arpeggiator has produced.

You can add Event Processors on Program and on Layer level.  

• If more than one Event Processor are active, the leftmost is served first, then it hands its processed data over to the next Event Processor on its right side, and so on:
• the rightmost Event Processor on Program level hands over its processed data to all leftmost Layer Event Processors.
• the rightmost Event Processor on Layer level hands over its processed data to all Keygroups of this Layer.
  
  
• Its a good idea to have dedicated folders when you make Script Processor presets. The default file path for all Script Processors is ...UVI/Falcon/User Presets/Event Processors, and the extension is just '*.Preset' (for all Script Processors).  
  If you save all presets in the same folder its  unclear what preset is associated with what Script Processor device.
  
  
• Midi CC events and AT created by Event Processors on Layer level will not be processed.
  Concerned are: Arpeggiator, Midi CC Lfo, Polyphonic Seq (Poly AT), Step Line.
  If you want to use Midi CC sequences, you can only use it on Program level.
  Arpeggiator has one Midi CC sequence (CC freely eligible), Step Line has two (CC1 and CC2); Polyphonic Seq has one Poly AT sequence.