With the help of a third-party cryptography-library (OpenSSL, GnuTLS, or MbedTLS) I could solve that issue. This was the main reason I wanted to see if I could compile my own FFmpeg binaries. Windows XP doesn't support TLS 1.2 and the latest compatible FFmpeg binary back then couldn't open TLS 1.2 encrypted https-urls either, which a lot of websites started using. This all began end 2016 when (as far as I could tell) no one was willing to create WinXP- and old-CPU compatible FFmpeg binaries anymore. The correct way is to remove FFmpeg 5.0 in PATH, only reserve FFmpeg 4.4.1.On Zeranoe's forum I had a topic where once every 4 months I would post new FFmpeg binaries that are Windows XP compatible and will work on old CPUs without SSE2 instruction sets (like my own AMD Athlon XP 3200+).īecause Zeranoe took down his forum not so long ago I thought I'd create a topic here on Doom9 in the hope some of you might still find these binaries useful. Simply edit line 79 and 80 in Common.m cannot solve the problem (I have tried this. When Mathematica get the path to FFmpeg 5.0, it falls into a loop. After the installation, there are two FFmpeg in PATH.
The problem is if you have installed FFmpeg 5.0, because its libraries are more up-to-date, Mathematica can't match and still reminds to install FFmpeg 4.4.1. If they do not match, message box will show and remind to install FFmpeg 4.4.1. If it is installed, then Mathematica will check if its libraries match the above version. In C:\Program Files\Wolfram Research\Mathematica\13.0\SystemFiles\Links\FFmpegTools\Kernel\Common.m, line 79 and 80: $WindowsWLFFmpegDlls = įor example, when you run $VideoDecoders, Mathematica will first find out if FFmpeg is installed on your computer and get its path. According to this post, I found the reason.
0 kommentar(er)
