[FFmpeg-trac] #9066(ffmpeg:new): Enable explicit output extension
FFmpeg
trac at avcodec.org
Thu Jan 21 08:32:30 EET 2021
#9066: Enable explicit output extension
-------------------------------------+----------------------------------
Reporter: tes45t | Owner:
Type: enhancement | Status: new
Priority: wish | Component: ffmpeg
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+----------------------------------
Comment (by tes45t):
@cehoyos That sounds like a too personal opinion. File extension is just a
part of the file name. Forcing a part of the file name to be the only way
to influence the muxer seems like a bizarre constraint to me. That would
be like if your nickname "cehoyos" means that you must work on operating
systems, because it ends with "os". But, as we know, you don't work on
developing an operating system, but instead you work on ffmpeg. Then, why
is your nickname not "cehoyffmpeg"? Isn't that misleading? Or if my
personal name is Patrick and I work in a bakery, should I change my
personal name to Patribakery?
I asure you that a lot of developers from my team share my opinion. If you
want, I can ask all of them to register on this website and upvote this
feature request or post a comment. File extension is just a string, and
should be totally unrelated to the ffmpeg encoding parameters. It is just
a file name, it should not dictate or influence any encoding algorithms or
muxer options. Besides that, I don't see the reason for your expressing
your personal opinion regarding this, since @Gyan said that they already
have a patch for this. I would suggest waiting a few weeks until @Gyan's
patch is merged and refrain from further discussing about this topic until
then. Thanks.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9066#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list