[mythtv-commits] Ticket #10173: Double framerate deinterlacer incorrectly invalidated

MythTV noreply at mythtv.org
Mon Nov 21 00:38:27 UTC 2011


#10173: Double framerate deinterlacer incorrectly invalidated
-----------------------------------------+------------------------
     Reporter:  krose@…                  |      Owner:  markk
         Type:  Bug Report - General     |     Status:  new
     Priority:  minor                    |  Milestone:
    Component:  MythTV - Video Playback  |    Version:  Trunk Head
     Severity:  medium                   |   Keywords:
Ticket locked:  0                        |
-----------------------------------------+------------------------
 This subset of --verbose playback illustrates the problem:

 {{{
 2011-11-20 19:18:30.893637 I  Trying to match best refresh rate 29.970Hz
 2011-11-20 19:18:30.893712 I  Trying 1920x1080 60.000 Hz
 2011-11-20 19:18:31.184949 I  SwitchToVideo: Video size 1920 x 1080:
     Switched to displaying resolution 1920 x 1080, 160mm x 90mm
 2011-11-20 19:18:31.257548 I  VDPAU: Created VDPAU render device 1920x1080
 2011-11-20 19:18:32.141666 I  VDP: GetFilteredDeint() : vdpau ->
 'vdpaubasicdoublerate'
 2011-11-20 19:18:32.199135 I  VidOutVDPAU: Enabled deinterlacing.
 2011-11-20 19:18:32.199860 I  Player(0): detectInterlace(Detect Scan,
 Interlaced Scan, 29.97, 1080) ->Interlaced Scan
 2011-11-20 19:18:32.199891 E  Player(0): Video sync method can't support
 double framerate (refresh rate too low for 2x deint)
 2011-11-20 19:18:32.250178 I  VDP: GetFilteredDeint(vdpaubasic) : vdpau ->
 'vdpaubasic'
 2011-11-20 19:18:32.298770 I  VidOutVDPAU: Enabled deinterlacing.

 }}}

 Why is the 2x temporal deinterlacer being invalidated for 29.97 fps
 content on a 60 Hz display? (I can't imagine I actually need a 59.94 Hz
 modeline, but even if I did, the log line "refresh rate too low for 2x
 deint" would be misleading.) Judging from the strobishness of the
 resulting video, it appears the 1x temporal deinterlacer just throws out
 one of the two fields, which is not really an acceptable state of affairs.

 One thing that may complicate affairs is that I have "Separate video modes
 for GUI and playback" on, with 24, 50, and 60 Hz modelines properly
 achieved by the relevant videos. I wonder if the deinterlacer check is
 comparing the video against the wrong refresh rate?

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/10173>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center


More information about the mythtv-commits mailing list