Windows XP compatible non-SSE2 FFmpeg binaries

[GMJCZP]

Thank you Manolito! I'll try all the information that you has written.

[Reino]

A user of my FFmpeg binaries (but not a Doom9 member, I think) notified me of a small regression; the absence of the drawtext filter, where ffmpeg-6.1-588-4006c71 (12 months ago) was the latest still working release.
I've done some searching and found that it all comes down to "avfilter/vf_drawtext: improve glyph shaping and positioning". Starting with this commit libharfbuzz is added as a dependency for the drawtext filter, which means that to enable the drawtext filter you have to configure and compile FFmpeg with --enable-libharfbuzz. I've done just that a moment ago. I've uploaded and replaced the latest release with it! So, same filename.

[FranceBB]

Thanks for that, Reino.
I don't generally use drawtext, but a friend of mine does to display the timecode. Hopefully it will make him happy.

[danbow]

Reino Hi. Can You help me. In latest versions ffmpeg-7.1 (2024-05-05), (2024-05-26), i use this:
ffmpeg -ss 5:33.667 -to 7:49.219 -i "360p.mp4" -cpucount 1 -f avi -c:v huffyuv -vf "mpdecimate,setpts=N/FRAME_RATE/TB" -an -sn "360p.avi"
and video output with 600 fps. In previous ffmpeg-6.2-609-238f9de-win32 (2024-01-01) same command out 23.976.
This video Initially 23.976fps, but with duplicate frames. Sorry. Thank You! Very much.

[Emulgator]

ffmpeg 7.0 (and 7.1) has removed some in 6.x depreciated, nonetheless there still valid and used command syntax.
Their logic seems to be : What we consider depreciated from one big version step (+1) on, may still be used within this new version (+1),
but will be removed in the following version (+2).
You may want to read that up in ffmpeg docs:

This release is not backwards compatible, removing APIs deprecated before 6.0. The biggest change for most library callers will be the removal of the old bitmask-based channel layout API, replaced by the AVChannelLayout API allowing such features as custom channel ordering, or Ambisonics. Certain deprecated ffmpeg CLI options were also removed...

[Reino]

Hello danbow.
I don't see a question in your post. But anyway, as I'm not an FFmpeg expert, I can't help you with usage questions like these. Though I can say that -to should always come after -i. See https://trac.ffmpeg.org/wiki/Seeking.
You're better off asking on the FFmpeg user mailinglist, or on StackOverflow.

[danbow]

My question: it not mistake ffmpeg? so and it is necessary in new version?

[GMJCZP]

I did all the tests and everything turned out perfect, both with libfdk-aac-2 and dmMediaConverter, many thanks to Reino and manolito!

[danbow]

And, i try run official ffmpeg-7.0.1-full_build 2024-05-26 on Windows 7 x64 - not starting. Stop supported?

[FranceBB]

Originally Posted by danbow

And, i try run official ffmpeg-7.0.1-full_build 2024-05-26 on Windows 7 x64 - not starting. Stop supported?

Welcome to the club, Win7 buddy.
The Windows Vista folks were waiting for you along with us, XP users.

[lvqcl]

Originally Posted by danbow

And, i try run official ffmpeg-7.0.1-full_build 2024-05-26 on Windows 7 x64 - not starting. Stop supported?

Probably https://github.com/GyanD/codexffmpeg...ent-2147215357

[Emulgator]

Respect for finding those needles in the haystack.

[manolito]

Please, respect the topic for this thread:
Windows XP compatible non-SSE2 FFmpeg binaries

Questions like there:

i try run official ffmpeg-7.0.1-full_build 2024-05-26 on Windows 7 x64

should be posted in a separate new thread...


Such a new thread would also be the place where I'd like to discuss other non-official FFmpeg versions like this one:

https://www.reddit.com/user/Veritabl...r_windows_x64/

Post was deleted

Also it could be a good place to discuss more generic tools to make "modern" applications compatible with Win7. Like this one:

Cheers
manolito

[danbow]

manolito forgive me please. Reino, manolito thank You very very much for this tool for xp users

[manolito]

Not sure if this is the appropriate thread, but since there is no separate FFmpeg forum in Doom9 I figured that I might just as well post it here...

It is about HDR to SDR conversions which uses the z.lip library. Up to version 6.xx this library had a bug which made sources with these properties fail:

If MediaInfo reports that the chroma subsampling of the source is 4:2:0 (Type2) then this FFmpeg command line will fail

This has been fixed by the z.lib devs for the current FFmpeg versions 7.xx. Here is my Readme for dmMediaConcerter (of cource also applies if FFmpeg is used via command line):

Using FFmpeg to convert HDR sources to SDR:
======================================================================

This video filter call will do it (thanks to dipje and Atak_Snajpera):


SD target:
----------
zscale=s=704x396,zscale=tin=smpte2084:min=bt2020nc:pin=bt2020:rin=tv:t=smpte2084:m=bt2020nc:p=bt2020:r=tv,zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt470bg,tonemap=tonemap=hable:desat=0,zscale=t=601:m=bt470bg:r=tv,format=yuv420p


Half HD target:
---------------
zscale=s=1280x720,zscale=tin=smpte2084:min=bt2020nc:pin=bt2020:rin=tv:t=smpte2084:m=bt2020nc:p=bt2020:r=tv,zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt709,tonemap=tonemap=hable:desat=0,zscale=t=bt709:m=bt709:r=tv,format=yuv420p


Full HD target:
---------------
zscale=s=1920x1080,zscale=tin=smpte2084:min=bt2020nc:pin=bt2020:rin=tv:t=smpte2084:m=bt2020nc:p=bt2020:r=tv,zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt709,tonemap=tonemap=hable:desat=0,zscale=t=bt709:m=bt709:r=tv,format=yuv420p


These FFmpeg parameter lines are meant to be inserted in the "Picture 
Settings -> More" field of dmMediaConverter. If you want to use them 
in an existing FFmpeg commandline you need to add them as a video 
filter and enclose the parameters in double quotes. 
Like:
-vf "parameter list"



________________________________________________________________________________

Note:
The following section only applies to FFmpeg versions up to 6.xx.
It is no longer needed for later FFmpeg versions from 7.0 upwards.

--------------------------------------------------------------------------------
If you use the source file directly as the FFmpeg input you may get 
borked colors in the output depending on the source format. If MediaInfo 
reports that the chroma subsampling of the source is 4:2:0 (Type2) then this 
FFmpeg command line will fail. The safest way to correct this is to use an 
AVS script with just the source filter as the input for FFmpeg (of course 
only if AviSynth is installed). 
Otherwise you have to pre-convert the source to a lossless intermediate 
file keeping all the source properties. Then use this lossless file as 
the input for FFmpeg and apply the HDR to SDR filter.
--------------------------------------------------------------------------------

Workarounds for these kind of HDR sources are no longer needed.


Cheers
manolito

[Reino]

Another round of FFmpeg binaries. See post #1 for details.

[FranceBB]

Thank you for keeping XP alive!

[Scruff]

Originally Posted by Reino

A user of my FFmpeg binaries (but not a Doom9 member, I think) notified me of a small regression; the absence of the drawtext filter, where ffmpeg-6.1-588-4006c71 (12 months ago) was the latest still working release.
I've done some searching and found that it all comes down to "avfilter/vf_drawtext: improve glyph shaping and positioning". Starting with this commit libharfbuzz is added as a dependency for the drawtext filter, which means that to enable the drawtext filter you have to configure and compile FFmpeg with --enable-libharfbuzz. I've done just that a moment ago. I've uploaded and replaced the latest release with it! So, same filename.

Hi all. @Reino, would you be able to rebuild 6.1.2009 please? It also has DrawText disabled but is the last build with XFade working properly. The v7 builds use double the memory and fail with "cannot allocate memory" errors if you have a long filter chain. Build 6.1.2009 seems to work properly but DrawText is missing.

Also, is there an updated helper script? The one at github is not working because some of the dependencies are no longer available. I managed to fix the first two errors I came across, but I am now stuck with "rubberband" failing with error "sndfile not found" - I can't seem to find the right package to fix the problem.

These are the fixes I've found so far for cross_compile_ffmpeg.sh:

426	-download_and_unpack_file http://zlib.net/zlib-1.3.tar.xz
	+download_and_unpack_file http://zlib.net/zlib-1.3.1.tar.gz

427	-cd zlib-1.3
	+cd zlib-1.3.1

552	-do_git_checkout https://github.com/xiph/opus.git
	+download_and_unpack_file http://ftp.osuosl.org/pub/xiph/releases/opus/opus-1.2.1.tar.gz

553	-cd opus_git
	+cd opus-1.2.1

686	-do_git_checkout https://github.com/breakfastquay/rubberband.git "" "" 18c06ab8c431854056407c467f4755f761e36a8e
	+download_and_unpack_file http://breakfastquay.com/files/releases/rubberband-3.3.0.tar.bz2

687	-cd rubberband_git
	+cd rubberband-3.3.0

[Reino]

Originally Posted by Scruff

would you be able to rebuild 6.1.2009 please? It also has DrawText disabled but is the last build with XFade working properly.

I can try.

Originally Posted by Scruff

Also, is there an updated helper script? The one at github is not working because [...]

Which one at Github? That doesn't look like mine, or at least not the latest one.

[Scruff]

Thanks mate.

The script I'm using is the one linked in Post#1 (https://github.com/Reino17/ffmpeg-windows-build-helpers). The changes I posted are changes I had to make myself. The first 2 (zlib-1.3.1 and opus-1.2.1) seem to have worked but I'm stuck at rubberband - that one requires sndfile and I don't know how to add that to the script properly.