[FFmpeg-trac] #8371(undetermined:closed): ffmpeg’s output section and ffprobe’s input section: Display the same pixel format
FFmpeg
trac at avcodec.org
Thu Nov 7 06:52:42 EET 2019
#8371: ffmpeg’s output section and ffprobe’s input section: Display the same pixel
format
-------------------------------------+-------------------------------------
Reporter: Kdmeizk | Owner:
Type: defect | Status: closed
Priority: normal | Component:
| undetermined
Version: git-master | Resolution: invalid
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Kdmeizk):
Replying to [comment:1 Cigaes]:
> ffmpeg and ffprobe will not lie to you. They tell you what they are
doing. You are misunderstanding the whole concept of pixel formats. Please
stop opening issues until you understand it better.
I can try to better explain what you misunderstood, because I did not
write explicitly or implicitly something like “ffmpeg and ffprobe lie”.
For the pixel formats, ffmpeg’s output section displays the value set to
“-pix_fmt” which is the pixel format “nv12”. In ffprobe, I believe the
function
“[https://git.videolan.org/?p=ffmpeg.git;a=blob;f=libavcodec/utils.c;hb=HEAD
avcodec_string]” is called and contains:
{{{
snprintf(buf + strlen(buf), buf_size - strlen(buf),
"%s", enc->pix_fmt == AV_PIX_FMT_NONE ? "none" :
av_get_pix_fmt_name(enc->pix_fmt));
}}}
So the pixel format “yuv420p” is displayed.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8371#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list