so im going to describe this midi issue, something Id like to do , but im not really sure how you would like midihub to attempt to solve it … so what modifiers might be need or not .
I have a synth engine that does not support a sustain pedal (CC64),
what Id like to do to put the sustain handling in the midihub basically by ‘withholding’ midi off messages.
CC64 > 0 : start caching note numbers for note_off (you can delete duplicates)
CC == 0 : send note offs for all held off. (I don’t think anyone cares about release velocities)
note: when a sustain pedal is lifted if only clears those notes that are not actively held, hence why we ‘cache’ note_off numbers.
so I can imagine this as a ‘simple modifier’ dedicated to the purpose,
OR perhaps this is an example where a scriptable/user created ‘modifier’ is preferable,
since its quite a specific user request, not sure how many would find it useful
so perhaps this is the sort of things users might build for themselves?
Id even be quite happy to write this in C against an api, and compile on ARM… perhaps this could lead to users sharing modules
C is not very friendly, but Im thinking its probably the easy solution initially, as just needs compile/linking into binary going to midihub. and Id be happy to have that as a separate development environment from the midihub app (so you dont have to start shipping compilers )
so, perhaps a first step, later a more friendly scripting language perhaps could be created, if the desire.