[FFmpeg-trac] #5081(ffmpeg:new): A wish for ffmpeg to be able to reference input properties
FFmpeg
trac at avcodec.org
Sun Jan 24 22:51:17 CET 2016
#5081: A wish for ffmpeg to be able to reference input properties
-------------------------------------+----------------------------------
Reporter: mulvya | 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 Misaki):
In the contrived example, -shortest might be able to accomplish the same
goal, but it might sometimes have some 'bugs'. (Audio ending slightly
before video if they come from the same input file, things like that...
-frames:v sometimes has similar issues)
In my experience, batch processing of diverse files is not ideal. One
example, a file that is really 30 fps, but was encoded at 60 fps causing
every other frame to be a duplicate. This doesn't show up in the file
properties, and leaving it that way will cause CPU usage to be about twice
as high during playback. Using a filter would remove the duplicate frames
automatically, but the file would still have '60 fps' in the properties,
so many video players (like VLC) will avoid using hardware decoding using
the default method (VDPAU) in Linux, even if it's actually just 30 fps and
could be played with no problems.
ffmpeg doesn't have a 'same quality as source' option, and common codecs
like h.264 don't seem to facilitate it. So basically, video encoding is
currently aimed at people with high-quality source videos. (Vine, and
maybe Instagram, use h264 for their videos and the options are the same as
the default in ffmpeg, so maybe they use it!)
--
Ticket URL: <https://trac.ffmpeg.org/ticket/5081#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list