FFME.Windows 4.1.280

FFME: WPF MediaElement Control Alternative

FFME is an advanced media control and a close drop-in replacement for Microsoft's WPF MediaElement Control. While the standard MediaElement uses DirectX (DirectShow) for media playback, FFME uses FFmpeg to read and decode audio and video. This means that for those of you who want to support stuff like HLS playback, or just don't want to go through the hassle of installing codecs on client machines, using FFME might just be the answer.

There is a newer version of this package available.
See the version list below for details.
Install-Package FFME.Windows -Version 4.1.280
dotnet add package FFME.Windows --version 4.1.280
paket add FFME.Windows --version 4.1.280
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

How to use FFME

In order to use the FFME MediaElement control, you will need to setup a folder with FFmpeg binaries and point to it from your application code.
Here are the steps:

  1. You can build your own FFmpeg shared binaries or download a compatible build from the wonderful Zeranoe FFmpeg Builds site: (https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.1-win32-shared.zip).
  2. Your FFmpeg build (see the bin folder) should have 3 exe files and a number of dll files and must match your app's architecture (32-bit or 64-bit). Copy all of them to a folder such as (c:\ffmpeg)
  3. Within you application's startup code (Main method), set Unosquare.FFME.MediaElement.FFmpegDirectory = @"path to ffmpeg binaries from the previous step";.
  4. Use the FFME MediaElement control as any other WPF control!
    For example: In your MainForm.xaml, add the namespace: xmlns:ffme="clr-namespace:Unosquare.FFME;assembly=ffme.win"
    And then add the FFME control your window: <ffme:MediaElement x:Name="Media" Background="Gray" LoadedBehavior="Play" UnloadedBehavior="Manual" />
    To play files or streams, set the Source property: Media.Source = new Uri(@"c:\your-file-here");

Happy coding!
Mario, Unosquare and the FFME contributors.

How to use FFME

In order to use the FFME MediaElement control, you will need to setup a folder with FFmpeg binaries and point to it from your application code.
Here are the steps:

  1. You can build your own FFmpeg shared binaries or download a compatible build from the wonderful Zeranoe FFmpeg Builds site: (https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.1-win32-shared.zip).
  2. Your FFmpeg build (see the bin folder) should have 3 exe files and a number of dll files and must match your app's architecture (32-bit or 64-bit). Copy all of them to a folder such as (c:\ffmpeg)
  3. Within you application's startup code (Main method), set Unosquare.FFME.MediaElement.FFmpegDirectory = @"path to ffmpeg binaries from the previous step";.
  4. Use the FFME MediaElement control as any other WPF control!
    For example: In your MainForm.xaml, add the namespace: xmlns:ffme="clr-namespace:Unosquare.FFME;assembly=ffme.win"
    And then add the FFME control your window: <ffme:MediaElement x:Name="Media" Background="Gray" LoadedBehavior="Play" UnloadedBehavior="Manual" />
    To play files or streams, set the Source property: Media.Source = new Uri(@"c:\your-file-here");

Happy coding!
Mario, Unosquare and the FFME contributors.

Release Notes

This is a release package of the Michelob build referencing bindings to FFmpeg version 4.1
     This package does not contain the required FFmpeg binaries. Please refer to the following URL for instructions on how to obtain the binaries: https://github.com/unosquare/ffmediaelement
     Release details: https://github.com/unosquare/ffmediaelement/milestone/10?closed=1

Version History

Version Downloads Last updated
4.1.290 189 3/31/2019
4.1.280 603 3/17/2019
4.0.270 3,940 9/24/2018
4.0.260 961 6/3/2018
4.0.250 625 5/20/2018
3.4.240 545 4/25/2018
3.4.230 761 3/29/2018
3.4.220 363 3/7/2018
3.4.210 305 2/19/2018
3.4.200 353 2/3/2018
3.4.0.2-rc1 192 2/1/2018
3.4.0.2-b9 228 1/18/2018
3.4.0.2-b7 286 1/8/2018
3.4.0.2-b6 366 12/14/2017
3.4.0.2-b5 202 12/12/2017
3.4.0.2-b4 192 12/12/2017
3.4.0.2-b3 204 12/11/2017
3.4.0.2-b2 176 12/11/2017