Transcription

Not every recording I transcribe is a Bible teaching or a home video. Some of it is confidential — calls from a counseling hotline, where people are talking about the hardest thing in their life. That kind of audio can’t go anywhere near a paid cloud API. Not because of cost. Because it isn’t mine to send anywhere. That ruled out Whisper’s API and ElevenLabs — the two services I’d already used and paid for — for this particular kind of file. I needed something that would run entirely on my own PC, touch nothing outside it, and cost nothing per file. My PC has no GPU. Whatever I built had to live with that too. ...

In an earlier post I described cloning an app — copying the audio player I’d built onto a tablet to give away. That was a copy: same content, same speaker, a second home. This post is about a step further. I took that same engine and pointed it at a different speaker, and then at a different kind of media — and it just worked. Each time, what should have been “build a whole new app” turned out to be “feed the engine something new.” ...

In the post on search I gave you the clean version: type a word, get every place it was said, tap to jump to that moment. That’s true now. But I made it sound smooth, and for a while it wasn’t. The search had a bug that wore me down — and tracking it down taught me one of the more useful lessons in this series. The symptom was maddening. You’d search a word, see a result, tap “play from here” — and the audio would start playing twenty minutes before the word you searched for. The search found the right thing. It just sent you to the wrong place in the recording. Sometimes by seconds, sometimes by twenty whole minutes. ...

In an earlier post I turned hundreds of hours of recorded Bible teaching into text. AI transcription is good, but not perfect — it mishears words, especially names and rare terms. So the obvious next step was to ask a smart language model to clean up the mistakes. These models have basically read the whole Bible, so I figured fixing a few scripture typos would be easy for them. It wasn’t. And the way it failed taught me something that goes well beyond transcripts — to anyone using AI to correct text against a trusted source. ...

I thought I was done. The tablet was in his hands. The ownership was his — his domain, his account, his server. A lifetime of teaching, gathered and searchable. I’d built a legacy and given it away. The end. And then, at that very handover, the eighty-year-old man told me what was missing. There were teachings, he said, that we didn’t have — recordings that belonged in his life’s work but weren’t in our collection. He knew, because it’s his life’s work, and no one knows it better than the man who lived it. So the “finished” gift wasn’t finished. The tablet is back on my desk right now, plugged in, getting its update. On Sunday I hand it back: Version 2.0. ...

A pile of audio is a black box. You know the teacher said something about a certain verse. You can almost hear it. But it’s somewhere inside hundreds of hours of recordings, in one lecture out of hundreds, at a point you can’t remember. Without a way to search, those recordings are write-only: you can keep adding to them, but you can never really get anything back out. The bigger the collection grows, the more it buries. ...

My wife listens to a Bible teacher every morning. After I built her an app to make that easier (the first post in this series), she asked for one more thing. It turned out to be the hardest part of the project. Could we also read his teachings, she said, not just hear them? Reading helps her study. She wanted the words on a screen. “Sure,” I thought. “I’ll just turn the audio into text.” How hard could it be? In 2026, turning speech into text is mostly a solved problem. ...