Readit News logoReadit News
davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
IMTDb · 5 months ago
Our meetings often involve a mix of onsite and offsite employees. Typical setup might be CEO + CTO + a VP in a room, connected as a single zoom client to the call (either of these 3 guys depending on who got in the meeting room first), then few additional people joining remotely from home each on their own zoom instance. The guys on the meeting room are using a dedicated camera in the meeting room that captures the entire room, and has all participants in sight. Is this a setup you are trying to address; how are you able to recognize speakers in this configuration ?

Most transcript system we have tried bundle everything that is said by the onsite people as a single entity which pretty much destroys the value of the transcript; especially if people in that room disagree with each other; reading the transcript makes it feel that the onsite guys is very schizophrenic

davidgu · 5 months ago
That’s a great question! We partner with a number of different transcription providers that use AI to identify different speakers based on the sound of their voice. This prevents all the speakers from a conference room from being bundled together as the same person. We’re also going to be looking to add this functionality to our own transcription service in the coming months.
davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
wferrell · 5 months ago
I did. Were you trying to get VCs to know about you? Or more like a twilio billboard that just said ask your devs?
davidgu · 5 months ago
The postcards were part of a dev-focused campaign to get people curious enough to check us out. We kept it minimal to stand out amongst other mail.
davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
ripped_britches · 5 months ago
I’m interested in how you expect to keep market share if this capability can be offered by the webrtc service provider. I saw the other comment about multiple providers, but many enterprises have just one preferred path. For example I’ve been recording Google drive calls and the transcript goes straight into my Google drive.
davidgu · 5 months ago
For internal use cases like recording your own meetings into Google Drive, the native tools work fine.

Where we come in is for companies building products that need to support all of their customers across Zoom, Meet, Teams, Webex, etc. Most enterprises don’t want five different integrations, and native APIs often come with restrictions (like only the organizer being able to access the file, or recordings not being available until after the call).

davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
agwp · 5 months ago
Have you explored using speaker diarization and speaker identification, given that pyannote etc. takes this approach?

I'm curious given your decision to capture speaker names from the screen. I see the merits during desktop recording, but I can also see how this limits utility when trying to offer the same functionality across desktop and other scenarios (e.g. in-person meetings, audio uploads etc.)

davidgu · 5 months ago
We already support diarization in the Desktop Recording SDK by capturing the meeting platform’s speaker-change events, so you get a diarized transcript plus precise “speaker started talking” timestamps out of the box. We also support voice-signature diarization via third-party STT providers for participants calling in from the same room

For in-person meetings and audio uploads, this is on our roadmap and in development. More to come on this!

davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
giveita · 5 months ago
I have Loom recorded a Zoom meeting so get it. I think for corporates though the integrated approaches are so so convenient. Have your meeting and get a summary email by doing nothing (or one click opt in). I feel like your solution is for edge cases where the mainstream ways are not possible.
davidgu · 5 months ago
Just to clarify, we’re the infra layer that reliably captures and normalizes meeting data across platforms. The real value for users is what developers build on top: automated analysis, enrichment, and workflows (not the capture itself)

Modern LLMs can power sales coaching, medical scribing, legal review, support QA, and compliance reporting but they need consistent inputs to process. We handle capture/formatting/edge cases so developers can focus on models and UX

davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
apollopower · 5 months ago
Congrats Recall team, I've been a customer for the past 1.5 years and the entire infra layer behind meetings has let our company really focus on "what makes our beer taste better" instead of having to worry about building universal support for different (and tedious) platforms like Teams and Zoom. Eager to give the desktop recording sdk a try soon.
davidgu · 5 months ago
Thanks and love to hear this!
davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
orliesaurus · 5 months ago
Congrats on ur launch. Amanda has the strongest LinkedIn game I have ever seen in my life. On the other hand the product is IMHO at risk? Models like Whisper, DistilWhisper, TinyLlama, miniGPT-4, OpenHermes, Vosk, and Llama.cpp make Recall.ai meeting transcription easy to replicate. IMHO in 1 weekend you can build an open-source tech stacks that can rival or EVEN surpass the value brought....or am I tripping?
davidgu · 5 months ago
Amanda says thank you so much!

I actually agree that it’s become incredibly easy to transcribe conversations using open-source models, and that’s not where Recall adds the most value. The hard part is building the infrastructure that allows you to get real-time access to the raw audio, video, and transcript data directly from the meeting platforms. We abstract all of that away and provide you with a clean interface to access that data. Once you get the data, you could use any of the models that you mentioned to do your own transcription, or transcribe using Recall’s transcription models.

davidgu commented on Launch HN: Recall.ai (YC W20) – API for meeting recordings and transcripts    · Posted by u/davidgu
Hansenq · 5 months ago
Wow, congrats on finally using up your single Launch HN, David and Amanda! :wink:

No but seriously, y'all have built not only an incredible product that I had the chance to demo, but a great company as well, through your previous pivots and cofounder changes. You're building schlep tools that product companies _definitely_ don't want to do, years before it was clear there was a market here, and do it well.

There's definitely demand for a native screen recorder, and I think it's the right move to be agnostic to privacy (the lower down the stack you go, the more permissable you should be about use-cases). Imagine how much competition in file storage there would have been had there been an API provider for Dropbox's Finder sync technology (though you could argue it just incentivizes large companies like Hubspot to build their own screen recording feature into their platform, rather than enabling new startups like Gong but I digress).

Y'all deserve the success that you have, and wishing you all the best of luck with the new product launch!

davidgu · 5 months ago
Thanks! Really appreciate the kind words

u/davidgu

KarmaCake day449January 22, 2018
About
Co-founder at https://www.recall.ai/
View Original