| You click it, a window flashes up and disappears, then the menu appears | That's normal. The program opens a separate window for the menu, and its own window closes straight after |
| After you press Enter the screen sits still for tens of seconds, as if it has frozen | It hasn't frozen: it's loading the speech components, which have to be read back in from disk if they haven't been used for a while. The screen shows the progress item by item (for example · 語音處理元件(scipy)… ✓ 27.2 秒, "speech-processing component (scipy) … ✓ 27.2 s"); as long as you can see that, all is well. Warming it up before the meeting avoids the wait |
| Straight after installing, features 1/3/6 say "載不起語音處理元件(scipy)" ("couldn't load the speech-processing component (scipy)") | Windows 11's Smart App Control first blocks newly installed components that don't have a cloud reputation yet (seen on one laptop, 2026-09-20). Wait a few minutes and try again — it usually lets them through on its own. To check, double-click 6_診斷.bat and see whether those lines say BLOCKED or OK; use it once they're back to OK. Feature 5 works offline and doesn't need those components, so you can still use it meanwhile |
| No captions appear at all | Check the PC is actually playing sound; for an online meeting, remember to choose 1 and not 2. The meeting app's speaker must be set to Windows' default playback device: the new Teams has no option to follow the system default, so pick the same device by hand in Teams' device settings (tested on one laptop, 2026-09-19). The "聲音來源:…" ("audio source: …") line on screen at the start shows which device is being recorded. Feature 6 is the exception: when you choose "whatever the PC is playing", set the meeting app's speaker to route ①, the one you chose in the menu, not the usual Windows default |
| You choose the microphone and the program says "沒有可用的聲音來源" ("no usable audio source") and exits | This PC has no microphone attached, or Windows privacy settings are blocking it (Settings → Privacy & security → Microphone) |
| You choose "microphone" with headphones plugged in: which microphone does it pick up? | On some PCs, plugging in headphones that have a microphone (a headset) automatically switches to the microphone on the headphones (for example laptops with a single combined headset jack), and it only switches back to the PC's microphone when you unplug them (tested on one laptop, 2026-09-19). If the headphones are plugged in but not worn and you choose "microphone", it picks up the headset mic hanging to one side: unplug the headphones, or switch back to the PC's microphone under Settings → System → Sound → Input. The screen shows which one it's using at the start (the "麥克風:…" ("microphone: …") line). If the PC has two or more microphones, the menu asks which microphone to use, and you can simply pick the PC's built-in one there |
| The transcript header says "可能不完整" ("may be incomplete") | There are six causes: ① nothing recognised in the later part of the recording (silence, music, noise) ② the same words repeated heavily, so they were dropped when the transcript was tidied up ③ a problem in one segment: a whole stretch in the later part or the middle of that segment not recognised, the two recognition passes not agreeing, or the text flooded with the same handful of sentences, over and over ④ a line the first pass heard is missing from the tidied-up text, and re-transcribing it on its own didn't bring it back (the header gives the time and the speaker) ⑤ the recording has sound, but the transcript doesn't cover that time (over 10 seconds in a row, or at least 6 seconds in total within any 30 seconds; typically English spoken in a Chinese meeting, music or applause — the header gives the time range; when the recording is noisy from start to finish and speech is hardly louder than the background, this check can't see well, and the header adds an ℹ️ note that does not count as a gap) ⑥ the times of the paragraphs overlap or go backwards (typical of very long recordings that mix several languages; the header gives the time range — listen to that stretch against the recording).
For ①, ② and "nothing in the later part of a segment", the header says which minute recognition got up to; otherwise, it names the segment and the time range where the problem is. If you need that part, cut it out and run it again on its own (for ②, ③ and ④ the header also suggests how to cut it). If it was the later part or the middle of a segment that wasn't recognised and the cut-out part comes back with content, it had been skipped; if nobody was really speaking, the result will be empty.
Passages marked as repeated were not really said that many times, so don't quote them word for word. |
| You closed the window partway through a transcription | The program deletes the temporary recording and the cloud copy before exiting. For recordings over 28 minutes, the segments already finished stay in .partial.json — rescue them with feature 5. Under 28 minutes it's processed as one segment, so closing it while recognition is still running means the whole thing has to be run again. If something goes wrong only after that segment has fully finished (a failure writing the file, say), the .partial.json is still left, so have a look on the desktop for it first |
| The network drops partway through transcribing or translating | When the connection is completely down (a Wi-Fi outage, say), the program waits for the network to come back: it tries again every 20 seconds, for up to 5 minutes, and carries on as soon as it returns (the screen says "The internet connection is back"); if the network is merely unstable and drops for a moment, it just retries a few times as before. If it is still down after 5 minutes: transcribing stops — for a recording over 28 minutes, the parts already fully transcribed still become a transcript (the header lists the missing parts); a recording of 28 minutes or less (or one that stops in its first part) produces nothing, so transcribe the whole thing again once the network is working. The exceptions: if it drops at the speaker-segmentation step, the program switches to an estimate and still finishes; if it drops while re-transcribing missed passages, those are skipped and listed in the header. Translating stops, and what has been translated is still saved, with the untranslated paragraphs marked (the same happens if you press Ctrl+C while it is waiting; if nothing has been translated yet, Ctrl+C leaves no file). When the input to translate is a recording, the transcribing and translating steps can each wait up to 5 minutes |
| The same sentence appears twice | Echo in a hybrid meeting: the meeting PC's speakers and microphone are picking each other up. Switch to headphones |
| The people in the room are captured, but not the online participants | The online participants have to be taken straight from the PC: have the caption PC join the meeting too and choose "Both" (see option 1 under hybrid meetings). Turning up the loudspeakers doesn't help |
| The caption text is too small | In the caption window, press Ctrl + + to enlarge it (you can press it repeatedly) and Ctrl + - to shrink it; there's a reminder of this on screen at the start as well. Ctrl + 0 is the official "reset size" key, but it clashes with the 自然輸入法 (Going Natural) Chinese input method, so we don't recommend it |
| The captions suddenly stop (the headset plug came loose, or it was unplugged and plugged back in) | The program reconnects automatically and shows "✓ 麥克風接回來了" ("✓ microphone reconnected") or "✓ 電腦聲音接回來了" ("✓ computer audio reconnected") (or "✓ 電腦聲音改從這顆錄:…" ("✓ computer audio is now recorded from: …") when it switches to another device); if that never appears, press Ctrl+C to stop and start again (all the captions so far are saved) |
| Chinese shows up as boxes or garbled characters | Open it with "Windows Terminal" instead (search for Terminal in the taskbar); the older Command Prompt handles Chinese fonts poorly |
| A passage in the transcript just says "(整理後的逐字稿略去了這段)" ("this passage was left out of the tidied-up transcript") | Usually that speaker said nothing but "mm" and "right" all meeting. The line is kept so that the speaker names you typed don't all shift out of line |
| The folder won't delete, saying it needs administrator rights | It's almost never a rights problem. ① Close any File Explorer window that has this folder open ② restart and delete it before anything else ③ only then double-click 8_刪不掉時救援.bat |
| The key was pasted wrong, has expired, or you want to change it | Press 9, "API key settings", in the menu: you can switch to another key, check whether the current one works, or clear the key saved on this PC |
| The screen says "API 金鑰有問題" ("there's a problem with the API key") | For live captions, first press Ctrl+C to stop, then go back to the menu and press 9 to check the key or change it. When a transcription or translation doesn't succeed, the menu checks with Google once by itself, and if that confirms the key is bad, it asks you straight away whether you want to change it |
| The screen says "Google 專案這個月的花費上限到了" ("the Google project has reached this month's spend cap") | It's not a network problem: this Google project has spent up to the monthly cap set in AI Studio, and Google pauses it until the 1st of next month. To restore it now: at aistudio.google.com, open Spend on the left → Monthly spend cap → Edit spend cap and raise the cap (this needs owner or editor access to the project; if it still can't connect after you raise it, wait a few minutes and try again). Live captions reconnect by themselves; a transcription or translation that stopped halfway has to be run again |
| Feature 6 is running, but there's no interpreter voice at all from the headphones or speakers | First check that the line at the top of the screen, "🔊 翻譯語音將從「⋯」播出" ("🔊 the translated voice will play from '…'"), names the device you're actually wearing or listening to. If it doesn't, go back to the menu, run feature 6 again and pick the right device at "where do you want to hear the interpreter"; if it does, turn that device's volume up, or check in the speaker icon at the bottom right of Windows that it isn't muted. At the end, the screen says "共送出約 N 秒到「⋯」" ("sent about N seconds to '…'") — that's how much was sent to the device, which doesn't guarantee you could hear it, so a number there doesn't prove the device is fine |
| Feature 6 with the microphone: after the speaker stops, the captions keep repeating the same sentence without stopping | The interpreter voice is coming out of the speakers and the microphone is recording it back in, so the model keeps translating its own voice — and you are charged the whole time. Press Ctrl+C to stop first; then put on headphones, pick the headphones you're wearing at "where do you want to hear the interpreter", and start again |
| No sound from the speakers after using feature 6 | Finishing normally, pressing Ctrl+C and clicking the window's X all switch back to your original speakers automatically. If it crashes or is closed from Task Manager, it switches back automatically when you return to the menu (or next time you open the menu); if you can't wait, click the speaker icon at the bottom right and pick your original speakers yourself. If you set the meeting app's (Teams/Zoom/Webex) speaker to ① as described, the program can't change that — switch it back yourself |
| Feature 6 is set up, but you can still hear the original audio | The meeting app (Teams/Zoom/Webex) has its own speaker setting. Go into its audio settings and set the speaker to route ① directly; the new Teams has no option to follow the system default, so set it before you start. Remember to switch it back to the one you normally listen on afterwards |
| Feature 6 (or feature 3 with "fast") keeps running after you press Ctrl+C | It first shows "收到 Ctrl+C,正在收尾" ("Ctrl+C received, wrapping up"), and takes about 3–5 seconds to save the files before it ends. You can also end it at that point with the X in the top-right corner of the window, but the tidied-up .md won't be produced (the word-for-word .txt is still there), and the menu closes as well; feature 6's sound output still switches back automatically |
| You want to know what's actually wrong | Double-click 6_診斷.bat and it lists whether Python, the packages, ffmpeg, the key and the files are all there, and it actually finds the microphone and computer-sound recording devices and opens each one for a moment (no sound is kept). Just screenshot it and send it in |