Hey everyone! 👋 I saw the announcement about the new 'live notes' beta feature in tl;dv and got super curious. I’ve been using tl;dv mostly to timestamp meetings for my team’s retrospectives, but taking notes separately in a doc has always been a bit clunky.
Has anyone here gotten access to the beta and tried it out? I’m really wondering how it works in practice. A few specific things I’m hoping to learn:
* Does it feel like it slows down your meeting at all, or is it pretty seamless?
* Can you easily link a note to a specific timestamp in the recording automatically?
* What’s the export or integration look like? For my pipelines, I often need to pull key decisions or action items from meetings into our project management tools (or even as metadata for data lineage notes 😅).
I’m still pretty new to orchestrating all our data workflows (Airflow is… a lot), so any tool that can help streamline steps *before* the pipeline (like requirement gathering from meetings) is a huge win for me. The idea of having notes tied directly to the recording sounds amazing for clarity.
Would love to hear any early impressions, good or bad! Even screenshots of how it looks in action would be super helpful. Thanks in advance
null
I've been testing the beta for about two weeks with my product team, focusing on requirement-gathering sessions. To answer your specific questions directly: the note-taking interface itself is surprisingly unobtrusive and doesn't slow the meeting. The friction, however, comes from a slight mental context switch if you're also the facilitator, as you're managing the UI while speaking.
Regarding your second and third points, the timestamp linking is automatic and works well - each bullet you create is anchored to the moment you create it, which is the core value proposition. The export functionality is currently the beta's weakest link, in my evaluation. You can share a link to the notes-with-recording view, but there's no direct API push or clean export to project management tools yet. This is a critical gap for the ROI case, as it creates another manual step for pipeline integration. I'm told it's on the roadmap, but the viability hinges on how quickly those integrations materialize and their flexibility.
PM by day, reviewer by night.