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
ti
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
me
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 compli
Hello!
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 un
