The main goal of Smooth Streaming (SSF) is to provide a way to stream video and provide an automatic fallback mechanism when there is network congestion and avoid constant rebuffering. The client can communicate with the server and request low bandwidth video when the connection is slow and higher quality video when the connection recovers. This mechanism is automatically built-in to Silverlight players.
The content can be static (on-demand) or live (broadcast situations). Both of them are explained in the following material.
Sample HTML files that can be used to quickly add Smooth Streaming capabilities to your web server can be found in
Here are the instructions for quickly testing them in your web server. These instructions are for an IIS Server with Smooth Streaming capabilities. At the time this tutorial was written, the IIS Smooth Streaming capabilities were provided through IIS Media Services. More information can be found at https://www.iis.net/downloads/category/serve-media. If the link has moved, search for "IIS Smooth Streaming".
In general, the HTML pages with the player and the SSF content are stored on the web server and are accessed from client computers. For testing purposes, keep them on your development computer and access them through http://localhost before deploying to a real web server. It is best to start with a testing server that does not have too many security restrictions so you don't run into authentication and "access denied" errors until you become familiar with the process.
The following steps are for Windows Vista, but Windows XP, Windows 7, Windows 8/8.1, and Windows 10 all have similar steps:
Check whether IIS is working by going to http://localhost. If you see the IIS or your page, skip to step 4.
Enable IIS. In most operating systems, this can be done by going to "Control Panel"->"Programs and Features"->"Turn Windows Features On or Off" and selecting "Internet Information Services".
Make sure IIS is working by going to http://localhost. You should now see the standard IIS page or your default web server page. If you don't, go back to step 2 and install more options.
Install IIS Media Services Extension by going to https://azure.microsoft.com/en-us/products/media-services/ and clicking the "Install IIS Media Services" button. If you do not have the "Microsoft Web Platform Installer", you will have to install that first. Again, if the link does not work, search for "IIS Media Services" and install it from there.
Copy the contents of
C:\\inetpub\\wwwroot\\SSF . (Copy the entire directory).
Enable the Live Smooth Streaming by going to "Control Panel"->"Administrative tools"->"Internet Information Services (IIS) Manager". Click on Sites\Default Web Site\SSF, then click on the Live Smooth Streaming link. If you see a note on the right side saying "Application pool settings must be enabled to enable Live smooth streaming. Click here to update application pool settings", then click on it and click OK on the following message box.
You should now see a "Live.isml" in the Live smooth streaming publishing points. If you do not see this, then make sure you are in "Features view" and that you have selected SSF folder under the "Default Web Site" on the left side.
Test that it is all working by going to a client computer and playing the static HTML sample using the following url: http://<server-address>/SSF/Static.html.
This should start playing the video clip present in SSF\Static. Note that you need to have Silverlight installed on the client computer in order to see the video. If you don't have Silverlight installed, then install it and reload the page.
Test that live streaming is working. First you will need to start uploading the live content, after which you can start playing it. Note that this content will be cached on the server and you will only be able to upload the contents once. The second time you try to upload content to an existing IIS Smooth Streaming Publishing point you will get the Win32 error ERROR_INTERNET_CONNECTION_ABORTED (0x80072EFE).
To upload the content, run the ConvertSSF demo, select the source file and choose the following target filename:
Start the conversion and let it run. Note that you won't be able to stop and restart the conversion (you will get the 0x80072EFE error). If you want to replace the live stream, you will need to shut down the live publishing stream by going into the list of live publishing points, clicking on Live.isml and then clicking on Shut down publishing point. After that, you can run the conversion again.
It is best to choose a long file so you can also check out the seeking feature.
Play the live stream by opening the following URL on a client computer:
(Note that when you push video to the server, you push to a .ISML file; and when you play, you play the corresponding .HTML file.
Now that you have successfully played the same streams,create your own static or live streaming points.
For static streams:
For live streams:
Create a new live point (C:\inetpub\wwwroot\SSF\MyLive.isml). Copy Live.isml as MyLive.isml
Copy C:\inetpub\wwwroot\SSF\Live.html as C:\inetpub\wwwroot\SSF\MyLive.html
Change the following line from the end of MyLive.html:
<param name="InitParams" value="mediaurl=Live.isml/manifest" />
<param name="InitParams" value="mediaurl=MyLive.isml/manifest" />
Push live content using the ConvertSSF demo and setting the output file format to
Play the new html file: http://<server-address>/SSF/MyLive.html
Note that static streams are described in .ISM files, while the live points use a .ISML file.
Of course, you can create your own player page and you can pass the URL as a parameter so you don't have to create a new HTML file for each stream. How to do that is beyond the scope of this tutorial.
The SSF content is generated by the LEAD SSF Writer. See the Using the LEAD SSF Writer topic for more details on how to use this filter and about the compressions supported by the Smooth Streaming Format.
At the time of publishing, there is a known issue with Microsoft IIS Media Services Extensions failing to install on Windows 10. It displays an error indicating IIS Version 7.0 or greater is required to install IIS Media Services 4.1. A work-around modifying a registry key and installing an extension has been suggested in the IIS forums. This work-around has been verified to resolve the IIS Media Services Extension installation issue.