The reader isn’t perfect. While it works well for most scenes, certain tricky lines can trip it up. Fortunately, with a few small tweaks, you can usually fix the issue and keep your scene running smoothly.

Below are common reasons why a cue might not be recognized - and how to fix them.

Common causes

• Formatting Differences

  Words can be written in multiple ways. For example:

  →  “Okay” vs. “Ok”

• Homophones

  Words or phrases that sound similar can confuse the reader.

  →  “Ice scream” vs. “I scream”

• Filler Words

  Sounds like “uh,” “ah,” or “hmm” may not register properly.

The good news? Most of these issues are easy to fix yourself.

🛠️ Fixes & Workarounds

1. Match What the Reader Hears

On the right, you’ll see what the reader thinks you’re saying:

Example: You said “cigs,” but the reader hears “sec”

To fix this, change your line to match what the reader hears - in this case, replace “cigs” with “secs”.

2. Trim Filler Words

If you're using filler sounds like “uh…” or “hmm…”, they may disrupt cue detection.

Example: You say: “Uh, okay.” Reader hears: “Okay” (ignores “Uh”)

To fix it:

• Remove filler words from the cue line.
• Add a short pause (e.g. 1 second) to give yourself time to speak naturally.

3. Remove or Simplify the Line

You can delete unnecessary words - or even the entire line - and add a pause to keep the timing right.

Example: Delete “You know what I mean?” Add a 2-second pause instead.

4. Report the Line

If you’ve tried the above and the issue persists:

• Tap Report on the line.
• We’ll use your feedback to improve cue recognition for future runs.
• We’ll use the feedback to improve the speech recognition algorithm in general.