[FFmpeg-trac] #11026(undetermined:new): Recent version provides useless progress information
FFmpeg
trac at avcodec.org
Fri May 24 15:39:17 EEST 2024
#11026: Recent version provides useless progress information
-------------------------------------+-------------------------------------
Reporter: Jozef | Type: defect
Chutka |
Status: new | Priority: normal
Component: | Version: git-
undetermined | master
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
In the most recent ffmpeg, when muxing stdin data into .mp4 the progress
information is pretty useless and provides no valuable info:
{{{
ffmpeg -r 25 -f h264 -i - -map 0 -f mp4 -vcodec copy -pix_fmt yuv420p -t
60 -y out.mp4
Input #0, h264, from 'fd:':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive),
1280x720, 25 fps, 1200k tbr, 1200k tbn
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Output #0, mp4, to 'out.mp4':
Metadata:
comment : Created in wide.video $APP_VERSION
encoder : Lavf61.3.104
Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709,
progressive), 1280x720, q=2-31, 25 fps, 1200k tbr, 12800 tbn
[mp4 @ 0x29690c0] Timestamps are unset in a packet for stream 0. This is
deprecated and will stop working in the future. Fix your code to set the
timestamps properly
size= 0KiB time=N/A bitrate=N/A speed=N/A
size= 0KiB time=N/A bitrate=N/A speed=N/A
...
[out#0/mp4 @ 0x2969000] video:93KiB audio:0KiB subtitle:0KiB other
streams:0KiB global headers:0KiB muxing overhead: 7.367472%
size= 100KiB time=N/A bitrate=N/A speed=N/A
}}}
...its missing frame and time information.
However, when encoding is involved there is valuable `frame=` and `time=`
info provided.
{{{
ffmpeg -r 25 -f rawvideo -pix_fmt rgba -s 1280x720 -i - -map 0 -f mp4
-vcodec libopenh264 -pix_fmt yuv420p ...
...
frame= 39 fps=0.0 q=-0.0 size= 0KiB time=00:00:01.56 bitrate=
0.2kbits/s speed=3.11x
frame= 103 fps=103 q=-0.0 size= 0KiB time=00:00:04.12 bitrate=
0.1kbits/s speed=4.11x
}}}
This is a regression as ffmpeg 6.0 provided valid frame+time information
even for the first example (muxing only).
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11026>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list