3 ms·
Conversely, if you perform a task frequently you want to be able to script it out and automate it away.
by tartoran 6y ago
Conversely, if you perform a task frequently you want to be able to script it out and automate it away.
- jerf 6y agoWhy not both? GUIs can be built that can emit the command-line equivalent. In ffmpeg's case, I would be looking for a GUI beyond just "here's all the command line parameters, only in a form"... the hardest thing is taking something I already know what I want to do, and encoding it into the command line, because the way to encode a graph into a command line is not obvious. It is easy in principle but there are so many degrees of freedom in how it is done that I can never remember it all. This is a perfect time for a visual language.
- reshie 6y agothere is winff(not sure of its state today) its totally just a gui frontend even shows you it working in console for an example of something already written. scripting can help with more complicated operations but just for common shorthand there are aliases which can be written out scripts single command lines and pointing to script files.
- iso1210 6y agoI use ffmpeg not infrequently, but rarely to do the same thing, so automation doesn't help. Knowing how filter chains work and having access to the filter documentation is great.