Vishal Sood

Building your first Smooth Streaming Player using SSME

vsood — Wed, 14 Oct 2009 22:24:00 GMT

In this post I plan to cover building a very basic Smooth Streaming Player using Smooth Streaming Media Element (SSME) part of Smooth Streaming Player Development Kit. In other words, building a “Hello World” equivalent for Smooth Streaming Client (“Hello Smooth Streaming”). This post is split into two parts. In the first part, I will be covering how to get basic playback working in a browser window for Smooth Streaming content. This should be really easy as you will see. In the second part, we would add some basic playback controls like Play, Pause, Stop and Volume controls.

Prerequisites

You should either have Visual Web Developer or Visual Studio installed along with Silverlight Tools for Visual Studio. You can get more information on this here.
Install the Smooth Streaming Developer Kit available here.
This is not a XAML overview session so basic XAML knowledge is required.

Building a Simple Smooth Streaming Player for Playback

The very first thing I wanted to cover here was just basic playback. There are no controls. All you get is a browser window that shows the video playing.

The below outlines steps to achieve this:

Open Visual Web Developer or Visual Studio.
Go to: File –> New Project.
Chose Visual C# as project Type and then select Silverlight. Choose Silverlight Application, name it SimplePlayer.
In your project go to references and add a reference to Microsoft.Web.Media.Smoothstreaming.dll (available as a part of Player development Kit)
Modify MainPage.xaml as under. Set the SmoothStreamingSource property in XAML to the location of the Smooth Streaming content. Replace <<Add your URL here>> with the URL of the content (E.g., it will look something like http://example.com/a.isml/Manifest)

Code Snippet

<UserControl x:Class="SimplePlayer.MainPage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" 
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    xmlns:SSME="clr-namespace:Microsoft.Web.Media.SmoothStreaming;assembly=Microsoft.Web.Media.SmoothStreaming"
    mc:Ignorable="d" d:DesignWidth="640" d:DesignHeight="480">
  <Grid x:Name="LayoutRoot">
    <SSME:SmoothStreamingMediaElement AutoPlay="True" x:Name="SmoothPlayer" SmoothStreamingSource="<<Add your URL here>>" Grid.Row="0" />
  </Grid>
</UserControl>

This is all you need to get a basic playback working with Smooth Streaming Media Element.

Adding Playback Controls to your Player

Next, once you have the basic playback working, you may want to add some basic controls like Play/Pause button, Stop Button and Volume Control.

Here is what you will see after completing the steps below:

The UI layout

Here are the pieces we need for this in terms of the layout.

Have portion of the screen, which will display the slider control for volume and Play/Pause and Stop buttons
We need a portion for the Video to display
We need to hook these buttons/slider to SSME

For the overall layout, we are using XAML constructs of Stack Panels. here is how we do it in this example:

Code Snippet

<UserControl x:Class="SimplePlayer.MainPage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" 
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    xmlns:SSME="clr-namespace:Microsoft.Web.Media.SmoothStreaming;assembly=Microsoft.Web.Media.SmoothStreaming"
    mc:Ignorable="d" d:DesignWidth="640" d:DesignHeight="480">
  <Grid x:Name="LayoutRoot">
        <Grid.RowDefinitions>
            <RowDefinition Height="0.95*"></RowDefinition>
            <RowDefinition Height="0.05*"></RowDefinition>
        </Grid.RowDefinitions>
        <SSME:SmoothStreamingMediaElement AutoPlay="True" x:Name="SmoothPlayer" SmoothStreamingSource="<<Add your URL here>>" Grid.Row="0" />
        <StackPanel Orientation="Horizontal" Grid.Row="1">
            <TextBlock x:Name="Volume" VerticalAlignment="Center" Text="Volume" Width="50" />
            <Slider x:Name="VolumeBar" Width="60" Value="{Binding Path=Volume, ElementName=SmoothPlayer, Mode=TwoWay}" />
            <Button x:Name="PlayButton" Width="50" Click="PlayButton_Click" Loaded="PlayButton_Loaded"/>
            <Button x:Name="StopButton" Content="Stop" Width="50" Click="StopButton_Click" />
        </StackPanel>
    </Grid>
</UserControl>

We have a Grid with two rows: the first row is SSME and second is a horizontal Stack Panel that has volume slide and Pause / Stop buttons. This is all we need to get the basic layout.

Linking UI to SSME

The next step after getting the UI is to link it back to SSME. We already know how to play the video in SSME. In this section I would cover how to hook up the buttons and the slider.

Silverlight has a concept of template binding that can be used here. In the case of slider, we have a slider volume UI control and a volume property on SSME. All we need to do here is to tell Silverlight via the XAML to bind the slider value to the volume property on SSME. Here is how we do it:

Code Snippet

<Slider x:Name="VolumeBar" Width="60" Value="{Binding Path=Volume, ElementName=SmoothPlayer, Mode=TwoWay}" />

If you see, all we are doing here is saying that bind the Slider Value to the SmoothPlayer’s Volume Path (or property).

For the Play / Pause and Stop buttons, we take a slightly different approach here:

Code Snippet

<Button x:Name="PlayButton" Width="50" Click="PlayButton_Click" Loaded="PlayButton_Loaded"/>
<Button x:Name="StopButton" Content="Stop" Width="50" Click="StopButton_Click" />

Here we want the following to happen:

For the Play/Pause button, we want to do some actions when the button is loaded and then a different action when it is clicked. For this, we hook these actions to PlayButton_Click and PlayButton_Loaded methods in the MainPage.xaml.cs file
For the Stop button we just need to handle the click so we hook up Click with StopButton_Click method.

In the MainPage.xaml.cs file we need to have these methods and do the needful there. Here is what we are doing in this example:

Note: There are other (better) ways of coding this but for simplicity I have tried to keep it very basic for this example

PlayButton_Loaded

Code Snippet

private void PlayButton_Loaded(object sender, RoutedEventArgs e)
{
    //We need to prepopulate the value of Play/Pause button content, we need to check AutoPlay
    switch (SmoothPlayer.AutoPlay)
    {
        case false:
            PlayButton.Content = "Play";
            break;
        case true:
            PlayButton.Content = "Pause";
            break;
    }
}

PlayButton_Click

Code Snippet

private void PlayButton_Click(object sender, RoutedEventArgs e)
{
    //Monitor the state of the content to determine the right action to take on this button being clicked
    //and then change the text to reflect the next action
    switch (SmoothPlayer.CurrentState)
    {
        case MediaElementState.Playing:
            SmoothPlayer.Pause();
            PlayButton.Content = "Play";
            break;
        case MediaElementState.Stopped:
        case MediaElementState.Paused:
            SmoothPlayer.Play();
            PlayButton.Content = "Pause";
            break;
    }
}

StopButton_Click

Code Snippet

private void StopButton_Click(object sender, RoutedEventArgs e)
{
    //This should simply stop the playback
    SmoothPlayer.Stop();
    //We should also reflect the chang on the play button
    PlayButton.Content = "Play";
}

Summary

In this post, we looked at creating a basic player with common controls for playback of Smooth Streaming Content. Let me know if you have issues or need further help. In subsequent posts I would be diving into adding more features into this player.

The project sample for this example is availble here(SimplePlayer.zip).

Note: These are just samples meant for educational purposes and there is no guarantee conferred on the quality of code

IIS Advanced Logging 1.0 Released

vsood — Mon, 12 Oct 2009 21:11:00 GMT

We proudly announce the release of IIS Advanced Logging 1.0.

IIS Advanced Logging 1.0 includes the following features:

Client-side logging. Advanced Logging builds capabilities into IIS to accept client-side consumption metrics. This provides relevant and important user engagement metrics that your customers will love.
Centralized logging. Advanced Logging provides capabilities to set up a central log farm that collects and logs client-side metrics. This reduces the effort required to collect distributed logs, and consolidated log collection results in more efficient post-processing. I wanted to clarify that this is not for all logging. Note: This is for client-side logging.
Multiple Logs per request. Advanced Logging provides capabilities to filter information relevant to specific purposes by creating multiple logs per request, with each log containing data relevant to the log's purpose. For example, Quality of Service (QoS) data in one log and Analytics data in another. All the post-processing required to distill the information using today's solutions is no longer needed.
Real-time logging. Advanced Logging can extend the platform to support real-time analytics, helping you to provide real-time reports to customers or work with partners to do the same.
Rich/Flexible logging. Advanced Logging does not assume what is important to you. Instead, it provides enough control to specify what fields are important to you, add additional fields with ease, and provide policies around log rollover and request filtering. These capabilities do not exist today. Now you can log any of the HTTP request/response headers, IIS server variables, and client-side fields with simple configuration through the management console.
Application Logging. Making use of the IIS configuration system, Advanced Logging provides capabilities to generate separate logs for sites, applications and so on.
Module Specific Log fields. If you are developing modules for IIS, you can specify custom fields that can be collected in logs.
Log Filtering. Logging now has the ability to filter requests to be logged based on the values in the log fields

You can learn more about the feature by reading the walkthroughs:

Getting started with Advanced Logging
Real-Time Logging
Client Logging
Learn more about the feature on - http://www.iis.net/extensions/AdvancedLogging

We eagerly await your feedback and comments on the Advanced Logging Discussion Forum.

IIS Smooth Streaming Player Development Kit 1.0 – Beta 1 Released

vsood — Fri, 09 Oct 2009 19:08:00 GMT

Today, we released IIS Media Services 3.0 that supports both On Demand, Live Smooth Streaming and IIS Advanced Logging. Please refer to the announcement of this release in Chris Knowlton’s blog post for details. As a part of this release, we are very both excited and pleased to announce and release a Beta of IIS Smooth Streaming Player Development Kit 1.0. This is intended to aid the development of rich Smooth Streaming players and experiences. This Kit allows you to build players for both On Demand and Live playback with full DVR capabilities, Live Ad Insertion, Multiple Camera Angles and many more such rich functionalities. This Kit is available for download here – Download IIS Smooth Streaming Player Development Kit 1.0 – Beta 1.

The kit includes:

Smooth Streaming Player SDK – This enables developers and designers to build rich Smooth Streaming player experiences. We are providing a .net (Silverlight) based SDK with full XAML support. The core part of this infrastructure is Smooth Streaming Media Element that is similar to Silverlight Media Element if you are already familiar with Silverlight development platform. There is initial documentation of the APIs are available on MSDN.
Push Encoder – This tool allows you to simulate a live stream for testing purposes.
Sample Smooth Streaming Player (built on Smooth Streaming Player SDK) – This is a sample that uses Smooth Streaming Player SDK and enables you to test the IIS Media Services 3.0.

More instructions on using the Sample player and Push Encoder to test Live Smooth Streaming in your environment are available in the walkthrough here.

As I mentioned earlier, the Smooth Streaming Media Element (SSME) APIs provide an easy interface for developers and designers to create rich Smooth Streaming experiences using the Silverlight platform. These APIs provide support for simple operations like Play, Pause and Stop and also more complex ones like scheduling Ads, selecting and tracking bit-rates for Smooth Streaming playback and many more. Please stay tuned on this blog for samples on how to use these APIs to build experiences. I will start with basic playback and progress on to building richer player applications.

In the meantime here is a high level overview of features that SSME supports today:

Basic Playback controls
- APIs like Play, Pause, Stop, etc.
- Events for Playback and Diagnostics
- Properties to track position, etc.
Advanced Playback support
- DVR support for Live Smooth Streaming
- Trick Play: Slow Motion
Monetization
- Ad Playback integration – scheduling capabilities, tracking Ad progress
- Live Ad Insertion w/ Live Smooth Streaming
- Rich Analytics w/ IIS Advanced Logging
Content Protection – PlayReady integration
XAML support for designers
Selecting Tracks for playback (e.g., restrict the bit-rates available, support multiple camera angles in a single stream, etc.)
Support for progressive download Ads/content
Almost all of the Silverlight Media Element APIs are available for Smooth Streaming w/ SSME

Resources

Download IIS Smooth Streaming Player Development Kit 1.0 – Beta 1
API documentation for Smooth Streaming Player SDK
More Information on Smooth Streaming
More Information on Live Smooth Streaming

Hope you have fun using this SDK, the same way we did developing it.

Happy Smooth Streaming.

Video: TechEd NA 2009 - Advanced Video Delivery with IIS

vsood — Sat, 16 May 2009 20:11:00 GMT

Earlier this week I gave a TechEd session on IIS Media Services - Smooth Streaming, Advanced Logging and the IIS Media Services Ecosystem overall. Thanks to everyone who made it to this talk. It was really nice to have you there and your interest in technology was immense.

Here is the recorded session delivered with Smooth Streaming in case you were not able to make it to the talk.

Advanced Logging – How does Real-time logging work?

vsood — Fri, 20 Mar 2009 17:41:00 GMT

We announced and release a Beta for a sparkling new Logging module for IIS at MIX 09. This is a super rich logging module with a lot of functionality that our team will continue to blog about. Today, I wanted to share more technical details on how my favorite feature, real-time logging work in Advanced Logging.

Before we go into details, you may want to take a short pause and read some overview material in my blog post, extension page for Advanced Logging or go over the custom logging walkthrough. Okay, I will now assume you are somewhat familiar with this module.

Next, let us take a scenario - You have a SL or any HTTP client that collects analytic information that you want to be able to send to IIS web server and get that captured in a log file. Let’s add a little twist, while you want this you also want to be able to write custom code that can consume this log information in real time and enable you to do some real time reporting. The reason you want to do that is just to provide a report on real-time interactions by clients or simply monitor your network in real-time.

Here is how IIS Advanced Logging helps

Let us go over this architecture, step-by-step:

The clients on the left hand side (could be Silverlight application, native Silverlight runtime, could be ASP.net or anything really), sends a HTTP POST message with the log in the body. It is a simple XML format and you can find details in the walkthrough Real-time Logging.
This message lands on an IIS server that has Advanced Logging (AL) installed. The client logging functionality in AL parses this message and raises an internal event.
The core server-side logging functionality gets this event and then looks up the log configuration to compose a log entry and writes it to the file. (Note: you would need to have relevant configuration so that AL knows what fields to expect. You can find an example in the Client logging walkthrough.
In addition, just before an entry is written to the log file, server-side logging raises another event using public APIs (IIS HTTP_TRACE_EVENT infrastructure) that can be consumed by a simple module written by YOU. Believe me, it is a simple module. You can find details and sample code in the walkthrough Real-time Logging.
Now, your module can take this information push it to a service in the cloud, a DB and produce reports in real-time.

Let me know if you need more details. The best to learn more is to try it out :).

IIS Advanced Logging Beta is now Live

vsood — Wed, 18 Mar 2009 19:29:00 GMT

We proudly announce the Beta of IIS Advanced Logging. With Advanced Logging you will be able to capture rich details in your logs and process them in real-time. These capabilities make this feature really compelling by helping you monetize your content with better analytics and improve service with rich QOS information.

IIS Advanced Logging includes the following features:

Client-side logging. Advanced Logging builds capabilities into IIS to accept client-side consumption metrics. This provides relevant and important user engagement metrics that your customers will love.
Centralized logging. Advanced Logging provides capabilities to set up a central log farm that collects and logs client-side metrics. This reduces the effort required to collect distributed logs, and consolidated log collection results in more efficient post-processing. I wanted to clarify that this is not for all logging. Note: This is for client-side logging.
Multiple Logs per request. Advanced Logging provides capabilities to filter information relevant to specific purposes by creating multiple logs per request, with each log containing data relevant to the log's purpose. For example, Quality of Service (QoS) data in one log and Analytics data in another. All the post-processing required to distill the information using today's solutions is no longer needed.
Real-time logging. Advanced Logging can extend the platform to support real-time analytics, helping you to provide real-time reports to customers or work with partners to do the same.
Rich/Flexible logging. Advanced Logging does not assume what is important to you. Instead, it provides enough control to specify what fields are important to you, add additional fields with ease, and provide policies around log rollover and request filtering. These capabilities do not exist today. Now you can log any of the HTTP request/response headers, IIS server variables, and client-side fields with simple configuration through the management console.
Application Logging. Making use of the IIS configuration system, Advanced Logging provides capabilities to generate separate logs for sites, applications and so on.
Module Specific Log fields. If you are developing modules for IIS, you can specify custom fields that can be collected in logs.

You can learn more about the feature by reading the walkthroughs:

Getting started with Advanced Logging
Real-Time Logging
Client Logging
Learn more about the feature on - http://www.iis.net/extensions/AdvancedLogging

We eagerly await your feedback and comments on the Advanced Logging Discussion Forum.

The world of Syndication: Atom 1.0 vs. RSS 2.0?

vsood — Mon, 06 Oct 2008 00:39:57 GMT

Syndication has become and inseparable part of the internet. There are two major syndication formats that exist today – RSS 2.0 (Really Simple Syndication) and Atom 1.0 (Atom Syndication Format). While they achieve the same end result, there are differences. This post attempts to enable you to decide which is more suited to your publishing.

RSS 2.0 is a frozen specification copyrighted by Harvard and Atom 1.0 is a specified in RFC4287. Atom came about as a result of pursuit to fix shortcoming of RSS since RSS was a frozen format. The table below lists the differences in the two specifications/standards:

	Atom 1.0	RSS 2.0	Who wins?
Content Model	Allows text, escaped HTML, well-formed XHTML, XML, base-64 encoded binary or pointer to web content outside the feed.	Text or Escaped HTML	This is a major advantage for Atom, writing escaped HTML affects the readability of RSS feeds
Partial Content	Has separate `<summary>` or `<content>` tags.	Has a `<description>` field. This could contain complete content or just synopsis but has no way of identifying what it contains.	This is another win for Atom, helps you have a synopsis and complete view inside a feed reader
Auto Discovery	Uses the MIME Type `application/atom+xml` which is registered with IANA. In addition the feed has a self link to enable auto subscription in readers	The MIME Type `application/rss+xml` is often used but not recognized by IANA	Having a registered MIME Type and auto subscription really helps discovery. Another Atom win.
Format Flexibility	Atom syndication format allows entries linking to the feed or standalone entries	RSS only recognizes a `<rss>` document.	This is also an Atom win, having standalone entries enables scenarios like linking to entries only.
Extensibility	Atom defines a well-defined structure to extend the default namespace and has specific guidelines on readers should interpret these.	RSS has to fixed namespace, however you could include external XML namespaces.	Atom has a slight advantage here as external namespaces extensions in RSS are not easily discoverable. In Atom’s case these extensions have a corresponding namespace tag
Languages	Atom uses xml:lang for language specificity	RSS has a separate `<language>` tag for language specificity	No one.
Encryption	Atom allows the option to encrypt entries using XML Encryption or XML Digital Signature. In addition the feed could be encrypted entire feed using standard web encryption techniques	RSS only allows encrypting using standard web encryption techniques.	Atom has extra level of encryption possible.
Adoption	Most sites that publish both RSS and Atom feeds.	Most sites that publish both RSS and Atom feeds.	RSS has an advantage of being the first mover, the term RSS has become synonymous with syndication.
Modularity	All elements part of Atom’s namespace can be used outside Atom’s context due to way it was designed	RSS elements cannot be used outside the context of RSS	This has proved to be the one of the major factors of Atom’s popularity and its used in data interactions like those enabled by Google GData

As you might have realized that Atom has considerable benefits over RSS. More and more services online are using Atom as more than just a feed format. Google’s GData and Microsoft’s Project Astoria are great examples and testimonies of Atom 1.0’s strengths as a format. They extend its namespace and harness the capabilities of Atom Publishing Protocol to pass data between their services.

While, I was writing, I realized that I was still publishing an RSS 2.0 feed for my blog (default supported by Drupal). I switched it to Atom 1.0. Have you? My recommendation to you would be switch to Atom as your base feed. Having said that, RSS is still very popular and consumed by many, it is good to retain your RSS feed too. Atom preserves most aspects of RSS so a simple transform (e,g, using XSLT) should be able to help you create and RSS feed from the Atom one.

If you know more examples that demonstrate Atom / RSS’s strength please post your comments below. I would love to hear from you.

Additional Reading:

While I was writing this post, I found RSS20AndAtom10Compared very useful
Atom on Wikipedia
RSS on Wikipedia
RFC 4287 – Atom Syndication Format
RFC 5023 – Atom Publishing

Web Playlists SMIL conversion tool

vsood — Fri, 12 Sep 2008 16:38:00 GMT

With the RC version of Web Playlists, we moved from a custom XML format to a SMIL-based format for storing playlists. As a result of this change the old isx format has been retired. However, Brian Blum (a dev) in our team crafted a tool to help convert the old files. The tool can be downloaded here. Thank you Brian!

As both old and the new SMIL-based playlist formats are XML by nature, this tool uses a XSL to transform the old isx to the new SMIL-based isx format. Another reason for doing this is Brian wanted you to be able to do any minor changes if you so desire without needing to look into the code.

The tool usage is simple and as follows:

isxTranslate.exe /? Coverts prerelease input files for IIS 7.0 Web Playlists to the release format.

Usage: isxTranslate /i PLAYLISTDIR /x XSLT

where PLAYLISTDIR is the path to your playlist files and

XSLT is the xslt to use to convert the playlists.

Example: isxtranslate /i c:\inetweb\wwwroot\playlists /x c:\tools\isx.xsl

Note: This tool is just to help migrate old files and is not released as a part of Web Playlists RC download. As a result this tool is not officially supported. We will be happy to answer any questions and would encourage you to use media forum for your questions.

DOWNLOAD THE TOOL HERE

Web Playlists Release Candidate (RC) Released

vsood — Fri, 12 Sep 2008 16:08:00 GMT

I am pleased to announce that the Web Playlists Release Candidate (RC) release is ready for you to download and deploy.

This release supports upgrade from the previous Go Live release. (Note: It is recommended that if you have a release earlier than Go Live, you should uninstall the old build and then use the downloads below to do a fresh installation.)

You can get the RC downloads here:

32 bit - Download
64 bit - Download
SDK - Download

Here is a list of walkthroughs published that will help you get going with this release:

Please refer to the online readme for more details.

For general information on how Web Playlists work, please see this post.

For us, this release was primarily about two things:

A step towards embracing open standards - The playlist format now is SMIL-based and additionally you can output the playlist in any XML/text format. The walkthrough talks more about this feature and illustrates and example where you can use ATOM as an output format.
Even more thorough testing - This is incremental release over our earlier Go Live release and our test team has tested it even more than previous release

The three key new features in Web Playlists RC release are:

Ability to customize output format - This release enables you to change the response to a Web Playlists request to a format understood by your app. This feature works by taking and XSL style-sheet from you and transforming the ASX response according to it. The walkthrough talks about this in more details.
Allow Client-side Caching - Earlier releases of Web Playlists disabled the client-side caching using http headers. We got customer requests suggesting that although this is a great security feature, they would like to control this so in this release we allow you just that. You can control, whether clients can cache content or not.
SMIL-based playlist format - Earlier releases used a custom XML. With this release, we are moving a step closer to open standards. We are now using a SMIL-based format. While, Web Playlists does not support the entire SMIL syntax, the sub-set supported is fully SMIL compliant. For those upgrading from previous builds, there is a tool available here to convert old isx files.

We would like to hear what you feel about this release and would love to hear how you are using it.

Got more questions or need support?: Please use media forum.

Web Playlists - using SMIL as input format

vsood — Thu, 07 Aug 2008 16:40:00 GMT

In our strive to make it utmost convenient for our customers to use Web Playlists, we are considering another feature. In my last post I discussed the option of being able to configure the output format for Web Playlists and use open standards like ATOM as possible output in addition to ASX today. We are actually thinking of allowing you to add a XSLT and then be able to configure the output format of your choice that way.

Continuing on the same lines I wanted to explore the option of a standard input format this time. Today we use POX. While this works, it has the problems of not being understood by other media servers and honestly you have to learn a new format. The idea we have now is to use SMIL as an input format. Windows Media Services already understands the SMIL input for Server-side Playlists and so do many other media server platforms. For this release, we are exploring supporting only a sub-set of SMIL modules- SMIL Structure, Media Object (audio,video and ref) and Metainformation modules.

Here is an example of the SMIL playlist would look like. We haven't closed on this yet and would love to hear any inputs you might have here (the example uses SMIL 2.1 but it would really work with SMIL 2.0 or SMIL 3.0 too)

<!DOCTYPE smil PUBLIC "-//W3C//DTD SMIL 2.1//EN"
                      "http://www.w3.org/2005/SMIL21/SMIL21.dtd">  
<smil xmlns="http://www.w3.org/2005/SMIL21/Language">
  <head>
    <meta name="title" content="Web Playlists Sample"/>    
    <meta name="author" content="IIS.net"/>    
    <meta name="copyright" content="(c)2008 Microsoft Corporation"/>
    <meta name="timeToLive" content="1440"/>    
    <meta name="inactivityTimeout" content="120"/>    
  </head>
  <body>
    <ref src="a.wmv" >
      <param name="canSkipForward" value="true" />
      <param name="canSkipBack" value="true" />
      <param name="canSeek" value="true" />
    </ref>
  </body>
</smil>

How do you feel about this change? We would love to hear from you.

Web Playlists output format

vsood — Sat, 26 Jul 2008 21:36:00 GMT

We recently release the Go Live of Web Playlists module and I am sure a lot of you are already beginning to realize the potential of this feature.

After the release our very smart set of engineers are figuring what can we do with this feature next? There is always a balance we need to draw in the features we can support and how soon can we get the product out, so that our customers (you) can benefit from it.

One thing we wanted to explore and hear your feedback on is the output format for the Web Playlists. While we allow you to change the input format, using custom providers, we do not have a way for you to change the output format. Currently, Web Playlists outputs ASX (client-side playlist) as the output. If you don' know much about ASX, it is basically a client-side playlist format (XML based) supported by Windows Media Player and Silverlight. You can also make it work with the Flash player and we have more details here. You can read more about the ASX format on MSDN here.

The question I have for all you is how much do you care about the output format? Would it be beneficial if we enabled you to output the client side playlist in format of your choice (other than ASX) too, or supported something like ATOM syndication format (RFC 4287)out of the box? In our team we deeply care about your feedback so any thoughts are really helpful.

If you have more questions, I will love to answer them.

Making Web Playlists URLs better with URL Rewrite module

vsood — Tue, 22 Jul 2008 03:21:09 GMT

I have been recently reading about the entire RESTful web services and constantly looking at how we can make our modules more REST friendly in terms of URL look-n-feel and also the output they return (if any). I blogged about RESTful web services in case anyone is interested in knowing more about REST.

At the same time, if you were following Bill's blog, IIS team released URL re-write module. IIS pipeline architecture is such that it almost always requires an extension, URL re-write module helps overcome this limitation. In this post I plan to cover how we can make Web Playlists URLs look prettier (and aligned to REST principles).

Today, Web Playlists URLs are look something like this http://www.example.com/a.isx. For someone looking at this URL and trying to understand, it does mean much. As you have been following my blog all this while ;), you know what isx is (Web Playlists file) but not everyone does. One of the principles of REST as I see applied is that URLs should tell you a lot about what to expect in the response. Let us see how we can live this principle for Web Playlists.

Consider the URLs below

These URLs clearly tell me what to expect as a response. It tells me that response will be a playlist of some kind.

Creating a Rule

Let us take the URL http://example.com/Playlist('a'). In this case the URL tells you that there is a playlist 'a' that this URL refers to. This syntax is very much similar to the Astoria syntax. "Astoria" is the code name for ADO.net Data Services. They are heavily investing in defining URL syntax. Let us see how we can get our existing URLs to look like more like Astoria URLs.

We need to first install URL re-writer module. This is an Out of Band module available for free download from http://www.iis.net site: 32-bit and 64-bit. Once you install you will see the Icon for URL re-writer appear in IIS Manager (highlighted below)

(click to see a larger image)

Double-click on the icon and then click "Add Rule...". Then add rule as per image below:

(click to see a larger image)

For the people familiar with IIS configuration files, this creates the following entry in the IIS config file

(click to see a larger image)

How does this rule work?

If we dissect this rule, "^(.*)/*Playlist$(.*)$$" pattern says that in URL match everything before "/Playlist" and then match everything in between (). As per the URL re-writer module semantics these will be stored in {R:1} and {R:2} variables which are then used while re-writing the rule. (E.g., in http://example.com/Playlist('a') {R:1} becomes blank and {R:2}becomes a. This is because only URL relative to site root are matched. Thus as per the rule the initial URL will be re-written as http://example.com/a.isx which is understood by the IIS7 pipeline.

Re-cap

In this post I ran through an example of how you could use URL-writer to create friendlier URLs for Web Playlists. I would really like to encourage you to play with URL re-write module to create the other URL form (http://example.com/Playlist/a) and share it as comments to this blog.

I would suggest starting with the walkthroughs here. Happy re-writing and looking forward to your comments.

Web Playlists Go Live release is now ready for downloads

vsood — Mon, 21 Jul 2008 21:33:00 GMT

I am really excited to announce that Web Playlists Go Live was just released to public. Here are the download links for the same:

Here is a list of walkthroughs published on the all new learn.iis.net:

Here is more about this release: http://www.iis.net/Downloads/files/playlist/WebPlaylists_Readme_GoLive.htm.

For general information on how Web Playlists work, please see this post.

Web Playlists Go Live release includes these key features:

Support for all digital media files types. Any digital media file type that can be downloaded from a Web server can be added to a Web playlist by using this feature.
Nested Web playlist media entries. Web playlist files (.isx) can be added as media entries to the Web playlists that you create, up to five levels deep. For more information about how nested playlists work in this feature, see Creating a Simple Playlist.
Remote HTTPd media entries. Content locations that begin with the httpd:// URL prefix can be added as media entries to the Web playlists that you create, allowing you to reference a remote Web server page that returns a custom URL or path for the media item to be played.
Session settings. Allows you to specify the maximum number of clients that can connect to the playlist and the amount of content that must be watched before skip functionality is enabled on the client.
Session provider settings. Allows you to add ASP.NET session persistence and provides an additional level of control for the content on a Web server by configuring multiple options that specify how long the content referenced by a playlist is available to users.
Impersonation settings. Allows for media items that are protected by user credentials to be added to playlists.
ASX import. Allows for quick conversion of client-side playlists (files with .asx file name extensions) for files stored on the Web server to Web playlists.
Custom providers. A COM interface is included that you can use to write native and .NET-based custom providers that extend the default behavior of Web Playlists. For more information, see the Extending Web Playlists through custom providers.

Got more questions or need support?: Please use media forum.

Web Playlists - How does that thing work?

vsood — Thu, 01 May 2008 04:31:00 GMT

Web Playlists! CTP2 been out there for a little more than a week now and some of you simply love it. Others, I am sure love it but I just don't know about that. Some others wonder how it works and the documentation available is a drop in the ocean. Firstly...(read more)

Short-cut to integrate Web Playlists with an existing web application

vsood — Tue, 29 Apr 2008 05:57:32 GMT

If you read my post / walkthroughs you probably know about the extensibility interface shipped with CTP2. You can use that to integrate into existing business logic applications or web applications. However, in this post I am going to talk about a shortcut...(read more)