FFME.Windows
7.0.361-beta.1
dotnet add package FFME.Windows --version 7.0.361-beta.1
NuGet\Install-Package FFME.Windows -Version 7.0.361-beta.1
<PackageReference Include="FFME.Windows" Version="7.0.361-beta.1" />
paket add FFME.Windows --version 7.0.361-beta.1
#r "nuget: FFME.Windows, 7.0.361-beta.1"
// Install FFME.Windows as a Cake Addin #addin nuget:?package=FFME.Windows&version=7.0.361-beta.1&prerelease // Install FFME.Windows as a Cake Tool #tool nuget:?package=FFME.Windows&version=7.0.361-beta.1&prerelease
FFME: The Advanced WPF MediaElement Alternative
⭐ Please star this project if you like it and show your appreciation via PayPal.Me
Status Updates
- If you would like to support this project, you can show your appreciation via PayPal.Me
- Current Status: (2024-06-26) - BETA 1 Release 7.0.361.1 is now available, (see the <a href="https://github.com/unosquare/ffmediaelement/releases">Releases</a>)
- NuGet Package available here: https://www.nuget.org/packages/FFME.Windows/
- FFmpeg Version: <a href="https://ffmpeg.org/download.html">7.0</a> -- Make sure you download one built as a SHARED library and for your right architecture (typically x64)
- BREAKING CHANGE: Starting realease 4.1.320 the
Source
dependency property has been downgraded to a notification property. Please use the asynchronousOpen
andClose
methods instead. - I have been learning a ton while writing this project. You can find my latest video and rendering experiments <a href="https://github.com/mariodivece/ffplaysharp">here (if you are curious)</a>
Please note the current NuGet realease might require a different version of the FFmpeg binaries than the ones of the current state of the source code.
Quick Usage Guide for WPF Apps
Get Started
Open Visual Studio and create a new WPF Application.
Target Framework must be set to .net 5.0 or above
Install the NuGet Package from your Package Manager Console:
PM> Install-Package FFME.Windows
Acquire the FFmpeg shared binaries (either 64 or 32 bit, depending on your app's target architecture)
by either
Building your own
I recommend the Media Autobuild Suite please don't ask for help on it here.
or
Downloading a compatible build
For a x64 build
- the dlls are located here, 7.0 x64,
combine the contents of the
bin
folder of both downloaded folders into a separate folder e.gc:\ffmpeg\x64
.
The resulting contents of the folder e.g
c:\ffmpeg\x64
should be so- avcodec-59.dll
- avdevice-59.dll
- avfilter-8.dll
- avformat-59.dll
- avutil-58.dll
- ffmpeg.exe
- ffplay.exe
- ffprobe.exe
- swresample-4.dll
- swscale-6.dll
- the dlls are located here, 7.0 x64,
combine the contents of the
Within your application's startup code (Main method)
set the Unosquare.FFME.Library.FFmpegDirectory variable to the path of the folder where the DLLs and EXEs are located, e.g.
Unosquare.FFME.Library.FFmpegDirectory = @"c:\ffmpeg";
And use the FFME MediaElement control as you would any other WPF control.
Example
in your main window (e.g MainWindow.xaml)
Add the namespace:
xmlns:ffme="clr-namespace:Unosquare.FFME;assembly=ffme.win"
Add the FFME control:
<ffme:MediaElement x:Name="Media" Background="Gray" LoadedBehavior="Play" UnloadedBehavior="Manual" />
Play files or streams, by calling the asynchronous method, Open:
await Media.Open(new Uri(@"c:\your-file-here"));
Close the media, by calling:
await Media.Close();
Additional Usage Notes
- Remember: The
Unosquare.FFME.Windows.Sample
provides usage examples for plenty of features. Use it as your main reference. - The generated API documentation is available here
Features Overview
FFME is an advanced and close drop-in replacement for <a href="https://msdn.microsoft.com/en-us/library/system.windows.controls.mediaelement(v=vs.110).aspx">Microsoft's WPF MediaElement Control</a>. While the standard MediaElement uses DirectX (DirectShow) for media playback, FFME uses <a href="http://ffmpeg.org/">FFmpeg</a> 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.
FFME provides multiple improvements over the standard MediaElement such as:
- Fast media seeking and frame-by-frame seeking.
- Properties such as Position, Balance, SpeedRatio, IsMuted, and Volume are all Dependency Properties.
- Additional and extended media events. Extracting (and modifying) video, audio and subtitle frames is very easy.
- Easily apply FFmpeg video and audio filtergraphs.
- Extract media metadata and specs of a media stream (title, album, bit rate, codecs, FPS, etc).
- Apply volume, balance and speed ratio to media playback.
- MediaState actually works on this control. The standard WPF MediaElement is severely lacking in this area.
- Ability to pick media streams contained in a file or a URL.
- Specify input and codec parameters.
- Opt-in hardware decoding acceleration via devices or via codecs.
- Capture stream packets, audio, video and subtitle frames.
- Change raw video, audio and subtitle data upon rendering.
- Perform custom stream reading and stream recording.
... all in a single MediaElement control
FFME also supports opening capture devices. See example URLs below and issue #48
device://dshow/?audio=Microphone (Vengeance 2100):video=MS Webcam 4000
device://gdigrab?title=Command Prompt
device://gdigrab?desktop
If you'd like audio to not change pitch while changing the SpeedRatio property, you'll need the SoundTouch.dll
library v2.1.1 available on the same directory as the FFmpeg binaries. You can get the SoundTouch library here.
About how it works
First off, let's review a few concepts. A packet
is a group of bytes read from the input. All packets
are of a specific MediaType
(Audio, Video, Subtitle, Data), and contain some timing information and most importantly compressed data. Packets are sent to a Codec
and in turn, the codec produces Frames
. Please note that producing 1 frame
does not always take exactly 1 packet
. A packet
may contain many frames
but also a frame
may require several packets
for the decoder to build it. Frames
will contain timing informattion and the raw, uncompressed data. Now, you may think you can use frames
and show pixels on the screen or send samples to the sound card. We are close, but we still need to do some additional processing. Turns out different Codecs
will produce different uncompressed data formats. For example, some video codecs will output pixel data in ARGB, some others in RGB, and some other in YUV420. Therefore, we will need to Convert
these frames
into something all hardware can use natively. I call these converted frames, MediaBlocks
. These MediaBlocks
will contain uncompressed data in standard Audio and Video formats that all hardware is able to receive.
The process described above is implemented in 3 different layers:
- The
MediaContainer
wraps an input stream. This layer keeps track of aMediaComponentSet
which is nothing more than a collecttion ofMediaComponent
objects. EachMediaComponent
holdspacket
caching,frame
decoding, andblock
conversion logic. It provides the following important functionality:- We call
Open
to open the input stream and detect the different stream components. This also determines the codecs to use. - We call
Read
to read the next available packet and store it in its corresponding component (audio, video, subtitle, data, etc) - We call
Decode
to read the following packet from the queue that each of the components hold, and return a set of frames. - Finally, we call
Convert
to turn a givenframe
into aMediaBlock
.
- We call
- The
MediaEngine
wraps aMediaContainer
and it is responsible for executing commands to control the input stream (Play, Pause, Stop, Seek, etc.) while keeping keeping 3 background workers.- The
PacketReadingWroker
is designed to continuously read packets from theMediaContainer
. It will read packets when it needs them and it will pause if it does not need them. This is determined by how much data is in the cache. It will try to keep approximately 1 second of media packets at all times. - The
FrameDecodingWroker
gets the packets that thePacketReadingWorker
writes and decodes them into frames. It then converts those frames intoblocks
and writes them to aMediaBlockBuffer
. This block buffer can then be read by something else (the following worker described here) so its contents can be rendered. - Finally, the
BlockRenderingWorker
reads blocks form theMediaBlockBuffer
s and sends those blocks to a plat-from specificIMediaRenderer
.
- The
- At the highest level, we have a
MediaElement
. It wraps aMediaEngine
and it contains platform-specific implementation of methods to perform stuff like audio rendering, video rendering, subtitle rendering, and property synchronization between theMediaEngine
and itself.
A high-level diagram is provided as additional reference below.
Some Work In Progress
Your help is welcome!
- I am planning the next version of this control,
Floyd
. See the Issues section.
Windows: Compiling, Running and Testing
Please note that I am unable to distribute FFmpeg's binaries because I don't know if I am allowed to do so. Follow the instructions below to compile, run and test FFME.
- Clone this repository and make sure you have <a href="https://dotnet.microsoft.com/download/dotnet-core/3.1">.Net Core 3.1 or above</a> installed.
- Download the FFmpeg shared binaries for your target architecture: <a href="https://ffmpeg.org/download.html">FFmpeg Windows Downloads</a>.
- Extract the contents of the <code>zip</code> file you just downloaded and go to the <code>bin</code> folder that got extracted. You should see 3 <code>exe</code> files and multiple <code>dll</code> files. Select and copy all of them.
- Now paste all files from the prior step onto a well-known folder. Take note of the full path. (I used
c:\ffmpeg\
) - Open the solution and set the <code>Unosquare.FFME.Windows.Sample</code> project as the startup project. You can do this by right clicking on the project and selecting <code>Set as startup project</code>. Please note that you will need Visual Studio 2019 with dotnet 5.0 SDK for your target architecture installed.
- Under the <code>Unosquare.FFME.Windows.Sample</code> project, find the file
App.xaml.cs
and under the constructor, locate the line <code>Library.FFmpegDirectory = @"c:\ffmpeg";</code> and replace the path so that it points to the folder where you extracted your FFmpeg binaries (dll files). - Click on <code>Start</code> to run the project.
- You should see a sample media player. Click on the <code>Open</code> icon located at the bottom right and enter a URL or path to a media file.
- The file or URL should play immediately, and all the properties should display to the right of the media display by clicking on the <code>Info</code> icon.
- You can use the resulting compiled assemblies in your project without further dependencies. Look for
ffme.win.dll
.
ffmeplay.exe Sample Application
The source code for this project contains a very capable media player (FFME.Windows.Sample
) covering most of the use cases for the FFME
control. If you are just checking things out, here is a quick set of shortcut keys that ffmeplay
accepts.
Shortcut Key | Function Description |
---|---|
G | Example of toggling subtitle color |
Left | Seek 1 frame to the left |
Right | Seek 1 frame to the right |
+ / Volume Up | Increase Audio Volume |
- / Volume Down | Decrease Audio Volume |
M / Volume Mute | Mute Audio |
Up | Increase playback Speed |
Down | Decrease playback speed |
A | Cycle Through Audio Streams |
S | Cycle Through Subtitle Streams |
Q | Cycle Through Video Streams |
C | Cycle Through Closed Caption Channels |
R | Reset Changes |
Y / H | Contrast: Increase / Decrease |
U / J | Brightness: Increase / Decrease |
I / K | Saturation: Increase / Decrease |
E | Example of cycling through audio filters |
T | Capture Screenshot to desktop/ffplay folder |
W | Start/Stop recording packets (no transcoding) into a transport stream to desktop/ffplay folder. |
Double-click | Enter fullscreen |
Escape | Exit fullscreen |
Mouse Wheel Up / Down | Zoom: In / Out |
Thanks
In no particular order
- To the <a href="http://ffmpeg.org/">FFmpeg team</a> for making the Swiss Army Knife of media. I encourage you to donate to them.
- To the <a href="https://github.com/naudio/NAudio">NAudio</a> team for making the best audio library out there for .NET -- one day I will contribute some improvements I have noticed they need.
- To Ruslan Balanukhin for his FFmpeg interop bindings generator tool: <a href="https://github.com/Ruslan-B/FFmpeg.AutoGen">FFmpeg.AutoGen</a>.
- To Martin Bohme for his <a href="http://dranger.com/ffmpeg/">tutorial</a> on creating a video player with FFmpeg.
- To Barry Mieny for his beautiful <a href="http://barrymieny.deviantart.com/art/isabi4-for-Windows-105473723">FFmpeg logo</a>
Similar Projects
- <a href="https://github.com/higankanshi/Meta.Vlc">Meta Vlc</a>
- <a href="https://github.com/Microsoft/FFmpegInterop">Microsoft FFmpeg Interop</a>
- <a href="https://github.com/Sascha-L/WPF-MediaKit">WPF-MediaKit</a>
- <a href="https://libvlcnet.codeplex.com/">LibVLC.NET</a>
- <a href="http://playerframework.codeplex.com/">Microsoft Player Framework</a>
License
- Please refer to the <a href="https://github.com/unosquare/ffmediaelement/blob/master/LICENSE">LICENSE</a> file for more information.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0-windows7.0 is compatible. |
.NET Framework | net48 is compatible. net481 was computed. |
-
.NETFramework 4.8
- FFmpeg.AutoGen (>= 7.0.0)
-
net8.0-windows7.0
- FFmpeg.AutoGen (>= 7.0.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on FFME.Windows:
Package | Downloads |
---|---|
ScreensPro.Controls
This package contains controls and converters for layouts to be consumed ScreensPro. |
GitHub repositories (2)
Showing the top 2 popular GitHub repositories that depend on FFME.Windows:
Repository | Stars |
---|---|
Milkitic/Osu-Player
A multifunctional media player for osu and osuer. Modern interface with WPF.
|
|
AntonyCorbett/OnlyM
Simple Media Player (audio, video and images) for use in meetings.
|
Version | Downloads | Last updated |
---|---|---|
7.0.361-beta.1 | 417 | 6/26/2024 |
7.0.360-beta.1 | 137 | 5/22/2024 |
4.4.350 | 30,085 | 6/5/2021 |
4.3.340 | 3,172 | 11/28/2020 |
4.2.330 | 13,192 | 12/28/2019 |
4.2.320 | 1,953 | 11/16/2019 |
4.1.310 | 7,610 | 7/1/2019 |
4.1.300 | 2,795 | 4/19/2019 |
4.1.290 | 954 | 3/31/2019 |
4.1.280 | 5,882 | 3/17/2019 |
4.0.270 | 8,125 | 9/24/2018 |
4.0.260 | 2,074 | 6/3/2018 |
4.0.250 | 1,698 | 5/20/2018 |
3.4.240 | 1,726 | 4/25/2018 |
3.4.230 | 2,313 | 3/29/2018 |
3.4.220 | 1,238 | 3/7/2018 |
3.4.210 | 1,166 | 2/19/2018 |
3.4.200 | 1,364 | 2/3/2018 |
3.4.0.2-rc1 | 871 | 2/1/2018 |
3.4.0.2-b9 | 886 | 1/18/2018 |
3.4.0.2-b7 | 992 | 1/8/2018 |
3.4.0.2-b6 | 1,148 | 12/14/2017 |
3.4.0.2-b5 | 882 | 12/12/2017 |
3.4.0.2-b4 | 881 | 12/12/2017 |
3.4.0.2-b3 | 912 | 12/11/2017 |
3.4.0.2-b2 | 806 | 12/11/2017 |
This is a release package of the Floyd Engine build referencing bindings to FFmpeg version 4.4
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/16?closed=1