Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

The Ekdahl FAR - Command language: Difference between revisions

From KNAS Wiki
No edit summary
No edit summary
Line 140: Line 140:


'''FAR < 1.1:'''
'''FAR < 1.1:'''
<pre>
The ''command'' responsible for mapping ''command strings'' to different ''MIDI messages'' is ''midieventhandler'' or ''mev'' for short. The first ''parameter'' of ''mev'' is the type of ''MIDI message'' that we want to remap


* '''''noteon''''' - Note on
'''FAR < 1.1'''
* '''''noteoff''' -'' Note off
* '''''pat''' -'' Poly after touch
The ''command'' responsible for mapping ''command strings'' to different ''MIDI messages'' is 'midieventhandler' or 'mev' for short. The first ''parameter'' of 'mev' is the type of ''MIDI message'' that we want to remap
* '''''cat''''' - Channel after touch
* '''''pb''''' - Pitch bend
* '''noteon''' - Note on
* '''''pc''''' - Program change
* '''noteoff''' - Note off
* '''''cc''''' - Continuous controller
* '''pat''' - Poly after touch
* '''cat''' - Channel after touch
* '''pb''' - Pitch bend
* '''pc''' - Program change
* '''cc''' - Continuous controller
The second ''parameter'' is the ''command string'' that is to be associated with the ''MIDI Message'' - with the exception of the '''cc'''-type, here the second ''parameter'' is the ''controller number'' (0 - 127) and the third ''parameter'' is the ''command string''.


The second ''parameter'' is the ''command string'' that is to be associated with the ''MIDI Message'' - with the exception of the ''cc''-type, here the second ''parameter'' is the ''controller number'' (0 - 127) and the <u>third</u> ''parameter'' is the ''command string''.
'''FAR 1.1'''
</pre>
The ''commands'' responsible for mapping ''command strings'' to different ''MIDI messages'' are as follows
* '''noteon/non''':''commands'' - Sets the ''commands'' executed for a 'note on' ''MIDI message''
* '''noteoff/nof''''':commands'' - Sets the commands executed for a 'note off' ''MIDI message''
* '''polyaftertouch/pat''''':commands'' - Sets the commands executed for a 'poly aftertouch' ''MIDI message''
* '''channelaftertouch/cat''''':commands'' - Sets the commands executed for a 'channel aftertouch' ''MIDI message''
* '''pitchbend/pb''''':commands'' - Sets the commands executed for a 'pitch bend' ''MIDI message''
* '''programchange/pc''''':commands'' - Sets the commands executed for a 'program change' ''MIDI message''
* '''continuouscontrollerdata/ccd''''':controller:commands'' - Sets the ''commands'' executed for 'continuous controller' no ''controller''


<pre>
'''FAR 1.1:'''
The ''commands'' responsible for mapping ''command strings'' to different ''MIDI messages'' are as follows
* '''noteon/non''''':commands'' - Sets the commands executed for a ''note on'' ''MIDI message''
* '''noteoff''/nof'''''<nowiki/>'':commands'' - Sets the commands executed for a ''note off MIDI message''
* '''polyaftertouch/pat''''':commands'' - Sets the commands executed for a ''poly aftertouch MIDI message''
* '''channelaftertouch/cat''''':commands'' - Sets the commands executed for a ''channel aftertouch MIDI message''
* '''pitchbend/pb''''':commands'' - Sets the commands executed for a ''pitch bend MIDI message''
* '''programchange/pc''''':commands'' - Sets the commands executed for a ''program change MIDI message''
* '''continuouscontrollerdata/ccd''''':controller:commands'' - Sets the commands executed for ''continuous controller'' no ''controller''
</pre>


We can of course use the ''rqi''-command to check the current mapping, below we are asking what the current ''command string'' associated with the ''pitch bend'' ''MIDI message'' is<pre>
We can of course use the ''rqi''-command to check the current mapping, below we are asking what the current ''command string'' associated with the ''pitch bend'' ''MIDI message'' is<pre>