<?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 DRM HSE</title><link>https://www.drmhse.com/tags/whisper/</link><description>Recent content in Whisper on DRM HSE</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 05 Aug 2026 09:15:35 +0300</lastBuildDate><atom:link href="https://www.drmhse.com/tags/whisper/index.xml" rel="self" type="application/rss+xml"/><item><title>Narrating Book-Length Text on One Machine</title><link>https://www.drmhse.com/posts/narrating-book-length-text-local-tts/</link><pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.drmhse.com/posts/narrating-book-length-text-local-tts/</guid><description>&lt;p>You cannot proofread sixteen hours of audio.&lt;/p>
&lt;p>Everything below follows from that. Correctness has to be established by machinery, because the one method you would trust — sitting down and listening to all of it — costs two working days per pass and nobody does it twice. A twelve-hour render must also survive being interrupted, and if the audio drives an interface that highlights words as they are spoken, every word needs a timestamp good to a fraction of a second.&lt;/p></description></item></channel></rss>