[FFmpeg-trac] #10284(ffprobe:new): Captured HD DVR (HDHomeRun) streams (in the UK) - wrongly identified as 1080p when it should be 1080i

[FFmpeg]

#10284: Captured HD DVR (HDHomeRun) streams (in the UK) - wrongly identified as
1080p when it should be 1080i
-------------------------------------+-------------------------------------
             Reporter:  minxster     |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  ffprobe
              Version:  6.0          |               Resolution:
             Keywords:  interlaced,  |               Blocked By:
  ffprobe, mpegts                    |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by minxster):

 @Marton Balint : you raise a good point with other fields possibly
 changing, but from what I've tested, aspect and resolution don't change,
 at least not in the UK (as far as I can tell).

 That said, I hear you about using the -show_frames, I'll take a look at
 that and see what I can do with it.

 The media server are clearly using ffmpeg to check the file(s) and then
 they proceed to transmit the files according. But they don't check the
 frames. Both of their respective clients seem dumb and just play what
 they're sent, but they take a que from the media server on what the format
 is. I've raised this with Plex, was actually told to come here and log my
 issue. And don't get me wrong, there are ways to make media servers and
 their clients better without needing ffmpeg changes, but alas everything
 is out of my hands. I'm stuck between a rock and hard place, just trying
 to record and playback DVB-T2 and nothing seems to work right.

 All of that said, it's only certain files (DVR files) that mess-up during
 playback and it all comes back to how ffmpeg decided it was progressive,
 then the media platforms continues this "problems" without better checks.
 If ffmpeg has come back and said either "mixed" or "interlaced", then it
 would have played find.

 Left hand not talking to right hand, here I am stuck in the middle (with
 you) LOL

 @Balling - thinks for the references, the years that people have been
 posting question/problems shows that people are struggling. For me, it
 just would have made sense for DVB-T2 just just be progressive and nothing
 else. But then again, it's an old format now! I wonder what the next mess-
 of-a-format that'll come along; that said HEVC interlaced looks like a
 PITA!
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10284#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker