[FFmpeg-trac] #9456(ffprobe:new): ffprobe coded_width, coded_height, and all dec_ctx->properties fields broken (regression)

[FFmpeg]

#9456: ffprobe coded_width, coded_height, and all dec_ctx->properties fields
broken (regression)
-------------------------------------+-------------------------------------
             Reporter:  Gregory      |                    Owner:  (none)
  Beauregard                         |
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:  ffprobe
              Version:  git-master   |               Resolution:
             Keywords:  codecpar     |               Blocked By:
  regression                         |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Old description:

> Summary of the bug: The coded_height and coded_width parameters don't
> work in ffprobe; they always display the same as the width and height
> fields.
> How to reproduce: Run the following command on any 1080p h264 file.
> Expected coded_height is 1088, but it will show 1080.
> {{{
> ffprobe -select_streams v -show_entries stream=coded_width,coded_height
> file.mkv
> }}}
>
> This behavior is a regression since
> https://github.com/FFmpeg/FFmpeg/commit/04f49645a519233f3638104e0df5215758652fcb
>
> This behavior was also broken in the past and was fixed in
> https://trac.ffmpeg.org/ticket/6958 before regressing.
>
> ffprobe should not be outputting wrong info

New description:

 Summary of the bug: The coded_height and coded_width parameters don't work
 in ffprobe; they always display the same as the width and height fields.
 How to reproduce: Run the following command on any 1080p h264 file.
 Expected coded_height is 1088, but it will show 1080.
 {{{
 ffprobe -select_streams v -show_entries stream=coded_width,coded_height
 file.mkv
 }}}

 This behavior is a regression since
 04f49645a519233f3638104e0df5215758652fcb

 This behavior was also broken in the past and was fixed in
 https://trac.ffmpeg.org/ticket/6958 before regressing.

 ffprobe should not be outputting wrong info

--
Comment (by Carl Eugen Hoyos):

 Please provide the command line you tested together with the complete,
 uncut console output and an input sample to make this a valid ticket.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9456#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker