You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor steno and add STENO_PROTOCOL = [all|txbolt|geminipr] (#17065)
* Refactor steno into STENO_ENABLE_[ALL|GEMINI|BOLT]
* Update stenography documentation
* STENO_ENABLE_TXBOLT → STENO_ENABLE_BOLT
TXBOLT is a better name but BOLT is more consistent with the
pre-existing TX Bolt related constants, which all drop the "TX " prefix
* Comments
* STENO_ENABLE_[GEMINI|BOLT|ALL] → STENO_PROTOCOL = [geminipr|txbolt|all]
* Add note on lacking V-USB support
* Clear chord at the end of the switch(mode){send_steno_chord} block
* Return true if NOEVENT
* update_chord_xxx → add_xxx_key_to_chord
* Enable the defines for all the protocols if STENO_PROTOCOL = all
* Mention how to use `steno_set_mode`
* Set the default steno protocol to "all"
This is done so that existing keymaps invoking `steno_set_mode` don't
all suddenly break
* Add data driver equivalents for stenography feature
* Document format of serial steno packets
(Thanks dnaq)
* Add missing comma
Copy file name to clipboardexpand all lines: docs/feature_stenography.md
+96-27
Original file line number
Diff line number
Diff line change
@@ -8,46 +8,107 @@ The [Open Steno Project](https://www.openstenoproject.org/) has built an open-so
8
8
9
9
Plover can work with any standard QWERTY keyboard, although it is more efficient if the keyboard supports NKRO (n-key rollover) to allow Plover to see all the pressed keys at once. An example keymap for Plover can be found in `planck/keymaps/default`. Switching to the `PLOVER` layer adjusts the position of the keyboard to support the number bar.
10
10
11
-
To use Plover with QMK just enable NKRO and optionally adjust your layout if you have anything other than a standard layout. You may also want to purchase some steno-friendly keycaps to make it easier to hit multiple keys.
11
+
To enable NKRO, add `NKRO_ENABLE = yes` in your `rules.mk` and make sure to press `NK_ON` to turn it on because `NKRO_ENABLE = yes` merely adds the possibility of switching to NKRO mode but it doesn't automatically switch to it. If you want to automatically switch, add `#define FORCE_NKRO` in your `config.h`.
12
+
13
+
You may also need to adjust your layout, either in QMK or in Plover, if you have anything other than a standard layout. You may also want to purchase some steno-friendly keycaps to make it easier to hit multiple keys.
12
14
13
15
## Plover with Steno Protocol :id=plover-with-steno-protocol
14
16
15
-
Plover also understands the language of several steno machines. QMK can speak a couple of these languages, TX Bolt and GeminiPR. An example layout can be found in `planck/keymaps/steno`.
17
+
Plover also understands the language of several steno machines. QMK can speak a couple of these languages: TX Bolt and GeminiPR. An example layout can be found in `planck/keymaps/steno`.
18
+
19
+
When QMK speaks to Plover over a steno protocol, Plover will not use the keyboard as input. This means that you can switch back and forth between a standard keyboard and your steno keyboard, or even switch layers from Plover to standard and back without needing to activate/deactivate Plover.
20
+
21
+
In this mode, Plover expects to speak with a steno machine over a serial port so QMK will present itself to the operating system as a virtual serial port in addition to a keyboard.
16
22
17
-
When QMK speaks to Plover over a steno protocol Plover will not use the keyboard as input. This means that you can switch back and forth between a standard keyboard and your steno keyboard, or even switch layers from Plover to standard and back without needing to activate/deactivate Plover.
23
+
> Note: Due to hardware limitations, you might not be able to run both a virtual serial port and mouse emulation at the same time.
18
24
19
-
In this mode Plover expects to speak with a steno machine over a serial port so QMK will present itself to the operating system as a virtual serial port in addition to a keyboard. By default QMK will speak the TX Bolt protocol but can be switched to GeminiPR; the last protocol used is stored in non-volatile memory so QMK will use the same protocol on restart.
25
+
!> Serial stenography protocols are not supported on [V-USB keyboards](compatible_microcontrollers#atmel-avr).
20
26
21
-
> Note: Due to hardware limitations you may not be able to run both a virtual serial port and mouse emulation at the same time.
27
+
To enable stenography protocols, add the following lines to your `rules.mk`:
28
+
```mk
29
+
STENO_ENABLE = yes
30
+
```
22
31
23
32
### TX Bolt :id=tx-bolt
24
33
25
-
TX Bolt communicates the status of 24 keys over a very simple protocol in variable-sized (1-5 byte) packets.
34
+
TX Bolt communicates the status of 24 keys over a simple protocol in variable-sized (1–4 bytes) packets.
26
35
27
-
### GeminiPR :id=geminipr
36
+
To select TX Bolt, add the following lines to your `rules.mk`:
37
+
```mk
38
+
STENO_ENABLE = yes
39
+
STENO_PROTOCOL = txbolt
40
+
```
28
41
29
-
GeminiPR encodes 42 keys into a 6-byte packet. While TX Bolt contains everything that is necessary for standard stenography, GeminiPR opens up many more options, including supporting non-English theories.
42
+
Each byte of the packet represents a different group of steno keys. Determining the group of a certain byte of the packet is done by checking the first two bits, the remaining bits are set if the corresponding steno key was pressed for the stroke. The last set of keys (as indicated by leading `11`) needs to keep track of less keys than there are bits so one of the bits is constantly 0.
30
43
31
-
## Configuring QMK for Steno :id=configuring-qmk-for-steno
44
+
The start of a new packet can be detected by comparing the group “ID” (the two MSBs) of the current byte to that of the previously received byte. If the group “ID” of the current byte is smaller or equal to that of the previous byte, it means that the current byte is the beginning of a new packet.
32
45
33
-
Firstly, enable steno in your keymap's Makefile. You may also need disable mousekeys, extra keys, or another USB endpoint to prevent conflicts. The builtin USB stack for some processors only supports a certain number of USB endpoints and the virtual serial port needed for steno fills 3 of them.
46
+
The format of TX Bolt packets is shown below.
47
+
```
48
+
00HWPKTS 01UE*OAR 10GLBPRF 110#ZDST
49
+
```
50
+
51
+
Examples of steno strokes and the associated packet:
GeminiPR encodes 42 keys into a 6-byte packet. While TX Bolt contains everything that is necessary for standard stenography, GeminiPR opens up many more options, including differentiating between top and bottom `S-`, and supporting non-English theories.
34
59
35
-
```make
60
+
To select GeminiPR, add the following lines to your `rules.mk`:
61
+
```mk
36
62
STENO_ENABLE = yes
37
-
MOUSEKEY_ENABLE = no
63
+
STENO_PROTOCOL = geminipr
38
64
```
39
65
40
-
In your keymap create a new layer for Plover. You will need to include `keymap_steno.h`. See `planck/keymaps/steno/keymap.c` for an example. Remember to create a key to switch to the layer as well as a key for exiting the layer. If you would like to switch modes on the fly you can use the keycodes `QK_STENO_BOLT` and `QK_STENO_GEMINI`. If you only want to use one of the protocols you may set it up in your initialization function:
66
+
All packets in the GeminiPR protocol consist of exactly six bytes, used as bit-arrays for different groups of keys. The beginning of a packet is indicated by setting the most significant bit (MSB) to 1 while setting the MSB of the remaining five bytes to 0.
41
67
42
-
```c
43
-
voideeconfig_init_user() {
44
-
steno_set_mode(STENO_MODE_GEMINI); // or STENO_MODE_BOLT
45
-
}
68
+
The format of GeminiPR packets is shown below.
69
+
```
70
+
1 Fn #1 #2 #3 #4 #5 #6
71
+
0 S1- S2- T- K- P- W- H-
72
+
0 R- A- O- *1 *2 res1 res2
73
+
0 pwr *3 *4 -E -U -F -R
74
+
0 -P -B -L -G -T -S -D
75
+
0 #7 #8 #9 #A #B #C -Z
46
76
```
47
77
48
-
Once you have your keyboard flashed launch Plover. Click the 'Configure...' button. In the 'Machine' tab select the Stenotype Machine that corresponds to your desired protocol. Click the 'Configure...' button on this tab and enter the serial port or click 'Scan'. Baud rate is fine at 9600 (although you should be able to set as high as 115200 with no issues). Use the default settings for everything else (Data Bits: 8, Stop Bits: 1, Parity: N, no flow control).
78
+
Examples of steno strokes and the associated packet:
On the display tab click 'Open stroke display'. With Plover disabled you should be able to hit keys on your keyboard and see them show up in the stroke display window. Use this to make sure you have set up your keymap correctly. You are now ready to steno!
83
+
### Switching protocols on the fly :id=switching-protocols-on-the-fly
84
+
85
+
If you wish to switch the serial protocol used to transfer the steno chords without having to recompile your keyboard firmware every time, you can press the `QK_STENO_BOLT` and `QK_STENO_GEMINI` keycodes in order to switch protocols on the fly.
86
+
87
+
To enable these special keycodes, add the following lines to your `rules.mk`:
88
+
```mk
89
+
STENO_ENABLE = yes
90
+
STENO_PROTOCOL = all
91
+
```
92
+
93
+
If you want to switch protocols programatically, as part of a custom macro for example, don't use `tap_code(QK_STENO_*)`, as `tap_code` only supports [basic keycodes](keycodes_basic). Instead, you should use `steno_set_mode(STENO_MODE_*)`, whose valid arguments are `STENO_MODE_BOLT` and `STENO_MODE_GEMINI`.
94
+
95
+
The default protocol is Gemini PR but the last protocol used is stored in non-volatile memory so QMK will remember your choice between reboots of your keyboard — assuming that your keyboard features (emulated) EEPROM.
96
+
97
+
Naturally, this option takes the most amount of firmware space as it needs to compile the code for all the available stenography protocols. In most cases, compiling a single stenography protocol is sufficient.
98
+
99
+
The default value for `STENO_PROTOCOL` is `all`.
100
+
101
+
## Configuring QMK for Steno :id=configuring-qmk-for-steno
102
+
103
+
After enabling stenography and optionally selecting a protocol, you may also need disable mouse keys, extra keys, or another USB endpoint to prevent conflicts. The builtin USB stack for some processors only supports a certain number of USB endpoints and the virtual serial port needed for steno fills 3 of them.
104
+
105
+
!> If you had *explicitly* set `VIRSTER_ENABLE = no`, none of the serial stenography protocols (GeminiPR, TX Bolt) will work properly. You are expected to either set it to `yes`, remove the line from your `rules.mk` or send the steno chords yourself in an alternative way using the [provided interceptable hooks](#interfacing-with-the-code).
106
+
107
+
In your keymap, create a new layer for Plover, that you can fill in with the [steno keycodes](#keycode-reference) (you will need to include `keymap_steno.h`, see `planck/keymaps/steno/keymap.c` for an example). Remember to create a key to switch to the layer as well as a key for exiting the layer.
108
+
109
+
Once you have your keyboard flashed, launch Plover. Click the 'Configure...' button. In the 'Machine' tab, select the Stenotype Machine that corresponds to your desired protocol. Click the 'Configure...' button on this tab and enter the serial port or click 'Scan'. Baud rate is fine at 9600 (although you should be able to set as high as 115200 with no issues). Use the default settings for everything else (Data Bits: 8, Stop Bits: 1, Parity: N, no flow control).
110
+
111
+
To test your keymap, you can chord keys on your keyboard and either look at the output of the 'paper tape' (Tools > Paper Tape) or that of the 'layout display' (Tools > Layout Display). If your strokes correctly show up, you are now ready to steno!
51
112
52
113
## Learning Stenography :id=learning-stenography
53
114
@@ -60,7 +121,7 @@ On the display tab click 'Open stroke display'. With Plover disabled you should
60
121
The steno code has three interceptable hooks. If you define these functions, they will be called at certain points in processing; if they return true, processing continues, otherwise it's assumed you handled things.
This function is called when a chord is about to be sent. Mode will be one of `STENO_MODE_BOLT` or `STENO_MODE_GEMINI`. This represents the actual chord that would be sent via whichever protocol. You can modify the chord provided to alter what gets sent. Remember to return true if you want the regular sending process to happen.
This function is called when a keypress has come in, before it is processed. The keycode should be one of `QK_STENO_BOLT`, `QK_STENO_GEMINI`, or one of the `STN_*` key values.
This function is called after a key has been processed, but before any decision about whether or not to send a chord. If `IS_PRESSED(record->event)` is false, and `pressed` is 0 or 1, the chord will be sent shortly, but has not yet been sent. This is where to put hooks for things like, say, live displays of steno chords or keys.
139
+
This function is called after a key has been processed, but before any decision about whether or not to send a chord. This is where to put hooks for things like, say, live displays of steno chords or keys.
140
+
141
+
If `IS_PRESSED(record->event)` is false, and `n_pressed_keys` is 0 or 1, the chord will be sent shortly, but has not yet been sent. This relieves you of the need of keeping track of where a packet ends and another begins.
142
+
143
+
The `chord` argument contains the packet of the current chord as specified by the protocol in use. This is *NOT* simply a list of chorded steno keys of the form `[STN_E, STN_U, STN_BR, STN_GR]`. Refer to the appropriate protocol section of this document to learn more about the format of the packets in your steno protocol/mode of choice.
79
144
145
+
The `n_pressed_keys` argument is the number of physical keys actually being held down.
146
+
This is not always equal to the number of bits set to 1 (aka the [Hamming weight](https://en.wikipedia.org/wiki/Hamming_weight)) in `chord` because it is possible to simultaneously press down four keys, then release three of those four keys and then press yet another key while the fourth finger is still holding down its key.
147
+
At the end of this scenario given as an example, `chord` would have five bits set to 1 but
148
+
`n_pressed_keys` would be set to 2 because there are only two keys currently being pressed down.
80
149
81
150
## Keycode Reference :id=keycode-reference
82
151
83
-
As defined in `keymap_steno.h`.
152
+
You must include `keymap_steno.h` to your `keymap.c` with `#include "keymap_steno.h"` before you can use these keycodes
84
153
85
154
> Note: TX Bolt does not support the full set of keys. The TX Bolt implementation in QMK will map the GeminiPR keys to the nearest TX Bolt key so that one key map will work for both.
86
155
@@ -124,10 +193,10 @@ As defined in `keymap_steno.h`.
124
193
|`STN_SR`|`STN_SR`| `-S`|
125
194
|`STN_DR`|`STN_DR`| `-D`|
126
195
|`STN_ZR`|`STN_ZR`| `-Z`|
127
-
|`STN_FN`|| (GeminiPR only)|
128
-
|`STN_RES1`||(GeminiPR only)|
129
-
|`STN_RES2`||(GeminiPR only)|
130
-
|`STN_PWR`||(GeminiPR only)|
196
+
|`STN_FN`|| (Function)|
197
+
|`STN_RES1`||(Reset 1)|
198
+
|`STN_RES2`||(Reset 2)|
199
+
|`STN_PWR`||(Power)|
131
200
132
201
If you do not want to hit two keys with one finger combined keycodes can be used. These are also defined in `keymap_steno.h`, and causes both keys to be reported as pressed or released. To use these keycodes define `STENO_COMBINEDMAP` in your `config.h` file.
0 commit comments