FFME.Windows 4.1.300

FFME: The Adavanced WPF MediaElement Alternative

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.1.300
dotnet add package FFME.Windows --version 4.1.300
<PackageReference Include="FFME.Windows" Version="4.1.300" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add FFME.Windows --version 4.1.300
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Here is a quick guide on how to get started.

  1. Open Visual Studio (v2019 recommended), and create a new WPF Application. Target Framework must be 4.6.1 or above.
  2. Install the NuGet Package from your Package Manager Console: PM&gt; Install-Package FFME.Windows
  3. You need FFmpeg shared binaries (64 or 32 bit, depending on your app's target architecture). Build your own or download a compatible build from Zeranoe FFmpeg Builds site.
  4. Your FFmpeg build should have a bin folder with 3 exe files and some dll files. Copy all those files to a folder such as c:\ffmpeg
  5. Within you application's startup code (Main method), set Unosquare.FFME.Library.FFmpegDirectory = @&quot;c:\ffmpeg&quot;;.
  6. Use the FFME MediaElement control as any other WPF control.
    For example: In your MainForm.xaml, add the namespace: xmlns:ffme=&quot;clr-namespace:Unosquare.FFME;assembly=ffme.win&quot; and then add the FFME control your window's XAML: &lt;ffme:MediaElement x:Name=&quot;Media&quot; Background=&quot;Gray&quot; LoadedBehavior=&quot;Play&quot; UnloadedBehavior=&quot;Manual&quot; /&gt;
  7. To play files or streams, simply set the Source property: Media.Source = new Uri(@&quot;c:\your-file-here&quot;);. Since Source is a dependency property, it needs to be set from the GUI thread.

Here is a quick guide on how to get started.

  1. Open Visual Studio (v2019 recommended), and create a new WPF Application. Target Framework must be 4.6.1 or above.
  2. Install the NuGet Package from your Package Manager Console: PM&gt; Install-Package FFME.Windows
  3. You need FFmpeg shared binaries (64 or 32 bit, depending on your app's target architecture). Build your own or download a compatible build from Zeranoe FFmpeg Builds site.
  4. Your FFmpeg build should have a bin folder with 3 exe files and some dll files. Copy all those files to a folder such as c:\ffmpeg
  5. Within you application's startup code (Main method), set Unosquare.FFME.Library.FFmpegDirectory = @&quot;c:\ffmpeg&quot;;.
  6. Use the FFME MediaElement control as any other WPF control.
    For example: In your MainForm.xaml, add the namespace: xmlns:ffme=&quot;clr-namespace:Unosquare.FFME;assembly=ffme.win&quot; and then add the FFME control your window's XAML: &lt;ffme:MediaElement x:Name=&quot;Media&quot; Background=&quot;Gray&quot; LoadedBehavior=&quot;Play&quot; UnloadedBehavior=&quot;Manual&quot; /&gt;
  7. To play files or streams, simply set the Source property: Media.Source = new Uri(@&quot;c:\your-file-here&quot;);. Since Source is a dependency property, it needs to be set from the GUI thread.

Release Notes

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

Version History

Version Downloads Last updated
4.1.300 90 4/19/2019
4.1.290 206 3/31/2019
4.1.280 648 3/17/2019
4.0.270 4,013 9/24/2018
4.0.260 963 6/3/2018
4.0.250 627 5/20/2018
3.4.240 548 4/25/2018
3.4.230 763 3/29/2018
3.4.220 365 3/7/2018
3.4.210 308 2/19/2018
3.4.200 355 2/3/2018
3.4.0.2-rc1 194 2/1/2018
3.4.0.2-b9 230 1/18/2018
3.4.0.2-b7 288 1/8/2018
3.4.0.2-b6 368 12/14/2017
3.4.0.2-b5 205 12/12/2017
3.4.0.2-b4 195 12/12/2017
3.4.0.2-b3 207 12/11/2017
3.4.0.2-b2 179 12/11/2017