[FFmpeg-trac] #8626(avfilter:open): pp=linblenddeint failure

[FFmpeg]

#8626: pp=linblenddeint failure
-------------------------------------+------------------------------------
             Reporter:  markfilipak  |                    Owner:
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:  avfilter
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+------------------------------------

Comment (by markfilipak):

 Major new symptom: For the attached file: '2001 1m58s -ss 1188 -to 1294
 p24.mkv', at exactly 48 seconds and thereafter, FPS drops from 59.940 (+/-
 2 FPS) to 11.988. In some cases, the video freezes a few seconds later.

 In the logs: "[matroska @ 00000248fae72880] Starting new cluster due to
 timestamp". Is the running time 48 seconds when those notices begin? I
 think so, but, heck, I don't know. What is the point of "[matroska @
 00000248fae72880] Starting new cluster due to timestamp" in log files when
 it doesn't provide any informative metrics? Wouldn't providing the
 'timestamp @ running time' be helpful?

 Filters tested:
 yadif essentially turns the 55-telecine into 46-telecine.
 yaepblur worsens the combing of the frames that flow through it (i.e., 1
 frame in 5). After 48 seconds, every frame is combed.
 pp=lowpass5 is somewhat effective. After 48 seconds, every frame is
 combed.
 pp=ffmpegdeint essentially turns the 55-telecine into 46-telecine.

 At this point, I reran the tests, but with subtitles turned off (-sn).

 The 48-second phenomenon does not happen with subtitles off (-sn) and
 "[matroska @ 00000248fae72880] Starting new cluster due to timestamp" does
 not appear in logs.

 The source video: '2001 1m58s -ss 1188 -to 1294 p24.mkv' is attached.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/8626#comment:59>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker