System & Meeting Audio Capture
Resolve problems capturing your computer’s or a meeting’s audio.
When you want to transcribe a video call, a webinar, or any sound playing on your computer, Kalima captures your system (desktop) audio instead of, or alongside, your microphone. If the meeting audio isn’t making it into your transcript, the cause is almost always one small setting in the browser share prompt or your capture mode. This page walks through the most common issues and how to fix each one.
The single most common reason system audio isn’t transcribed: the “Share audio” checkbox in the browser’s screen-share prompt was not ticked. Look for it in the bottom corner of that dialog before you confirm.
Quick checklist
Capturing system audio in the browser
In a web browser, Kalima captures your computer’s audio through the browser’s built-in screen- and tab-sharing permission. Set the audio source to Desktop audio, press record, and the browser asks you to choose a screen, window, or tab to share, and whether to include its audio.
Sharing a single browser tab is the most reliable way to capture audio in a browser. In the share prompt, choose the tab, make sure “Share tab audio” is enabled, and confirm. This is ideal for transcribing a web-based call, a video, or a streamed talk playing in that tab.
Browser support for capturing system or tab audio varies. Some browsers only let you share tab audio, and some don’t expose audio in the share prompt at all. For dependable meeting capture across any app, use the Kalima desktop app, which captures meeting audio natively.
Capturing audio with the desktop app
The Kalima desktop app records your computer’s meeting audio directly, without the browser share dialog. On Windows it can isolate the audio of a single meeting app, and if that source is silent it automatically falls back to system-wide audio (or your microphone) so you’re never left with a silent recording. Start a recording from the Studio or accept a Meeting Assist prompt, choose a capture mode that includes meeting audio, and grant the screen/audio sharing permission if your operating system asks. See Capturing Audio & Screen for the full walkthrough.
Common problems & fixes
The browser share prompt almost certainly didn’t include audio. When you press record with Desktop audio selected, the prompt has a “Share audio” or “Share tab audio” checkbox, tick it before confirming. If you confirmed without it, stop and start the recording again to get a fresh prompt. If your browser shows no audio option for what you chose, share a single browser tab instead (most reliable) or use the desktop app.
Capturing system and tab audio depends on your browser, and not every browser exposes audio in the share prompt, some only offer it for a tab share, others not at all. Try sharing the specific browser tab that’s playing the audio, or share your whole screen if that browser offers system audio. For dependable capture in any meeting app, install the Kalima desktop app, which records meeting audio natively without relying on the browser prompt.
Audio for an individual application window isn’t available in every browser. Many browsers only expose audio when you share a browser tab or your entire screen. If you need a specific app’s audio in the browser, share the tab (for web apps) or the whole screen. On Windows, the desktop app can target a single app’s audio directly through its source picker.
Your recording is capturing only the microphone, not the meeting’s audio. Switch the audio source to Desktop audio so the call’s sound is captured, and tick “Share audio” in the share prompt. To get both sides, the call and your own voice, turn on Include microphone so your mic is blended into the same transcript. In the desktop app, choose a capture mode that includes meeting audio and grant any screen/audio sharing permission your operating system requests.
Set the audio source to Desktop audio, then turn on the Include microphone toggle that appears beneath the source picker. This mixes your mic with the captured system audio so both the meeting and your commentary land in a single transcript. The toggle only appears when Desktop audio is selected.
Targeting a single app’s audio is a desktop-app feature on Windows. In the Kalima desktop app, the source picker lets you choose the exact window or app to capture, with preview thumbnails to confirm you’ve got the right one (use Refresh if your target isn’t listed yet). If that isolated source happens to be silent, Kalima automatically falls back to system-wide audio or your microphone so the recording isn’t lost.
Isolating a single app’s audio is a Windows-only capability. On macOS and Linux, the desktop app captures system-wide audio (you may be asked to grant a screen/audio sharing permission) rather than one app in isolation. The whole meeting is still transcribed, it just includes any other sounds playing on your computer, so mute unrelated apps for the cleanest result.
On mobile, set the audio source to Device audio. This captures your device’s audio through screen sharing, the same way Desktop audio works on a computer. Follow your device’s screen-share prompt and allow audio when asked.
A delay usually comes from the network or a high-latency input device rather than the capture itself. If you’ve mixed in your microphone, a Bluetooth/wireless headset or a virtual audio cable adds delay, Kalima shows a brief advisory when it detects one. Switch to a wired or built-in microphone and a stronger connection. The live latency badge in the Studio shows how quickly results are arriving (green is fast).