Opened 11 years ago
Closed 10 years ago
#5421 closed defect (fixed)
Encoder is no longer displayed, qp range is wrong
| Reported by: | Michael Niedermayer | Owned by: | |
|---|---|---|---|
| Priority: | important | Component: | undetermined |
| Version: | git-master | Keywords: | codecpar regression |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | yes | |
| Analyzed by developer: | no |
Description
./ffmpeg-ref -i matrixbench_mpeg2.mpg out.h264 Stream #0:0: Video: h264 (libx264), yuv420p, 720x576 [SAR 16:15 DAR 4:3], q=-1--1, 25 fps, 25 tbn, 25 tbc vs. ./ffmpeg -i matrixbench_mpeg2.mpg out.h264 Stream #0:0: Video: h264, yuv420p, 720x576 [SAR 16:15 DAR 4:3], q=2-31, 25 fps, 25 tbn
the 2-31 qp range is an mpeg range likely not what the h264 encoder uses
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Keywords: | regression added |
|---|---|
| Priority: | normal → important |
| Version: | unspecified → git-master |
comment:3 by , 10 years ago
| Reproduced by developer: | set |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
From a quick inspection this happens because ffmpeg.c prints using the muxer context, instead of printing the actual encoder contexts - and the muxer only has codecpar information now, which doesn't contain any more than shown here.
When ffmpeg.c is updated to codecpar, printing of the output streams should be changed to use the actual encoding context instead.