FFMpeg Windows XP Updated Builds by CoRoNe

[FranceBB]

Old deprecated build by @VistaLover: http://lists.infradead.org/pipermail/get_iplayer/2017-May/010711.html

New Build (by @CoRoNe @Reino): https://rwijnsma.home.xs4all.nl/files/ffmpeg/?C=M;O=D

Please use the build made by @CoRoNe / @Reino which are updated.

Official Doom9 (international Encoding Forum) discussion: https://forum.doom9.org/showthread.php?t=181802

Edited September 3, 2020 by FranceBB

[Qniemiec]

Hi there, the download link posted above doesn't work anymore, could you please upload your file/s again, or would this provoke any trouble with Zeronoe (he himself has deleted his last XP-compatible ffmpeg version completely from his repository, so only _very_ old versions still exist hera and there).

Greetings, QN

[VistaLover]

4 hours ago, Qniemiec said:

the download link posted above doesn't work anymore, could you please upload your file/s again

You can access the same build here ; BTW, that link is contained within the following get_iplayer mailing list post:

http://lists.infradead.org/pipermail/get_iplayer/2017-May/010711.html

I am the author of that post, also the person who compiled that FFmpeg build; now I don't want to bring up plagiarism into this discussion, but it seems the internet is such a small place after all

Just compare, if you will (posted Dec 28th, 2017):

On 12/28/2017 at 2:33 AM, FranceBB said:

I noticed that FFmpeg code itself has not stopped being XP compatible, but the inclusion by Zeranoe of some external libs that are either themselves by default not compatible or have become incompatible at some stage of their development is what broke Zeranoe builds.

to (posted May 10th, 2017):

Quote

The FFmpeg code itself has not stopped being XP/Vista compatible, but the inclusion by Zeranoe of some external libs that are either themselves by default not compatible or have become incompatible at some stage of their development is what broke recent Zeranoe builds on XP/Vista. E.g., --enable-libmfx breaks builds on XP, while --enable-libx265 without the -DWINXP_SUPPORT=ON flag breaks builds on both XP/Vista (and it's the reason behind errors like: https://squarepenguin.co.uk/forums/thread-1307.html )

FWIW, MSFN forum member @CoRoNe compiles and offers, out of pure comradeship, recent, XP compatible, FFmpeg builds, though his are optimised for older processors ; he has, not long ago, announced new builds in another thread, here is his post Enjoy!

Edited October 18, 2018 by VistaLover

[FranceBB]

This discussion is way outdated. @CoRoNe keeps ffmpeg updated here: https://rwijnsma.home.xs4all.nl/files/ffmpeg/?C=M;O=D

@VistaLover I generally help people on Doom9 and I remember when they were talking about ffms2000 and I found your mailing post, but, just like Avisynth plugins, I generally re-compile them myself with the assembly optimisations available for my CPU using Visual Studio. If I remember correctly, you disabled some assembly optimisations and I didn't like that, however I tried to compile it with Intel Parallel Studio but it didn't work, so I ended up using Visual Studio (disabling the same things you pointed out because I read your post and you saved me a lot of time, really), but enabling assembly optimisations available to my CPU at the time.

I apologize if it sounded like plagiarism, but trust me, no harm was intended at all.

By the way, Vangelis, since you are the same person of "VistaLover", I wanna ask you something now that I have the chance ^^

During the last few days I've been trying to compile the latest VSFilter for XP and it does compile with v141_xp toolset (and specifying /Zc:threadSafeInit-), but it doesn't work and ends up with an Invalid Access Memory Location (998) on run-time.

I noticed that two kernel calls are missing in Windows XP: InitializeProcThreadAttributeList and DeleteProcThreadAttributeList.

Unfortunately, these two functions have been introduced in Windows Vista.

InitializeProcThreadAttributeList is a bool.
It returns a zero value if it fails or a non-zero value if it succeeds.
It has lpAttributeList (which is the attribute list and it can be NULL to determine the buffer size required to support the specified number of attributes), dwAttributeCount (which is the count of attributes to be added to the list), dwFlags (which is a reserved parameter and it must be zero) and lpSize.

BOOL InitializeProcThreadAttributeList(
  LPPROC_THREAD_ATTRIBUTE_LIST lpAttributeList,
  DWORD                        dwAttributeCount,
  DWORD                        dwFlags,
  PSIZE_T                      lpSize
);

DeleteProcThreadAttributeList is a void and thus it does not return a value. It simply has lpAttributeList which is the attribute list created by the InitializeProcThreadAttributeList function.

void DeleteProcThreadAttributeList(
  LPPROC_THREAD_ATTRIBUTE_LIST lpAttributeList
);

I took a look at Wine and it seems that they implemented the call, so I tried to take their implementation and use it as a wrapper to basically direct the call to it instead of to the kernel, but unfortunately it didn't work.

This is the project: https://github.com/pinterf/xy-VSFilter

Shouldn't the v141_xp output a valid xp binary and get rid of those things, especially 'cause they are not included inside VSFilter itself but are probably a dependency?

Thank you in advance.

Edited October 18, 2018 by FranceBB

[Reino]

14 hours ago, FranceBB said:

This discussion is way outdated. @CoRoNe keeps ffmpeg updated here: https://rwijnsma.home.xs4all.nl/files/ffmpeg/?C=M;O=D

I do, but I announce them on Zeranoe's forum. I try to release a new build every 4 months or so.

14 hours ago, FranceBB said:

During the last few days I've been trying to compile the latest VSFilter for XP and it does compile with v141_xp toolset (and specifying /Zc:threadSafeInit-), but it doesn't work and ends up with an Invalid Access Memory Location (998) on run-time.

I'm using 3DYD's LAV Filters fork for WinXP. Maybe their code/changes can help you with that.

[i4004]

just wanted to say thanks, and that avatar is suspiciously familiar....

[Reino]

Hehe. Zoom Player's old icon.

[mirh]

Friendly reminder that anybody can have its own ffmpeg with blackjack, hookers, and even XP support.

The hard part, more than coding or whatever, is setting up the build enviroment if any. For which there are handy helper scripts thankfully

https://github.com/jb-alvarado/media-autobuild_suite

https://github.com/rdp/ffmpeg-windows-build-helpers

[Samuel]

Before an appropied presentation, i want to write my first post. I find a ffmpeg binary supported by XP a just replace the .exe in 2 software, myponi and Vov Screen Recorder and there is no sign of problems. the file is dated april, 2019. just i wonder if there is a mirror like videohelp or similar and is this a vanilla bulid or custom? a serch in google not point to anything usefull for legacy version

ffmpeg-N-93674-g1e01f66-win32-static_legacy.7z
https://rwijnsma.home.xs4all.nl/files/ffmpeg/?C=M;O=D

Edited April 12, 2020 by Samuel

[FranceBB]

16 minutes ago, Samuel said:

Before an appropied presentation, i want to write my first post. I find a ffmpeg binary supported by XP a just replace the .exe in 2 software, myponi and Vov Screen Recorder and there is no sign of problems. the file is dated april, 2019. just i wonder if there is a mirror like videohelp or similar and is this a vanilla bulid or custom? a serch in google not point to anything usefull for legacy version

ffmpeg-N-93674-g1e01f66-win32-static_legacy.7z
https://rwijnsma.home.xs4all.nl/files/ffmpeg/?C=M;O=D

Indeed. I cleanup the topic a bit and I removed my build. I left the link to the old @VistaLover build but I wrote that I strongly encourage users about using @Reino builds.

[Reino]

4 hours ago, Samuel said:

the file is dated april, 2019. just i wonder if there is a mirror like videohelp or similar and is this a vanilla bulid or custom? a serch in google not point to anything usefull for legacy version

That particular release is first of all an old one already. There are newer releases. They're just named differently.
As far as I know my binaries are not on videohelp.com. Why should they be?
There's no "vanilla FFmpeg build". Every FFmpeg binary is essentially a custom build considering the vast amount of libraries one can include during the compilation process.
"Legacy" as in legacy hardware. When I started compiling my own FFmpeg binaries they needed to work on my ancient AMD Athlon XP 3200+ (non-SSE2) cpu. My binaries should work on a Intel Pentium 3.

@FranceBB Did you change the thread-title? :D

[FranceBB]

37 minutes ago, Reino said:

When I started compiling my own FFmpeg binaries they needed to work on my ancient AMD Athlon XP 3200+ (non-SSE2) cpu.

@FranceBB Did you change the thread-title?

I remember the AMD Athlon 3200+ as it was one of my CPUs. I still have it in my garage along with the motherboard. It was my upgrade from a Sempron and it was blazing fast compared to the Sempron back in the days thanks to the added cache and the 2.2GHz which was way higher than the 1.6GHz of the Sempron. Besides, those were the monocore golden days of AMD before falling down against Intel. I still remember that AMD used to even mock Intel by calling their Athlon 3200 because although they had a clock of 2.2GHz, they were as fast as an Intel 3.2GHz. Because of the lower clock to have the same speed, they were cooler than Intel CPUs, however this different implementation which was good for AMD during the monocore days, prevented them from releasing good parallelized multicore which led to a total defeat against Intel in the long run. After the AMD Athlon 3200+ I bought the AMD Athlon 3800+ which I overclocked from 2.8GHz to 3.2GHz.

Ah... Good old days... After that AMD had a failure after another... AMD Athlon 64 dual core were crap, as well as the Phoenom II x4 and the Phoenom II X6 which I purchased. After yet the last delusion about my 6 core which was WORSE than an Intel i5, leaving alone an i7, I decided to move to Intel and I've been happy ever since.

 

Oh, as to the title, I did change it 'cause I think there was a mess and people were ending up by downloading either my build which was outdated or VistaLover's build which was outdated, when instead there's a series of updated builds made by you that everyone should use. You deserve the topic xD

[Reino]

The motherboard... a ASUS A7N8X-E Deluxe by any chance?

Though I appreciate the gesture, I still prefer Zeranoe's forum thread as my primary thread for my binaries, so maybe you could mention https://ffmpeg.zeranoe.com/forum/viewtopic.php?f=3&t=6930 in your first post?

[FranceBB]

2 hours ago, Reino said:

The motherboard... a ASUS A7N8X-E Deluxe by any chance?

Though I appreciate the gesture, I still prefer Zeranoe's forum thread as my primary thread for my binaries, so maybe you could mention https://ffmpeg.zeranoe.com/forum/viewtopic.php?f=3&t=6930 in your first post?

Nope, I didn't have that ASUS, I should check the model somewhere but it wasn't that one.

As to the topic, I thought about mentioning it in the first place and will do it right now since you asked, but the reason why I didn't do it is that zeranoe's forum requires TLS1.3 which isn't supported on XP unless you have Roytam browsers.

[RainyShadow]

Lucky guys, to have the fastest CPU for socket 462... Mine is merely  an AthlonXP 3000+. Still rocking on my main PC :)

 

Are you aware of any ffdshow fork or unofficial build newer than v.4534 ?