You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/media-services/latest/asset-create-asset-upload-portal-quickstart.md
+92-53Lines changed: 92 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Use portal to upload, encode, and stream content
3
3
description: This quickstart shows you how to use portal to upload, encode, and stream content with Azure Media Services.
4
4
ms.topic: quickstart
5
-
ms.date: 08/31/2020
5
+
ms.date: 01/14/2022
6
6
author: IngridAtMicrosoft
7
7
ms.author: inhenkel
8
8
manager: femila
@@ -16,96 +16,135 @@ This quickstart shows you how to use the Azure portal to upload, encode, and str
16
16
17
17
## Overview
18
18
19
-
* To start managing, encrypting, encoding, analyzing, and streaming media content in Azure, you need to create a Media Services account and upload your high-quality digital media file into an **asset**.
19
+
* To start managing, encrypting, encoding, analyzing, and streaming media content in Azure, you need to [create a Media Services account](account-create-how-to.md).
20
20
21
21
> [!NOTE]
22
-
> If your video was previously uploaded into the Media Services account using Media Services v3 API or the content was generated based on a live output, you will not see the **Encode**, **Analyze**, or **Encrypt** buttons in the Azure portal. Use the Media Services v3 APIs to perform these tasks.
22
+
> If you previously uploaded a video into the Media Services account using Media Services v3 API or the content was generated based on a live output, you will not see the **Encode**, **Analyze**, or **Encrypt** buttons in the Azure portal. Use the Media Services v3 APIs to perform these tasks.
23
23
24
24
Review the following:
25
-
26
-
*[Cloud upload and storage](storage-account-concept.md)
27
-
*[Assets concept](assets-concept.md)
28
-
* Once you upload your high-quality digital media file into an asset (an input asset), you can process it (encode or analyze). The processed content goes into another asset (output asset).
25
+
*[Assets concept](assets-concept.md)
26
+
*[Cloud upload and storage](storage-account-concept.md)
27
+
*[Naming conventions for resource names](media-services-apis-overview.md#naming-conventions)
28
+
29
+
* Once you upload your high-quality digital media file into an asset (an input asset), you can process it (encode or analyze). The processed content goes into another asset (output asset).
29
30
*[Encode](encode-concept.md) your uploaded file into formats that can be played on a wide variety of browsers and devices.
30
31
*[Analyze](analyze-video-audio-files-concept.md) your uploaded file.
31
32
32
-
Currently, when using the Azure portal, you can do the following: generate a TTML and WebVTT closed caption files. Files in these formats can be used to make audio and video files accessible to people with hearing disability. You can also extract keywords from your content.
33
+
Presently, when using the Azure portal, you can perform the operations such as generating TTML and WebVTT closed caption files. Files in these formats can be used to make the audio and video files accessible to people with hearing or visual disability. You can also extract keywords from your content.
33
34
34
-
For a rich experience that enables you to extract insights from your video and audio files, use Media Services v3 presets (as described in [Tutorial: Analyze videos with Media Services v3](analyze-videos-tutorial.md)). <br/>If you want more detailed insights, use [Video Analyzer for Media](../../azure-video-analyzer/video-analyzer-for-media-docs/index.yml) directly.
35
-
* Once your content is processed, you can deliver media content to client players. To make videos in the output asset available to clients for playback, you have to create a **streaming locator**. When creating the **streaming locator**, you need to specify a **streaming policy**. **Streaming policies** enable you to define streaming protocols and encryption options (if any) for your **streaming locators**.
36
-
37
-
Review:
35
+
For a rich experience that enables you to extract insights from your audio and video files, use Media Services v3 presets. For more information, see [Tutorial: Analyze videos with Media Services v3](analyze-videos-tutorial.md). If you require detailed insights, use [Video Analyzer for Media](../../azure-video-analyzer/video-analyzer-for-media-docs/index.yml) directly.
36
+
37
+
* After the content gets processed, you can deliver media content to the client players. To make the videos in the output asset available to the clients for playback, you have to create a [streaming locator](stream-streaming-locators-concept.md). When creating a streaming locator, you need to specify a [streaming policy](stream-streaming-policy-concept.md). Streaming policies enable you to define streaming protocols and encryption options (if any) for your streaming locators. For information on packaging and filtering content, see [Packaging and delivery](encode-dynamic-packaging-concept.md) and [Filters](filters-concept.md).
*[Packaging and delivery](encode-dynamic-packaging-concept.md)
42
-
*[Filters](filters-concept.md)
43
-
* You can protect your content by encrypting it with Advanced Encryption Standard (AES-128) or/and any of the three major DRM systems: Microsoft PlayReady, Google Widevine, and Apple FairPlay. The [Encrypt content with the Azure portal](drm-encrypt-content-how-to.md) quickstart shows how to configure content protection.
39
+
* You can protect your content by encrypting it with Advanced Encryption Standard (AES-128) or/and any of the three major DRM systems such as Microsoft PlayReady, Google Widevine, and Apple FairPlay. For information on how to configure the content protection, see [Quickstart: Use portal to encrypt content](drm-encrypt-content-how-to.md).
1. Choose a **Storage account** from the pull down menu.
57
+
58
+
59
+
60
+
1. Browse the file that you want to upload. This creates an **Asset name** for your media. If required, you can edit this **Asset name**.
50
61
51
-
## Upload
62
+
> [!TIP]
63
+
> If you want to choose multiple files, add them to one folder in Windows File Explorer. When browsing to **Upload files**, select all the files. This creates multiple assets.
64
+
65
+
1. Select the desired option at the bottom of the **Upload new assets** window.
66
+
1. Navigate to your **Assets** resource window. After a successful upload, a new asset gets added to the list.
67
+
68
+
## Add transform
69
+
70
+
1. Under the **Media Services** services, select **Transforms + jobs**.
52
71
53
-
1. Sign in at the [Azure portal](https://portal.azure.com/).
54
-
1. Locate and click on your Media Services account.
55
-
1. Select **Assets (new)**.
56
-
1. Press **Upload** in the top of the window.
57
-
1. Drag and drop or browse to a file that you want to upload.
72
+
58
73
59
-
If you navigate to your assets window, you will see that a new asset was added to the list:
74
+
1. Select **Add transform**.
75
+
1. In the **Add a transform** window, enter the details.
76
+
1. If your media is a video, select **Encoding** as your **Transform type**. Select a **Built-in preset name** from the pull down menu. For more information, see [EncoderNamedPreset](/rest/api/media/transforms/create-or-update#encodernamedpreset).
60
77
61
-
78
+
62
79
63
-
## Encode
80
+
1. Select **Add**.
64
81
65
-
1. Select **Assets (new)**.
66
-
1. Select your new asset (added in the last step).
67
-
1. Click **Encode** at the top of the window.
82
+
## Encode (Add job)
68
83
69
-
Pressing this button starts the encoding job. When it completes successfully generates an output asset that contains the encoded content.
84
+
1. Select either **Assets** or **Transforms + jobs**.
85
+
1. Select **Add job** at the top of the resource window.
86
+
1. In **Create a job** window, enter the details. Select **Create**.
70
87
71
-
If you navigate to your assets window, you will see that the output asset was added to the list:
88
+
72
89
73
-
90
+
1. Navigate to **Transforms + jobs**. Select the **Transform name** to check the job status.
91
+
92
+
A job goes through multiple stages, such as **Scheduled**, **Queued**, **Processing**, and **Finished**.
74
93
75
-
## Monitor the job progress
94
+
76
95
77
-
To view job status, navigate to **Jobs**. The job usually goes through the following states: Scheduled, Queued, Processing, Finished (the final state). If the job has encountered an error, you get the Error state.
96
+
If the job has encountered an error, you get the **Error** state.
1. Navigate to your **Assets** resource window. After the job gets created successfully, it generates an output asset that contains the encoded content.
99
+
100
+
80
101
81
102
## Publish and stream
82
103
83
-
To publish an asset, you now need to add a streaming locator to your asset.
104
+
To publish an asset, you need to add a streaming locator to your asset and run the streaming endpoint.
84
105
85
-
### Streaming locator
106
+
### Add streaming locator
86
107
87
-
1. In the **Streaming locator** section, press **+ Add a streaming locator**.
88
-
This publishes the asset and generates the streaming URLs.
108
+
1. Under Media Services, select **Assets**.
109
+
1. Select the output asset.
110
+
1. Select **New streaming locator**.
89
111
90
-
> [!NOTE]
91
-
> If you want for your stream to be encrypted, you need to create a content key policy and set it on the streaming locator. For details, see [Encrypt content with the Azure portal](drm-encrypt-content-how-to.md).
92
-
1. In the **Add streaming locator** window, you choose one of the predefined streaming policies. For detailed information, see [streaming policies](stream-streaming-policy-concept.md)
112
+
1. In **Add streaming locator** window, enter the details. Select a predefined **Streaming policy**. For more information, see [streaming policies](stream-streaming-policy-concept.md).
95
115
96
-
Once the asset has been published, you can stream it right in the portal.
116
+
1. If you want your stream to be encrypted, [Create a content key policy](drm-encrypt-content-how-to#create-a-content-key-policy) and select it in the **Add streaming locator** window.
99
119
100
-
Or, copy the streaming URL and use it in your client player.
120
+
1. Select **Add**. This publishes the asset and generates the streaming URLs.
101
121
102
-
> [!NOTE]
103
-
> Make sure the [streaming endpoint](stream-streaming-endpoint-concept.md) is running. When you first create a Media Service account, the default streaming endpoint is created and it is in a stopped state, so you need to start it before you can stream your content.<br/>You're only billed when your streaming endpoint is in the running state.
122
+
104
123
105
-
## Cleanup resources
124
+
### Start streaming endpoint
125
+
1. Once the asset gets published, you can stream it right in the portal. You can also copy the streaming URL and use it in your client player.
126
+
127
+
Make sure the [streaming endpoint](stream-streaming-endpoint-concept.md) is running. When you first create a Media Services account, a default streaming endpoint gets created and remains in a stopped state. **Start** the streaming endpoint to stream your content. You're only billed when your streaming endpoint is in the running state.
128
+
129
+
1. Select the output asset.
130
+
1. Select **Start streaming endpoint?**. Select **Start** to run the streaming endpoint. The status of **default** streaming endpoint changes from **Stopped** to **Running**. Your billing will start now.
131
+
132
+
You can now use the streaming URLs to deliver content.
106
133
107
-
If you intend to try the other quickstarts, you should hold on to the resources created. Otherwise, go to the Azure portal, browse to your resource groups, select the resource group under which you ran this quickstart, and delete all the resources.
134
+
108
135
109
-
## Next steps
136
+
1. Select **Reload player**.
137
+
138
+
### Stop streaming endpoint
139
+
140
+
1. Navigate to **Media Services** and select **Streaming endpoints**.
141
+
1. Select your streaming endpoint **Name**. In this quickstart, we are using the **default** streaming endpoint. The current state is **Running**.
142
+
1. Select **Stop**. This opens the **Stop streaming endpoint?** window. Select **Yes**.
143
+
144
+
145
+
146
+
Now, the **default** streaming endpoint is in a **Stopped** state. You cannot use the streaming URLs to deliver the content.
147
+
148
+
## Cleanup resources
110
149
111
-
[Use portal to encrypt content](drm-encrypt-content-how-to.md)
150
+
If you intend to try the other quickstarts, you should hold on to the resources created for this quickstart. Otherwise, sign in to the Azure portal, browse to your resource group, select the resource group under which you followed this quickstart, and delete all the resources.
0 commit comments