“Not yet”, he said. Thus I decided to start authoring one given two main motivations:

• To learn more about scriptcs.
• My past experiences in high profile events

There isn’t much to say regarding the first bullet (learning new stuff is part of my DNA); however I will expand on the second one.

During the last few years I have had the opportunity to be part of the streaming operations war room in high profile events (such as the London 2012 Olympics) where things happen really fast and troubleshooting can be stressful. Sometimes you need to quickly check the state of an asset or a job status and there is certainly no time to launch Visual Studio, start building a console application, etc. to look over everything.

At that time, we had a lot of tooling helping on a daily basis and a few handy tools to check things over. However…wouldn’t it have been great if you could have just started your console and started coding away to interact with Windows Azure Media Services?

Now it’s possible

Go ahead and take a look at the docs of this script pack to get started. I would like to thanks Damian Schenkelman for his contributions to the script pack

If you want to learn more about scriptcs, be sure to check out the project wiki and read the blog posts created by the community.

Happy scripting.

Ez.

This new release includes new functionality and some breaking changes that you should be aware in order to recompile you app against this new SDK. The Media Services Documentation on MSDN will be fully updated by 11/27, but you don’t have to wait until then to migrate your app.

Nick Drouin published some code snippets here, which will help you get started with the new SDK. (BTW, I strongly recommend reading Nick’s blog for getting sample code and how-to articles around using various features of Media Services)

Windows Media Services SDK 2.0 Release Notes

Media Services General Issues

Media Services SDK for .NET Issues

Changes since June 2012 release

SDK Changes

The following changes require any code written against the June 2012 Preview release to be modified:

Assets

IAsset.Create(assetName) is the ONLY asset creation function.  IAsset.Create no longer uploads files as part of the method call.

The IAsset.Publish method and the AssetState.Publish enumeration value have been removed from the Services SDK.  Any code that relies on this value must be re-written.

FileInfo

This class has been removed and replaced by IAssetFile.  See below.

IAssetFiles

Replaces FileInfo and has a different behavior. To use it, instantiate the IAssetFiles object, followed by a file upload either using the Media Services SDK or the Windows Azure Storage SDK. The following IAssetFile.Upload overloads can be used:

• IAssetFile.Upload(filePath).  Synchronous method.  Blocks the thread and is recommended only when uploading a single file.
•  IAssetFile.UploadAsync(filePath, blobTransferClient, locator, cancellationToken).  Asynchronous method.  This is the preferred upload mechanism. Known bug: using the cancellationToken will indeed cancel the upload; however, the cancellation state of the tasks can be any of a number of states. You must properly catch and handle exceptions. 

Locators

The Origin-specific and Windows Azure CDN-specific versions have been removed. The SAS-specific context.Locators.CreateSasLocator(asset, accessPolicy) will be marked deprecated, or removed by GA. See the Locators section under New Functionality for updated behavior.

New Functionality

The following functionality is new in the November 2012 release.

Deleting entities

IAsset, IAssetFile, ILocator, IAccessPolicy, IContentKey objects are now deleted at the object level, i.e. IObject.Delete(), instead of requiring a delete in the Collection, that is cloudMediaContext.ObjCollection.Delete(objInstance).

Locators

Locators must now be created using the CreateLocator method and use the LocatorType.SAS or LocatorType.OnDemandOrigin enum values as an argument for the specific type of locator you want to create.  

New properties were added to Locators to make it easier to obtain usable URIs for your content. This redesign of Locators was meant to provide more flexibility for future third-party extensibility and increase ease-of-use for media client applications.

Asynchronous Method Support

Asynchronous support has been added to all methods. 

Enjoy the new SDK!

We had the opportunity to try the bits as part of the TAP program and I can tell you that this is worth trying. The usage of the SDK API is really friendly and with the getting started and how to documents (see below) you will be able to get started in a heartbeat.

Supported Features

This preview release supports:

Encoding

• Use the Windows Azure Media Encoder and work with a range of standard codecs and formats, including industry-leading IIS Smooth Streaming, MP4, and conversion to Apple HTTP Live Streaming.
• Convert entire libraries or individual files with total control over input and output.
• Supported video and audio codecs:
  • H.264 High, Main and Baseline Profiles
  • AAC-LC
  • HE-AAC
  • VC-1 (Windows Media Video 9) Simple, Main and Advanced Profiles
  • Windows Media Audio Standard
  • Windows Media Audio Professional
• Supported format conversions:
  • ISO MP4 (.mp4) to Smooth Streaming File Format (PIFF 1.3) (.ismv; .isma)
  • Smooth Streaming File Format (PIFF) to Apple HTTP Live Streaming (.msu8, .ts)

Content Protection

• Encrypt live or on-demand video and audio with standard MPEG Common Encryption or Microsoft PlayReady, the industry’s most accepted DRM for premium content.

On-Demand Streaming

• Streaming Origin support for Smooth Streaming and Apple HTTP Live Streaming
• Seamlessly deliver content via Windows Azure CDN or a third-party CDN.
  • Add a scalable origin server with or without a CDN.
  • Scale to millions of users by adding a Windows Azure CDN or a third-party CDN.

Here is a list of resources that will help you get started with Windows Azure Media Services:

• Preview Account Setup: http://social.msdn.microsoft.com/Forums/en-US/MediaServices/thread/a9d3d1b4-09eb-4a28-ad1d-a1f4cf3123cb
• Release notes and known issues of the June 2012 preview: http://social.msdn.microsoft.com/Forums/en-US/MediaServices/thread/acbeb3a0-6ba9-44c7-9486-a74d24439745
• Windows Azure Media Services Documentation: http://msdn.microsoft.com/en-us/library/hh973629
  • Getting Started with the Media Services SDK for .NET: http://msdn.microsoft.com/en-us/library/hh973620
  • Building Applications with the Media Services SDK for .NET: http://msdn.microsoft.com/en-us/library/hh973613
  • Building Applications with the Windows Azure Media Services REST API: http://msdn.microsoft.com/en-us/library/hh973618
• How to use Media Services: http://www.windowsazure.com/en-us/develop/net/how-to-guides/media-services/
• Windows Azure Media Services Forum: http://social.msdn.microsoft.com/Forums/en-US/MediaServices
• Media Services Status on Twitter: https://twitter.com/#!/WAMSStatus

Stay tuned! Many exciting features are planned for future releases.

Ez.

The 2.0 release was built using the Silverlight 5 Beta bits, which already expired so some users were getting the message “This application was created for an expired beta release of Silverlight. Please contract the owner of this application and have them upgrade their application using an official release of Silverlight” when trying to use the application.

Happy editing,

Ez.

My first try to fix this was, obviously, reinstalling the IIS Media Services package. Sadly, that didn’t help.

After that, I started to think that the problem could be in the handler mapping, so I took a look at them in IIS and I found that the SmoothHandler in the Default Web Site has an Unspecified path type instead of the usual File path type.

Changing the path type back to File, solved the issue.

Alternatively, if you don’t have local configurations, you can revert the Handler Mappings to its parent.

Hope this helps,

Ez.

A few months ago, Microsoft published the Beta version of the IIS Transform Manager. This new release contains an incredible set of new features, explained here by Chris Knowlton.

Back in the Alpha days, I wrote an IIS Transform Manager Task that takes an Microsoft Media Platform Video Editor (formerly Rough Cut Editor) Project XML file (which includes the EDL) as input, and outputs a new encoded video that represents the MMP Video Editor edits.

The Beta version introduced a few breaking changes (mainly due to interfaces renaming) so I decided to publish an updated version of the task, so you can use it without having to perform the changes.

The updated task can be downloaded from here.

Happy Transforming!

Microsoft just released the SP1 version of the Silverlight Rough Cut Editor.

This service pack addresses some of the most requested requirements by the community.

In this post you will find detailed information about what this release contains.

Service Pack Content

In this service pack you will find:

• The RCE migrated to Visual Studio 2010, Silverlight 4 and IIS Smooth Streaming Client 1.5.
• Issues fixed that improve CPU performance.
• Bug fixing.
• An enhanced setup experience with automation scripts for Windows 7, Windows 2008 and Windows 2008 R2.
• Composite Stream Manifest generation integrated with the RCE.
• An updated version of the Composite Stream Manifest generator that supports  manifest compression and the new IIS Media Services 4.0 manifest format (duration based).
• A new Assets Data Provider that retrieves the assets from a plain XML.
• A source code refactoring that takes advantage of the Smooth Streaming Plugin provided by the Silverlight Media Framework.

New Setup Experience

Two packages were released as part of the SP1. One contains the source code and the other one contains the binaries ready to be hosted.

In both packages you will find a start here document that will help you to install the Rough Cut Editor. They also contain a new set of scripts to automate the deployment in 3 platforms: Windows 7, Windows 2008 and Windows 2008 R2.

The scripts will first detect if the pre-requisites required to run the the RCE are installed and then, will perform all the operations required to leave the RCE up and running in your environment.

After installing the package, you will find a shortcut in the desktop to run the solution.

Composite Stream Manifest Generator Additions

The IIS Media Services 4.0 has a new manifest format (duration based instead of time based) and also adds support for a new repeat tag “r” to obtain more compression in the manifest.

The new format is compatible with the previous version of the Smooth Streaming Media Element (SSME) , but the manifest compression feature it is only compatible with SSME >= v1.5.

For more information about these changes, please read this blog post from Giuseppe Guerrasio.

The Composite Stream Manifest generator now outputs CSMs following the new proposed format and also has the ability to compress the output manifest.

In the Test Page of the CSM generator, you will find a new checkbox that will allow you to test the manifest compression.

You can read more about the CSM generator in this blog post.

Composite Manifest Generation integrated with the RCE.

How many times you were using the RCE and wanted to quickly generate a CSM to check how your edits look like? Before SP1, you were required to export the RCE project, copy its content and paste it on the generator test page, generate the manifest, copy the generation output and host the CSM. Looong process. You can imagine how quickly that turns into a repetitive task.

The RCE SP1 has the CSM generator integrated as part of the Output module. Now you select a CSM output, click Export and the CMS will be generated and hosted for you. The generated CSM ends up in the RCE.Web/encode/CSM directory.

I hope you find this new release useful. If you have comments, questions, suggestions or any issue, please visit the Rough Cut Editor community site.

Happy editing!

�

My friend John Deutscher is leading these efforts. John has a lot of experience with media management software and a passion to make developers lives’ easier. He was also one of the masterminds behind the Rough Cut Editor (RCE), a lightweight, Web-based Silverlight video editing tool. As a client tool, it submits edit decision lists, but does not include the logic for transcoding. But it’s highly extensible, and from time-to-time, we’ve been asked about extending the tool to add an encoding workflow process.

�

The real question here is whether the RCE should take care of that. Instead, Why not take advantage of the tools available out there and use them to manage the complexity of the encoding process?

�

This post is result of exploring the feasibility of using the IIS Transform Manager to take an RCE Project XML file (which includes the EDL) as input, and creating the necessary task to output a new encoded video that represents the RCE edits?

So with that goal in mind, I started to build a proof of concept of the scenario, depicted in the following diagram:

PoC Diagram – (icons from picol.org)

The Ingredients

• Internet Information Services (IIS) 7 or higher
• Microsoft .NET Framework 3.5 Service Pack 1
• Microsoft .NET Framework 4 (required for use with Expression Encoder 4.0)
• Silverlight Runtime
• IIS Transform Manager 1.0 (Alpha)
• Microsoft Silverlight Rough Cut Editor configured to use the File System Data Provider (check the related topic on the RCE documentation)
• Microsoft Expression Encoder 4 Trial or Pro
• Sample videos (required for use with the RCE and the File System Data Provider)

The Recipe

OK. Let’s assume we have all the ingredients in place and that we are ready to start.

The first thing to do is to create the Transform Manager Task. This task will parse the RCE Project XML, extract the edits metadata and use that information with the Expression Encoder 4 API to perform the encoding.

I will not copy all the code for the Task in the post (you can download that from here. Make sure to include into the libs folder the EE4 and IIS Transform Manager assemblies in order to build the project), but instead let me highlight a few things:

1. To create a custom Task for the IIS Transform Manager you must implement the ITransformTask interface (Microsoft.Web.Media.TransformManager.Sdk.dll)
2. Once you have created the task, you must create a task definition xml file (the task definition schema can be found here).
   The following is the Task Definition for the RCE Project task:

   <taskDefinition xmlns=“http://schemas.microsoft.com/iis/media/v4/TM/TaskDefinition#“> <name>RCE Project Task</name> <id>7F8A89DA-1DF9-409A-9869-A5CDCA017998</id> <properties namespace=“http://schemas.microsoft.com/RCE/V1#” prefix=“rce“> <property name=“preset” value=“” /> </properties> <description xml:lang=“en“>Invokes Expression Encoder 4 to produce a video based on the edits metadata defined on an RCE Project File</description> <inputDirectory></inputDirectory> <outputDirectory>RCEProjectTaskOutput</outputDirectory> <taskCode> <type architecture=“x86” >RCE.TransformManager.Tasks.RCEProjectTask, RCE.TransformManager.Tasks, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null</type> </taskCode> </taskDefinition> �

   As you can see, it defines a property called preset, which is intended to be used to provide the Expression Encoder 4 preset.

   – The input directory points to the directory where the source videos are located (which is the same directory used on the RCE File System Data Provider configuration)

   – The output directory will be later used by an XCopy task defined on the Job Template that will copy the resulting files back to the source videos directory (making the resulting video available to the RCE)

3. Register the task with the IIS Transform Manager. A great tutorial on how to do custom task registration can be found here, but it basically involves two steps:- Copy the custom task assembly to C:Program FilesIISTransform Manager (on a x86 computer) or to to C:Program Files (x86)IISTransform Manager (on a x64 computer)

   – Copy the custom task definition XML file to the %ProgramData%MicrosoftIISTransform ManagerConfigurationTask Definitions directory

�

Once you have your Transform Manager task ready and configured, launch the Internet Information Services and configure the IIS Transform Manager.

First, stop and start the IIS Transform Manager service so it can detect the new task, then follow these steps to create a job template.

1. Create a New Job Template (Transform Manager > Job Templates > New) and fill the Name field.
2. Click Add to launch the Add Task dialog.
3. Select the RCE Project Task and the XCopy Task and click OK.
4. Make sure that the task definitions list shows the RCE Project task on top of the XCopy task (use the Move Up / Move Down buttons to adjust it)
5. Select the RCE Project Task and click Edit.
6. Fill the input directory field and the preset property. Click OK to save.Note: I’m using one of the predefined presets of EE4 (VC1-ScreenEncoding VBR for Silverlight), but you can use any you prefer.
7. Select the XCopy task and click Edit.
8. Fill the fields as described below. Click OK to save.
   • Input Directory: RCEProjectTaskOutput
   • Arguments: RCEProjectTaskOutput* “d:mediademovideos” /E /Y /INote: (replace d:mediademovideos with the input directory you defined on the RCE Project Task)�
9. Click OK to save the job template.

�

Now it is time to add the Watch Folder. For the sake of simplicity, in the PoC, I will use the folder where the RCE exports the project output. This folder is located at

RCE.WebencodeQueue.

1. Create a new watch folder (Transform Manager > Watch Folders > New)
2. Fill the watch folder settings:
   • Name. The name of the folder
   • Physical Path. The watch folder path (%RCEDirectory%/RCE.WebencodeQueue)
   • File Filter. Use *.jobreq here, which is the extension the RCE Export operation output.
   • Job Template. Select the RCE Job Template
3. Click OK to save the watch folder.
4. Finally, select the watch folder and click Enable and then click Start. This will leave the watch folder ready to use.

�

Great!. Everything is cooked. Let’s see how it tastes.

1. Launch the RCE and perform a couple of edits. I’ve four videos on my library and I created an edit of around 1 minutes and 56 seconds using two of those videos.
2. Select the Output Tab, and click Export to export the RCE project.
3. Open the IIS and go to the Job Monitor option of the IIS Transform Manager. You will see that your job is running!!
4. Once the encoding is completed, the second task of the job is going to be executed, copying the new file on the folder you configured.
5. Refresh the RCE (press F5), and you’ll see a new video on the library, with the exact same duration of the edit you created.

�

The End

We just proved that the RCE and the IIS Transform Manager can easily work together. The IIS Transform Manager’s extensibility allowed us to create a simple task to integrate the RCE export process with it and to output a new encoded video that represents the RCE edits. And this is just the beginning…

�

Hope this helps,

Happy Transforming!

�

THE CODE AND THIS POSTING IS PROVIDED “AS IS” WITH NO WARRANTIES, AND CONFERS NO RIGHTS.

• When I set the position on the Smooth Streaming Media Element, the displayed frame is not updated.
• I can only get the frame displayed to update when playback is resumed.

The default behavior of the SSME doesn’t allow to seek inside fragment (chunks) boundaries, so if you seek to any position in within the same 2-seconds chunk of video, you always get the same frame displayed. The change to enable this is really simple, but is one of those hidden gems of the SSME.

The Smooth Streaming Media Element can be configured using an XML file in which you can set a wide range of settings. One of these settings is actually the one to enable accurate seeks on the SSME.

4 Steps to success

1. In your Silverlight project, add an Xml file and named it config.xml. You add the file to the Silverlight project, because it needs to be part of the XAP package.
2. Copy the following content into the file:
   

   <?xml version=”1.0″ encoding=”utf-8″ ?> <LiveSmoothStreamingSettings> � <BufferingEngineSettings ForceAccurateSeeks=”true”/> </LiveSmoothStreamingSettings>

3. Save the file.
4. Add the following attribute in XAML for the SSME.
   

   e.g., <XYZ:SmoohtStreamingMediaElement ConfigPath=”config.xml”>

   Alternatively, you can set this programatically:

   this.ConfigPath = “Config.xml”;

Hope this helps.

Enjoy!

One of the main features used during the Olympics was the ability to generate Composite Stream Manifests (CSM) based on projects the editors created using the Rough Cut Editor.

Today, we are happy to announce that the Composite Stream Manifest generator code was just published on the RCE site on Code Gallery: http://code.msdn.microsoft.com/RCE.

Once you download the source code package, you will find the following folder structure:

The ManifestGenerator folder contains the source code for the CSM generator and a WCF service ready to consume which converts your RCE projects into Composite Stream Manifests.

The WCF service contains two operations:

[ServiceContract]
public interface IManifestGeneratorService
{
    [OperationContract]
    string GetSubClipManifest(Uri manifestUri, double markIn, double markOut);

    [OperationContract]
    string GetManifest(string projectXml, string pbpDataStreamName, string adsDataStreamName);
}

• The GetSubClipManifest operation will generate a CSM of one clip. This operation is useful when you want to quickly generate a CSM based on a Mark In and Mark Out you set to a clip. The parameters expected are the clip manifest Uri and the mark in and mark out values (in ticks).
• The GetManifest operation will generate a CSM based on an RCE project. This operation will allow you to convert all the cuts you made on the RCE into a manifest that can be played by the Smooth Streaming Media Element. The parameters expected are the RCE project xml and the desired names for the ads and markers text streams.

The package also contains a test page that will allow you to test the service without having to deal with the WCF service. Thanks to JPG for the UI.

�

I hope this helps you to generate Composite Stream manifests. If you have questions, suggestions or comments, please visit us on the RCE forums.

�

Happy editing!.

Ez.