It won't always give you a perfect answer the first time, but it's much better than memorizing the manual or interpreting a forum discussion. Haven't used it for ffmpeg, but lots of other command lines.
I would far rather look at the manual or a forum discussion, because then I know I'm getting something real. With LLMs, odds are decent that I'm getting something which doesn't actually exist, but it sure would be nice if it did.
I've had someone post a problematic ffmpeg command into a prompt to ask why it wasn't working. It didn't work so well. By the time that someone rejiggered their prompt, I had found the issue.
Comments
One of the best uses of LLMs is to help find the right command line options for tools like ffmpeg.
Prior to LLMs, I made an ffmpeg command line builder. It definitely doesn't cover everything, but handles simple common tasks quite well.
https://ffmpeg-commander.com
It won't always give you a perfect answer the first time, but it's much better than memorizing the manual or interpreting a forum discussion. Haven't used it for ffmpeg, but lots of other command lines.
I find it helps if you paste in the the ffmpeg manual and get the ai to use that as source. Helps it stick to real params.
Because ffmpeg is built on the Unix chained utility philosophy I find ai is also good at building scripts the use it as well
I would far rather look at the manual or a forum discussion, because then I know I'm getting something real. With LLMs, odds are decent that I'm getting something which doesn't actually exist, but it sure would be nice if it did.
I've had someone post a problematic ffmpeg command into a prompt to ask why it wasn't working. It didn't work so well. By the time that someone rejiggered their prompt, I had found the issue.