| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Use make-sensitivity-knob
|
|
This makes the MIDI controller stay in sync with the programmer state
values. It's kind of a coarse solution, though. It would be better to:
1. Only re-assert the map if the changed parameter currently appears on
the MIDI control surface
2. Only re-assert the part of the map related to the parameter
Almost as a side-effect, this enables switching between multiple control
maps. Just call 'set-midi-control-map!' on the controller with the new
map.
|
|
|
|
|
|
|
|
My control surface (A&H Xone:K2) seems to respond badly to being blasted
with note on/off events to turn its LEDs on and off: some of the LEDs
end up in the wrong state. The effect is reproducible using a small
test program using the ALSA API from C, which excludes multi-threading
problems in Starlet and buffer overruns in the ALSA device. The
controller simply doesn't cope well with large numbers of events
arriving in quick succession.
Adding a very small delay seems to completely fix the problem without
causing any noticable flicker.
|
|
This avoids a deadlock if the midi readout isn't happening for some
reason.
|
|
|
|
|
|
|
|
|
|
|
|
get-cc-value now returns #f if the position of the fader is unknown.
Some other changes were needed to accommodate that.
|
|
|
|
|
|
This removes the midi-led and midi-control classes, which only seemed to
be making things more complicated.
|
|
|
