|
| 1 | +--- |
| 2 | +title: Azure Media Services live transcription | Microsoft Docs |
| 3 | +description: This article explains what the Azure Media Services live transcription is. |
| 4 | +services: media-services |
| 5 | +documentationcenter: '' |
| 6 | +author: Juliako |
| 7 | +manager: femila |
| 8 | +editor: '' |
| 9 | + |
| 10 | +ms.service: media-services |
| 11 | +ms.workload: media |
| 12 | +ms.tgt_pltfrm: na |
| 13 | +ms.devlang: ne |
| 14 | +ms.topic: article |
| 15 | +ms.date: 08/27/2019 |
| 16 | +ms.author: juliako |
| 17 | + |
| 18 | +--- |
| 19 | + |
| 20 | +# Live transcription (preview) |
| 21 | + |
| 22 | +Azure Media Service delivers video, audio, and now text in different protocols. When you publish your live stream using MPEG-DASH or HLS/CMAF, then along with video and audio, our service will deliver the transcribed text in IMSC1.1 compatible TTML, packaged into MPEG-4 Part 30 (ISO/IEC 14496-30) fragments. If using delivery via HLS/TS, then text is delivered as chunked VTT. |
| 23 | + |
| 24 | +This article describes how to enable live transcription when streaming a Live Event with Azure Media Services v3. Before you proceed, make sure you are familiar with the use of Media Services v3 REST APIs (see [this tutorial](stream-files-tutorial-with-rest.md) for details). You should also be familiar with the [live streaming](live-streaming-overview.md) concept. It is recommended to complete the [Stream live with Media Services](stream-live-tutorial-with-api.md) tutorial). |
| 25 | + |
| 26 | +> [!NOTE] |
| 27 | +> Currently, live transcription is only available as a preview feature in the West US 2 region. It supports transcription of spoken words in English to text. The API reference for this feature is in this document – since it is in preview, the details are not available with our REST documents. |
| 28 | +
|
| 29 | +## Creating the Live Event |
| 30 | + |
| 31 | +To create the Live Event, you would send the PUT operation to the 2019-05-01 version, such as: |
| 32 | + |
| 33 | +``` |
| 34 | +PUT https://management.azure.com/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Media/mediaServices/:accountName/liveEvents/:liveEventName?api-version=2019-05-01-preview&autoStart=true |
| 35 | +``` |
| 36 | + |
| 37 | +The operation has the following body (where a pass-through Live Event is created with RTMP as the ingest protocol). Note the addition of a transcriptions property. The only allowed value for language is en-US. |
| 38 | + |
| 39 | +``` |
| 40 | +{ |
| 41 | + "properties": { |
| 42 | + "description": "Demonstrate how to enable live transcriptions", |
| 43 | + "input": { |
| 44 | + "streamingProtocol": "RTMP", |
| 45 | + "accessControl": { |
| 46 | + "ip": { |
| 47 | + "allow": [ |
| 48 | + { |
| 49 | + "name": "Allow All", |
| 50 | + "address": "0.0.0.0", |
| 51 | + "subnetPrefixLength": 0 |
| 52 | + } |
| 53 | + ] |
| 54 | + } |
| 55 | + } |
| 56 | + }, |
| 57 | + "preview": { |
| 58 | + "accessControl": { |
| 59 | + "ip": { |
| 60 | + "allow": [ |
| 61 | + { |
| 62 | + "name": "Allow All", |
| 63 | + "address": "0.0.0.0", |
| 64 | + "subnetPrefixLength": 0 |
| 65 | + } |
| 66 | + ] |
| 67 | + } |
| 68 | + } |
| 69 | + }, |
| 70 | + "encoding": { |
| 71 | + "encodingType": "None" |
| 72 | + }, |
| 73 | + "transcriptions": [ |
| 74 | + { |
| 75 | + "language": "en-US" |
| 76 | + } |
| 77 | + ], |
| 78 | + "vanityUrl": false, |
| 79 | + "streamOptions": [ |
| 80 | + "Default" |
| 81 | + ] |
| 82 | + }, |
| 83 | + "location": "West US 2" |
| 84 | +} |
| 85 | +``` |
| 86 | + |
| 87 | +You should poll the status of the Live Event until it goes into the “Running” state, which indicates that you can now send a contribution RTMP feed. You can now follow the same steps as in this tutorial, such as checking the preview feed, and creating Live Outputs. |
| 88 | + |
| 89 | +## Delivery and playback |
| 90 | + |
| 91 | +Review the [Dynamic packaging overview](dynamic-packaging-overview.md#to-prepare-your-source-files-for-delivery) article of how our service uses dynamic packaging to deliver video, audio, and now text in different protocols. When you publish your live stream using MPEG-DASH or HLS/CMAF, then along with video and audio, our service will deliver the transcribed text in IMSC1.1 compatible TTML, packaged into MPEG-4 Part 30 (ISO/IEC 14496-30) fragments. If using delivery via HLS/TS, then text is delivered as chunked VTT. You can use a web player such as the [Azure Media Player](use-azure-media-player.md) to play the stream. |
| 92 | + |
| 93 | +> [!NOTE] |
| 94 | +> If using Azure Media Player, use version 2.3.3 or later. |
| 95 | +
|
| 96 | +## Known issues |
| 97 | + |
| 98 | +At preview, following are the known issues with Live Transcription |
| 99 | + |
| 100 | +* The feature is available only in West US 2. |
| 101 | +* Applications need to use the preview APIs, described in the [Media Services v3 OpenAPI Specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/mediaservices/resource-manager/Microsoft.Media/preview/2019-05-01-preview/streamingservice.json) specification. |
| 102 | +* The only supported language is English. |
| 103 | +* With respect to content protection, only AES envelope encryption is supported. |
| 104 | + |
| 105 | +## Next steps |
| 106 | + |
| 107 | +[Media Services overview](media-services-overview.md) |
0 commit comments