Google is introducing two new smartphone apps designed to help folks who are deaf or hard of hearing. One is the previously-announced Sound Amplifier app for Android phones, which is available starting today. It lets you put on smartphone headphones to reduce background noise, amplify quiet sounds, and leave loud noises alone.

The other is a new app called Live Transcribe which uses speech-to-text technology to display captions on a smartphone display in near real-time.

Live Transcribe is rolling out in a limited beta starting today, and both apps will be available pre-installed on Pixel 3 smartphones.

Google has been in the speech-to-text business for years. Google Voice provides automatic transcripts of voicemail messages, and while the results are imperfect, they’ve gotten better over time thanks to machine learning. The same goes for the support for voice commands for Android devices, which eventually led to the creation of Google Assistant, which allows users to interact with a wide range of devices using voice.

Live Transcribe leverages the company’s existing technology so that all you need is a smartphone with a microphone and a screen to display closed captioning for real-time conversations without the need for a person to be typing away a transcript.

As someone who’s spent a lot of time typing up transcripts of interviews for podcasts and radio stories over the years, I can certainly see how this technology could have applications beyond providing a new way for deaf and hard of hearing people to communicate — although I’m not sure if Google has any plans to let users export a transcript (and there are already existing services that provide automated transcriptions of spoken word audio).

But Google is positioning Live Transcribe as an accessibility service, and for good reason — there are hundreds of millions of people affected by hearing loss and I suspect many of them could take advantage of a tool like this.

Once you’ve installed Live Transcribe on a smartphone, you can use it by enabling it in Accessibility Settings, and then opening the app from the accessibility button in the navigation bar.

The app should be able to recognize “over 70 languages and dialects,” and in addition to providing captions for spoken words, it allows participants in a conversation to type responses with a keyboard. There’s also support for external microphones for improved accuracy.

 

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign

or...

Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

2 replies on “Google’s Live Transcribe mobile app displays closed captions for the real world”

  1. I’ve got to admit, Google transcription capabilities are pretty remarkable. I got to use Google Pixels call screening service for the first time the other day, and seeing a whole paragraph of text appearing on the screen, word perfect, was eye-opening.

    And the automated closed captioning service provided by YouTube these days is a whole world better that it was just two to three years ago.

    This comment was dictated using my Android phone with just a few minor edits. the main problem I have these days, is the awkwardness of dictating in the first place, but that’s omething you can get a used to in time, and certainly, when you’re having a conversation with a deaf person, that should not be an issue.

    1. They certainly can be good, but they can also be laughably awful – the transcription of voicemails in Hangouts is great for unintended humor value, but often near-useless for figuring out the actual content of a message. Unlike, say, voice typing on Android, or in a gDoc, which I find to be mostly error-free. We’ll hope this product uses the latter and not the former…

Comments are closed.