Windows XP compatible non-SSE2 FFmpeg builds

Announcements made by users.
Post Reply
Reino
Posts: 77
Joined: Thu Aug 22, 2013 5:14 pm
Contact:

Windows XP compatible non-SSE2 FFmpeg builds

Post by Reino » Sat Apr 27, 2019 12:17 pm

(Kyle ("Zeranoe") accidentally removed the "Making Zeranoe builds work under XP & XP builds by rogerdpack"-topic, so I've created a new one.)

I still own an AMD Athlon XP 3200+ (no SSE2) pc running a highly tweaked Windows XP Pro SP3 install, which I'm still quite font of.
An increasing amount of software doesn't work on WinXP and/or my old cpu anymore. FFmpeg however isn't one of them.

Some time ago I've made an extraction-script for a handful of Dutch video-on-demand websites. It's sort of like a lite version of Youtube-dl.
FFmpeg has officially dropped support for Windows XP. Zeranoe's FFmpeg builds don't work on my pc anymore either. So about 2 years ago I decided to try building my own FFmpeg binaries by forking Roger Pack's ffmpeg-windows-build-helpers script.
With a legacy hardware/software compatible FFmpeg build I could yet again open/download video-urls (extracted by my "BashGemist" script) on my old pc. And of course I've decided to share it with the rest of the world.

Build configuration:

Code: Select all

configuration:
  --arch=x86
  --target-os=mingw32
  --cross-prefix=/cygdrive/m/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/bin/i686-w64-mingw32-
  --pkg-config=pkg-config --pkg-config-flags=--static
  --extra-version=Reino
  --enable-gray
  --enable-version3
  --disable-debug
  --disable-doc
  --disable-htmlpages
  --disable-manpages
  --disable-podpages
  --disable-txtpages
  --disable-w32threads
  --enable-avisynth
  --enable-frei0r
  --enable-filter=frei0r
  --enable-gmp
  --enable-gpl
  --enable-libaom
  --enable-libass
  --enable-libbluray
  --enable-libbs2b
  --enable-libcaca
  --extra-cflags=-DCACA_STATIC
  --enable-libfdk-aac
  --enable-libflite
  --enable-libfontconfig
  --enable-libfreetype
  --enable-libfribidi
  --enable-libgme
  --enable-libgsm
  --enable-libilbc
  --enable-libmp3lame
  --enable-libmysofa
  --enable-libopencore-amrnb
  --enable-libopencore-amrwb
  --enable-libopenh264
  --enable-libopenmpt
  --enable-libopus
  --enable-librubberband
  --enable-libsnappy
  --enable-libsoxr
  --enable-libspeex
  --enable-libtheora
  --enable-libtwolame
  --extra-cflags=-DLIBTWOLAME_STATIC
  --enable-libvidstab
  --enable-libvmaf
  --enable-libvo-amrwbenc
  --enable-libvorbis
  --enable-libvpx
  --enable-libwebp
  --enable-libx264
  --enable-libx265
  --enable-libxavs
  --enable-libxml2
  --enable-libxvid
  --enable-libzimg
  --enable-libzvbi
  --enable-mbedtls
  --extra-cflags='-march=pentium3'
  --extra-cflags='-mtune=athlon-xp'
  --extra-cflags=-O2
  --extra-cflags='-mfpmath=sse'
  --extra-cflags=-msse
  --enable-static
  --disable-shared
  --prefix=/cygdrive/m/ffmpeg-windows-build-helpers-master/ffmpeg_local_builds/sandbox/cross_compilers/mingw-w64-i686/i686-w64-mingw32
Changelog (30-08-2019):

Code: Select all

MinGW-w64 buildscript:
  gcc 8.3.0          --> gcc 9.2.0

FFmpeg buildscript:
  cmake 3.14.5       --> cmake 3.15.2
  bzip2 1.0.6        --> bzip2 1.0.8
  SDL2 2.0.9         --> SDL2 2.0.10
  freetype 2.10.0    --> freetype 2.10.1
  fontconfig 2.13.91 --> fontconfig 2.13.92
  lame_git           --> lame_svn
  mpg123-1.25.10     --> mpg123-1.25.12
  libopenmpt 0.4.5   --> libopenmpt 0.4.6
  *_git              --> latest commit

  ffmpeg 4.2-1811-g89b9690 (N-94137) --> ffmpeg 4.3-327-g83e0b71 (N-94698)

Other:
  libfdk-aac 2.0.0-183-g4edc5c4    --> libfdk-aac 2.0.0-185-gcc5c85d
  frei0r-plugins 1.6.1-94-gf1b1074 --> frei0r-plugins 1.6.1-97-gb965471
  curl 7.65.1_mbedtls_zlib         --> curl-7.65.3_mbedtls_zlib
FFmpeg downloads
Other downloads
Github repository
Last edited by Reino on Fri Aug 30, 2019 9:48 pm, edited 3 times in total.

anuswara
Posts: 18
Joined: Thu Aug 11, 2011 5:16 pm

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by anuswara » Sat Apr 27, 2019 9:13 pm

Hi,

thanks. Sorry if I dont understand the code of the name: does ffmpeg-N-93674-g1e01f66 means that it is the 4.1.3 al-Khwarizmi?
thanks.

(PS: I warmly hope that this will be and remain the stable topic for this matter).

Reino
Posts: 77
Joined: Thu Aug 22, 2013 5:14 pm
Contact:

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by Reino » Sun Apr 28, 2019 8:44 am

Unless specified otherwise, I'm always using the latest git version.
And you can easily find out for yourself. With the SHA-1 commit hash, ffmpeg-N-93674-g1e01f66, visit https://github.com/FFmpeg/FFmpeg/commit/1e01f66 and you'll see that this commit was made on April 22 (but pushed on April 26).
So yes, it's newer than FFmpeg 4.1.3 "al-Khwarizmi".

manolito
Posts: 13
Joined: Wed Apr 20, 2016 4:02 pm

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by manolito » Sun Apr 28, 2019 1:10 pm

Thanks very much to CoRoNe for keeping up providung us XP users with current FFmpeg builds... :D

Both the static and the shared builds passed all my tests without any hiccups.

Thanks again
manolito

anuswara
Posts: 18
Joined: Thu Aug 11, 2011 5:16 pm

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by anuswara » Sun Apr 28, 2019 2:22 pm

Thanks again to Corone from me too (Vista32 SP2 user).

See you on friday 30th august :)

Reino
Posts: 77
Joined: Thu Aug 22, 2013 5:14 pm
Contact:

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by Reino » Sun Jun 30, 2019 2:58 pm

An interim update with most notably:
- Added libvmaf filter (Netflix's VMAF).
- Renamed all new releases in a more recognizable way, including a version and build string for FFmpeg.

Please visit the following urls on how to use libvmaf:
https://ffmpeg.org/ffmpeg-filters.html#libvmaf
https://github.com/Netflix/vmaf/blob/ma ... ith-ffmpeg

https://ffmpeg.org/ffmpeg-filters.html#libvmaf:
If no model path is specified it uses the default model: vmaf_v0.6.1.pkl.
You need to download 'vmaf_v0.6.1.pkl' and 'vmaf_v0.6.1.pkl.model', or this filter won't work.
By default FFmpeg is looking in '/usr/local/share/model/' for this file, so you always need to specify the path.
If you downloaded both files in the same map as 'ffmpeg.exe':

Code: Select all

ffmpeg.exe -i main -i ref -lavfi "libvmaf=model_path=vmaf_v0.6.1.pkl" -f null -
If you downloaded both files in another map:

Code: Select all

ffmpeg.exe -i main -i ref -lavfi "libvmaf=model_path='D\:/other_map/vmaf_v0.6.1.pkl'" -f null -
See post #1 for more info.

Reino
Posts: 77
Joined: Thu Aug 22, 2013 5:14 pm
Contact:

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by Reino » Fri Aug 30, 2019 9:45 pm

Fresh builds. See post #1.

With every new build FFmpeg is getting bigger and bigger. Gradually, but still.
That's why I'd like to ask you all as user; do you / we really need all these external libraries?
I personally never use libbs2b, libcaca, libopencore-amrwb, libxavs, or libzvbi to name just a few.
It would be pointless to include some exotic library if no one will ever use it after all.

manolito
Posts: 13
Joined: Wed Apr 20, 2016 4:02 pm

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by manolito » Sat Aug 31, 2019 5:56 pm

I totally agree with you. For most of the libraries you mention I have no idea what they are for. So I am all for some kind of cleanup effort.

Thanks again for still taking care of us retro WinXP users...

Cheers
manolito


//EDIT//
Took the new builds to my test bench. Both the static and the shared builds passed all my tests with flying colors, no problems whatsoever... :mrgreen:

Reino
Posts: 77
Joined: Thu Aug 22, 2013 5:14 pm
Contact:

Re: Windows XP compatible non-SSE2 FFmpeg builds

Post by Reino » Sun Sep 01, 2019 8:40 am

manolito wrote:
Sat Aug 31, 2019 5:56 pm
I totally agree with you. For most of the libraries you mention I have no idea what they are for. So I am all for some kind of cleanup effort.
I'll see to it next time.
manolito wrote:
Sat Aug 31, 2019 5:56 pm
Thanks again for still taking care of us retro WinXP users...
It's in my own interest too, because I'm also still one of them. ;) But you're welcome of course.
manolito wrote:
Sat Aug 31, 2019 5:56 pm
Took the new builds to my test bench. Both the static and the shared builds passed all my tests with flying colors, no problems whatsoever... :mrgreen:
That's good to hear. Thanks for letting me know.

Post Reply
'