What is Custom Speech?
Custom Speech allows you to evaluate and improve the Microsoft speech-to-text accuracy for your applications and products. Follow the links in this article to start creating a custom speech-to-text experience.
What's in Custom Speech?
Before you can do anything with Custom Speech, you'll need an Azure account and a Speech service subscription. After you have an account, you can prep your data, train and test your models, inspect recognition quality, evaluate accuracy, and ultimately deploy and use the custom speech-to-text model.
This diagram highlights the pieces that make up the Custom Speech area of the Speech Studio. Use the links below to learn more about each step.
Subscribe and create a project. Create an Azure account and subscribe to the Speech service. This unified subscription gives you access to speech-to-text, text-to-speech, speech translation, and the Speech Studio. Then use your Speech service subscription to create your first Custom Speech project.
Upload test data. Upload test data (audio files) to evaluate the Microsoft speech-to-text offering for your applications, tools, and products.
Evaluate and improve accuracy. Evaluate and improve the accuracy of the speech-to-text model. The Speech Studio will provide a Word Error Rate, which you can use to determine if additional training is required. If you're satisfied with the accuracy, you can use the Speech service APIs directly. If you want to improve accuracy by a relative average of 5% to 20%, use the Training tab in the portal to upload additional training data, like human-labeled transcripts and related text.
Train and deploy a model. Improve the accuracy of your speech-to-text model by providing written transcripts (10 to 1,000 hours) and related text (<200 MB) along with your audio test data. This data helps to train the speech-to-text model. After training, retest. If you're satisfied with the result, you can deploy your model to a custom endpoint.
Set up your Azure account
You need to have an Azure account and Speech service subscription before you can use the Speech Studio to create a custom model. If you don't have an account and subscription, try the Speech service for free.
If you plan to train a custom model with audio data, pick one of the following regions that have dedicated hardware available for training. This will reduce the time it takes to train a model and allow you to use more audio for training. In these regions, the Speech service will use up to 20 hours of audio for training; in other regions it will only use up to 8 hours.
- Australia East
- Canada Central
- Central India
- East US
- East US 2
- North Central US
- North Europe
- South Central US
- Southeast Asia
- UK South
- US Gov Arizona
- US Gov Virginia
- West Europe
- West US 2
After you create an Azure account and a Speech service subscription, you'll need to sign in to the Speech Studio and connect your subscription.
- Sign in to the Speech Studio.
- Select the subscription you need to work in and create a speech project.
- If you want to modify your subscription, select the cog button in the top menu.
How to create a project
Content like data, models, tests, and endpoints are organized into projects in the Speech Studio. Each project is specific to a domain and country/language. For example, you might create a project for call centers that use English in the United States.
To create your first project, select Speech-to-text/Custom speech, and then select New Project. Follow the instructions provided by the wizard to create your project. After you create a project, you should see four tabs: Data, Testing, Training, and Deployment. Use the links provided in Next steps to learn how to use each tab.
The Speech Studio (formerly known as "Custom Speech portal") was recently updated! If you created previous data, models, tests, and published endpoints in the CRIS.ai portal or with APIs, you need to create a new project in the new portal to connect to these old entities.
Model and Endpoint lifecycle
Older models typically become less useful over time because the newest model usually has higher accuracy. Therefore, base models as well as custom models and endpoints created through the portal are subject to expiration after 1 year for adaptation and 2 years for decoding. See a detailed description in the Model and endpoint lifecycle article.