Trying it out:

Clone my fork of the vcpkg project (until the code gets upstream) git clone https://github.com/khouzam/vcpkg -b ffmpeg-openssl cd vcpkg bootstrap-vcpkg.bat (to build the VC package manager) vcpkg integrate install (from an admin command prompt to have Visual Studio integration). vcpkg install ffmpeg:x86-uwp ffmpeg:x64-uwp ffmpeg:arm-uwp ffmpeg:x86-windows ffmpeg:x64-windows (If you don't have CMake installed, you will be prompted to install it). You can select which flavors of builds you are looking for by choosing the different architecture or platform combination (uwp for store apps and windows for desktop apps). Notice how OpenSSL is automatically built and referenced when you build FFmpeg. Once completed you will get all the built binaries in your vcpkg\installed with the different architectures.

Prerequisites

• Windows 10 64-bit Insider Build 14971, or later (to ensure Bash/Windows interop is available)
• WSL & Developer Mode were enabled. You can follow these instructions.
• Visual Studio 2015 and the Windows 10 SDK. This is the toolchain that we’ll use to build FFmpeg.
• For now the Linux distribution needs to be 16.04 (needed for the new version of realpath). You can use do-release-upgrade on your own to update to 16.04 if you are still running 14.04

Build Steps

• Open a Bash console
• Navigate to the Windows filesystem, where you’ll clone the FFmpeg repo, for now its important to clone the repository using the linux version of git to get the unix line-endings properly set:

• Update the apt-get package index:

• Install the necessary dev tools in Bash using apt-get (C++ preprocessor, make, the yasm assembler and pkg-config)

• Download the gas-preprocessor for ARM and copy it to /usr/bin so that it is in your path:

• Clone the FFmpegInterop repo using the gillesk/wsl branch, including the FFmpeg submodule (this could be done on Windows or Linux side):

• Apply the FFmpeg patch (until we can try to push it upstream to FFmpeg)

• From a new Windows command prompt, navigate to the project folder and run the BuildFFmpeg.bat script, passing the WSL parameter

• You should now get a proper build in the FFmpeg/Output/… folder.

Things that had to change to make this possible

1. Changed the configure script for FFmpeg (and associated shell scripts) to call tools including their extensions (cl.exe instead of cl for example). This is necessary, because WSL can automatically launch Windows processes from the Linux side but only if the process is in the path and includes the full name. Linux doesn’t automatically append .exe and such to invoke a file.
2. Create a patch for FFmpeg and add it to the FFmpegInterop repo. (Until we can get them integrated in FFmpeg).
3. Changed the configure script to clean some \r that can get appended when running windows tools through the scripts.
4. Updated the FFmpegInterop repo to add a .gitattributes file, so that the FFmpegConfig.sh script using LF (not necessary if cloned or checked out through Linux).
5. Updated the FFmpegInterop build script to have a new WSL optional parameter that builds using WSL instead of MSYS2.
6. Removed the code to make a symbolic link to the FFmpeg sources and just access the sources through a relative path because at the moment symbolic links don’t cross the subsystem boundary.

Comparing both systems

Personally, I’m still very excited by the fact that Silverlight is open enough to enable people to extend our functionality in such a way.

If you’re interested the code will be available on https://projectstarlight.codeplex.com/

The easiest way to try out the code is to open a local wave file from your drive using the OpenFileDialog (C:\Windows\Media has a bunch of little sound bites).

private void Button_Click(object sender, RoutedEventArgs e) 
{
    OpenFileDialog ofd = new OpenFileDialog(); 

    if (ofd.ShowDialog().Value)
    {
        Stream s = ofd.File.OpenRead();
        WaveMediaStreamSource wavMss = new WaveMediaStreamSource(s);
        try
        {
            me.SetSource(wavMss);
        }
        catch (InvalidOperationException)
        {
            // This file is not valid
        }
    }
} 

This snippet will play the wave file right away. Remember that to get the FileOpenDialog, you need to hook the handler to a user initiated action. An easy way for this, is to put a MediaElement and a button on a page.

<UserControl x:Class="SampleWave.MainPage"
    xmlns="https://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="https://schemas.microsoft.com/winfx/2006/xaml"
    Width="400" Height="300">
    <Grid x:Name="LayoutRoot" Background="White">
        <MediaElement Name="me"/>
        <Button Name="b" Width="200" Height="20" Content="Open" Click="Button_Click"/>
    </Grid>
</UserControl>

That’s it, you can now play wave files.