|
Modify MIDI events by expression
|
Previous Top Next |
| This optional field expects a boolean expression in a C like script language. By default all events are matching (that also match given channels).
|
| If filled then only matching events are modified by the modification expression.
|
| See more about MIDI event condition expressions written in gnscript syntax in page gnscript condition expressions syntax including examples.
|
| Hint: Use function Seek MIDI events by conditions (for experts) from menu analyse to test the condition expression.
|
| This field expects one or more expressions that modify current ev. if or switch might be used to conditionally modify events by certain criterias.
|
| Multiple statements must be separated by semicolon (;).
|
| See more about MIDI event modifiction expressions written in gnscript syntax in page gnscript event modification expression syntax including examples.
|
| Enter optional channel, optional condition and modification expression and use button run to start the modification.
|
| errors are displayed in the box below the modification edit box (in English language).
|
| Open a *.dlg text file to load previously stored settings for the dialog
|
| Saves current dialog settings into a .dlg text file for future reuse
|
| If searching and modification is successful then number of matching events and number of modified events will be displayed in the box below the condition.
|
| closes the dialog and generates a MIDI file opened in GNMIDI which contains the modifications done by the gnscript expressions.
|
| will show this page (also F1 key). Use also gnscript package at https://www.gnmidi.com to learn from script examples.
|
| If programming is too difficult for you then we can also offer to program user tools for your special purpose that can be used directly in GNMIDI.
|
| It can analyse or modify or generate MIDI files.
|
| In fact in most cases we can use the gnscript language for implementation.
|