[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):

 I'm working on a set of scripts that can detect the files correctly and
 then decide whether they need transcoding/re-encoding or not. Currently
 files passed to things like Plex or Jellyfin are hit or miss on whether
 they will play correctly. In the problem/case I posted about, both pieces
 of software incorrectly identified the file and playback was badly
 affected. And ironically, both are using a form (I know Plex has it's own
 custom version) of FFmpeg!

 Having a better scanning/checking facility, I think, is needed. Ideally
 we'd want to know if things are: (a) interlaced (b) progressive or (c)
 mixed. Maybe this needs to be an extra option of a "deep scan"? But
 clearly there are problems if files are miss-identified, wither it be
 media playback system, or people (like me) wanting to process the files
 correctly.

 By having FFmpeg/probe better identify file(s), I can at least have
 scripts to clear up the problem. Let alone the other dependency
 systems/apps being better off.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10284#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker