You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@
15
15
- If you would like to support this project, you can show your appreciation via [PayPal.Me](https://www.paypal.me/mariodivece/50usd)
16
16
- Current Status: (2019-12-28) - Release 4.2.330 is now available, (see the <ahref="https://github.com/unosquare/ffmediaelement/releases">Releases</a>)
17
17
- NuGet Package available here: https://www.nuget.org/packages/FFME.Windows/
18
-
- FFmpeg Version: 4.2.1 <ahref="https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.2.1-win32-shared.zip">32-bit</a> or <ahref="https://ffmpeg.zeranoe.com/builds/win64/shared/ffmpeg-4.2.1-win64-shared.zip">64-bit</a>
18
+
- FFmpeg Version: <ahref="https://ffmpeg.org/download.html">4.3.1</a> -- Make sure you download one built as a SHARED library and for your right architecture (typically x64)
19
19
- BREAKING CHANGE: Starting realease 4.1.320 the `Source` dependency property has been downgraded to a notification property. Please use the asynchronous `Open` and `Close` methods instead.
20
20
21
21
*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.*
@@ -25,7 +25,7 @@
25
25
Here is a quick guide on how to get started.
26
26
1. Open Visual Studio (v2019 preview recommended), and create a new WPF Application. Target Framework must be 4.6.1 or above, or .Net Core 3.0 or above.
27
27
2. Install the NuGet Package from your Package Manager Console: `PM> Install-Package FFME.Windows`
28
-
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](https://ffmpeg.zeranoe.com/builds/).
28
+
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 [FFmpeg Windows Downloads](https://ffmpeg.org/download.html).
29
29
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`
30
30
5. Within you application's startup code (`Main` method), set `Unosquare.FFME.Library.FFmpegDirectory = @"c:\ffmpeg";`.
31
31
6. Use the FFME `MediaElement` control as any other WPF control.
@@ -96,7 +96,7 @@ A high-level diagram is provided as additional reference below.
96
96
*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.*
97
97
98
98
1. Clone this repository and make sure you have <ahref="https://dotnet.microsoft.com/download/dotnet-core/3.1">.Net Core 3.1 or above</a> installed.
99
-
2. Download the FFmpeg **shared** binaries for your target architecture: <ahref="https://ffmpeg.zeranoe.com/builds/win32/shared/ffmpeg-4.2.1-win32-shared.zip">32-bit</a> or <ahref="https://ffmpeg.zeranoe.com/builds/win64/shared/ffmpeg-4.2.1-win64-shared.zip">64-bit</a>.
99
+
2. Download the FFmpeg **shared** binaries for your target architecture: <ahref="https://ffmpeg.org/download.html">FFmpeg Windows Downloads</a>.
100
100
3. 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.
101
101
4. Now paste all files from the prior step onto a well-known folder. Take note of the full path. (I used `c:\ffmpeg\`)
102
102
5. 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 Core 3.0 SDK for your target architecture installed.
@@ -139,7 +139,6 @@ The source code for this project contains a very capable media player (`FFME.Win
139
139
*In no particular order*
140
140
141
141
- To the <ahref="http://ffmpeg.org/">FFmpeg team</a> for making the Swiss Army Knife of media. I encourage you to donate to them.
142
-
- To Kyle Schwarz for creating and making <ahref="http://ffmpeg.zeranoe.com/builds/">Zeranoe FFmpeg builds available to everyone</a>.
143
142
- To the <ahref="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.
144
143
- To Ruslan Balanukhin for his FFmpeg interop bindings generator tool: <ahref="https://github.com/Ruslan-B/FFmpeg.AutoGen">FFmpeg.AutoGen</a>.
145
144
- To Martin Bohme for his <ahref="http://dranger.com/ffmpeg/">tutorial</a> on creating a video player with FFmpeg.
Copy file name to clipboardExpand all lines: Support/nugetdoc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
Here is a quick guide on how to get started.
2
2
1. Open Visual Studio (v2019 recommended), and create a new WPF Application. Target Framework must be .Net Core 3+ or .Net Framework 4.6.1+.
3
3
2. Install the NuGet Package from your Package Manager Console: `PM> Install-Package FFME.Windows`
4
-
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](https://ffmpeg.zeranoe.com/builds/).
4
+
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 [FFmpeg Windows Downloads](https://ffmpeg.org/download.html).
5
5
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`
6
6
5. Within you application's startup code (`Main` method), set `Unosquare.FFME.Library.FFmpegDirectory = @"c:\ffmpeg";`.
7
7
6. Use the FFME `MediaElement` control as any other WPF control.
Copy file name to clipboardExpand all lines: Support/readme.txt
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ How to use FFME
3
3
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.
4
4
Here are the steps:
5
5
6
-
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/).
6
+
1. You can build your own FFmpeg **shared** binaries or download a compatible build from the FFmpeg Windows Downloads page: (https://ffmpeg.org/download.html).
7
7
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)
8
8
3. Within you application's startup code (Main method), set Unosquare.FFME.Library.FFmpegDirectory = @"path to ffmpeg binaries from the previous step";.
9
9
4. Use the FFME MediaElement control as any other WPF control!
0 commit comments