Azure Media Services

How can we improve Azure Media Services?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add video meta data like video length to Asset object

    When we use Live, some useful properties like Video length, bitrate for CMS don't have from other system. It's usually video file like mp4 itself have data in property.
    it's useful if there is any Property via API for live streamings to put CMS.

    - Video length
    - Bitrate
    - Video Size

    10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
  2. Job status notification on user specified HTTP endpoint

    It would be great to have job status notifications delivered on a HTTP endpoint of my choice vs. getting notifications on Azure Queue

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
  3. Provide facility to add attributes to files being stored via Media Services to be able to locate these files.

    When we send any file to media service it is kind of depending upon either the file name or the response back from Media Service (i.e. the URL to access the blob). There is no way to associate properties / attributes to file while uploading so that neither response back is needed nor file name is important. It would be good to provide a way to add properties to file and then later search on those attributes.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Nick Drouin responded

    Hi Navin,

    I’ve moved your question to the Media Services (WAMS) section of UserVoice.

    Today, we do not offer a Content Management System (CMS) as an integral component of the Media Services Platform as a Service. We are engaged with existing CMS platform providers to build on top of WAMS. A CMS will typically offer file and asset level metadata storage, searchability, indexing, cross-referencing and web-page-content generation (think online video galleries).

    We have anticipated external CMS, and eventually integrated CMS services. To accommodate, we have designed in the IAsset.AlternateId property. The goal of this text string is for an external CMS to put their table-key into the AlternateId, that way, they can query:
    var theAsset = cloudMediaContext.Assets.Where(a => a.AlternateId == “SomeKeyGuid_FromTheCMS”).FirstOrDefault();

    The workflow is to use the CMS to find the file(s) or Asset via the metadata stored in the CMS, then find…

  4. Add better support for subtitles in SDK

    Given the ID of a media asset, there is no way to determine whether there is a subtitles file for that asset, except to search within the asset for a suitable file by the file extension. (i.e. get an asset that ends with VTT) And then, if you find one, there is no way to know what language it contains. There should be a way to do this through the SDK, storing the name of a subtitles file and its language attribute so that playback requires only the streaming URL to the asset, and the manifest would be properly updated…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
  5. Expose asset / file traffic (data transfer) information

    Azure Media Service bills customers by traffic volume (data transfer), however, I don't see a way for customers to know the actual traffic for their media files. This will be especially usefully if the customers are building a service for their clients, so they need to know which media assets are having what traffic volume.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
  6. videoId is dynamic type

    in https://docs.microsoft.com/en-us/azure/media-services/video-indexer/video-indexer-use-apis#code-sample
    when I run the part:

    // get the video id from the upload result
    var videoId = JsonConvert.DeserializeObject<dynamic>(uploadResult)["id"];
    Debug.WriteLine("Uploaded");
    Debug.WriteLine("Video ID: " + videoId);

    It gives me a RuntimeBinderException like this:
    Additional information: Cannot dynamically invoke method 'WriteLine' because it has a Conditional attribute.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
  7. Don't return 204 on content update

    Have a read:
    http://blog.ploeh.dk/2013/04/30/rest-lesson-learned-avoid-204-responses/
    When building a library like that node-azure-media library you want to provide a callback that the user can interpret. Not providing the updated entity in the body of the request is completely illogical and against any common practices. Please return a 200 with the updated entity in the body for ALL MERGE requests.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  REST API and Platform  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base