Windows azure media services encoder

Is this supposed to happen? Do we need to change our implementation and set the. Our apologies for the delay in getting the documentation out. How are you using the single-MP4 Asset after the encode is complete - is there a subsequent Task that requires that the MP4 file be the primary?

Recent Azure Media Service Problem seems to be related in a way, they also get the. Yeah it would have been nice to know beforehand, luckily our environment wasn't live but had it happened a month later things would have been worse off : We would appreciate if we could get emails when changes like these are released, and preferably in advance.

You can make it available in two steps: first, create a Streaming Locator , and second, build the streaming URLs that clients can use. The process of creating a Streaming Locator is called publishing. By default, the Streaming Locator is valid immediately after you make the API calls, and lasts until it's deleted, unless you configure the optional start and end times. In this example, you'll be streaming in-the-clear or non-encrypted content so the predefined clear streaming policy PredefinedStreamingPolicy.

ClearStreamingOnly is used. When using a custom Streaming Policy , you should design a limited set of such policies for your Media Service account, and re-use them for your StreamingLocators whenever the same encryption options and protocols are needed. Your Media Service account has a quota for the number of Streaming Policy entries. You shouldn't be creating a new Streaming Policy for each Streaming Locator. While the sample in this topic discusses streaming, you can use the same call to create a Streaming Locator for delivering video via progressive download.

In this sample, the default Streaming Endpoint is used. When you first create a Media Service account, this default Streaming Endpoint will be in a stopped state, so you need to call Start. In this method, you need the locatorName that was used when creating the Streaming Locator for the output Asset.

Generally, you should clean up everything except objects that you're planning to reuse typically, you'll reuse Transforms, and you'll persist StreamingLocators, etc. If you want your account to be clean after experimenting, delete the resources that you don't plan to reuse. For example, the following code deletes the job, created assets and content key policy:. If you no longer need any of the resources in your resource group, including the Media Services and storage accounts you created for this tutorial, delete the resource group you created earlier.

When developing a multi-threaded app, you should generate and use a new AzureMediaServicesClient object per thread. Check out the Azure Media Services community article to see different ways you can ask questions, give feedback, and get updates about Media Services. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.

Any additional feedback? Given what I can tell from your usage, you probably don't need that anyway. The side benefit of this would be that your encoder output file size will go down marginally, and hence the cost of encodes will too.

The only other point I would is regarding the workflow by which you get your video files into Azure in the first place. You say that you're uploading them into blob storage - I assume that you're subsequently copying them into an AMS asset so they can be configured as inputs for the job. If that's right, you may save a bit of time by uploading directly into an asset. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 7 years, 3 months ago. Active 7 years, 2 months ago. Viewed times. Improve this question. Trent Scheffert Trent Scheffert 1 1 silver badge 14 14 bronze badges. Add a comment.

For information, see How to generate thumbnails using Media Encoder Standard. For information, see How to trim videos using Media Encoder Standard.

For information, see How to create overlays using Media Encoder Standard. The Media Services blog. If your input video does not contain closed captioning, the output Asset will still contain an empty TTML file. Use the User Voice forum to provide feedback and make suggestions on how to improve Azure Media Services. You also can go directly to one of the following categories:.

Skip to main content. This browser is no longer supported.