<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Whisper on Clarence | Backend, AI, DevOps, Infrastructure</title>
    <link>https://clarence.tw/en/tags/whisper/</link>
    <description>Recent content in Whisper on Clarence | Backend, AI, DevOps, Infrastructure</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://clarence.tw/en/tags/whisper/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Speech AI and GPU Runtime: Notes on Deploying and Operating Kaldi and Whisper</title>
      <link>https://clarence.tw/en/posts/speech-ai-gpu-runtime/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0800</pubDate>
      
      <guid>https://clarence.tw/en/posts/speech-ai-gpu-runtime/</guid>
      <description>&lt;p&gt;Since 2022, part of my work has been bringing speech recognition technologies such as Kaldi and Whisper, together with GPU runtime, into real systems. That covers model inference, system deployment, and the performance maintenance that follows.&lt;/p&gt;
&lt;p&gt;This is not a full case study of a specific project, and it does not include internal architecture, data, or performance numbers. Instead, it describes how I approach this kind of work: how I think about the differences between Kaldi and Whisper, why I stabilize the GPU runtime first, and what I check after deployment. Technical details follow the official documentation, and the troubleshooting lessons come from articles I have published on &lt;a href=&#34;https://blog.clarence.tw/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;blog.clarence.tw&lt;/a&gt; (written in Chinese).&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
