1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
### The `wininput` backend
This backend allows using the mouse and keyboard as input and output channels on a Windows system.
For example, it can be used to create hotkey-like behaviour (by reading keyboard input) or to control
a computer remotely.
As Windows merges all keyboard and mouse input into a single data stream, no fine-grained per-device
access (as is available under Linux) is possible.
#### Global configuration
This backend does not take any global configuration.
#### Instance configuration
This backend does not take any instance-specific configuration.
#### Channel specification
The mouse is exposed as two channels for the position (with the origin being the upper-left corner of the desktop)
* `mouse.x`
* `mouse.y`
as well as one channel per mouse button
* `mouse.lmb`: Left mouse button
* `mouse.rmb`: Right mouse button
* `mouse.mmb`: Middle mouse button
* `mouse.xmb1`: Extra mouse button 1
* `mouse.xmb2`: Extra mouse button 2
All keys that have an [assigned virtual keycode](https://docs.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes)
are mappable as MIDIMonster channels using the syntax `key.<keyname>`, with *keyname* being one of the following specifiers:
* One of the keynames listed below (e.g., `key.enter`)
* For "simple" keys (A-z, 0-9, etc), simply the key glyph (e.g. `key.a`)
* A hexadecimal number specifying the virtual keycode
Keys are pressed once the normalized event value is greater than `0.9`, and released if under that.
The following keynames are defined in an internal mapping table:
| Key name | Description | Key name | Description |
|-------------------------------|-----------------------|-------------------------------|-----------------------|
| `backspace` | | `tab` | |
| `clear` | | `enter` | |
| `shift` | | `control` | |
| `alt` | | `capslock` | |
| `escape` | | `space` | |
| `pageup`, `pagedown` | | `end` | |
| `home` | | `pause` | |
| `numlock` | | `scrolllock` | |
| `insert` | | `delete` | |
| `printscreen` | | `up`, `down`, `left`, `right` | |
| `select` | | `print` | |
| `execute` | | `help` | |
| `apps` | | `sleep` | |
| `num0` - `num9` | | `multiply` | |
| `plus` | | `comma` | |
| `minus` | | `dot` | |
| `divide` | | `f1` - `f24` | |
| `lwin`, `rwin` | | `lshift`, `rshift` | |
| `lctrl`, `rctrl` | | `lmenu`, `rmenu` | |
| `previous`, `next` | Browser controls | `refresh` | Browser controls |
| `stop` | Browser controls | `search` | Browser controls |
| `favorites` | Browser controls | `homepage` | Browser controls |
| `mute` | | `voldown`, `volup` | |
| `nexttrack`, `prevtrack` | | `stopmedia`, `togglemedia` | |
| `mediaselect` | | `mail` | |
| `app1`, `app2` | | `zoom` | |
Example mappings:
```
generator.x > wi1.mouse.x
input.a > wi1.key.a
input.X > wi1.key.escape
```
Joystick and gamepad controllers with up to 32 buttons and 6 axes plus POV hat can be mapped as inputs to the
MIDIMonster. When starting up, the MIDIMonster will output a list of all connected and usable game controllers.
Controllers can be mapped using the syntax
* `joy<n>.<axisname>` for axes, where `<n>` is the ID of the controller and `<axisname>` is one of
* `x`, `y`: Main joystick / analog controller axes
* `z`: Third axis / joystick rotation
* `r`: Fourth axis / Rudder controller / Slider
* `u`, `v`: non-specific fifth/sixth axis
* `joy<n>.button<b>` for buttons, with `<n>` again being the controller ID and `b` being the button number between
1 and 32 (the maximum supported by Windows)
Use the Windows game controller input calibration and configuration tool to identify the axes and button IDs
relevant to your controller.
For button channels, the channel value will either be `0` or `1.0`, for axis channels it will be the normalized
value of the axis (with calibration offsets applied), with the exception of the POV axis, where the channel value
will be in some way correlated with the direction of view.
Example mappings:
```
input.joy1.x > movinghead.pan
input.joy1.y > movinghead.tilt
input.joy1.button1 > movinghead.dim
```
#### Known bugs / problems
Joysticks can only be used as input to the MIDIMonster, as Windows does not provide a method to emulate
Joystick input from user space. This is unlikely to change.
Keyboard and mouse input is subject to UIPI. You can not send input to applications that run at a higher
privilege level than the MIDIMonster. This limitation is by design and will not change.
Due to inconsistencies in the Windows API, mouse position input and output may differ for the same cursor location.
This may be correlated with the use and arrangement of multi-monitor desktops. If you encounter problems with either
receiving or sending mouse positions, please include a description of your monitor alignment in the issue.
Some antivirus applications may detect this backend as problematic because it uses the same system
interfaces to read keyboard and mouse input as any malicious application would. While it is definitely
possible to configure the MIDIMonster to do malicious things, the code itself does not log anything.
You can verify this by reading the backend code yourself.
|
