-
Notifications
You must be signed in to change notification settings - Fork 281
Troubleshooting: Common Issues
Some common problems and solutions are recorded here. If you're having a problem with Plover, see if it is described here along with a solution.
Also, please make sure to check the Plover bug tracker for known reported issues.
- Running in Debug Mode
- Issues
- Open Command Prompt or Powershell
- Navigate the Plover's installation folder where you can find
plover.exeandplover_console.exe - Type
start plover_console.exe --log-level debug
- Open Terminal
- Assuming Plover in installed in your applications folder, enter this into Terminal and hit enter:
/Applications/Plover.app/Contents/MacOS/Plover --log-level debug
plover.AppImage --log-level debug
Note: Initially, Plover is set up to use your computer keyboard as a steno machine. If you have a steno machine, you'll need to configure Plover to look for your machine. See the Supported Hardware page for configuration instructions specific to your machine.
If you know your machine has been configured correctly, and Plover doesn't recognize your keyboard or steno machine:
- Confirm your keyboard or steno machine is plugged into your computer.
- On the Plover control panel, check if it states the machine is connected or disconnected.
- If it states the machine is disconnected, press the Reconnect button (this is to the right of "connected" or "disconnected" message).
- If Plover still doesn't recognize your machine, try closing and relaunching Plover.
If Plover is enabled with arpeggiating and strokes were previously registered, check that arpeggiating has not begun. Press <space> (by default) to toggle arpeggiate.
Solution: in the serial settings, uncheck "Xon/Xoff" under "Flow control". This will solve the issue where using S and W in a chord causes Plover to ignore those keys.
If you're running Plover 4.x and are missing the plugins manager or it's not working as expected, you can try manually installing plugins
By default, Plover ships with three dictionaries: main.json, commands.json and user.json. This can be a source of confusion to new users.
If two dictionaries contain the same steno strokes, Plover will use the one in the dictionary that has the highest priority.
In Plover 3.x and below, the dictionaries in the dictionary list were prioritized from the bottom up.
In Plover 4 and above, the dictionaries order is configurable, but the default is to have the highest priority dictionary at the top, and it is labeled with a star ⭐.
By default, the user.json dictionary is placed at the highest priority. If you want new strokes to go to a different dictionary by default (for example, you have your own dictionary already), make sure that the target dictionary is the highest priority.
If you have your own dictionary already, you'll probably want to remove main.json and custom.json and add your own dictionary. This includes existing stenographers and users of another theory (Magnum, Phoenix).
We do not recommend you remove the commands.json dictionary from the dictionary list. This is because Plover has some concepts that users of other steno software will not be familiar with initially. Feel free to go through commands.json, and remap strokes that you want to use in your own theory.
main.json is the core default dictionary. It is based on Mirabai Knight's own personal dictionary, which follows a StenEd-style thoery. It contains over 140,000 entries and is adequate for anyone learning stenography. Mirabai uses this dictionary professionally for her realtime work.
commands.json contains some keyboard shortcuts and Plover-specific utilities. For example, the stroke to add a new translation: TKUPT. It also contains arrow key movements, copy and paste, and more.
Have a look inside to see some sample keyboard commands that Plover can do.
user.json is a blank dictionary. By default, the user.json dictionary is the highest priority - it is the first dictionary Plover will use. When you define new strokes, they will get added to this dictionary. This means you can see which strokes you've defined yourself, instead of trying to locate them inside the default dictionaries.
- Disable AutoKey if you're getting strange behavior with Plover.
Double check the following:
- Your machine is connected
- Plover's output is set to "Enabled"
- You can see strokes in the paper tape
If nothing is "typed" when you're focused in a program like "Notepad", something may be interfering with Plover's ability to send keystrokes.
You can try:
- Running Plover as an Administrator
- If you are a Citrix user, reinstall Citrix and make sure to opt-out of app protection
- If you use a keyboard instead of a steno machine, Plover needs Assistive Device Permissions. From the Catalina version of macOS, you may need to enable both the
Ploverapp and theenvapp under Security & Privacy > Privacy > Accessibility. - Plover will not work if you are using Karabiner Elements
macOS has a feature where holding down a key brings up an accent menu. This can sometimes drop keys when typing quickly, such as TO/FPLT producing t. instead of to. To disable this, follow the instructions in this article: "How to Disable the Character Accent Menu in OS X Mountain Lion".
- IBus does not handle the very fast simulated key presses of Plover. This can result in dropped or transposed letters (
HATbecomesAHTorAT).
- Plover does not handle dynamic keyboard layout switching: see bug #298
- It's a gnome-shell bug, unfortunately there's no known workaround.