This page demonstrates how to transcribe long audio files (longer than one minute) to text using the Speech-to-Text API and asynchronous speech recognition.
About asynchronous speech recognition
Batch speech recognition starts a long-running audio processing operation. Use asynchronous speech recognition to transcribe audio that is longer than 60 seconds. For shorter audio, synchronous speech recognition is faster and simpler. The upper limit for asynchronous speech recognition is 480 minutes (8 hours).
Batch speech recognition is only able to transcribe audio stored in Cloud Storage. The transcription output can be either provided inline in the response (for single-file batch recognition requests) or written to Cloud Storage.
The batch recognition request returns an Operation
that contains
information about the ongoing recognition processing of your request. You can
poll the operation to know when the operation is complete and transcripts are
available.
Before you begin
- Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
-
Make sure that billing is enabled for your Google Cloud project.
-
Enable the Speech-to-Text APIs.
-
Make sure that you have the following role or roles on the project: Cloud Speech Administrator
Check for the roles
-
In the Google Cloud console, go to the IAM page.
Go to IAM - Select the project.
-
In the Principal column, find all rows that identify you or a group that you're included in. To learn which groups you're included in, contact your administrator.
- For all rows that specify or include you, check the Role colunn to see whether the list of roles includes the required roles.
Grant the roles
-
In the Google Cloud console, go to the IAM page.
Go to IAM - Select the project.
- Click Grant access.
-
In the New principals field, enter your user identifier. This is typically the email address for a Google Account.
- In the Select a role list, select a role.
- To grant additional roles, click Add another role and add each additional role.
- Click Save.
-
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
-
Make sure that billing is enabled for your Google Cloud project.
-
Enable the Speech-to-Text APIs.
-
Make sure that you have the following role or roles on the project: Cloud Speech Administrator
Check for the roles
-
In the Google Cloud console, go to the IAM page.
Go to IAM - Select the project.
-
In the Principal column, find all rows that identify you or a group that you're included in. To learn which groups you're included in, contact your administrator.
- For all rows that specify or include you, check the Role colunn to see whether the list of roles includes the required roles.
Grant the roles
-
In the Google Cloud console, go to the IAM page.
Go to IAM - Select the project.
- Click Grant access.
-
In the New principals field, enter your user identifier. This is typically the email address for a Google Account.
- In the Select a role list, select a role.
- To grant additional roles, click Add another role and add each additional role.
- Click Save.
-
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
If you're using a local shell, then create local authentication credentials for your user account:
gcloud auth application-default login
You don't need to do this if you're using Cloud Shell.
Client libraries can use Application Default Credentials to easily authenticate with Google APIs and send requests to those APIs. With Application Default Credentials, you can test your application locally and deploy it without changing the underlying code. For more information, see Authenticate for using client libraries.
Also ensure you have installed the client library.
Enable access to Cloud Storage
Speech-to-Text uses a service account to access your files in Cloud Storage. By default, the service account has access to Cloud Storage files in the same project.
The service account email address is the following:
service-PROJECT_NUMBER@gcp-sa-speech.iam.gserviceaccount.com
In order to transcribe Cloud Storage files in another project, you can give this service account the Speech-to-Text Service Agent role in the other project:
gcloud projects add-iam-policy-binding PROJECT_ID \
--member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-speech.iam.gserviceaccount.com \
--role=roles/speech.serviceAgent
More information about project IAM policy is available at Manage access to projects, folders, and organizations.
You can also give the service account more granular access by giving it permission to a specific Cloud Storage bucket:
gcloud storage buckets add-iam-policy-binding gs://BUCKET_NAME \
--member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-speech.iam.gserviceaccount.com \
--role=roles/storage.admin
More information about managing access to Cloud Storage is available at Create and Manage access control lists in the Cloud Storage documentation.
Perform batch recognition with inline results
Here is an example of performing batch speech recognition on an audio file in Cloud Storage and reading the transcription results inline from the response:
Python
Perform batch recognition and write results to Cloud Storage
Here is an example of performing batch speech recognition on an audio
file in Cloud Storage and reading the transcription results from the output
file in Cloud Storage. Note that the file written to Cloud Storage is a
BatchRecognizeResults
message in JSON format:
Python
Perform batch recognition on multiple files
Here is an example of performing batch speech recognition on multiple audio files in Cloud Storage and reading the transcription results from the output files in Cloud Storage:
Python
Enable dynamic batching on batch recognition
Dynamic batching enables lower cost transcription for higher latency. This feature is only available for batch recognition.
Here is an example of performing batch recognition on an audio file in Cloud Storage with dynamic batching enabled:
Python
Override recognition features per file
Batch recognition by default uses the same recognition configuration for each
file in the batch recognition request. If different files require different
configuration or features, configuration can be overridden per file using
the config
field in the
[BatchRecognizeFileMetadata
][batch-file-metadata-grpc] message. See the
recognizers documentation for an example overriding
recognition features.
Clean up
To avoid incurring charges to your Google Cloud account for the resources used on this page, follow these steps.
-
Optional: Revoke the authentication credentials that you created, and delete the local credential file.
gcloud auth application-default revoke
-
Optional: Revoke credentials from the gcloud CLI.
gcloud auth revoke
Console
gcloud
Delete a Google Cloud project:
gcloud projects delete PROJECT_ID
What's next
- See the reference documentation for batch recognition.
- Learn how to transcribe streaming audio.
- Practice transcribing short audio files.
- Transcribe audio files using Chirp.
- For best performance, accuracy, and other tips, see the best practices documentation.