3 ms·
You're getting a lot of flak due to how you started off your comment, but I mostly agree with you. In my opinion there are two kinds of users: 1. Users who use
by koyote 10mo ago
You're getting a lot of flak due to how you started off your comment, but I mostly agree with you.
In my opinion there are two kinds of users:
1. Users who use FFmpeg regularly enough to know/understand the parameters.
2. Users who only use FFmpeg once in a while to do something specific.
This wrapper is superfluous for users in group number 1.
But group number 2 does not really get much out of it either, for the reasons you've mentioned.
As a member of group 2, I usually want to do something very specific (e.g. remove an audio track, convert only the video, remux to a different container, etc.).
A simple English wrapper does not help me here because it is not powerful enough; the defaults are usually not what I want.
What I need is a tool that will take a more detailed English statement of what I want to achieve and spit out the FFmpeg command with explanations for what each parameter does and how it achieves my goal.
We have this today: AI; and it mostly works (once you've gone through several iterations of it hallucinating options that do not exist...).
- qbow883 10mo agoThank you, this explains my thoughts really well.
- CamperBob2 10mo agoUsually when AI hallucinates an option that doesn't exist, the option really should exist. So then I tell it to add it. Then, several days later, I crawl away from fighting robots in a rabbit hole, and finally get around to doing what I set out to do in the first place....