Backend log swamped even with -v none

[Robin Gilks <g8ecj@…>]

I can't work out whether these errors in the backend log are from the recording or the playback (preview generation) process.

2010-01-28 22:50:16.861 [h264 @ 0x7ff02ad1f9e0]number of reference frames exceeds max (probably corrupt input), discarding one 2010-01-28 22:50:16.872 [h264 @ 0x7ff02ad1f9e0]number of reference frames exceeds max (probably corrupt input), discarding one 2010-01-28 22:50:16.881 [h264 @ 0x7ff02ad1f9e0]number of reference frames exceeds max (probably corrupt input), discarding one 2010-01-28 22:50:16.891 [h264 @ 0x7ff02ad1f9e0]number of reference frames exceeds max (probably corrupt input), discarding one

As you can see they arise about every 10mS, the bursts last up to 15 seconds (1500 lines of junk!!)

Running:

MythTV Version : 23167 MythTV Branch : branches/release-0-22-fixes Network Protocol : 50 Library API : 0.22.20091023-1 QT Version : 4.5.3 Options compiled in:

linux release using_oss using_alsa using_jack using_backend using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_libavc_5_3 using_live using_mheg

[sphery]

dup of #6729 ?

[danielk]

(In [23404]) Fixes #7982. Check if print_verbose_messages is empty before assuming it is not.