- \n
- Fix:
subprocess.run([\"ydotool\", \"type\", \"--key-delay\", \"2\", text + \" \"], env=env, check=True)<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n- Use the English-only model – changed MODEL_SIZE from “base” to “base.en”<\/li>\n<\/ol>\n\n\n\n
\n\n\n\nMicrophone Gain Tuning<\/h3>\n\n\n\n
The C930e has two independent gain stages that are easy to confuse:<\/p>\n\n\n\n
- \n
- PipeWire\/PulseAudio layer \u2014 what pavucontrol and KDE audio settings control<\/li>\n\n\n\n
- ALSA hardware layer \u2014 the USB device’s own gain register, invisible to PipeWire The hardware gain defaults to 100% (50dB), which saturates the signal before PipeWire even sees it. Reduce it with:
amixer -c 1 set 'Mic' 80%<\/code> . Find the right card number first witharecord -l<\/code>. <\/li>\n\n\n\n- To persist across reboots:
sudo alsactl store<\/code> <\/li>\n\n\n\n- To diagnose clipping, use
sox<\/code> on the recorded file:sox \/tmp\/whisper_audio.wav -n stat<\/code> Aim for a maximum amplitude of 0.4\u20130.7. Hitting 1.0 means hardware clipping regardless of software volume settings.<\/li>\n\n\n\n- Best approach to debugging the issue is listening to the recorded file to identify clipping or distortion yourself, then tuning the gain till it goes away.<\/li>\n<\/ul>\n\n\n\n
Recently I started experiencing pain at the dip joint of my ring finger. That prompted me to look into how I can use voice more instead of typing everything on my computer. Especially with AI use, the typing has increased a lot. <\/p>\n\n\n\n
There are a lot of great solutions that exist for macOS, Windows, iOS and Android, but for Linux, I wasn’t able to find anything that worked as easily, so I’m documenting my setup for others who are on Linux and want to use Voice to Text better.<\/p>\n\n\n\n
Note that my specific setup is Wayland and KDE, however, it can be adopted to non-Wayland and other distributions and desktops quite easily. Because it uses ydotool, it is not dependent on Wayland or KDE for text injection and should work in other desktop environments outside of Wayland and KDE reliably as well.<\/p>\n\n\n\n
Here is a high level flow diagram of how the system works:<\/p>\n\n\n\n
![\"\"](\"https:\/\/nramkumar.org\/tech\/wp-content\/uploads\/2026\/02\/output-2-scaled.png\")
<\/figure>\n\n\n\nHere are the setup instructions for the setup I am using:<\/p>\n\n\n\n
- \n
- Hardware – for microphone, I am using a Logitech C930E webcam that I had lying around. This was bought during the pandemic and hasn’t been used at all. Turns out it has a great microphone. You can also use a BT headset, but this works well for me.<\/li>\n\n\n\n
- Select the microphone as your input source, use the digital stereo input option if you have multiple options.<\/li>\n\n\n\n
- Install the necessary components:\n
- \n
- On Wayland, xdotool or trying to using wl-copy and then simulating ctrl+v to inject text into the active window does not work reliably. ydotool seems to be the most reliable way to inject text into the window under focus. ydotool essentially fakes\/mimics an actual input source (like a keyboard).<\/li>\n\n\n\n
- You will need arecord or ffmpeg for recording the stereo input to a wav file. Install via alsa-utils. You also need libnotify-bin (this shows a toast for recording\/transcribing which is helpful to keep track of what’s going on).<\/li>\n\n\n\n
- sudo apt install ydotool ydotoold<\/li>\n\n\n\n
- Since faster-whisper relies on ffmpeg, you will need a working install of ffmpeg<\/li>\n\n\n\n
- Create a python venv, we will use a python script that will do the capture + transcribe and inject into the focus window.<\/li>\n\n\n\n
- In the venv, install these: pip install faster-whisper<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Create the whisper_toggle python script <\/a>below<\/li>\n<\/ul>\n\n\n\n
import os\nimport sys\nimport subprocess\nimport time\nimport signal\nfrom faster_whisper import WhisperModel\n\n# --- CONFIGURATION ---\nMODEL_SIZE = \"base\"\nDEVICE = \"cpu\"\nCOMPUTE_TYPE = \"int8\"\nLOCK_FILE = \"\/tmp\/whisper_lock\"\nAUDIO_FILE = \"\/tmp\/whisper_audio.wav\"\n\ndef notify(message):\n print(f\"🔔 {message}\")\n subprocess.run([\"notify-send\", \"-t\", \"1000\", \"Whisper\", message])\n\ndef start_recording():\n # 1. Create lock\n with open(LOCK_FILE, \"w\") as f:\n f.write(str(os.getpid()))\n \n notify(\"Recording... (Press again to stop)\")\n \n # 2. Record using arecord\n # -q: Quiet mode\n cmd = [\"arecord\", \"-f\", \"S16_LE\", \"-c\", \"1\", \"-r\", \"16000\", \"-q\", AUDIO_FILE]\n \n try:\n # We use Popen so we can wait specifically for this process\n process = subprocess.Popen(cmd)\n process.wait()\n except KeyboardInterrupt:\n pass\n\ndef stop_and_transcribe():\n # 1. STOPPING\n # Give the OS a moment to flush the WAV header to disk\n time.sleep(0.5)\n \n if not os.path.exists(AUDIO_FILE):\n notify(\"❌ Error: Audio file missing.\")\n return\n\n vocab_path = os.path.expanduser(\"~\/whisper-tool\/vocab.txt\")\n rams_vocab = \"\"\n if os.path.exists(vocab_path):\n with open(vocab_path, \"r\") as f:\n # Join lines and remove extra whitespace to create a clean hint string\n rams_vocab = \", \".join([line.strip() for line in f if line.strip()]) \n\n notify(\"Transcribing...\")\n\n try:\n # 2. TRANSCRIBING\n # We load the model fresh each time (slower start, but saves RAM when idle)\n model = WhisperModel(MODEL_SIZE, device=DEVICE, compute_type=COMPUTE_TYPE)\n \n segments, _ = model.transcribe(\n AUDIO_FILE, \n beam_size=1,\n language=\"en\", # <--- FORCE ENGLISH\n vad_filter=True, # <--- IGNORE SILENCE\n initial_prompt=rams_vocab, # <--- VOCAB HINTS\n condition_on_previous_text=False\n )\n \n text = \" \".join([segment.text for segment in segments]).strip()\n \n if text:\n print(f\"📝 RESULT: {text}\")\n # We explicitly pass the YDOTOOL_SOCKET in case the hotkey environment lacks it\n env = os.environ.copy()\n env[\"YDOTOOL_SOCKET\"] = f\"{os.environ['HOME']}\/.ydotool_socket\"\n \n \n # Small delay for keyboard release\n time.sleep(0.1)\n \n # Paste using ydotool\n try:\n subprocess.run([\"ydotool\", \"type\", \"--delay\", \"2\", text + \" \"], env=env, check=True)\n except subprocess.CalledProcessError as e:\n print(f\"❌ ydotool type failed: {e}\") \n else:\n notify(\"⚠️ No speech detected.\")\n \n except Exception as e:\n notify(f\"❌ Error: {e}\")\n\ndef main():\n if os.path.exists(LOCK_FILE):\n # --- STOP SIGNAL ---\n print(\"🛑 Stop signal received. Finishing recording...\")\n \n # Send SIGINT (Ctrl+C) to arecord to make it save the file properly\n os.system(\"pkill -SIGINT arecord\")\n \n # Clean up lock\n if os.path.exists(LOCK_FILE):\n os.remove(LOCK_FILE)\n else:\n # --- START SIGNAL ---\n try:\n start_recording()\n # Script pauses here until arecord is killed by the second instance\n \n # Once killed, we proceed:\n stop_and_transcribe()\n finally:\n if os.path.exists(LOCK_FILE):\n os.remove(LOCK_FILE)\n\nif __name__ == \"__main__\":\n main()\n<\/code><\/pre>\n\n\n\n- \n
- You need to add yourself to the input group and create a udev rule that allows access to the \/dev\/uinput device (used by ydotool) to the input group:<\/li>\n<\/ul>\n\n\n\n
sudo usermod -aG input \"$USER\"\necho 'KERNEL==\"uinput\", GROUP=\"input\", MODE=\"0660\", OPTIONS+=\"static_node=uinput\"' \\\n | sudo tee \/etc\/udev\/rules.d\/80-uinput.rules >\/dev\/null\nsudo udevadm control --reload-rules && sudo udevadm trigger<\/code><\/pre>\n\n\n\n- \n
- Log out and log back in (so groups membership is updated)<\/li>\n\n\n\n
- Create a user-level ydotoold service so the daemon is started automatically when you log-in<\/li>\n<\/ul>\n\n\n\n
cat > ~\/.config\/systemd\/user\/ydotoold.service\n[Unit]\nDescription=ydotoold (uinput) daemon\n\n[Service]\nType=simple\nExecStart=\/usr\/bin\/ydotoold --socket-path=%h\/.ydotool_socket --socket-own=%U:%G\nRestart=on-failure\n\n[Install]\nWantedBy=default.target\nCtrl-D\n\nsystemctl --user daemon-reload\nsystemctl --user enable --now ydotoold.service<\/code><\/pre>\n\n\n\n- \n
- Make sure the daemon is running successfully.<\/li>\n\n\n\n
- Test the python script – run in one terminal, start speaking, run in another terminal. If it all works, you should see the text of what you spoke in the second terminal.<\/li>\n\n\n\n
- Map to a hot-key with KDE shortcut – I have mapped mine to ctrl+space.\n
- \n
- Add Command<\/li>\n\n\n\n
- <full venv path>\/python3 <path>\/whisper_toggle.py<\/li>\n\n\n\n
- Select your favored keyboard shortcut<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
Overall, this works surprisingly well, although it took a little bit of time and effort to set up. I really like how well it is working. One downside is when you’re actually using it to issue commands, it really does not work well. Those you probably have to type, but for any dictation like interface, this is pretty good. <\/p>\n\n\n\n
For injecting specific words like names of people or other uncommon words or spellings that you use, you can populate your vocabulary or text and the script will automatically inject that into your prompt. This seems to work quite well for especially names of people when I’m texting them from my computer using WhatsApp. <\/p>\n","protected":false},"excerpt":{"rendered":"
Fixes After Ubuntu 26.04 Upgrade After upgrading to Ubuntu 26.04 (Plasma 6.6.4), two bugs broke the tool: Microphone Gain Tuning The C930e has two independent gain stages that are easy to confuse: Recently I started experiencing pain at the dip joint of my ring finger. That prompted me to look into how I can use…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-635","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/posts\/635","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/comments?post=635"}],"version-history":[{"count":4,"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/posts\/635\/revisions"}],"predecessor-version":[{"id":703,"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/posts\/635\/revisions\/703"}],"wp:attachment":[{"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/media?parent=635"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/categories?post=635"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nramkumar.org\/tech\/wp-json\/wp\/v2\/tags?post=635"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- You need to add yourself to the input group and create a udev rule that allows access to the \/dev\/uinput device (used by ydotool) to the input group:<\/li>\n<\/ul>\n\n\n\n
- To persist across reboots:
- Use the English-only model – changed MODEL_SIZE from “base” to “base.en”<\/li>\n<\/ol>\n\n\n\n