[mythtv] svn 7080-7130 breaks DVB recording

[Allan Stirling]

David Shirley wrote:
> Hi All, (and Daniel :P)
> 
> Applied updates from 7080 upto 7130 and now my scheduled recordings fail:
> 
> 2005-08-25 13:34:10.898 Recording starts soon, AUTO-Startup assumed
> 2005-08-25 13:34:10.902 Started recording "Nice Guy Eddie" on channel:
> 1020 on cardid: 1, sourceid 1
> 2005-08-25 13:34:10.903 DVB#0 Opening DVB channel
> 2005-08-25 13:34:10.911 DVB#0 Using DVB card 0, with frontend DVICO
> FusionHDTV DVB-T Plus.
> 2005-08-25 13:34:10.910 scheduler: Schedule Change
> 2005-08-25 13:34:10.914 DVB#0 Trying to tune to channel 20.
> 2005-08-25 13:34:10.918 DVB#0 Frequency: 226500000 BW: 7MHz HP: Auto LP:
> AutoC: QAM-64 TM: 8K H: None GI: auto
> 2005-08-25 13:34:10.939 DVB#0 Event Status() frequency(226500000 Hz)
> 2005-08-25 13:34:10.941 DVB#0 Waiting for frontend event after tune.
> 2005-08-25 13:34:10.942 DVB#0 Frequency tuning successful.
> 2005-08-25 13:34:10.943 DVB#0 Tuned to frequency for channel 20.
> 2005-08-25 13:34:10.944 DVB#0 Closing DVB channel
> 2005-08-25 13:34:10.994 Changing from None to RecordingOnly
> 2005-08-25 13:34:11.018 Prog title: Nice Guy Eddie
> 2005-08-25 13:34:11.019 DVB#0 Opening DVB channel
> 2005-08-25 13:34:11.020 DVB#0 Using DVB card 0, with frontend DVICO
> FusionHDTV DVB-T Plus.
> 2005-08-25 13:34:11.043 DVBSignalMonitor: initial flags 0x7400000
> 2005-08-25 13:34:11.045 DTVSignalMonitor::SetProgramNumber(): 560
> 2005-08-25 13:34:11.048 SignalMonitor::Start() -- begin
> 2005-08-25 13:34:11.050 SignalMonitor::Start() -- end
> 2005-08-25 13:34:11.052 WaitForPMT: seen(0) matching(0)
> 2005-08-25 13:34:11.148 DVB#0 Signal Lock
> 2005-08-25 13:34:11.162 RunTableMonitor() -- begin (2)
> 2005-08-25 13:34:11.164 AddPIDFilter(0x0)
> 2005-08-25 13:34:11.171 AddPIDFilter(0x1ffb)
> 2005-08-25 13:34:11.221 AddPIDFilter(0x101)
> 2005-08-25 13:34:11.257 WaitForPMT: seen(1) matching(0)
> 2005-08-25 13:34:14.054 TVRec: Timed out waiting for lock -- aborting
> recording
> 2005-08-25 13:34:14.055 DVBSignalMonitor::Stop() -- begin
> 2005-08-25 13:34:14.056 SignalMonitor::Stop() -- begin
> 2005-08-25 13:34:14.063 SignalMonitor::Stop() -- end
> 2005-08-25 13:34:14.066 RunTableMonitor() -- shutdown
> 2005-08-25 13:34:14.067 RemovePIDFilter(0x0)
> 2005-08-25 13:34:14.068 RemovePIDFilter(0x101)
> 2005-08-25 13:34:14.069 RemovePIDFilter(0x1ffb)
> 2005-08-25 13:34:14.335 RunTableMonitor() -- end
> 2005-08-25 13:34:14.336 DVBSignalMonitor::Stop() -- end
> 2005-08-25 13:34:14.337 DVBSignalMonitor::Stop() -- begin
> 2005-08-25 13:34:14.338 SignalMonitor::Stop() -- begin
> 2005-08-25 13:34:14.339 SignalMonitor::Stop() -- end
> 2005-08-25 13:34:14.341 DVBSignalMonitor::Stop() -- end
> 2005-08-25 13:34:14.342 SignalMonitor::Stop() -- begin
> 2005-08-25 13:34:14.343 SignalMonitor::Stop() -- end
> 2005-08-25 13:34:14.344 StartRecorderPost() -- failed
> 2005-08-25 13:34:14.349 DVB#0 Closing DVB channel
> 
> @ 7080 I tried re-scanning the channels as per DK's earlier suggestion but
> this is a new one.

This is probably the same thing I'm finding. I'm trying to track it down 
at the moment.

It broke in change 7119. I'm wondering if the dvb-ttpci is having issues 
with events while the tablemonitor is running.

Changing:


r7118  	r7119
1962	 	#if 0
  	1959	#if 1

worked around the issue for me, however, this doesn't apply to current CVS.

Cheers,

Allan.