diff options
| author | Paul Davis <paul@linuxaudiosystems.com> | 2015-11-29 11:58:31 -0500 |
|---|---|---|
| committer | Paul Davis <paul@linuxaudiosystems.com> | 2015-11-29 11:58:36 -0500 |
| commit | 149f6795bb3272aa31cf3dc5276667fb7454e7e3 (patch) | |
| tree | cdcb7857fcfc9fc2242a7ad7aa5671c961dc02e5 /libs | |
| parent | 73d1de3b75172115beb6a30edacb4861893d97fd (diff) | |
no-op: add comment to faderport button ID definitions
Diffstat (limited to 'libs')
| -rw-r--r-- | libs/surfaces/faderport/faderport.h | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/libs/surfaces/faderport/faderport.h b/libs/surfaces/faderport/faderport.h index 8f920dfc4f..fc656d7f2a 100644 --- a/libs/surfaces/faderport/faderport.h +++ b/libs/surfaces/faderport/faderport.h @@ -106,6 +106,18 @@ class FaderPort : public ARDOUR::ControlProtocol, public AbstractUI<FaderPortReq boost::shared_ptr<ARDOUR::Port> input_port(); boost::shared_ptr<ARDOUR::Port> output_port(); + /* In a feat of engineering brilliance, the Presonus Faderport sends + * one button identifier when the button is pressed/released, but + * responds to another button identifier as a command to light the LED + * corresponding to the button. These ID's define what is sent + * for press/release; a separate data structure contains information + * on what to send to turn the LED on/off. + * + * One can only conclude that Presonus just didn't want to fix this + * issue because it contradicts their own documentation and is more or + * less the first thing you discover when programming the device. + */ + enum ButtonID { Mute = 18, Solo = 17, |