Changes

Jump to navigation Jump to search
1,175 bytes added ,  02:01, 5 January 2016
no edit summary
Line 17: Line 17:  
== On Windows ==
 
== On Windows ==
   −
You can use mxe-octave to include ffmpeg, there is already a target for it.
+
=== using official mxe-build and ffmpeg binaries ===
 +
 
 +
This is at the moment the preferred way for windows users and assumes that you've installed Octave from the official MXE build from https://ftp.gnu.org/gnu/octave/windows/ to the default path.
 +
 
 +
Download the ffmpeg binaries for windows from ffmpeg.zeranoe.com/builds/. You need the "32-bit Dev" and "32-bit Shared" archive. These instructions were tested with
 +
 
 +
* ffmpeg-20160105-git-68eb208-win32-shared.7z
 +
* ffmpeg-20160105-git-68eb208-win32-dev.7z
 +
 
 +
Now
 +
 
 +
* Extract the bin/*.dll from ffmpeg-20160105-git-68eb208-win32-shared.7z to C:\Octave\Octave-4.0.0\bin
 +
* Extract include/* from ffmpeg-20160105-git-68eb208-win32-dev.7z to C:\Octave\Octave-4.0.0\include
 +
  (You should now, for example, see C:\Octave\Octave-4.0.0\include\libavutil\version.h)
 +
* Extract lib/* from ffmpeg-20160105-git-68eb208-win32-dev.7z to C:\Octave\Octave-4.0.0\lib
 +
 
 +
Download a patched version (no pkg_config check for ffmpeg and PixelFormat -> AVPixelFormat) from [[Media:video-1.2.1_win_ffmpeg.tar.gz]]
 +
 
 +
Compile and install from Octave with
 +
<code>
 +
pkg -verbose install video-1.2.1_win_ffmpeg.tar.gz
 +
</code>
 +
 
 +
=== mxe-octave ===
 +
You can also use mxe-octave to include ffmpeg, there is already a target for it.
    
= Known bugs =
 
= Known bugs =
* On MXE-Octave with ffmpeg "clear all" after using "addframe" causes a segmentation fault
+
* On MXE-Octave with ffmpeg crosscompiled "clear all" after using "addframe" causes a segmentation fault
    
<code>
 
<code>
219

edits

Navigation menu