fingerlight
2020-03-12 22:42:56
I use information from my faders and encoders to point to the track for parameters I want to change and to switch what's being displayed on my Ableton Live screen. For example, if I move the volume fader for track 1, then Live will display the clip view for that track. Also, movements of my delay and reverb effects faders will be directed to the delay in track 1. If I move the volume fader for track 2, the clip view in track 2 will be displayed, and movements of the effects faders will be directed to track 2.... etc.
My problem is that the volume faders might be right on the border between two values, and sometimes a spurious value change might happen as a result of a slight vibration of my controllers... say a bump or brushing a fader inadvertently. encoders.. seem to be more stable, but still may be giving me similar problems. In that case, the "target" of my effects changes is no longer correct, and the Live screen is showing me the clip view for the wrong track.
Can someone show me a simple "debouncing" algorithm that I could apply, such that it requires 2 or maybe more consecutive value change messages from a fader to cause Midi Translator to output the changes I described above. Or some other strategy that would get rid of unintentional value changes in the faders. I have many faders ( about 20 tracks) so it would be good if the algorithm were simple.
<<edit -- oops, that wouldn't work since the only time my faders send a value change message is when there is movement of the fader, so if the value changes from, say 13, to 14 and stays there, I might want to use that new value, for volume change, but it would go unnoticed.... so some other way maybe?
Thanks,
Gabriel