Mark-XP Posted Thursday at 01:41 PM Posted Thursday at 01:41 PM (edited) 1 hour ago, nicolaasjan said: Don't the standalone Linux builds work (they have newer Python embedded)? yt-dlp_linux or (for 32bit) my yt-dlp_linux_x86. Oh NICE, thank you, yes they do work! Tbh, i simply ignored them until now, as the plain yt-dlp executable always did the job. Edit: Now, as i wanted to copy/deploy Python-3.12.5 from my dev-disk to the main System i discovered, that i didn't only ,brew' the executable (of about 36MB) but also an additional Python-3.12 folder in /usr/local/lib - of about 287 MB! So i decide to utilize this (now even more appreciated) Py-integrated version in the nearer future. And i'm wondering a bit, how the new XP-Version can be so small in size! Edited Thursday at 02:48 PM by Mark-XP Edit 1
nicolaasjan Posted Thursday at 05:49 PM Posted Thursday at 05:49 PM (edited) 4 hours ago, Mark-XP said: And i'm wondering a bit, how the new XP-Version can be so small in size! No idea. My homebrew Python 3.14 Linux standalone executable is even 51.7MB. 😮 Almost 100MB unpacked in the /tmp folder. Edited Thursday at 05:59 PM by nicolaasjan 2
VistaLover Posted Thursday at 11:16 PM Posted Thursday at 11:16 PM (edited) 18 hours ago, autodidact said: I also have Vista specific builds locally as I still run Vista x64. Thanks a lot for your reply ; as I wrote, Vista SP2 32-bit here; from 2016-2018 I used to use MABS (MSYS2/MinGW) to compile locally non-free ffmpeg builds; after that time, several MSYS2 components went Win7+ (e.g. "make") and by 2021, the compiler itself stopped being available for the 32-bit architecture; needless to say, latest MABS is meant for a recent version of Win10 64-bit; yes, you probably can still compile 32-bit binaries with it, but those won't run on Vista, possibly not on Win7, too ... The AnimMouse ffmpeg builds used to be Vista-compatible, but broke at some time (early 2022); as a Vista user too, you probably know those things already ... I'm not closely following current FFmpeg development ; at one time I was aware that the FFmpeg code itself continued to be NT 6.0 compatible (as opposed to NT 5.x), so that a "no-libs" compiled binary would launch normally under Vista; but a lot of the third party (external) libs built normally into FFmpeg are the main culprits for breaking Vista-support (x265 comes to mind, with its NUMA Win7+ functions ) ; it must be quite an enormous task today for you to restore NT 6.1/6.0 and even 5.x support on your custom FFmpeg builds; you are to be highly praised for this feat ... On a 32-bit, under-resourced (by today's standards ) machine, I practically have little use of most of those extra libs (especially video encoders); I rarely do video transcoding here, mostly audio transcoding is being performed; it's those many optional external libs that inflate static binaries' filesize and are the cause for broken NT 6.0 support, for all I know... 18 hours ago, autodidact said: I may be able to put something together in a 32-bit shared configuration that targets Vista. If you are willing to test? This would be XP incompatible, so Vista and up. Thanks for your intention! User Reino here (now on Win11) used to offer both static+shared 32-bit builds, targeting WinXP SP3 and an SSE-only CPU, ca. every 4 months ; it'd be very sweet from you if you managed to offer something similar, but for more recent CPUs (e.g. SSE2+) and on Vista+... FWIW, this thread started a long while ago and mentions "winxp" in its title, but is actually frequented now by members of various WinOSes ; so I hope you posting Vista+ FFmpeg builds will be OK ; of course, there's always that ... "Willing to test? " -> Simply throw "them" at me ... Best regards. Edited Thursday at 11:20 PM by VistaLover 2
j7n Posted yesterday at 07:36 AM Author Posted yesterday at 07:36 AM Ffmpeg has grown to be absolutely ginormous. I remember how they used to have their own encoders for h.264 and h.262 with shared parts. The new encoders are far too slow, and more encoders keep getting invented. If I needed video, I would use x264 instead. Some people actively promote ffmpeg as a solution for all, but it kinda tries to be a jack of all trades and not the best. I don't see a use for ffmpeg for YouTube downloads. So what is new? How do we rip today? What numbers to use for Safari HLS?
VistaLover Posted yesterday at 10:58 PM Posted yesterday at 10:58 PM (edited) @nicolaasjan : https://3dyd.github.io/pyinstaller-builds/ Your prayers have been answered! https://github.com/3dyd/pyinstaller-builds https://github.com/3dyd/pyinstaller/tree/6.16.0-xp Edited yesterday at 11:07 PM by VistaLover 3
nicolaasjan Posted 17 hours ago Posted 17 hours ago (edited) 7 hours ago, VistaLover said: @nicolaasjan : https://3dyd.github.io/pyinstaller-builds/ Your prayers have been answered! https://github.com/3dyd/pyinstaller-builds https://github.com/3dyd/pyinstaller/tree/6.16.0-xp Yes, I've already tested it and everything is working. 🙂 However, now the question is ; how long will yt-dlp on XP keep working?... 🤔 Soon, an external JavaScript runtime will be needed. Deno is out of the question on older systems and yt-dlp-getpot-jsi gave me errors on both Windows XP and Windows7 (see Issue 9 ). Edited 16 hours ago by nicolaasjan 2
j7n Posted 8 hours ago Author Posted 8 hours ago I watched my first video in a couple days. This works. -f 96,96-0 --extractor-args "youtube:player_client=web_safari" Some of the formats are in other languages. I wonder how it works if it is an AI speech synthesizer and the author gives it the text, or if the voice is entirely supplied by the author which would be a lot of work.
autodidact Posted 4 hours ago Posted 4 hours ago On 10/23/2025 at 7:16 PM, VistaLover said: "Willing to test? " -> Simply throw "them" at me ... FFmpeg shared for Vista x86. 2
VistaLover Posted 2 hours ago Posted 2 hours ago 1 hour ago, autodidact said: FFmpeg shared for Vista x86. Thanks! Launches OK here: ffmpeg version N-121515-gdefd5f3f64-WINVISTA Copyright (c) 2000-2025 the FFmpeg developers built with gcc 15.2.0 (Rev8, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d12va --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --enable-ffnvcodec --enable-nvdec --enable-mediafoundation --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libdav1d --enable-libaom --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-librav1e --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libkvazaar --enable-libmodplug --enable-librubberband --enable-libxavs --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-vulkan --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libvvenc --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-libcelt --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opencl --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 60. 14.100 / 60. 14.100 libavcodec 62. 16.100 / 62. 16.100 libavformat 62. 6.101 / 62. 6.101 libavdevice 62. 2.100 / 62. 2.100 libavfilter 11. 9.100 / 11. 9.100 libswscale 9. 3.100 / 9. 3.100 libswresample 6. 2.100 / 6. 2.100 Universal media converter usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}... Use -h to get full help or, even better, run 'man ffmpeg' Some remarks: 1. The extracted .7z archive results in a folder sized 125 MiB, i.e. ca. 100 MiB less compared to using both static FFmpeg.exe+FFprobe.exe binaries ... 2. --enable-libfdk-aac : I take it this means I can still use the "libfdk-aac-2.dll" file from inside the "libfdk-aac-2.0.3-158-d8e6b1a-win32-xpmod-P4.7z" archive to enable that (non-free) audio encoder? 3. This is just an observation, but this build configuration still contains a lot of flags/libs either not applicable to my platform (e.g. --enable-d3d12va) or ones I'd never use myself: --enable-cuda --enable-cuvid --enable-d3d12va --enable-nvenc --enable-nvdec --enable-mediafoundation --enable-libvpx --enable-libdav1d --enable-libaom --enable-libmysofa --enable-librav1e --enable-libkvazaar --enable-libxavs But I see what you did there ; this is not tailored specifically to an old Vista SP2 32-bit machine with iGPU (Intel), but is a full-fledged compile (full set of libs/filters/etc.), with minimum OS requirement lowered to NT 6.0; all those extra libs can still be used efficiently on a more recent WinOS, with more powerful H/W ... 4. N-121515-gdefd5f3f64 : For those who prefer a slightly different git-versioning scheme, this is equal to n8.1-dev-891-git-2025-10-25-gdefd5f3 i.e. built from a master branch code snapshot (commit defd5f3) authored today, which is the 891st commit after tag "n8.1-dev" was cut ... Really impressive, am much obliged! The retrocomputing communities are in high need of altruistic persons such as yourself! Take the best of care...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now