locked
Windows Azure Media Service Details RRS feed

  • Question

  • Guys, I need some information on WAMS, I trying for the first time WAM.

    We wanted to achieve below points

    1. Able to store the Video, Audio

    2. Handling the permission on Video and Audio

    3. Maintain the version of Video, Audio

    4. Encode and Decode the Video and Audio

    5. should be able to watch the video on-line stored in blob   

    6. Search for Video in the blob

     


    Friday, October 25, 2013 5:45 AM

Answers

  • Hi Sharan,

    We'll need to get a bit more information from you to answer your initial set of questions. There are some parts of the workflow that you describe that we support today, and some that are going to be custom work that you would build on top of the core platform services of WAMS

    I'll  quickly answer your basic questions and ask a few more as I go.

    1. Yes, WAMS provides the ability to upload and store both audio or video Assets.  We store the assets in an underlying Windows Azure Storage account. You can keep the files there indefinitely and also take advantage of geo-replicated storage.
    2. WAMS does not have the concept of users or roles built into it. That would need to be built on top of our components. Typically that is done using authentication at your web site layer before serving the content to your customers.  If you need to protect the content from unwanted distribution or access, you can use a Digital Rights Management solution like Microsoft PlayReady.  WAMS supports PlayReady encryption of content, but we do not provide the license delivery service where customer authentication and authorization would happen. For that we do provide 3rd party partners like EZDRM or BuyDRM,  or you can license and host a PlayReady server in an IaaS role on your own. 
    3. This one I would have to understand your scenario more.  Version control and management is typically done at a CMS layer or at a Digital Asset Management system.  WAMS is not a CMS or DAM.  We provide the platform to support encoding, streaming, encryption and storage of media assets.  We do not provide the content management APIs where versioning would best be implemented. Version is just Metadata about the underlying Asset.  A version control and management system could be built on top of our Assets API, but you would be responsible for tracking the version metadata and linking back to the Assets in our API. We support the Alternate ID property on our Asset Entities to allow for this "foreign key" mapping back to external metadata stores.
    4. This you can do in WAMS by publishing the encoded assets and playing them back in any one of the supported players or formats that we have. This includes Smooth Streaming in Silverlight or Flash, Apple HLS in iOS, and MPEG DASH support in modern browsers like IE 11 and Chrome.
    5. Search is a function of Asset Management or Content Management systems. Since WAMS does not provide a metadata API for Assets at this time, this would need to be a metadata system that you build using Table Storage or SQL Azure for tracking the custom metadata that you want to use.  You could then use the Alternate ID property on Assets to map back from your metadata to the WAMS stored Assets.  We have a number of customers that have built Asset management and CMS systems on top of WAMS in this fashion.   Search would then be an index on top of the metadata that you have stored in SQL or Azure Table Storage.   There are many indexing solutions out there, including open source ones like Lucene that could be used to provide search capabilities.   There is also future full text search capabilities coming from other Microsoft teams like SQL Azure.
    Friday, October 25, 2013 8:44 PM

All replies

  • Hi Sharan,

    We'll need to get a bit more information from you to answer your initial set of questions. There are some parts of the workflow that you describe that we support today, and some that are going to be custom work that you would build on top of the core platform services of WAMS

    I'll  quickly answer your basic questions and ask a few more as I go.

    1. Yes, WAMS provides the ability to upload and store both audio or video Assets.  We store the assets in an underlying Windows Azure Storage account. You can keep the files there indefinitely and also take advantage of geo-replicated storage.
    2. WAMS does not have the concept of users or roles built into it. That would need to be built on top of our components. Typically that is done using authentication at your web site layer before serving the content to your customers.  If you need to protect the content from unwanted distribution or access, you can use a Digital Rights Management solution like Microsoft PlayReady.  WAMS supports PlayReady encryption of content, but we do not provide the license delivery service where customer authentication and authorization would happen. For that we do provide 3rd party partners like EZDRM or BuyDRM,  or you can license and host a PlayReady server in an IaaS role on your own. 
    3. This one I would have to understand your scenario more.  Version control and management is typically done at a CMS layer or at a Digital Asset Management system.  WAMS is not a CMS or DAM.  We provide the platform to support encoding, streaming, encryption and storage of media assets.  We do not provide the content management APIs where versioning would best be implemented. Version is just Metadata about the underlying Asset.  A version control and management system could be built on top of our Assets API, but you would be responsible for tracking the version metadata and linking back to the Assets in our API. We support the Alternate ID property on our Asset Entities to allow for this "foreign key" mapping back to external metadata stores.
    4. This you can do in WAMS by publishing the encoded assets and playing them back in any one of the supported players or formats that we have. This includes Smooth Streaming in Silverlight or Flash, Apple HLS in iOS, and MPEG DASH support in modern browsers like IE 11 and Chrome.
    5. Search is a function of Asset Management or Content Management systems. Since WAMS does not provide a metadata API for Assets at this time, this would need to be a metadata system that you build using Table Storage or SQL Azure for tracking the custom metadata that you want to use.  You could then use the Alternate ID property on Assets to map back from your metadata to the WAMS stored Assets.  We have a number of customers that have built Asset management and CMS systems on top of WAMS in this fashion.   Search would then be an index on top of the metadata that you have stored in SQL or Azure Table Storage.   There are many indexing solutions out there, including open source ones like Lucene that could be used to provide search capabilities.   There is also future full text search capabilities coming from other Microsoft teams like SQL Azure.
    Friday, October 25, 2013 8:44 PM
  • Thanks for the reply ....
    Monday, October 28, 2013 8:49 AM