Why are speech-to-text services hard to use?
I came across a blog from Luis Quintanilla where he produced a console app to transcribe podcasts using the Microsoft Speech API.
The thing that instantly struck me was the hoops that he had to jump though to transcribe the podcast. The app had to:
Why, why, why? Every one of those steps is a chance for something to go wrong! This makes a whole load of work to produce a stable, reliable process to make use of a utility service to get transcripts from audio. After all its called AUTOMATIC SPEECH RECOGNITION so you need it to be automatable reliably right?
Why does it have to be that complex?
Good news… It doesn’t.
Speechmatics believe that it’s hard work and frustrating when using a utility becomes the hard part of a task, rather than being a tool that simply helps you solve the problems. So, the Speechmatics API has been designed to make it easy to consume, not get in the way. With the Speechmatics API you can:
What does that mean?
Firstly, why bother using an API at all, just register for using our web app and use the app to transcribe your audio directly and download the result or get the transcript emailed back to you.
Or use the API key after you register and use a single HTTP Post command to request the transcript and a single HTTP to retrieve the result (API docs are available).
Why not give it a go?
If you register, we will give you 60-minutes free transcription.
Other services that sound simple can be hard to use so you might not even get to the transcript. Ours is so easy to use and I am sure that the results will be great too.
Ian Firth, Speechmatics