From 9743a87f7c4a2582b5e49c9243a6b1b69b8a7a8f Mon Sep 17 00:00:00 2001 From: Alesya Huzik Date: Sun, 22 May 2022 19:57:00 +1000 Subject: [PATCH 1/2] set evdev key threshold to 0.5 --- backends/evdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backends/evdev.c b/backends/evdev.c index 8f7c4f9..5c1e357 100644 --- a/backends/evdev.c +++ b/backends/evdev.c @@ -478,7 +478,7 @@ static int evdev_set(instance* inst, size_t num, channel** c, channel_value* v) case EV_KEY: case EV_SW: default: - value = (v[evt].normalised > 0.9) ? 1 : 0; + value = (v[evt].normalised > 0.5) ? 1 : 0; break; } From 5f7e733f7694629d19c3f6ffa3380baf3a8ffefa Mon Sep 17 00:00:00 2001 From: Alesya Huzik Date: Sun, 22 May 2022 23:17:34 +1000 Subject: [PATCH 2/2] evdev: update threshold value in the docs --- backends/evdev.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backends/evdev.md b/backends/evdev.md index e7ba3cc..5130fef 100644 --- a/backends/evdev.md +++ b/backends/evdev.md @@ -79,7 +79,7 @@ Input devices may synchronize logically connected event types (for example, X an events. The MIDIMonster also generates these events after processing channel events, but may not keep the original event grouping. -`EV_KEY` key-down events are sent for normalized channel values over `0.9`. +`EV_KEY` key-down events are sent for normalized channel values over `0.5`. Extended event type values such as `EV_LED`, `EV_SND`, etc are recognized in the MIDIMonster configuration file but may or may not work with the internal channel mapping and normalization code.