... It does require a freeware prog called "KeyKit
" though so not ideal - most people will probably be using Bome anyway...
... which is a big mistake from musicians and programmers point of view! Any music software which would add "external .exe running support", e.g. to send internal midi data to this external keykit.exe can only win in the long term. To find out why you have to look to KeyKit or better lowkey.exe in more detail.
The available method *now* is
1. to export from any application some midi phrase/file/piece/events
2. then process them with lowkey.exe
3. reimport the output of lowkey back into the original (music) application into the same position (which is often not so easy to accomplish)
4. automate the whole process via AutoHotkey
Better would be if the original software could internally output into some temp directory some subdata of it's internal data representation, then link some external .exe to work on this data, resaving it with the same name, replace the original data with this "external processed data".
This would also have the nice sideeffect that 100s or 1000s of users would develop their own "open source" midi processing tools/algorithms/ideas which are nowhere available so far in this way.
Such processing tools would even support any host which support this processing chain! (e.g. Live, Logic, Cubase, ...) But this is too easy to implement, so let's forget this idea again.