XPost: alt.comp.os.windows-10, alt.comp.freeware   
   From: nospam@needed.invalid   
      
   On Wed, 7/16/2025 4:37 AM, Lawrence D'Oliveiro wrote:   
   > On Wed, 16 Jul 2025 08:13:32 +0200, Herbert Kleebauer wrote:   
   >   
   >> I suppose, most people already have ffmpeg installed (it is a   
   >> command line tool, so it doesn't need to be "installed", but just   
   >> copied to your disk) ...   
   >   
   >     ldo@theon:~> ls -l /usr/local/bin/ffmpeg   
   >     -rwxr-xr-x 1 root root 361952 Dec 15  2024 /usr/local/bin/ffmpeg   
   >   
   > Not large, but   
   >   
   > has a lot library dependencies, to implement its plethora of handlers   
   > for formats, codecs, filters etc.   
      
   Windows has a statically compiled FFMPEG.exe available from Gyan,   
   which does the job and can be dragged and dropped into your work folder.   
   WinXP needs an older version of FFMPEG, compared to what is distributed today.   
      
   And I hope all these commands people are using, you've actually   
   tested them and verified an animated GIF is the output. My experience   
   is, there are lots of failures to behold, before you develop a   
   recipe that produces an actual/live/functional animated GIF.   
   An animated GIF has a timing parameter for playback, yielding   
   either a slide show, or, a video-like effect.   
      
   If you ask for GIF output, you could end up with a folder-of-frames   
   with one GIF per frame offered. If the "movie" had a thousand   
   frames, there could be a thousand GIFs, each with a different   
   color table.   
      
   That's why I'm not going to be shooting from the hip, without   
   verifying the result is fit for purpose. Too much can go wrong   
   along the way, and it'll take all morning to make a good tool flow.   
   I've been to this rodeo before, I have "fail-experience" :-)   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)