https://kane.mx/tags/gemini-3.5-transcribe/Recent content in Gemini 3.5 Transcribe on The roadHugo -- gohugo.ioenMon, 07 Sep 2026 00:00:00 +0000https://kane.mx/posts/2026/gemini-transcribe-vs-funasr-aws/Mon, 07 Sep 2026 00:00:00 +0000https://kane.mx/posts/2026/gemini-transcribe-vs-funasr-aws/ <h2 id="1-the-three-phase-transcription-pipeline">1. The Three-Phase Transcription Pipeline</h2> <p>A production podcast transcript is not produced by one model call. The pipeline behind these measurements has three stages:</p> <ol> <li><strong>Phase 1:</strong> VAD, speech recognition, punctuation, timestamps, and speaker diarization.</li> <li><strong>Phase 2:</strong> speaker identity verification and label correction.</li> <li><strong>Phase 3:</strong> transcript cleanup, rewrite constraints, and quality gates.</li> </ol> <p>These phase names are local to this implementation, not an industry-standard taxonomy. For the economics comparison, the relevant boundary is Phase 1: the stage that Gemini Transcribe or FunASR can directly produce. The existing Phase 2 and Phase 3 implementations are held constant, so their shared LLM costs are excluded from both sides. This is a Phase 1 infrastructure comparison, not a total-pipeline TCO result; any provider-driven change in downstream inference or correction work must be measured separately.</p> <p><a href="https://kane.mx/posts/2026/gemini-transcribe-vs-funasr-aws/">Read More</a></p>