FFME.Windows 4.2.330

FFME is an advanced WPF MediaElement alternative. While the standard MediaElement uses DirectX (DirectShow) for media playback, FFME uses FFmpeg to read and decode audio and video.

Install-Package FFME.Windows -Version 4.2.330
dotnet add package FFME.Windows --version 4.2.330
<PackageReference Include="FFME.Windows" Version="4.2.330" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add FFME.Windows --version 4.2.330
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/).
  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.Library.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, call the asyncrhonous Open method: await Media.Open(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/).
  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.Library.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, call the asyncrhonous Open method: await Media.Open(new Uri(@"c:\your-file-here"));

Happy coding!
Mario, Unosquare and the FFME contributors.

Release Notes

This is a release package of the Floyd Engine build referencing bindings to FFmpeg version 4.2.0
     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/14?closed=1

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on FFME.Windows:

Repository Stars
AntonyCorbett/OnlyM
Simple Media Player (audio, video and images) for use in meetings.

Version History

Version Downloads Last updated
4.2.330 4,279 12/28/2019
4.2.320 1,076 11/16/2019
4.1.310 5,974 7/1/2019
4.1.300 1,587 4/19/2019
4.1.290 408 3/31/2019
4.1.280 2,805 3/17/2019
4.0.270 6,877 9/24/2018
4.0.260 1,271 6/3/2018
4.0.250 912 5/20/2018
3.4.240 801 4/25/2018
3.4.230 1,273 3/29/2018
3.4.220 573 3/7/2018
3.4.210 523 2/19/2018
3.4.200 621 2/3/2018
3.4.0.2-rc1 387 2/1/2018
3.4.0.2-b9 411 1/18/2018
3.4.0.2-b7 513 1/8/2018
3.4.0.2-b6 608 12/14/2017
3.4.0.2-b5 400 12/12/2017
3.4.0.2-b4 393 12/12/2017
3.4.0.2-b3 414 12/11/2017
3.4.0.2-b2 348 12/11/2017