The default SMF media player with Big Buck Bunny, an IIS Smooth Streaming video, loaded in Visual Basic .NET

Printer QR-Code in Visual Basic .NET The default SMF media player with Big Buck Bunny, an IIS Smooth Streaming video, loaded

Microsoft.SilverlightMediaFramework namespace, there are the .Core, .Plugins, and .Utilities namespaces and their associated assemblies. Be sure to refer-

Microsoft.Web.Media.SmoothStreaming.dll assembly. For progressive download projects, use the Micosoft.SilverlightMediaFramework.Plugins.Progressive. dll assembly instead.

<UserControl x:Class="SilverlightApplication57.MainPage" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:Core="clr-namespace:Microsoft.SilverlightMediaFramework.Core; assembly=Microsoft.SilverlightMediaFramework.Core" xmlns:Media="clr-namespace: Microsoft.SilverlightMediaFramework.Core.Media; assembly=Microsoft.SilverlightMediaFramework.Core">

<Grid x:Name="LayoutRoot" Background="White" Margin="15"> <Core:SMFPlayer> SMF player <Core:SMFPlayer.Playlist> <Media:PlaylistItem DeliveryMethod="AdaptiveStreaming" MediaSource= "http://video3.smoothhd.com.edgesuite.net/ondemand/ Big%20Buck%20Bunny%20Adaptive.ism/Manifest" /> </Core:SMFPlayer.Playlist> </Core:SMFPlayer> </Grid> </UserControl>

The Silverlight Media Framework player requires two namespaces to be included. The first B, Core, is for the player itself. The second C, Media, is for the playlists and features related to the media supported in the player. Due to the flexibility of the player, loading media takes a few more lines than the usual MediaElement. In particular, the player supports a playlist D with one or more playlist items queued in it. Each playlist item includes a single piece of media with a specified delivery method E. The valid values for DeliveryMethod are shown in table 20.9.

Table 20.9 Possible values for DeliveryMethod for the SMF player Value Description The default value. This will attempt to use the first media plug-in loaded. As this can be unreliable in players that support more than one type of media delivery method, always specify one of the following below. The player will use IIS Smooth Streaming. The player will use a progressive download approach for playing the media. This approach requires no server-side support. The player will use Windows Media Streaming to play the media.

It s important to realize that the delivery methods supported are entirely controlled by what plug-ins you package with your Silverlight application. If you leave out the Progressive Download plug-in, for example, your player won t support that delivery method. The Silverlight Media Framework is an excellent way to get a fully functional and feature-rich player up and running in a minimum amount of time. It s perfect for traditional video and audio. But what about media that ventures further into the nontraditional How about managed codecs or real-time-generated media For those, collectively called raw media, we have the Media Stream Source API.

Silverlight has a strong but finite set of codecs it natively supports for audio and video playback. If you want to use a format not natively supported, such as the WAV audio file format or the AVI video format, that wasn t an option until the Media Stream Source (MSS) API was added. The MSS API was included in Silverlight 2, but that version required you to transcode into one of the WMV/WMA/MP3 formats natively supported by Silverlight. In Silverlight 3, the MSS API was augmented to support raw media formats where you send the raw pixels or audio samples directly through the rest of the pipeline. This made its use much easier, as it required knowledge only of the format you want to decode. For the same reason, it runs faster, as an extra potentially CPU-intensive encoding step is avoided. The MediaStreamSource API supports simultaneous video and audio streams. In this section, we ll look at creating raw video as well as raw audio. In both cases, we ll use algorithmically derived data to drive the raw media pipeline.

To implement your own custom stream source, derive a class from MediaStreamSource. As the name suggests, this class will be used as the source for a MediaElement on the page. Table 20.10 shows that MediaStreamSource has several methods that you must override in your implementation.

Method Description Sets the next position to be used in GetSampleAsync. Call ReportSeekCompleted when done. Used to return diagnostic information. This method can be a no-op as it s not critical. If used, call ReportGetDiagnosticCompleted when done. Used to change between configured media streams. This method can be a no-op as it s not critical. If used, call ReportSwitchMediaStreamCompleted when done.