[mythtv] Still getting masses of errors on H264 startup

[Robin Gilks]

About a month ago I'm sure I saw a ticket that addressed this problem.

2010-03-18 18:33:14.569 [h264 @ 0x7f4f52ac3520]number of reference frames
exceeds max (probably corrupt input), discarding one
2010-03-18 18:33:14.569 [h264 @ 0x7f4f52ac3520]number of reference frames
exceeds max (probably corrupt input), discarding one
2010-03-18 18:33:14.569 [h264 @ 0x7f4f52ac3520]number of reference frames
exceeds max (probably corrupt input), discarding one
2010-03-18 18:33:14.569 [h264 @ 0x7f4f52ac3520]number of reference frames
exceeds max (probably corrupt input), discarding one
2010-03-18 18:33:14.569 [h264 @ 0x7f4f52ac3520]number of reference frames
exceeds max (probably corrupt input), discarding one
2010-03-18 18:33:14.569 [h264 @ 0x7f4f52ac3520]number of reference frames
exceeds max (probably corrupt input), discarding one

With the help of 'wc' I've just counted 450 lines like above in the space
of 300mS in the frontend log. After a week I'm up to 27megs of log file
:-(

mythfrontend --version
Please include all output in bug reports.
MythTV Version   : exported
MythTV Branch    : trunk
Network Protocol : 56
Library API      : 0.23.20100314-1
QT Version       : 4.5.3
Options compiled in:
 linux release using_oss using_alsa using_backend using_dvb using_frontend
using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu
using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus
using_qtwebkit using_v4l using_x11 using_xrandr using_xv
using_bindings_perl using_bindings_python using_opengl using_vdpau
using_ffmpeg_threads using_live using_mheg

Have I missed a fix in the last week?

Cheers

-- 
Robin Gilks