Mark-XP Posted yesterday at 01:41 PM Posted yesterday 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 yesterday at 02:48 PM by Mark-XP Edit 1
nicolaasjan Posted yesterday at 05:49 PM Posted yesterday 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 yesterday at 05:59 PM by nicolaasjan 2
VistaLover Posted 19 hours ago Posted 19 hours ago (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 19 hours ago by VistaLover
j7n Posted 10 hours ago Author Posted 10 hours ago 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?
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