If you're having issues with OctoCue receiver, here's a couple of checks that might fix things quickly:
OctoCue receiver does not support 32-bit Windows - 64-bit Windows is the only PC operating system supported.
On macOS, you'll need macOS 10.15.7 (a recent Catalina version) or later.
Each receiver machine connected to show needs to have a unique name; two machines with the same name connected to the same show will not work correctly.
To check this:
On windows, go to
About your PCand look at the
On macOS, it's in
This restriction does not apply to computers used as presenter clickers, or those used to access the show control dashboard.
We've seen this issue if you try to install OctoCue Receiver on a 32-bit version of Windows - only 64-bit Windows is supported.
Given the 4 GB RAM limit on 32-bit Windows, we wouldn't recommend running a show on a 32-bit OS.
This can happen if you're using Receiver 1.4.0+, which supports the
PptDirect feature when running on Windows.
What typically happens is the receiver is controlling PowerPoint direct, but also still sending out keypresses - hence the double slide advance issue.
To fix this, you'll need to check your configurations files, located at
If you'd like to use
PptDirect (recommended for better video playback compatibility):
keypress.json, make sure
useKeyPressis set to
usePptDirectis also set to
In this configuration, OctoCue will use
PptDirect when the OctoCue PowerPoint plugin is detected, but revert to emulated keypresses at all other times, so it can still control Keynote, Google Slides etc.
If either of these are set to
true, they'll always be active - hence the chance of double clicks occurring.
For full details of all the configuration settings available in OctoCue Receiver, see the Advanced configuration page.
On 11 Feb 2022, we noticed that Prezi running on Chrome 98 does not react to OctoCue clicks correctly. We're currently investigating this issue.
As a temporary workround, please run Prezi presentations in Microsoft Edge (tested on 98.0.1108.50).
May 2022: We've seen some issues with slow clicks on Windows. See this article for details and options.
We've seen a couple of issues of slow click response times on macOS. If you think you're having this issue, check your log files by right-clicking on the tray icon and selecting
View event logs.
On OctoCue Receiver 1.4.x or later, a typical click event looks like:
These times will normally be less than 500ms, but we've seen some very slow times (>2,000ms) on macOS 10.14 (Mojave) and earlier versions of 10.15 (Catalina).
In all cases, updating to the latest version of Catalina (or up to 11.x Big Sur) have fixed the issues.
We've seen some instances where the
Accessibility app permission fails to apply correctly in macOS.
[error] undefined entries in the receiver log:
To fix this we need to remove and re-add the
- Go to
Security & Privacy,
OctoCue Receiverfrom the list using the
OctoCue Receiverusing the
+button and browsing to your copy of
- Close and restart
We've only seen this on a small number of machines, and don't have good information on why this happens - if you've experienced this issue, we'd appreciate you dropping us a quick email and letting us know.
For an overview of app permission settings in macOS, see the macOS installation guide
Apple Script is the technology that OctoCue Receiver uses to emulate keypresses on macOS.
To test your Apple Script functions, we're going to run a couple of simple one-line Apple Script programs from the command line.
Before running test, please check the following:
- Your macOS version, which should be 10.15.7 or later
- That you've granted all the relevant permissions to OctoCue Receiver - both
- First, open a terminal window - first
spacebarto open spotlight, type
terminaland hit enter.
The first test is a simple function test. At the command prompt, run the following:
You should see the following dialog appear.
OK to close the window.
The next test will emulate a keypress:
You may get asked to grant the accessibility permission to the
Terminal application - see here for details
This command should output an
a character on your command line: