[mythtv-users] Problem when channel stops transmitting

[Michael T. Dean]

  On 01/11/2011 02:23 PM, Joacim J wrote:
> I am running separate backend and frontends with Ubuntu 10.04
>
> $ /usr/local/mythtv-0-23/bin/mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version   : 24691
> MythTV Branch    : branches/release-0-23-fixes
> Network Protocol : 56
> Library API      : 0.23.20100429-1
> QT Version       : 4.4.3
> Options compiled in:
>  linux release using_oss 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_bindings_perl using_bindings_python using_opengl 
> using_ffmpeg_threads using_live using_mheg
>
> The backend contains 2 DVB-T cards (one with 2 tuners)
>
> I have scheduled recordings on a children channel (Nickelodeon) and 
> often the tuner is in recording state on that channel and at 07.00 PM 
> the transmission stops and I get problems to tune in other channels.
>
> I have been running MythTV for several years and have upgraded all the 
> time but at some point I started to get this annoying problem.
>
> Do you have any idea what could be the problem and solution? (I really 
> love MythTV beside this problem)

I've seen similar on my system (ATSC) when tuning a subchannel that no 
longer exists.  On my system, the tuner in a pcHDTV HD-3000 card used to 
tune the "missing" channel becomes "stuck" until a reboot, but with an 
Avermedia A180, the card works fine after (though it 
does--obviously--fail to receive any data for the missing channel).

I have a strong feeling the problem in both our cases is either hardware 
or drivers.  Therefore, I recommend giving more details on your card 
types and which driver versions (and/or kernel versions) are in use.

Mike