Paying $26 for something similar doesn't feel good value.
We've tried something like this during a french python conf to get subtitles for deaf people. It was impossible to even understand the result.
automated subtitles are bad, i agree. but, in this case, the murderer was autocorrect.
Are you sure you're thinking of the automated subtitles? Some youtube videos have manually written captions too.
Also, I hate how the auto-generated CC spits out one word at a time while scrolling the lines up, and how it keeps the previous caption on screen mixed in with the next one during long moments of non-speech (if the speaker isn't in frame, it's hard to know what the context is). That's not how I read—it's not how anyone reads. I would rather it showed a single block at a time, with the current word highlighted.
And what's with the random "yeah yeah yeah", "[applause]", or "[music]" captions when it's just guessing? Better to put question marks than be completely wrong.
lack of punctuation and capitalisation also makes informal speech quite difficult to understand sentences just run into another makes it hard to know what's referring to what gets split into unnatural sentences... you get the point.
However, automated CC is good when you're trying to find a particular part of a long video, and you don't want to watch the whole thing just to find it. It's easy to skim the captions to find a relevant part.
There are several open source speech recognition systems (like Deepspeech and CMUSphinx) but there don't seem to be any user-friendly frontends for them.
Not sure if that helps you or not.