id summary reporter owner description type status priority milestone component version severity resolution keywords cc mlocked 8746 Incorrect positioning of OSD otto at kolsi dot fi markk "OSD is incorrectly positioned (and scaled?) with some recordings. This probably is related to situation where video format changes e.g. when program starts. I've attached picture showing incorrect OSD positioning, log with ""-v important,general,playback"" and version information. Log file was produced by starting playback, skipping forward into actual recording (format has changed) and bringing up the OSD. Grepping the log-file shows some interesting things. Interlace detection has wrong fps and resolution at some point: {{{ 2010-08-07 13:22:48.282 Player(0): detectInterlace(Detect Scan, Interlaced Scan, 25, 576) ->Interlaced Scan 2010-08-07 13:22:52.535 Player(0): detectInterlace(Detect Scan, Interlaced Scan, 29.97, 480) ->Interlaced Scan 2010-08-07 13:22:52.734 Player(0): detectInterlace(Detect Scan, Interlaced Scan, 25, 576) ->Interlaced Scan }}} OSD sizes: {{{ 2010-08-07 13:22:49.702 OSD: Loaded OSD: size 720x576 offset 0+0 2010-08-07 13:22:52.827 OSD: Loaded OSD: size 640x480 offset 0+0 }}} Don't know if this is different issue, side-effect or totally harmless, kernel deint is being used instead of yadif 2x? {{{ 2010-08-07 13:22:49.826 VideoOutput: Using deinterlace method yadifdoubleprocessdeint 2010-08-07 13:22:52.488 VideoOutput: Using deinterlace method yadifdoubleprocessdeint 2010-08-07 13:22:52.541 VideoOutput: Using deinterlace method kerneldeint 2010-08-07 13:22:52.682 VideoOutput: Using deinterlace method yadifdoubleprocessdeint 2010-08-07 13:22:58.519 VideoOutput: Using deinterlace method kerneldeint }}}" defect closed minor 0.25 MythTV - Video Playback Master Head medium Works for me 0