This blog post is to introduce what type of advertising support we have through Microsoft Media platform player framework(aka MMPPF). If you want to build a video application on Windows 8 platform, you may want to utilize this out-of-box advertising support to monetize your application. Read More Here
This is a walk-through of how to add VMAP (Digital Video Multiple Ad Playlist) support for your Windows 8 video application using Microsoft Media Platform Player Framework (aka MMPPF). If you want to know more about VMAP standard or overall advertising support for Windows 8 through MMPPF, you could refer to my the other blog.
1. Microsoft Media Platform Player Framework(download): currently this link points to Player Framework for Windows 8 Preview 5 (Refresh) and you should download and install Microsoft.PlayerFramework.vsix file showed below. It is also extremely useful to download Microsoft.PlayerFramework.Source.zip which is a sample application contain all the features that released. Read More Here
This blog is for demoing how to add closed caption for video by using Microsoft Media Platform Player Framework (MMPPF). MMPPF supports both Plain text and Timed Text closed caption.
This sample is build with Windows 8 RTM and Player framework preview 5, using Visual Studio 2012 RTM.
I am a program manager currently working on Windows Azure Media Services(WAMS) team. This blog is my first tempt for trying to explain what WAMS is. We released Windows Azure Media Services Preview in June 2012. Currently we offer a 90 days free trail period for developers. If you are a Azure subscriber, you have up to 1 TB encoding volume per month. And if you are on Azure 90 days free subscription plan, you will have up to 20 GB data in your storage account. You could check out this blog – how to sign up for Windows Azure Media Services. Continue Reading
Sometime uploading asset could take a long time and it is useful to track the uploading progress. We provide HTTP uploading currently and in the next release, we will support UDP fast upload with our partner.
To track progress, we provide UploadProgressEventArgs which describe the status of an upload operation.
Code Snippet showed as below: Read More here
Yesterday we announced the release of Smooth Streaming Client SDK Beta 2 for Windows Store Apps.The Smooth Streaming Client SDK Beta 2 for Windows Store Apps enables developers to build Windows Store applications that can play on-demand and live Smooth Streaming content with or without Microsoft PlayReady protection.
This blog will walk-through how you could access Windows Azure Media Services programmatically, and convert a .MP4 file into Smooth Streaming format. Before getting started, you should have the following items prepared:
- • Create a Media Services account in a new or existing Windows Azure subscription. If you don’t have one, you could check out my blog Getting started with Windows Azure Media Services.
- • Windows Azure SDK 1.6 (November 2011): [link]
- • Windows Azure Media Services SDK (June 2012 Preview): [link]
- • WCF Data Services 5.0 for OData V3: [link]
- • Visual Studio 2010 SP1 and .NET framework 3.5 SP1 and 4
This blog shows you how to request for Windows Azure Media Services Preview and create an account through Windows Azure portal.
Sign up for the preview
1. Go to windowsazure.com and obtain a free-trail account or login with your own account.
When you generate a media source for smooth streaming you may want to test whether it works with a default player. Here it is a great tool we provide for you to monitor the health of your video source: Smooth Streaming Health Monitor ( http://smf.cloudapp.net/healthmonitor ), built by an awesome developer Tim Greenfield. You could either use this player to test your media source (built with Microsoft Player Framework) or you could use the traffic dashboard provided in this health monitor to test your player and media source. This tool is great for you to debug and analyze your media application or media source. In figure 1 below, it shows how this tool looks like, and you could click for a larger view. Read the rest of the post…
This is the public signature of CacheRequest2 and it is inherited from CacheRequest.
Read the rest of the post…