Years ago, I had a Windows machine and ffmpeg would break all the time, so I used a static build for reliability. I'm happy to say that I have found MacPorts ffmpeg to be very reliable and of course up to date; I used it today to transcode from Apple ProRes 422 to H.264 for the Web for the first time. Last month I helped a friend adding an introduction video to a website with cropping, titles, and a logo bug added with ffmpeg
Sean On Fri, Dec 4, 2020 at 10:08 PM Richard L. Hamilton <[email protected]> wrote: > ff-Works is a GUI front-end for ffmpeg, possibly among other things. I can > see that it might be helpful given that the options for ffmpeg can be > difficult to get right, esp. for someone who rarely uses Terminal at all. > > When I looked at its web site (I don't have ff-Works myself), I did see a > mention of a static ffmpeg. I don't see how that should be necessary if > they're just running the command, but someone wishing to know whether that > was true would either have to try it, or ask the ff-Works folks directly. > > > On Dec 4, 2020, at 21:29, Ryan Schmidt <[email protected]> wrote: > > > > > > > > On Dec 3, 2020, at 11:44, K Hindall wrote: > > > >> I have never been a coder, which is why I have Macports. > >> > >> Now I need a static ffmpeg file (to run ff·Works, thereby proving that > I am not a coder!). I know that Macports uses dynamic libraries rather than > static ones and somehow that complicates the process, but ... that's as far > as my understanding goes. > >> > >> I would need either a port that would do it for me or *very* precise > instructions on how to do it. > >> > >> Does anyone know of either? I've poked around on the Web, but haven't > found anything that I can make sense of. > > > > So you would like an ffmpeg program that is statically linked to all of > the libraries that it depends on, rather than dynamically? We don't and > wouldn't offer that in MacPorts. > > > > Why do you need this? I haven't heard of ff·Works, but why would it need > a statically linked ffmpeg? Why can't it use our dynamically-linked ffmpeg? > Why would it care? > > > > > >
