You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Windows] System-audio loopback captures only silence on a Jabra EVOLVE 20 (USB) — works once that device is out of the picture
#763
Headset: Jabra EVOLVE 20 MS (USB), used as mic + output
Also available: onboard Realtek output/mic, Logitech webcam mic
Summary
When the Jabra EVOLVE 20 is the output device, Meetily's system-audio (loopback)
capture records only silence — recordings contain my microphone only, and other
participants are missing from the audio and transcript. As soon as the Jabra is out
of the path and Meetily falls back to the onboard Realtek output, system-audio
capture works perfectly.
What works
Microphone capture (once the headset's hardware mute is off).
System-audio capture via the Realtek output: clean, full-level (~188 kb/s,
~-19 dB), continuous speech captured and transcribed correctly.
What doesn't
System-audio capture via the Jabra EVOLVE 20 output: the mixed track is
mic-only. Level analysis shows close-mic content (peaks clipping at 0 dB) with no
far-end audio; the transcript contains only my own utterances.
How I isolated it
Recorded a real meeting with the Jabra as output → transcript had only my words;
audio was a mono mix containing mic only.
OS-level check: the Jabra output is the Windows default, unmuted, ~98%, and audio is being rendered to it (its peak meter moves on playback). So sound reaches the
exact endpoint Meetily is set to loop back, yet the capture is silent.
Unplugged the Jabra → Meetily fell back to the Realtek output → system audio was
captured cleanly and transcribed in full. Repeatable.
A possibly important clue
At the moment recording starts, the audio I hear in the headset noticeably changes.
The EVOLVE 20 has separate high-quality (stereo) and hands-free/communications
(mono) modes. My guess is that opening the mic stream forces the headset into
comms mode, which reconfigures the render pipeline, so the loopback tap Meetily
opened ends up on a now-empty/relocated stream. The Realtek codec doesn't
mode-switch, so its loopback tap stays valid. (Hypothesis — happy to help verify.)
Questions
Is loopback capture of USB communications headsets (that switch modes when the mic
opens) a known limitation on Windows?
Would re-initializing the loopback client after the device mode switch, or handling
format/endpoint changes mid-session, help?
Any recommended workaround besides using a non-Jabra output? A warning when the
loopback stream is delivering silence would also have saved a lot of debugging.
Environment note / workaround
For now: routing system audio through the Realtek output works. The caveat is that
you then hear the meeting from that device, so headset listening + loopback capture
on the Jabra isn't currently possible.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Environment
Summary
When the Jabra EVOLVE 20 is the output device, Meetily's system-audio (loopback)
capture records only silence — recordings contain my microphone only, and other
participants are missing from the audio and transcript. As soon as the Jabra is out
of the path and Meetily falls back to the onboard Realtek output, system-audio
capture works perfectly.
What works
~-19 dB), continuous speech captured and transcribed correctly.
What doesn't
mic-only. Level analysis shows close-mic content (peaks clipping at 0 dB) with no
far-end audio; the transcript contains only my own utterances.
How I isolated it
audio was a mono mix containing mic only.
is being rendered to it (its peak meter moves on playback). So sound reaches the
exact endpoint Meetily is set to loop back, yet the capture is silent.
captured cleanly and transcribed in full. Repeatable.
A possibly important clue
At the moment recording starts, the audio I hear in the headset noticeably changes.
The EVOLVE 20 has separate high-quality (stereo) and hands-free/communications
(mono) modes. My guess is that opening the mic stream forces the headset into
comms mode, which reconfigures the render pipeline, so the loopback tap Meetily
opened ends up on a now-empty/relocated stream. The Realtek codec doesn't
mode-switch, so its loopback tap stays valid. (Hypothesis — happy to help verify.)
Questions
opens) a known limitation on Windows?
format/endpoint changes mid-session, help?
loopback stream is delivering silence would also have saved a lot of debugging.
Environment note / workaround
For now: routing system audio through the Realtek output works. The caveat is that
you then hear the meeting from that device, so headset listening + loopback capture
on the Jabra isn't currently possible.
All reactions