e9925248
New member
This yields to follow up questions:One approach would be to have a line VelocitySensitive=Y (or N, standard if not present) for the stops/ranks just like we have the Percussive effect. Then for those stops that have Y one need to not throw away the velocity information like (I think) GO does at the moment in the MIDI processing.
* How should GO map a velocity to a sample volume?
* How does this integrate with the "second touch" velocity settings in GO?
* What if the volume changes during key press?
* What volume to use, if a sample is triggered multiple times (eg. via couplers and direct)?
* What to do, if a sample is triggered by a turning a coupler on, because a key is already pressed?
I want to first discuss the above questions, before integrating this.I'd like to have a feature to select which attack sample is played depending on the velocity of the attack (and not chosen randomly), but that's perhaps a bit far out...