2016-10-13 10:32 GMT+02:00 Reindl Harald <h.rei...@thelounge.net>:

> baseline won't solve the problems. It doesn't force low timebase and it
>> doesn't force yuv420p colorspace, it doesn't force FPS 30 limit, so things
>> won't work
>>
>
> *you* are the one operating ffmpeg and so it's under your control,
> practically everyone which is using ffmpeg writes some wrapper script
> around and never bother about details in the future


‚ÄčI've been reading this thread since the beginning, and I believe this
point wasn't stressed enough. ffmpeg is merely a tool that takes input, and
produce as output whatever you asked it to. It does not need to know the
specifics beyond the settings required to operate. Having the abilities to
set everything as required is enough.

Adding more command line options to ffmpeg as a convenience when the same
result can already be achieved in other ways seems inefficient, since many
people do write simple wrapper (sometime a single-line script) to fit their
needs anyway. Changing ffmpeg so that it tries to accomodate the specific
usages of everyone would probably be a nightmare to maintain, when a single
line shell/batch file would achieve the same.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to