nock
All guides

A little help2 min read

Get dictation back on track

No recording, no words, the wrong place, or the wrong spelling? Start with the part that went wrong. One small check is easier to follow than changing everything at once.

Let’s get into it
Black and white: wired earbuds plugged into a laptop under a desk lamp, with a checklist, a screwdriver and a glass of water.
Illustration for Nock
On this page 5 sections

The words are missing or in the wrong place

Click into a normal text field, such as a blank note or an email draft. Type a few words with your keyboard. This checks that the field is ready to receive text.

Leave the cursor there and dictate one short sentence. If that works, return to the app where you first noticed the problem and try the same steps.

The recording does not start

Check the dictation shortcut in Nock, especially if you have changed it. Make sure Nock has microphone permission and is using the microphone you expect.

A headset, display, or dock may bring another microphone with it. Choose the one you are speaking into, then try a short recording in a quiet place.

  • Is the intended microphone selected?
  • Is the microphone muted on the device or headset?
  • Are you using the shortcut shown in Nock?

The same word keeps coming out wrong

Add the name or term to your own words list. Project names, people’s names, and words from your work are good places to start.

Text replacements can help with phrases you use often. If the words are right but Nock changes your phrasing too much, reduce the amount of cleanup.

Cloud dictation is not returning words

Check your internet connection and available cloud allowance. Nock shows your usage, and the pricing page lists the allowance for each plan.

You can switch to on-device dictation when you want to keep writing offline. Try a short sentence first, then return to what you were doing.

Make a useful note for support

If the problem continues, describe the app you were writing in, the action you took, and what happened. Include what you expected to happen instead.

A short example and the checks you have already tried give support a clear place to start.

More in the docs 3 links