A tool for creating custom external midi rules
Posted: Wed Mar 24, 2010 7:34 am
Dear Astinov,
I've finished writing a little Java application for myself which presents a Graphical user interface to create custom rulesets for the 4 external midis.
What it does:
It parses the expressionlist.tpk file to include all the possible techniques, articulations and conditions (and I also added some which were not in that file, like under-slur).
It presents a list of the rules for each external midi port/midi channel. The user can add rules&remove rules, and move rules around with the click of a button. For each rule it presents in a list the conditions that apply to that rule (ex. if the articulation is staccato), and the actions that rule will take (ex. keyswitch 24 before the note). Conditions and actions can be added/removed from a list with the click of a button. It also maintains an instrumentlist so the user can remember easily which port/channel uses which patch.
It can read/write the .prules files, but it doesn't touch any other files, besides the parsing of the expressionlist (so my custom expressions also show up automaticaly if I change them).
Now the questions is, can I release it to the public, or would you guys have a problem with that?
I've finished writing a little Java application for myself which presents a Graphical user interface to create custom rulesets for the 4 external midis.
What it does:
It parses the expressionlist.tpk file to include all the possible techniques, articulations and conditions (and I also added some which were not in that file, like under-slur).
It presents a list of the rules for each external midi port/midi channel. The user can add rules&remove rules, and move rules around with the click of a button. For each rule it presents in a list the conditions that apply to that rule (ex. if the articulation is staccato), and the actions that rule will take (ex. keyswitch 24 before the note). Conditions and actions can be added/removed from a list with the click of a button. It also maintains an instrumentlist so the user can remember easily which port/channel uses which patch.
It can read/write the .prules files, but it doesn't touch any other files, besides the parsing of the expressionlist (so my custom expressions also show up automaticaly if I change them).
Now the questions is, can I release it to the public, or would you guys have a problem with that?