Mac Dictation Shows Nothing? Check the Language Download

If Mac dictation produces no text, first find the failed stage: shortcut → microphone → recognition → cleanup → insertion. A missing language model can stop on-device recognition, but a moving orb alone does not prove that a language download is the fix.

For Apple’s built-in Dictation, start in System Settings → Keyboard → Dictation. For Ducduc’s Dictation language unavailable card, use its language action, which differs between the classic engine and the newer macOS 26 engine. This maker-authored guide explains both paths without treating every empty input as a model problem.

Identify the symptom before reinstalling anything

Symptom	Check first	What it tells you
Pressing the key shows no listening UI	Shortcut, app running, key conflict	Recording may never have started
Listening starts, but the level stays flat	Input device, input volume, Microphone permission	Recognition has little or no usable sound
Level moves, no raw text; language-unavailable card	Speech Recognition permission, language, local model, engine availability	Audio capture can work while recognition fails
History has text; cleanup reports failure	Network, provider configuration, quota or local model	Recognition already succeeded
History has text; cursor gets nothing	Focus, Accessibility permission, secure input, copy card	Delivery can fail independently of recognition

A level meter reacting to your voice confirms only that some audio is arriving. It does not establish Speech Recognition permission or the ability to insert text.

If Apple’s built-in Dictation is failing

Follow Apple’s troubleshooting checklist: confirm Dictation is enabled, choose the language and region you speak, check its shortcut, and select a working microphone with sufficient input volume. Test in an ordinary Notes document with the cursor in the body.

When Voice Control is on, standard Dictation is unavailable; Apple’s Dictation guide explains that distinction. Check the text beneath Dictation in Keyboard settings to see whether your configuration uses on-device processing or requires a connection. Do not assume every language, field and hardware combination works offline.

If the key launches another tool or Siri, use the fn/Globe conflict guide. You do not need another app merely to confirm the microphone, shortcut and language settings.

Ducduc: check the requested language and permissions

In Settings → Dictation → Recognition language, Chinese (with mixed English) requests zh-CN; English requests en-US. The relevant model is for the language Ducduc requests, not necessarily your system display language or keyboard layout. Traditional Chinese output is a separate script setting.

Under System Settings → Privacy & Security, check Ducduc’s Microphone and Speech Recognition permissions. Accessibility is a separate permission used for interaction with target apps. If audio is silent, inspect Sound → Input, select the intended device, and watch the system input meter. Retest after reconnecting or changing an external microphone.

For a clean diagnosis, use one dictation tool at a time. Disabling Voice Control for a test removes a variable; its documented conflict with Apple Dictation does not by itself prove the cause of a Ducduc failure.

macOS 14–15, or the classic engine: check Dictation languages

1. Click Open Dictation Settings on Ducduc’s card, or open System Settings → Keyboard → Dictation.
2. Add or select the matching language and region under Languages. On these versions, use Edit beside the language list.
3. Keep a working connection available while macOS prepares required language assets. Returning to the app does not prove a background download is complete.
4. Start a fresh short dictation in Ducduc. If the card persists, record its exact detail text, language, Mac model and macOS version.

The classic engine requests on-device recognition. Apple documents the relationship between requiring on-device recognition and a recognizer supporting it. A supported locale is not proof that local recognition is ready on this Mac.

A language download is one useful check, not a universal repair. Transient service failures and hardware/language support can also matter. A Speech recognizer unavailable (en-US) message and repeated recognition errors warrant different evidence from a No speech detected card.

macOS 26 with the newer engine: use its model download

When Settings → Dictation → Recognition has the newer engine enabled, Ducduc can offer Download speech model. Click it and watch the progress. If installation succeeds while its card is still open, the reviewed implementation retries that dictation; if you have dismissed it, start the next session yourself.

The newer engine uses system-managed assets. Apple’s AssetInventory documentation explains that SpeechAnalyzer modules require the appropriate downloaded models. This is a separate asset path from the classic Dictation pane.

Ducduc also requests assets in the background when appropriate. While the newer path is not ready, it can use the classic engine, which has its own requirements. If installation fails or that locale is unsupported, the card explains the error and offers Open Dictation Settings. Repeatedly clicking download will not add support for an unsupported locale.

Test offline without overinterpreting the result

After preparing models online, use a harmless sentence such as “This is a local recognition test” or “这是一次本机识别测试。” These are suggested test inputs, not recorded outcomes.

1. Save your work and temporarily disconnect the Mac’s network connections.
2. In Ducduc, dictate into an ordinary Notes field.
3. Check History for recognized text separately from the cleanup status.
4. Restore the connection after the test.

A raw transcript appearing establishes that recognition worked offline in that session. It does not benchmark accuracy or prove every feature is local. If History has text but cloud cleanup fails, model installation is no longer the relevant failure for that run. If History is empty, check audio, permission, model and engine errors before concluding which one failed.

Apple’s own Dictation working offline is a useful comparison, but does not prove that a third-party app’s selected engine is ready. Platform compatibility on an Intel Mac likewise does not guarantee on-device support for every requested language. Include the processor type in a support report.

Recognition works, but cleanup or insertion fails

With no connection, cloud cleanup cannot complete. Ducduc preserves recognized text and labels the fallback; a configured local model in Hybrid mode may clean it instead. Offline mode skips Ducduc’s cloud cleanup route, but does not disable Ollama’s cloud features. For same-Mac cleanup, use a loopback endpoint, a downloaded local model and disable Ollama cloud features. The Ollama setup guide covers that separate model.

If History already has the result, check the destination instead of redownloading speech assets. Use the copy card for manual paste, then investigate Accessibility, focus changes or Secure Keyboard Entry in terminals.

Download Ducduc if its on-device recognition and reviewable text workflow fit your needs. If it remains blocked, send feedback with app/build, macOS version, processor, selected language and engine, exact error, whether the meter moves, and whether History contains text. A short redacted example is enough; private audio is not required to report the stage that failed.