I think in general a lot of problems with commandline software in general exist when the software begins to exceed the ability of a commandline to act as a workable UI. Naturally there are reasons to provide serialised instructions to a piece of software, but in many cases that isn't really intended as a user interface, it's intended as an API. The discoverability of a CLI is near zero, and the lack of examples in the documentation doesn't help. For many tasks, software with as many complexities as ffmpeg desperately needs a GUI. P _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
- Re: [FFmpeg-user] flame about confusing command ... Carl Eugen Hoyos
- Re: [FFmpeg-user] flame about confusing comm... Michael Koch
- Re: [FFmpeg-user] flame about confusing ... Reindl Harald
- Re: [FFmpeg-user] flame about confu... Michael Koch
- Re: [FFmpeg-user] flame about c... Reindl Harald
- Re: [FFmpeg-user] flame about c... Paul B Mahol
- Re: [FFmpeg-user] flame about c... Reindl Harald
- Re: [FFmpeg-user] flame about c... Michael Koch
- Re: [FFmpeg-user] flame about confusing command line opti... Reindl Harald
- Re: [FFmpeg-user] flame about confusing command line... Carl Eugen Hoyos
- Re: [FFmpeg-user] flame about confusing command line opti... Phil Rhodes
- Re: [FFmpeg-user] flame about confusing command line... Reindl Harald
- Re: [FFmpeg-user] flame about confusing command ... Phil Rhodes
- Re: [FFmpeg-user] flame about confusing comm... Reindl Harald