Skip to content

Commit b33ab5e

Browse files
authored
Merge pull request #89331 from Juliako/v1v2migration
new topic
2 parents 51157de + dc21178 commit b33ab5e

File tree

6 files changed

+116
-19
lines changed

6 files changed

+116
-19
lines changed

articles/media-services/previous/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,8 @@
5858
- name: Migrate from Windows Azure Media Encoder
5959
href: migrate-windows-azure-media-encoder.md
6060
displayName: WAME
61+
- name: Migrate from Indexer v1 and v2
62+
href: migrate-indexer-v1-v2.md
6163
- name: Manage
6264
items:
6365
- name: Accounts

articles/media-services/previous/legacy-components.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,15 @@ Over time, there have been steady improvements and enhancements to Media Service
2222

2323
## Legacy components and migration guidance
2424

25-
### Media processors
26-
2725
We are announcing deprecation of the *Windows Azure Media Encoder* (WAME) and *Azure Media Encoder* (AME) media processors. These processors are being retired on November 30, 2019.
2826

2927
* [Migrate from Windows Azure Media Encoder to Media Encoder Standard](migrate-windows-azure-media-encoder.md)
3028
* [Migrate from Azure Media Encoder to Media Encoder Standard](migrate-azure-media-encoder.md)
3129

30+
We are also announcing deprecation of *Azure Media Indexer* and *Azure Media Indexer 2*. The [Azure Media Indexer](media-services-index-content.md) media processor will be retired on October 1st of 2020. The [[Azure Media Indexer 2 (preview)](media-services-process-content-with-indexer2.md) media processors will be retired on January 1 of 2019. [Azure Media Services Video Indexer](https://docs.microsoft.com/azure/media-services/video-indexer/) replaces these legacy media processors.
31+
32+
* [Migrate from Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer](migrate-indexer-v1-v2.md).
33+
3234
## Next steps
3335

3436
[Migration guidance for moving from Media Services v2 to v3](../latest/migrate-from-v2-to-v3.md)

articles/media-services/previous/media-services-index-content.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,18 +13,19 @@ ms.workload: media
1313
ms.tgt_pltfrm: na
1414
ms.devlang: dotnet
1515
ms.topic: article
16-
ms.date: 03/18/2019
16+
ms.date: 09/22/2019
1717
ms.author: juliako
1818
ms.reviewer: johndeu
1919

2020
---
2121
# Indexing Media Files with Azure Media Indexer
22+
23+
> [!NOTE]
24+
> The [Azure Media Indexer](media-services-index-content.md) media processor will be retired on October 1st of 2020. [Azure Media Services Video Indexer](https://docs.microsoft.com/azure/media-services/video-indexer/) replaces this legacy media processor. For more information, see [Migrate from Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer](migrate-indexer-v1-v2.md).
25+
2226
Azure Media Indexer enables you to make content of your media files searchable and to generate a full-text transcript for closed captioning and keywords. You can process one media file or multiple media files in a batch.
2327

24-
> [!IMPORTANT]
25-
> When indexing content, make sure to use media files that have clear speech (without background music, noise, effects, or microphone hiss). Some examples of appropriate content are: recorded meetings, lectures, or presentations. The following content might not be suitable for indexing: movies, TV shows, anything with mixed audio and sound effects, poorly recorded content with background noise (hiss).
26-
>
27-
>
28+
When indexing content, make sure to use media files that have clear speech (without background music, noise, effects, or microphone hiss). Some examples of appropriate content are: recorded meetings, lectures, or presentations. The following content might not be suitable for indexing: movies, TV shows, anything with mixed audio and sound effects, poorly recorded content with background noise (hiss).
2829

2930
An indexing job can generate the following outputs:
3031

articles/media-services/previous/media-services-process-content-with-indexer2.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -12,29 +12,28 @@ ms.workload: media
1212
ms.tgt_pltfrm: na
1313
ms.devlang: dotnet
1414
ms.topic: article
15-
ms.date: 03/19/2019
15+
ms.date: 09/22/2019
1616
ms.author: juliako
1717
ms.reviewer: adsolank
1818
---
1919
# Indexing Media Files with Azure Media Indexer 2 Preview
20-
## Overview
20+
21+
> [!NOTE]
22+
> The [Azure Media Indexer 2](media-services-process-content-with-indexer2.md) media processor will be retired on January 1 of 2020. [Azure Media Services Video Indexer](https://docs.microsoft.com/azure/media-services/video-indexer/) replaces this legacy media processor. For more information, see [Migrate from Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer](migrate-indexer-v1-v2.md).
23+
2124
The **Azure Media Indexer 2 Preview** media processor (MP) enables you to make media files and content searchable, as well as generate closed captioning tracks. Compared to the previous version of [Azure Media Indexer](media-services-index-content.md), **Azure Media Indexer 2 Preview** performs faster indexing and offers broader language support. Supported languages include English, Spanish, French, German, Italian, Chinese (Mandarin, Simplified), Portuguese, Arabic, Russian, and Japanese.
2225

2326
The **Azure Media Indexer 2 Preview** MP is currently in Preview.
2427

2528
This article shows how to create indexing jobs with **Azure Media Indexer 2 Preview**.
2629

27-
> [!NOTE]
28-
> The following considerations apply:
29-
>
30-
> Indexer 2 is not supported in Azure China and Azure Government.
31-
>
32-
> When indexing content, make sure to use media files that have very clear speech (without background music, noise, effects, or microphone hiss). Some examples of appropriate content are: recorded meetings, lectures, or presentations. The following content might not be suitable for indexing: movies, TV shows, anything with mixed audio and sound effects, poorly recorded content with background noise (hiss).
33-
>
34-
>
35-
36-
This article gives details about **Azure Media Indexer 2 Preview** and shows how to use it with Media Services SDK for .NET
30+
## Considerations
3731

32+
The following considerations apply:
33+
34+
* Indexer 2 is not supported in Azure China 21Vianet and Azure Government.
35+
* When indexing content, make sure to use media files that have very clear speech (without background music, noise, effects, or microphone hiss). Some examples of appropriate content are: recorded meetings, lectures, or presentations. The following content might not be suitable for indexing: movies, TV shows, anything with mixed audio and sound effects, poorly recorded content with background noise (hiss).
36+
3837
## Input and output files
3938
### Input files
4039
Audio or video files

articles/media-services/previous/media-services-release-notes.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,14 @@ We want to hear from our customers so that we can focus on fixing problems that
4242
## <a id="rest_version_history"/>REST API version history
4343
For information about the Media Services REST API version history, see the [Azure Media Services REST API reference].
4444

45+
## September 2019
46+
47+
### Deprecation of media processors
48+
49+
We are announcing deprecation of *Azure Media Indexer* and *Azure Media Indexer 2*. The [Azure Media Indexer](media-services-index-content.md) media processor will be retired on October 1st of 2020. The [Azure Media Indexer 2 (preview)](media-services-process-content-with-indexer2.md) media processors will be retired on January 1 of 2020. [Azure Media Services Video Indexer](https://docs.microsoft.com/azure/media-services/video-indexer/) replaces these legacy media processors.
50+
51+
For more information, see [Migrate from Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer](migrate-indexer-v1-v2.md).
52+
4553
## August 2019
4654

4755
### Deprecation of media processors
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
---
2+
title: Migrate from Indexer v1 and v2 to Azure Media Services Video Indexer | Microsoft Docs
3+
description: This topic discusses how to migrate from Azure Media Indexer v1 and v2 to Azure Media Services Video Indexer.
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: na
14+
ms.topic: article
15+
ms.date: 09/20/2019
16+
ms.author: juliako
17+
18+
---
19+
# Migrate from Media Indexer and Media Indexer 2 to Video Indexer
20+
21+
The [Azure Media Indexer](media-services-index-content.md) media processor will be retired on October 1st of 2020. The [Azure Media Indexer Indexer 2 (preview)](media-services-process-content-with-indexer2.md) media processors will be retired on January 1 of 2020. [Azure Media Services Video Indexer](https://docs.microsoft.com/azure/media-services/video-indexer/) replaces these legacy media processors.
22+
23+
Azure Media Services Video Indexer is built on Azure Media Analytics, Azure Search, Cognitive Services (such as the Face API, Microsoft Translator, the Computer Vision API, and Custom Speech Service). It enables you to extract the insights from your videos using Video Indexer video and audio models. To see what scenarios Video Indexer can be used in, what features it offers, and how to get started, see [Video Indexer video and audio models](../video-indexer/video-indexer-overview.md).
24+
25+
You can extract insights from your video and audio files by using the [Azure Media Services v3 analyzer presets](../latest/analyzing-video-audio-files-concept.md) or directly by using the [Video Indexer APIs](https://api-portal.videoindexer.ai/). Currently, there is an overlap between features offered by the Video Indexer APIs and the Media Services v3 APIs.
26+
27+
> [!NOTE]
28+
> To understand when you would want to use Video Indexer vs. Media Services analyzer presets, check out the [comparison document](../video-indexer/compare-video-indexer-with-media-services-presets.md).
29+
30+
This article discusses the steps for migrating from the Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer.
31+
32+
## Migration options
33+
34+
|If you require |then |
35+
|---|---|
36+
|a solution that provides a speech-to-text transcription for any media file format in a closed caption file formats: VTT, SRT, or TTML<br/>as well as additional audio insights such as: keywords, topic inferencing, acoustic events, speaker diarization, entities extraction and translation| update your applications to use the Azure Video Indexer capabilities through the Video Indexer v2 REST API or the Azure Media Services v3 Audio Analyzer preset.|
37+
|speech-to-text capabilities| use the Cognitive Services Speech API directly.|
38+
39+
## Getting started with Video Indexer
40+
41+
The following section points you to relevant links: [How can I get started with Video Indexer?](https://docs.microsoft.com/azure/media-services/video-indexer/video-indexer-overview#how-can-i-get-started-with-video-indexer)
42+
43+
## Getting started with Media Services v3 APIs
44+
45+
Azure Media Services v3 API enables you to extract insights from your video and audio files through the [Azure Media Services v3 analyzer presets](../latest/analyzing-video-audio-files-concept.md).
46+
47+
**AudioAnalyzerPreset** enables you to extract multiple audio insights from an audio or video file. The output includes a VTT or TTML file for the audio transcript and a JSON file (with all the additional audio insights). The audio insights include keywords, speaker indexing, and speech sentiment analysis. AudioAnalyzerPreset also supports language detection for specific languages. For detailed information, see [Transforms](https://docs.microsoft.com/rest/api/media/transforms/createorupdate#audioanalyzerpreset).
48+
49+
### Get started
50+
51+
To get started see:
52+
53+
* [Tutorial](../latest/analyze-videos-tutorial-with-api.md)
54+
* AudioAnalyzerPreset samples: [Java SDK](https://github.com/Azure-Samples/media-services-v3-java/tree/master/AudioAnalytics/AudioAnalyzer) or [.NET SDK](https://github.com/Azure-Samples/media-services-v3-dotnet/tree/master/AudioAnalytics/AudioAnalyzer)
55+
* VideoAnalyzerPreset samples: [Java SDK](https://github.com/Azure-Samples/media-services-v3-java/tree/master/VideoAnalytics/VideoAnalyzer) or [.NET SDK](https://github.com/Azure-Samples/media-services-v3-dotnet/tree/master/VideoAnalytics/VideoAnalyzer)
56+
57+
## Getting started with Cognitive Services Speech Services
58+
59+
[Azure Cognitive Services](https://docs.microsoft.com/azure/cognitive-services/) provides a speech-to-text service that transcribes audio streams to text in real time that your applications, tools, or devices can consume or display. You can use speech-to-text to [customize your own acoustic model, language model, or pronunciation model](../../cognitive-services/speech-service/how-to-custom-speech-train-model.md). For more information, see [Cognitive Services speech-to-text](../../cognitive-services/speech-service/speech-to-text.md).
60+
61+
> [!NOTE]
62+
> The speech-to-text service does not take video file formats and only takes [certain audio formats](https://docs.microsoft.com/azure/cognitive-services/speech-service/rest-speech-to-text#audio-formats).
63+
64+
For more information about the text-to-speech service and how to get started, see [What is speech-to-text?](https://docs.microsoft.com/azure/cognitive-services/speech-service/speech-to-text)
65+
66+
## Known differences from deprecated services
67+
68+
You will find that Video Indexer, Azure Media Services v3 AudioAnalyzerPreset, and Cognitive Services Speech Services services are more reliable and produces better quality output than the retired Azure Media Indexer 1 and Azure Media Indexer 2 processors.
69+
70+
Some known differences include:
71+
72+
* Closed caption files in SAMI format will no longer be supported. This is an older caption format that is no longer widely used. It is replaced by TTML, WebVTT, and SRT.
73+
* Audio Indexing Blob (AIB) files will no longer be supported. This feature was specific to the Indexer 1 technology and is no longer offered.
74+
* Cognitive Services Speech Services does not support keyword extraction. However, Video Indexer and Media Services v3 AudioAnalyzerPreset both offer a more robust set of keywords in JSON file format.
75+
76+
## Contact us
77+
78+
If you have questions on the deprecation of Azure Media Indexer 1 and Azure Media Indexer 2 or on migrating to any of the other services, please reach out to us via [email protected]
79+
80+
## Next steps
81+
82+
* [Legacy components](legacy-components.md)
83+
* [Pricing page](https://azure.microsoft.com/pricing/details/media-services/#encoding)
84+
85+

0 commit comments

Comments
 (0)