I've been running into a persistent and frankly bizarre issue with tl;dv over the last few weeks, and I'm starting to suspect this is less a "me" problem and more a fundamental gap in their documentation or a silent regression in their audio capture logic. The tool bills itself as a reliable meeting recorder, but reliability goes out the window when it arbitrarily decides one participant's audio stream isn't worth capturing.
The scenario is consistently reproducible in my environment: recurring Zoom meetings with a standard set of internal and external participants. Every time, without fail, tl;dv will capture the video and audio of *everyone* except for one specific external participant. This person is not on mute locally, their audio is perfectly clear to everyone else in the live meeting, and they appear normally in the Zoom participant list. Yet, the resulting tl;dv transcript shows "[No Audio]" for every one of their utterances, and the playback is silent for their video feed. This isn't a transient network issue; it happens across multiple meetings, on different days, with this same individual.
I've done the standard troubleshooting dance, of course, which feels increasingly like a ritual to appease support bots rather than solve a problem:
* Verified the participant is not excluded in any capture settings (there are none for individuals, anyway).
* Ensured we're using the direct Zoom integration, not the desktop app's system audio capture (which is a recipe for disaster).
* Confirmed the issue persists whether I, as the host, start the recording or if it's started via the calendar integration.
The silence from tl;dv's official resources on this is deafening. Their help center articles are a monument to the obvious, covering "make sure your mic isn't muted" but nothing about selective, participant-level audio capture failures within a platform integration. This reeks of a permissions or stream-identification issue within Zoom's API that tl;dv isn't handling gracefully.
Before I rip out the entire setup and script something myself using Zoom's raw APIs and Whisper, has anyone else deconstructed this particular failure mode? I need to know if this is a known limitation with external participants in certain Zoom license tiers, or if there's some hidden OAuth scope or meeting setting that acts as a landmine. My finance team will have my head if I can't produce accurate records of these conversations, and "sorry, the AI recorder decided not to listen to your client" isn't a viable excuse.
-- Cam
Trust but verify.